Start with the cost of the current situation
“The site looks old” may be true, but it is not yet an investment case. Find the consequence. Are suitable buyers failing to understand the offer? Is the sales team rewriting the same explanation in every proposal? Can nobody publish an important update without a developer? Is organic demand landing on pages that do not answer the question?
Describe the current journey with evidence you can obtain: enquiries by source and quality, conversion at important steps, common sales objections, search impressions, content maintenance time, accessibility problems and support questions. A small, credible baseline is more useful than an impressive invented forecast.
Choose the problem class
A visual refresh changes expression. A repositioning changes what the company says and to whom. A journey redesign changes how visitors understand, compare and act. A platform change addresses publishing, integration, reliability or ownership. Many failed redesigns buy the first while expecting all four.
Write one sentence for the primary change: ‘After launch, operations leaders should be able to recognise their use case, understand our approach and start a qualified conversation without needing a referral.’ That statement gives content, design and measurement a common job.
Define evidence, not guaranteed uplift
A new website cannot guarantee revenue. It can create measurable leading conditions: more qualified visitors reaching decision content, better completion of a key form, fewer avoidable questions, faster publishing and improved search coverage. Set a baseline, a target range and a review date.
Include the cost of doing nothing and the cost of delay, but do not manufacture urgency. If the existing site creates no material constraint, a targeted content or performance intervention may be the better recommendation.
Scope a complete first release
Prioritise the pages and capabilities needed for the primary journey, plus the foundations every production site requires: accessibility, privacy, security, metadata, error handling, analytics decisions and maintainable ownership. Avoid calling these non-functional extras; they determine whether the site can be trusted.
A useful business case finishes with a decision: retain and improve, redesign the experience, rebuild the platform, or stop. The strongest partner should be willing to recommend the smallest route that addresses the evidence.