SEO for Internal Stakeholder Buy-In: Building the Business Case Document

SEO budget is won more readily by a document that speaks in investment, return and risk than by one about tactics. An executive isn’t approving crawl budget work; the decision is about a defensible projection with a visible method and an honest downside. Two parts carry the document: a one-page summary that stands on its own, and a return method rigorous enough to survive finance. One rule governs both. A modest, defensible projection can outlast an impressive number with hidden assumptions, because the impressive number may invite the whole case to be dismissed the moment one assumption is questioned.

A business case is a forward-looking request for resources you don’t have yet. It has to make the request credible before any results exist.

Each stakeholder reads a different document

The same business case is read by several people, and each role looks for something different, roughly as follows. Write it so each finds the answer without asking:

The executive reads for return and strategic fit: does this move the company where it is going, and when does it pay back.
Finance reads for assumptions: where each input came from, what happens if it is wrong, and whether the conclusion survives a challenge to the inputs.
Engineering reads for workload: what this costs to build and to maintain, and whether the plan admits it.
Marketing reads for fit: how this complements paid and other channels instead of competing with them for the same credit.

A case that satisfies the executive but collapses under finance’s questions hasn’t been approved. It has been deferred.

The summary stands alone

Assume the one-page summary is the only page the decision-maker reads. On its own, it has to carry the recommendation, the investment, the expected return and payback period, the main risk and the strategic reason, in language that needs no appendix. If the summary only makes sense after page nine, it has failed.

This is a discipline, not formatting. Forcing the whole case onto one self-contained page shows whether you have a case, or a list of tactics hoping to add up to one.

Build the return so finance argues with inputs

The method has to be open enough that a skeptic argues about your assumptions instead of dismissing your math. Three parts carry it:

The value of the traffic you expect to win. Projected sessions, the share that converts, and the value of a conversion. The forecast is an input; cite where it came from and how it was bounded.
An attribution factor below one. Organic search shares credit with other touches in multi-step journeys, so a model that gives it sole credit can read as dishonest to finance. Discounting attributed value yourself shows you understand how revenue is credited, and heads off an easy objection before it is raised.
A payback period. How long until cumulative return covers cumulative investment, including the ramp when SEO produces little while content is built, crawled and indexed.

Any return multiple or benchmark you cite needs a named, current, verifiable source. If you can’t verify it, cut it and present the return as a range built from your own visible inputs. Illustrative figures used to walk through the method are fine when they are labeled as hypothetical where they appear, and never presented as data.

Frame the competitive threat, carefully

Opportunity framing (“we could capture this demand”) competes with every other growth proposal on the table. Threat framing (“competitors are building visibility in our core category while we stand still, and that gap costs more to close later”) can move a decision faster, because a widening gap reads as a clock running. Use it only where it is true, and keep it qualitative and defensible. “Competitors publish consistently in segments where we have no presence” is a claim you can support in the room. An invented count of positions they gained is one a skeptic can take apart with one question.

Put the ramp in the case

SEO costs from the first day and returns later. Google’s SEO Starter Guide says “Some changes might take effect in a few hours, others could take several months,” and “In general, you likely want to wait a few weeks to assess whether your work had beneficial effects in Google Search results.” A case that draws full returns from the first month promises what the channel can’t be counted on to deliver. The first quarter or two can look like pure cost, and a reviewer who wasn’t warned may read that as failure.

So show the ramp explicitly: investment starting at once, return arriving later, and the cumulative lines crossing at the payback point you stated. Naming the slow start before anyone asks can turn an objection into evidence that you understand the channel. It also helps protect the program after approval, because when the early months come in light, the people who signed off already expected it.

Make it survive being forwarded

A business case can travel beyond the meeting where it is presented: forwarded, skimmed by people you never spoke to, and quoted out of context. So:

put the source next to every number;
label every assumption as an assumption;
make the recommendation impossible to miss, not something the reader infers from a chart.

Any figure used only to illustrate the method needs its “hypothetical” label where it appears. A reader who forwards the document won’t carry your spoken caveat with it, and an illustrative multiple that travels without its label becomes, to the next reader, a claim you can’t support.

Answer the algorithm objection with sensitivity analysis

An objection that can sink SEO cases is “what if the algorithm changes?” The Starter Guide itself notes that not every change produces a noticeable effect in search results. Answer the objection before it’s asked:

A downside scenario. Show the case with a materially smaller upside and a longer timeline, and show whether it still clears a reasonable bar or at least limits the loss.
A break-even threshold. State the performance level below which the case stops working, so the decision-maker can judge how robust the bet is.

Volunteer the attribution discount, the downside scenario and the break-even threshold before finance asks. Conservative inputs you raise yourself can turn skepticism into trust, because you have done the reviewer’s work and the case still stands. A single aggressive figure does the opposite: it rests the whole argument on one number that one challenged assumption can topple.

Frequently asked questions

How precise should the projection be?

Defensible rather than impressive. A conservative range with an attribution factor below one and a stated break-even can survive scrutiny. A precise figure built on optimistic inputs may invite rejection on the first challenged assumption.

How is a business case different from a quarterly review?

The business case asks for budget before results exist. A quarterly review reports on what funded work produced. One requests resources; the other accounts for them.

How long should the case say results will take?

Say it with Google’s own framing: some changes can show within hours, others can take several months. Build the payback period on that ramp, and show the downside if it runs long.