Most marketing automation proposals die in the same place: the finance meeting. Not because the numbers are wrong, but because they're the wrong numbers — vendor ROI slides presented to a CFO who was asking a different question. This article gives you the one-page business case structure that survives that meeting: the problem, the cost of inaction, the expected return, and the risk mitigation — in that order, on one page.
Why Automation Proposals Get Rejected
Three recurring failure patterns:
- Benefits without a baseline. "Automation will improve conversion" — by how much, from what current number? Without a measured starting point, there's nothing to hold the claim against.
- No cost of inaction. The proposal compares the project to doing nothing for free. But doing nothing isn't free — leads keep decaying, manual work keeps consuming senior time, and the stack keeps drifting apart. The real comparison is automation vs. the status quo's real cost, laid out in the real cost of a disconnected marketing stack.
- A business case that's actually a feature list. "It has lead scoring and dynamic segmentation" is not a business case. A CFO funds outcomes, not features.
The One-Page Business Case Structure
Five blocks, one page, in this order:
1. The problem (two sentences)
What manual/disconnected marketing costs today, in numbers.
"Sales follows up 62% of inbound leads manually within 48 hours; 31% are never contacted. Marketing spends ~11 hrs/week on hand-built reporting and list exports."
2. The cost of inaction (the block everyone skips)
Project the current problem forward 12 months: lost lead value from slow follow-up, senior salary hours absorbed by manual work, budget wasted on channels you can't attribute. This is the anchor that makes "do nothing" a decision with a price tag, not a safe default.
3. The investment (phased, fully loaded)
Licence + implementation + admin time + integration — the full picture, not the sticker price. The discipline of counting every cost line is covered in marketing automation ROI: how to calculate it honestly — use the same cost model in your business case so the two documents agree.
4. The expected return (conservative, sourced)
Three benefit lines that survive scrutiny: reclaimed efficiency (hours actually redeployed), conversion lift (5–15% year one, not 50%), and recovered spend. The broader value case behind these lines is in the benefits of business process automation; the mechanism for the recovered-spend line — monthly reallocation from underperforming channels — is detailed in budget reallocation: the monthly governance ritual.
5. Risk mitigation (the pilot gate)
What happens if it doesn't work: a phased pilot with a kill criterion. "Pilot on lead routing + one nurture track for 90 days; scale only if response time drops below X and SQL conversion improves by Y." A stated exit is what gets a cautious CFO to yes.
The CFO Test
Before you submit, check the one-pager against what finance actually evaluates:
- Cost of the problem today — sourced, not estimated
- Phased investment — with the ugly first-year multiple visible
- Payback period — defensible maths, 9–14 months, not 3
- What happens if we do nothing — quantified
If any of the four is missing, the case is a marketing document, not a business case.
A Worked Example (One Page, Real Numbers)
A 40-person B2B software company, presented as it went to the board:
| Block | Number |
|---|---|
| Problem | 31% of leads never contacted; 11 hrs/week manual ops |
| Cost of inaction (12 mo) | £46,000 (lost lead value + senior time + unattributed spend) |
| Investment (pilot, 90 days) | £9,400 fully loaded |
| Expected return (pilot window) | £14,000 conservative |
| Kill criterion | <15% response-time improvement → stop, total exposure capped at £9,400 |
Approved in one meeting. The pilot hit its gate in 71 days.