I've watched deals stall at a very specific moment. Not during negotiation. Not at legal review. At the point where the champion tries to take the business case upstairs.
The pattern is consistent: the champion is engaged, the commercial conversations have gone well, the internal appetite seems real. Then the business case goes to the CFO or the board and the feedback that comes back is "we need more justification." What they mean is: this doesn't feel like it was written for us.
Most business cases are templates. They have a standard ROI framework, industry benchmarks as placeholders, and a cost-benefit analysis that could apply to any organisation of similar size in the same sector. The vendor spent time populating the numbers. The prospect's senior leadership spent approximately thirty seconds working out that the document was a template.
A business case that could have been sent to any company in the sector signals that you haven't understood this one.
The deals I see close have something different at their centre. They're built around what practitioners in complex sales call Measurable Business Outcomes: the specific metrics that matter to that organisation, in their language, tied to the objectives their leadership has already publicly committed to. The CFO isn't looking for a generic efficiency gain; they're looking to see their own Q3 priorities reflected back at them.
Buying committees compound the problem. The average B2B purchase involves 11 or more stakeholders. The champion who built the initial case often can't be in every room where it gets evaluated. The document has to advocate for the deal without them present. A generic business case cannot do that. It will be challenged by a finance director who has different priorities to the operational lead who ran the evaluation, and the champion won't be there to contextualise.
Business case built on industry benchmarks and standard ROI calculator, sent as PDF attachment
Business case mapped to the prospect's stated MBOs, using their metrics, their language, and their specific constraints
The information to build an outcome-mapped business case is almost always available. Annual reports name strategic priorities. Earnings calls quote the metrics leadership is accountable to. LinkedIn posts from the CFO reveal what's keeping them focused this quarter. Job postings signal investment areas. The work is listening and connecting what you hear to what you already know.
When I ask prospects early in a conversation what success looks like for their leadership team specifically, the answers are rarely abstract. They name numbers, they name initiatives, they name the person who owns the outcome. That's the vocabulary the business case needs to use. The closer the document maps to the language the board is already using internally, the easier the champion's job becomes when they present it.
The champion can't be in every room where the business case gets evaluated. The document has to advocate for the deal without them.
The boilerplate ROI calculator also has a credibility problem. When a prospect sees a generic model with adjustable inputs and industry-average assumptions, it signals something about the vendor's investment in understanding their specific situation. The implicit message is that this deal is interchangeable with any other. That undermines trust at the precise moment you need it most, when the decision-maker forms their view of whether this vendor will deliver.
Building a personalised business case takes longer. It requires asking better questions earlier in the process, maintaining those notes, and synthesising them into a narrative rather than a spreadsheet. The effort is disproportionate to the template approach. So is the close rate.
The deals that stall at the business case stage rarely stall because of price. They stall because the case didn't make the decision easy for the people who were never in the original discovery calls. Fixing that starts long before the document is written.