Building the internal case for a website investment

Website projects rarely fail because nobody can see a problem. They fail because the case is framed badly. The argument becomes "the site feels dated" or "we need a refresh" when the real issue is commercial friction, operational drag, or lost confidence at the point of enquiry.

If you need budget approval, senior buy-in, or board support, your job is not to sell a new website. Your job is to show why the current setup is now getting in the way and how the work will stay under control.

---

Start with the business symptoms

The most persuasive internal cases begin with symptoms that other people already recognise.

Examples:

• sales leads are less qualified because pages do not explain fit properly
• paid traffic lands on weak pages that do not answer obvious questions
• teams keep rewriting, patching, or manually sending the same information
• campaign launches take too long because the site is awkward to update
• buyers still ask basic questions after visiting the site

Those are easier for leadership to understand than a list of design dislikes.

Good internal cases usually answer one core question early: what is the current site making harder than it should be?

---

Use evidence leaders already trust

You do not need perfect analytics to build a strong case. You do need evidence that feels grounded.

Useful sources include:

• sales call notes
• CRM comments on poor-fit or confused enquiries
• campaign landing-page performance
• support inbox patterns
• examples of slow internal publishing or approval loops
• direct screenshots of poor mobile or content experiences

The point is not to prove every detail beyond doubt. The point is to show that the problem is real, repeated, and expensive enough to justify action.

Directional evidence is fine if it is honest. Inflated certainty is not.

---

Put a price on delay

Many internal cases fail because they describe benefits but ignore the cost of waiting.

That cost might be:

• wasted paid traffic hitting weak pages
• months of slow campaign execution because the site cannot flex
• ongoing sales time spent correcting misunderstanding
• repeated internal effort fixing the same publishing issues
• lower confidence from larger buyers reviewing the site

Even rough numbers help here. If the site wastes a paid campaign every quarter or delays new-page launches by several weeks, that is already a business case.

Waiting has a cost. Name it.

---

Present options, not one emotional ask

Decision-makers respond better when they can compare options.

In many situations, there are three sensible paths:

• Do nothing for now and accept the cost of delay
• Run focused improvement work on the pages and paths doing the most damage
• Commission wider rebuild work because the issues are structural

This makes the conversation calmer. You are not asking for a giant leap of faith. You are showing that you have looked at the alternatives and have a reason for the recommendation.

If you are still deciding between improvement and rebuild, use do you need a website rebuild or a focused improvement?.

---

Show how delivery risk will be controlled

Senior approval often hinges less on the website itself and more on whether the work feels manageable.

Your internal case should cover:

• what phase one includes and what it does not
• who owns day-to-day decisions
• how quality will be reviewed
• what success looks like in the first 3 to 6 months
• how the site will be looked after after launch

This is where many cases feel weak. They ask for money but do not explain how scope, approvals, and delivery risk will be handled.

The more consequential the job, the more important that section becomes.

---

Build the one-page case

In most organisations, a useful internal case can fit onto one page.

Include:

• Current problem: what the site is making harder than it should be
• Evidence: examples, data, and observed friction
• Commercial effect: what delay is costing
• Recommended path: focused improvement, phased redesign, or rebuild
• Scope assumptions: what is included first
• Decision model: who signs off what
• Timing and budget: realistic range, not wishful thinking

If the document cannot be understood in five minutes, it usually needs tightening.

---

Questions to answer before you ask for approval

Before you take the case upstairs, pressure-test it with these questions:

• What exactly needs to change for the business, not just the website?
• Which pages or journeys matter most first?
• What happens if we do nothing for another six months?
• Is the recommendation proportionate to the problem?
• Who will make decisions fast enough for the work to move?

If you cannot answer those clearly, do more scope work before asking for approval.

This is also where the project often benefits from a short discovery phase or a structured briefing pass rather than jumping straight into proposals.

---

What a strong internal ask sounds like

A strong internal ask is measured, not dramatic. It sounds like this:

"The current website is slowing down high-intent enquiries and taking too much internal effort to maintain. We have evidence from campaign performance, sales questions, and publishing delays. We recommend a phased website improvement starting with the core service and contact paths, with clear ownership and a defined review process."

That is much stronger than "the site needs modernising".

---

Make the next step small and sensible

If approval for a full project feels unlikely, do not force it. Ask for the next sensible step instead:

• discovery and scoping
• a focused audit
• phase-one improvement work

Smaller asks often unlock the larger decision later because they reduce ambiguity first.

If you are at proposal stage already, pair this with how to compare website proposals without defaulting to cheapest. If you need a clearer planning route before that, use start a project.