Most business cases I see follow the same pattern. Someone wants to implement a new system — a CRM, a CPQ tool, a customer portal. They put together a document. It lists the features. It estimates the cost. It projects the 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, the €80/hour is inflated, and the team will find other ways to fill that time anyway.
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.
I’ve helped build business cases for CRM, CPQ, and marketing automation projects for over ten years. The ones that get approved and lead to successful implementations all have something in common. They don’t lead with cost savings. They don’t lead with features. And they always include something most business cases ignore entirely: the cost of doing nothing.
Cost savings are the weakest argument you can make
Cost savings sound safe. They’re easy to calculate, easy to defend, and easy to approve. That’s why they’re the default.
But they have a structural problem. A business case built on cost savings frames the entire initiative as an expense reduction exercise. The project becomes about spending less, not growing more. That framing follows the project from approval through implementation and into how success is measured.
This matters because it constrains the scope. A cost savings framing says: automate what we do today so it takes fewer people or less time. It doesn’t ask whether what we do today is the right process. It doesn’t question whether the current approach is leaving revenue on the table.
The same CPQ implementation framed two different ways:
Cost savings framing: “Reps spend 3 hours per quote manually. This tool reduces it to 30 minutes. That saves 2.5 hours per quote across 200 quotes per month.”
Revenue impact framing: “Our average quote turnaround is 5 days. Competitors respond in 24 hours. We estimate we lose 15–20% of competitive deals on response time alone. Reducing turnaround to same-day protects an estimated €X in pipeline per quarter.”
The first saves time. The second protects revenue. The second gets a bigger budget, more executive attention, and a broader mandate to redesign the process rather than just automate it.
The cost of doing nothing is the argument nobody makes
Every business case calculates the cost of the proposed solution. Almost none calculate the cost of not implementing it.
This is the most powerful number in any business case, and it’s consistently missing.
What does it cost your company right now that renewals are reactive? That nobody sees them coming until 30 days before expiry? You can calculate this. Look at your renewal rate. Look at the accounts that churned or renewed flat instead of with an uplift. 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 in the last twelve months where you weren’t first to respond. Estimate the win rate difference between first-response and late-response deals. Apply that 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. The business case should quantify it, because it changes the conversation from “can we afford to do this?” to “can we afford not to?”
This reframing also shifts the urgency. 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, €Y in competitive deals, and €Z in support capacity.” Deferral now has a price tag.
Revenue impact changes who pays attention
A cost savings business case gets reviewed by finance and operations. It competes with other cost reduction proposals. The ceiling on approval is the size of the savings.
A revenue impact business case gets reviewed by commercial leadership. The VP of sales, the CRO. They evaluate it against growth targets. The ceiling on approval is the size of the revenue at risk or the revenue opportunity. That’s a bigger number and a more strategic conversation.
This also changes the project scope. A cost savings mandate produces a narrow implementation: replicate the current process in a new tool, make it faster, done. A revenue impact mandate produces a broader one: redesign the quoting process so we win more competitive deals, build a renewal system that protects retention, create a portal that drives expansion.
The second mandate is harder to execute. It’s also the one that actually transforms the business.
The business case is discovery in disguise
Here’s what I’ve learned from building these: the process of constructing a proper business case is the same work as project discovery. The two exercises overlap almost entirely.
To build a revenue-impact business case, you have to understand the current process. Where do deals stall? Where does the handoff break? What data is missing?
You have to quantify the gaps. What’s the current quote turnaround time? What’s the renewal rate? What percentage of support volume is self-servable?
You have to define what success looks like. Not “the tool is live.” What metric moves? By how much? Measured how? Over what period?
If you do this work properly, you’ve already mapped the current state, identified the process problems, quantified the impact, and defined the target state. That’s discovery. The business case document is just the output format.
How to structure it
If I were building a business case for a CRM, CPQ, or portal initiative tomorrow, here’s the structure I’d use.
Section 1: The cost of the current state. Specific, quantified costs of how things work today. Quote turnaround time multiplied by deals affected. Manual renewal process multiplied by renewal volume. Support hours spent on self-servable questions. Use your own data, not industry benchmarks. Your CFO knows whether your numbers are real.
Section 2: The revenue at risk or the revenue opportunity. What revenue is being lost, leaked, or left on the table? Competitive deals lost to slower response. Renewals that churn because nobody engaged proactively. Expansion that doesn’t happen because adoption signals aren’t visible. Frame each one as a number.
Section 3: The target state. Not a feature list. 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.” Describe what changes in how the business operates.
Section 4: The metrics and timeline. What gets measured, the current baseline, the target, and by when. 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 is signing up for.
Section 5: The investment. Now the cost. After the reader already understands what’s being lost and what will change. The cost of the solution looks different when it follows four sections of quantified impact than when it leads the document.
The business case most people write vs. the one that works
Typical: “We need Salesforce CPQ. Here are the features. Here’s the license cost. Here’s a projected ROI based on time savings. Please approve.”
The one that works: “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, not product dissatisfaction. Our dealers account for 35% of revenue but can’t generate quotes without calling our team, capping channel growth. Here’s how we fix each of these, what it costs, and how we’ll measure the impact.”
The first is a purchase request. The second is a strategic proposal.
That framing doesn’t happen by accident. It happens because someone did the discovery work before writing the document. Talked to sales about where deals stall. Pulled the data on turnaround times, discount patterns, and renewal rates.
Don’t start with the tool. Start with the cost of the problem. The rest writes itself.