Most business cases follow the same pattern. Someone wants to implement a new system. They put together a document listing features, estimating costs, projecting savings: “This tool saves 10 hours per week across the sales team. At €80/hour, that’s €41,600 per year. The tool costs €35,000. ROI: positive in year one.”

Finance looks at it. The math checks out. The project gets approved — or it doesn’t, because someone argues the 10 hours is optimistic and the team will find other things to fill the time. Either way, the business case failed at its actual job. Not because the numbers were wrong, but because it was built around the wrong argument.

Cost savings are the weakest argument

Cost savings frame the entire initiative as an expense reduction exercise. The project becomes about spending less, not growing more. It also constrains scope — a cost savings framing says: automate what we do today so it takes fewer people or less time. It doesn’t ask whether the current approach is leaving revenue on the table.

The same CPQ implementation framed two ways: “Reps spend 3 hours per quote manually, this tool reduces it to 30 minutes” versus “Our average quote turnaround is 5 days, competitors respond in 24 hours, we estimate we lose 15 to 20% of competitive deals on response time alone.” The first saves time. The second protects revenue. The second gets a bigger budget, more executive attention, and a broader mandate.

The cost of doing nothing

Every business case calculates the cost of the proposed solution. Almost none calculate the cost of not implementing it. That’s the number that’s consistently missing.

What does it cost right now that renewals are reactive? Look at your renewal rate, look at the accounts that churned or renewed flat, multiply the gap by the number of renewals per year. That’s the annual cost of your current renewal process. What does it cost that quotes take five days? Count the deals where you weren’t first to respond and apply that win rate difference to your average deal size. That’s revenue you’re already losing.

The cost of doing nothing isn’t hypothetical. It’s happening every month. A cost savings business case can always be deferred: “We’ll do it next quarter, the savings will still be there.” A cost-of-inaction business case creates pressure: “Every month we wait, we lose €X in renewal uplift.” Deferral now has a price tag.

Revenue impact changes who pays attention

A cost savings business case gets reviewed by finance. A revenue impact business case gets reviewed by commercial leadership — the VP of sales, the CRO — evaluated against growth targets. The ceiling on approval is the size of the revenue at risk, which is a bigger number and a more strategic conversation.

How to structure it

Start with the cost of the current state: specific, quantified costs of how things work today, using your own data, not industry benchmarks. Then the revenue at risk — competitive deals lost to slow response, renewals that churn because nobody engaged proactively, expansion that doesn’t happen because adoption signals aren’t visible. Frame each as a number.

Then the target state. Not a feature list, but a process description: “Renewal opportunities are created automatically at 90 days. A pre-built quote with uplift is attached. Health scoring flags at-risk accounts.” Then the metrics and timeline — quote turnaround from 5 days to same-day within 3 months, renewal rate from 82% to 90% within 12 months. These are the commitments the project team signs up for.

Only then: the investment. The cost of the solution looks different when it follows four sections of quantified impact than when it leads the document.

flowchart LR
    C["Current-state cost<br/>What is already leaking?"] --> R["Revenue at risk<br/>What happens if we wait?"]
    R --> T["Target state<br/>How the process works"]
    T --> M["Metrics and timeline<br/>What will change by when?"]
    M --> I["Investment<br/>What it costs to fix"]
    I --> A["Strategic proposal"]

“We’re losing an estimated €400K per year in competitive deals because our quote turnaround is five days. Our renewal rate is 82% and we estimate 60% of the gap to 90% is caused by reactive processes. Here’s how we fix each of these, what it costs, and how we’ll measure the impact.”

That’s a strategic proposal. The version that leads with features and license costs is a purchase request.

Don’t start with the tool. Start with the cost of the problem.