How to build an SEO business case

Why one page

The people who approve budget read many requests. Long decks bury the numbers they need. A single page forces you to lead with the decision, the cost and the return. The detail still exists, in an appendix with the full model, but it supports the page rather than replacing it.

One page also makes the case easy to forward. If your manager needs to take it to the CFO, it should survive without you in the room.

The one-page structure

Use these seven parts, in this order.

1. The ask. One sentence. "We request $48,000 over 12 months for SEO, reviewed at month 6."
2. The opportunity. What search demand exists that you do not capture today. Use the non-branded keyword groups from your traffic forecast.
3. Expected return. Added sales, revenue and gross profit in a cautious and an expected case. Profit, not revenue.
4. Cost. Every line: agency or freelance fees, content, tools, links and internal time.
5. Payback month. The month cumulative profit is expected to cover cumulative cost, in each case.
6. Risks. What could make the cautious case wrong, and what you would do about it.
7. Measurement. The KPIs you will report monthly and the review point where budget can change.

If the work is large, add a line on scope: which pages, which fixes, in which order. Our process page shows how we break a programme into phases that each have their own check-in.

What a CFO asks first

Finance leaders think in cash, risk and alternatives. Expect these questions, and answer them on the page.

• "Is that revenue or profit?" Show gross profit. Revenue-based ROI looks larger, and finance will discount the whole case if they catch it.
• "When do we get the money back?" Give a payback month for each case, not just an annual ROI.
• "What happens if it does not work?" Name the review point and the signals you will check. A phased budget limits the downside.
• "Why not spend it on ads?" Compare cost per sale over the same period. Our SEO vs paid ads guide shows how.
• "Would these sales happen anyway?" Exclude branded search and show only the uplift above your baseline.
• "Where did this number come from?" Every input should trace to a source. That is the job of the assumptions table.

Stating your assumptions

Assumptions are not a weakness to hide. They are what makes the forecast checkable. Put them in a short table, each with its source and a note on confidence.

Mark which inputs are measured and which are estimates. Then show which ones matter most. If a half-point change in conversion rate moves payback by four months, say so. It tells finance where the real risk sits, and it often points to work like conversion rate optimisation that de-risks the plan.

Finding the payback month

Payback is the first month in which cumulative added gross profit is at least equal to cumulative SEO cost. Here is a worked example. The figures are illustrative, not a client result.

The plan costs $4,000 a month. In the expected case, added gross profit is $0 in month 1 and grows by $800 each month after that. So month 2 adds $800, month 3 adds $1,600, and month 12 adds $8,800. At $55 profit per sale, month 12 is 160 added sales.

Cumulative profit catches cumulative cost in month 11, so that is the payback month. Year-one ROI is ($52,800 − $48,000) ÷ $48,000 = 10%.

Now the cautious case. Profit grows by $500 a month instead of $800. By month 12, cumulative profit is $33,000 against $48,000 of cost, a year-one ROI of −31%. Payback moves to month 17, when cumulative profit and cost both reach $68,000.

Put both on the page. "Payback in month 11 expected, month 17 cautious" is a far stronger sentence than a single hopeful date. It also tells finance how long to wait before judging the work. For more on the factors that move this month, read how long SEO takes to pay back.

Naming the risks

Every SEO plan carries risk. Listing it does not weaken the case. It shows you have thought about what could go wrong and planned a response. Keep it to three or four lines, each with a signal you will watch and the action you will take.

• Slower rankings than planned. Signal: target pages still outside the top 20 at month 6. Response: shift effort to pages already close to page one, and review link support.
• Traffic without sales. Signal: organic sessions on track, conversions flat. Response: review search intent and run conversion tests before adding more pages.
• Search results change. Signal: clicks fall while positions hold, often because of new features above the results. Response: re-check CTR assumptions and adjust the forecast openly.
• Technical problems. Signal: pages not indexed or site speed slipping after a release. Response: a fix list agreed with the development team, with dates.

Each risk links back to a KPI in the measurement section. That way the monthly report tells finance whether a risk is turning real, long before the payback month arrives.

Presenting it

Lead with the ask and the payback range. Keep the full model in the appendix and offer to walk through it. Propose a review at month 6 with clear signals: indexed pages, rankings for target groups, organic sessions to those pages and early conversions. Those are leading indicators. Revenue and cost per sale are the results. Our guide to SEO KPIs that matter explains which belong in each report.

You can get first-pass numbers in minutes from the ROI calculator, then refine them with your own data. Check the cost line against our published pricing. If you want the model built and stress-tested for you, our forecasting and business case service produces the page, the appendix and the assumptions sheet.