Buying decisions get made during the internal conversations happening about you, without you.
When you're not in the room, your champion has to explain the problem, defend the priority, field the questions, and help a group decide what to do next. Which means your deal is only as strong as the message they can carry into those conversations.
So give them one page they can understand, mark up, and repeat in their own words.
I've used this framework with my own teams to win millions in complex deals, and most of what it's worth shows up while you're building the page with your buyers (more on that below).
The business case is the sales process
Most sellers treat a business case like a late-stage deliverable. Months of meetings happen, a value engineer gets pulled in, and someone tries to turn a pile of notes into a polished document for approval.
Which is backwards, since only a fraction of your deals make it to a late stage without a clear business case anyway.
So flip it: building the business case is the sales process. Every conversation helps you write it, every gap on the page tells you what to learn next, and every edit from the buying team gives you evidence that the deal is becoming theirs.
In one page, you can see whether the deal is actually moving (and you can score it):
- Discovery: Have you found a costly problem and a compelling reason to change?
- Executive alignment: Is the project tied to a priority leadership already recognizes?
- Multithreading: Does the page reflect one person's view, or input from the full buying group?
- Demos: Do you know which outcomes and capabilities matter enough to shape the agenda?
- Forecasting: Are the timing, investment, decision process, and internal dependencies visible?
- Champion building: Has your champion changed the language so it will land with their team?
Doing a demo? Use the case to design the agenda. Meeting an executive? Send it as the pre-read. Multithreading? Ask each new person you meet to challenge the problem statement. Negotiating? Bring the conversation back to the outcomes and investment the team already agreed on.
One document captures the deal, and guides the next step.
What does a good one-page business case look like?
The strongest business cases share three qualities:
- It's internal. It reads like the buying team wrote it, using their words, data, priorities, and project names.
- It's concise. An executive can scan it quickly and understand why the project matters now.
- It's specific. The page contains numbers, dates, names, and phrases that could only belong to this account.
This is also why a beautiful vendor-branded deck usually works against you. Buyers don't want to forward your marketing materials to an executive and defend the obvious bias. A plain page in their language travels further. And if your executive thinks in Situation, Complication, Recommendation, use the consulting-style version instead.
When should you start writing it?
Early. Right after the first discovery meeting.
You won't have every number or answer yet, which is fine. Start with a few sentences about the problem and leave the gaps visible. Those blanks aren't a sign the document failed, they're your plan for the next conversation.
For example, if your first draft says, "Every month, [number] employees spend [hours] fixing [problem], which puts [company priority] at risk," you now know exactly what to ask for next: reach, frequency, severity, and the executive priority affected.
As the deal progresses, the business case should get stronger. By Stage 2, aim for about two-fifths complete. By the time you're asking an executive to approve the project, it should be nearly complete, with the buying team's fingerprints all over it.
Build it like LEGO: five connected blocks
A business case is easier to write when you stop treating it like one big document. Think of it like LEGO: five blocks that build on each other, with each one supporting the next.
1. Priority-driven headline
Reference an internal phrase, strategic initiative, or project codename that's already familiar to the executive team.
"Improve loyalty" is generic. Here's a headline from one of my worked examples: "Because we've filed to go public with loyalty named a top-four priority, we should turn MyMike's from a points program into a behavioral platform by Q2." It names the event (the IPO filing), the priority, and the date.
A useful headline structure is:
[Buying team] should [recommended action] by [timeline]. This will create [target outcome] while avoiding [cost of the problem].
The headline gives an executive the whole argument before they decide whether to keep reading, and the date in it should be a real compelling event, one that matters to them whether or not you're in the deal.
2. The problem statement
Your problem statement should explain who is affected, how often it happens, what it costs, why it threatens a larger priority, and what gets worse if the team waits.
A simple way to quantify the loss is:
Loss = reach × frequency × severity
Reach is how many people or transactions are affected. Frequency is how often the problem occurs. Severity is the gap between the current state and the acceptable one.
Then put the cost and consequence into a pair of sentences:
Every [frequency], at least [reach] are affected by [problem], costing us [loss]. That means [immediate implication], and if it's not addressed by [timeline], then [larger consequence].
Here's how it read for Drift: "Every month, at least 50,000 visitors hit our site, but only 1% convert on our forms, costing us 500 demos and $2.5 million in new sales. This means we're spending more on paid ads to hit our targets, driving up our CAC."
Don't guess at the inputs. Ask your buyer for their estimate, write it down, then help the team find the data that can make the number defensible.
If you're coaching a team on this, the Mad Libbed Problem Statements exercise turns the template into a five-minute game. Each rep fills in the blanks from a real discovery call, and the room scores every statement on how specific it is, live.
3. Recommended approach
There are lots of ways an executive can solve a problem. So this block should never read, "Buy our software." First align on the strategic shift, practice, or project the team believes will work.
For a content platform, it's less "use our content automation system" and more "shift the mix of new leads from paid to organic sources." Your product can enable that approach, but the buying team needs to believe in the approach before they compare vendors.
Spell out the conditions that must be true for the approach to work, how the team has tested those assumptions, and the capabilities any solution will need. Which moves the conversation from a product pitch to a plan.
4. Target outcomes
Show a vivid before and after, then connect it to the executive metrics the team already tracks.
"A modern workflow" is a measure of change. For Expedia, the payoff read: "If Expedia dropped call volumes from 58% to 15% of bookings, they're saving almost $75M per year in support costs." That's a measure of value.
Keep the list short. Three meaningful outcomes with current values, target values, and a time to impact are more useful than twelve optimistic benefits.
5. Required investment
Who needs to invest what, by when? Those dates become the backbone of your mutual action plan.
This includes pricing, but it's bigger than price. Include the people, time, data, legal work, security review, training, and change management required to make the project successful. And try to include two scenarios. It's a bit counterintuitive, but adding a choice will accelerate the process, as long as you don't go overboard with options.
A credible business case explains the whole decision. That includes the cost of getting the good outcome, not just the size of the good outcome.
What this looks like in a real deal
After my first startup was acquired, I helped move the company upmarket. One of our champions led grantmaking at a major foundation with $50 million in annual grantable funds. She believed our software could help 30 nonprofits build a more sustainable base of individual donors, but the purchase was unusual and required board approval.
So we didn't start with an ROI calculator or product deck. We helped her survey the nonprofits, gathered the fundraising data, and turned it into a one-page memo for the board packet.
The core problem statement was:
Every year, 200 of the Foundation's grantees raise less than 20% of their annual budget from individual donors, which is costing the Foundation more than $20 million in follow-on funding to keep these programs operational. If this is not addressed this fiscal year, the Foundation will be unable to allocate funding for new initiatives in its strategic plan.
Her response was immediate: "My board needs to see this."
That's the standard. The page should help your champion say something their executive needs to hear, with evidence the executive can trust.
Three mistakes that weaken the case
1. Making it yours, not theirs
How many edits came directly from the buying team?
Those edits stand in for ownership, and we all take a greater stake in what we help create. At the start of the pandemic, one of our champions was rolling out a virtual try-on program for a major international retail brand, and she'd built so much of the plan herself that she told us, "I swear I'll quit my job if we don't get this done." Part of her was joking. But a part of her was serious.
Ask your champion, "If I share a recap of what I've captured so far, would you be open to weighing in with a comment or two?" Then make the next version visibly better because of their input.
2. All numbers, no narrative
An ROI model on its own is a future maybe, with no context around it.
The narrative explains why the problem matters, why it matters now, and why this approach is the right response. The numbers make that story concrete and defensible. You need both.
3. Your branding, not theirs
A heavily branded document signals that the message came from a vendor. Keep the page plain, or use the buying team's brand. Then list your champion and the key people on the deal as the authors.
If it looks internal, sounds internal, and contains internal evidence, your champion can use it without having to translate everything first.
What do you do with the first draft?
Share it. Even if it's rough and full of gaps (a forwardable email makes it easy for your champion to pass along).
In the next meeting, ask two questions:
- What here resonates, that you think we should highlight?
- What have we missed?
Fold the answers into Version 2. Then bring the page into every relevant conversation, ask each person to challenge it, and keep strengthening the case over time.
So start early, write it with the buying team, and keep it internal, concise, and specific. Building it together is what exposes your discovery gaps and gets a dysfunctional buying group on the same page, and it hands your champion a message they can carry into rooms you'll never enter.
And if you're rolling this out to a whole team, the 1-Page Business Case workshop exercise has each rep build one for a real deal in about ten minutes, then score the draft to find the gap that's holding it back.