A business case is a structured argument for why a proposed initiative deserves resources — time, capital, people. It answers five questions: What is the problem? What is the proposed solution? What is the expected return? What are the risks? What happens if we do nothing? Every organisation makes resource allocation decisions. The business case is the mechanism that forces those decisions to be explicit rather than political. Without one, capital flows to whoever argues loudest, whoever has the most seniority, or whoever cornered the CEO at lunch. With one, capital flows — at least theoretically — to the initiative whose logic survives scrutiny.
The format varies. McKinsey formalised the structured business case in the 1960s as a consulting deliverable: situation, complication, resolution, supported by quantitative analysis of costs, benefits, and risks. The British government's Green Book methodology requires a five-case model — strategic, economic, commercial, financial, and management — for any public spending above a threshold. Amazon uses six-page narrative memos that read like arguments, not slide decks. The surface differs. The underlying discipline is identical: make the assumptions explicit, quantify what can be quantified, and force the decision-maker to confront the trade-offs rather than hiding them in a financial model's nested tabs.
The most dangerous business cases are the ones that look rigorous but aren't. A thirty-page document with a discounted cash flow model projecting revenue to 2035, complete with three scenarios and a sensitivity analysis, can be pure fiction if the assumptions driving the model are wrong. Revenue projections extrapolated from a single quarter. Market size pulled from a Gartner report without questioning whether the company can address any of it. Cost estimates that omit integration complexity, organisational resistance, or regulatory risk. The spreadsheet creates the illusion of precision. The assumptions behind it determine whether the precision means anything. Jeff Bezos understood this when he banned PowerPoint at Amazon and required narrative memos instead. A narrative forces the author to connect assumptions to conclusions in prose — which makes logical gaps visible in ways that bullet points and charts never do.
The best business cases do something counterintuitive: they spend more time on the "do nothing" scenario and the critical assumptions than on the projected upside. The projected upside is the easy part — anyone can build a model showing a positive return if they control the inputs. The hard part is identifying the two or three assumptions that, if wrong, would invalidate the entire thesis. A business case for entering the Chinese market that doesn't identify "regulatory approval within 18 months" as a critical assumption isn't a business case — it's a sales pitch. A business case for acquiring a competitor that doesn't model the integration costs realistically isn't an analysis — it's advocacy. The discipline of the business case is intellectual honesty under institutional pressure to be optimistic.
The "do nothing" scenario is where most business cases fail hardest. Organisations treat inaction as costless — the default state against which the proposed initiative looks attractive by comparison. But inaction has costs. Market share erodes. Competitors advance. Technical debt compounds. Key employees leave. The business case that models the cost of inaction alongside the cost of action gives the decision-maker a genuine comparison rather than a choice between "invest" and "nothing happens." The strongest cases make inaction feel as risky as action — because it usually is.
Section 2
How to See It
A business case is operating whenever someone translates a proposed initiative into a structured argument that connects problem, solution, costs, returns, and risks into a coherent narrative. The diagnostic signature is explicitness: the assumptions are stated, the trade-offs are visible, and the decision-maker can interrogate the logic rather than simply accepting or rejecting a recommendation.
You're seeing a Business Case when someone responds to "should we do this?" not with enthusiasm or a slide deck but with a structured argument that addresses both the upside and the conditions under which the initiative would fail.
Strategy
You're seeing a Business Case when a leadership team evaluates a market entry decision by modelling the expected return under three scenarios — base, upside, and downside — and explicitly identifies the assumptions that differentiate the scenarios. The conversation moves from "China is a huge market" to "our base case assumes regulatory approval within 18 months, a local distribution partner signed within 6 months, and customer acquisition costs 40% higher than domestic."
Capital Allocation
You're seeing a Business Case when a CFO requires every initiative above a spending threshold to submit a written case that includes expected ROI, payback period, risk factors, and the cost of inaction. The requirement forces teams to think through their proposals before competing for budget — and gives the allocation committee a common format for comparing fundamentally different investments.
Product
You're seeing a Business Case when a product manager justifies a feature investment by quantifying the expected impact on retention, revenue, or activation — and identifying the assumption that must hold for the investment to pay off. "We believe this feature will increase 30-day retention by 4 points. The critical assumption is that the retention drop is caused by the onboarding gap, not by product-market fit issues in this segment."
Leadership
You're seeing a Business Case when a CEO rejects a proposal not because the numbers are wrong but because the assumptions are untested. "Your model shows a 3x return, but it assumes we can hire 40 engineers in 6 months in a market where our competitors are paying 20% more. What's the case if hiring takes 12 months instead?"
Section 3
How to Use It
The primary application of a business case is resource allocation under uncertainty: deciding which initiatives deserve capital, people, and attention when the information is incomplete and the future is unknowable. The framework's discipline is in forcing assumptions to the surface — making the invisible logic visible and debatable.
Decision filter
"Before approving any initiative, ask: what are the three assumptions that must hold for this to work? If any of them fail, does the case still stand? If the case depends on all three assumptions being correct simultaneously, the actual probability of success is far lower than the projected return implies."
As a founder
Write the business case for your company's next major initiative as a narrative memo, not a spreadsheet. Start with the problem — what customer pain or market gap the initiative addresses. Then the proposed solution, including why this approach rather than the alternatives you considered and rejected. Then the expected return, with explicit assumptions. Then the risks — what could go wrong, and what you would do if it did. Then the cost of inaction — what happens to the business if you don't pursue this.
The discipline is not in the document. It is in the thinking the document forces. A business case written honestly will surface the two or three critical unknowns that determine whether the initiative succeeds or fails. Those unknowns become your testing priorities — the things you need to validate before committing full resources.
As an investor
Evaluate business cases by attacking the assumptions, not the projections. Every founder can build a model that shows a 10x return. The model's quality depends entirely on the inputs. Ask the founder to identify their three most critical assumptions and explain what evidence supports each one. A founder who can name their assumptions and describe how they would test them understands their business at a deeper level than one who presents projections as facts.
The most revealing question in diligence: "What would have to be true for this to fail?" A founder who has thought through the failure conditions has built a business case. A founder who cannot articulate them has built a pitch.
As a decision-maker
Use the business case framework to create a common language for resource allocation across your organisation. Require every initiative above a spending threshold to submit a structured case in a standard format. The format enforces comparison: when every proposal follows the same structure — problem, solution, return, assumptions, risks, cost of inaction — the allocation committee can compare an R&D investment against a marketing investment against an acquisition on common terms.
The standard format also prevents decision-making by charisma. Without a structured process, the initiative with the most persuasive sponsor wins — not the initiative with the strongest logic. The business case levels the playing field by making the argument visible independently of the person presenting it.
Common misapplication: Using the business case as a post-hoc justification rather than a pre-decision analysis. Teams that have already decided to pursue an initiative and then write a business case to "get approval" are not analysing — they are advocating. The assumptions will be chosen to support the conclusion rather than to test it. The tell: a business case where every assumption trends favourable and the downside scenario still shows a positive return.
Second misapplication: Treating the financial model as the business case. The model is a tool within the case — it quantifies the expected return under stated assumptions. It is not the argument itself. A business case with a beautiful DCF model and no discussion of why the assumptions are credible is a spreadsheet pretending to be a strategy.
Third misapplication: Ignoring the cost of inaction. Most business cases compare the proposed initiative against a static baseline — implying that doing nothing preserves the status quo. In competitive markets, the status quo is deteriorating. The company that does nothing while competitors invest is not standing still — it is falling behind. The business case that models inaction as costless systematically understates the relative value of acting.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The leaders below transformed the business case from a bureaucratic exercise into a strategic weapon. Each built systems that forced rigorous thinking before resource commitment — and created organisational cultures where the quality of the argument mattered more than the seniority of the person making it.
One replaced slide decks with narrative memos. The other bet his career on a business case that most of his board thought was insane.
Bezos banned PowerPoint at Amazon in the early 2000s and replaced it with the six-page narrative memo — a structured business case written in complete prose. Every significant initiative at Amazon required a memo that laid out the problem, the proposed solution, the expected impact, and the risks. Meetings began with fifteen to twenty minutes of silent reading before any discussion. The format forced authors to construct complete arguments rather than hide behind bullet points.
The memo format became Amazon's internal business case standard. When Andy Jassy proposed what would become AWS in 2003, the business case was a narrative memo arguing that Amazon's internal infrastructure capabilities could be productised as a service. The critical assumption: developers at other companies would trust Amazon to host their applications. Bezos approved the investment not because the financial projections were compelling — they were speculative — but because the memo identified the critical assumptions clearly enough to test them. AWS generated $90 billion in revenue in 2023.
Jobs made the business case for the iPhone to Apple's board in 2004 — a case that required Apple to enter an industry it had never competed in, invest billions in development, negotiate with carriers who controlled distribution, and bet the company's reputation on a product category with a 90% failure rate for new entrants. The business case rested on a single critical assumption: consumers would pay a premium for a phone that was also a computer, even if it meant compromising on phone-specific features like battery life and reception quality.
The case against was formidable. Nokia and Motorola dominated mobile hardware. Carriers controlled the customer relationship. Microsoft and BlackBerry owned the enterprise market. Every previous attempt to build a premium smartphone — by companies with far more telecom experience than Apple — had failed commercially. Jobs's business case succeeded because it identified the assumption the incumbents were wrong about: that the phone's primary job was calling and texting. The iPhone bet that the primary job was computing — and that customers would pay $499 for a pocket computer that also made calls. The assumption held. Apple's iPhone generated over $200 billion in revenue in 2023 alone.
Section 6
Visual Explanation
The diagram maps the business case as a linear argument — problem to solution to return to risks — with the critical assumptions layer beneath. The assumptions are the load-bearing structure: if any one fails, the entire case above it weakens. The decision gate at the bottom forces the comparison that most organisations skip: the cost of action versus the cost of inaction. Most decision-makers evaluate only whether the initiative is worth the investment. The business case asks the harder question: is inaction worth the erosion?
Section 7
Connected Models
The business case connects to models that describe how resources should be allocated, how risk should be assessed, and how arguments should be structured. Some reinforce the framework's logic by providing tools for the analysis it requires. Others create tension by exposing the framework's limits — the decisions where structured argumentation breaks down.
Reinforces
Reversible vs Irreversible Decisions
The business case framework is most valuable for irreversible decisions — the ones where the cost of being wrong is high and the ability to correct course is limited. Jeff Bezos's Type 1 / Type 2 decision framework maps directly: Type 1 decisions (irreversible) deserve a rigorous business case. Type 2 decisions (reversible) should be made quickly without the overhead. The business case prevents overthinking reversible decisions — and underthinking irreversible ones.
Reinforces
Opportunity Cost
Every business case implicitly argues that this initiative is the best use of the resources it requires. Opportunity cost makes that argument explicit: what else could these resources do? The strongest business cases don't just show a positive return — they show a return that exceeds the next-best alternative. A project with a 15% expected return is a bad investment if the same capital could earn 25% elsewhere.
Leads-to
Pre-Mortem Analysis
The pre-mortem extends the business case's risk section by asking a more psychologically effective question. Instead of "what could go wrong?" the pre-mortem asks "assume the initiative has failed — why?" The reframe gives team members permission to articulate concerns they might suppress in a standard risk discussion. The pre-mortem is where the business case's polite risk section meets genuine organisational honesty.
Reinforces
Scenario Analysis
Section 8
One Key Quote
"Most decisions should probably be made with somewhere around 70% of the information you wish you had. If you wait for 90%, in most cases, you're probably being slow."
— Jeff Bezos, 2017 Letter to Shareholders
Bezos captured the fundamental tension in every business case: the analysis is never complete, the assumptions are never certain, and waiting for perfect information is itself a decision — a decision to cede speed to competitors who act on less. The business case is not a tool for eliminating uncertainty. It is a tool for making uncertainty visible so the decision-maker can act despite it.
The 70% threshold has a corollary: a business case that claims certainty is lying. The honest business case identifies what falls within the 70% that is knowable and what falls within the 30% that is not — and structures the decision around testing the unknowns rather than pretending they don't exist. The companies that make the best resource allocation decisions are the ones that build business cases quickly, identify the critical assumptions honestly, and move to test those assumptions through action rather than through more analysis.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
The business case is one of the most widely required and widely abused tools in corporate decision-making. In theory, it forces rigorous thinking about resource allocation. In practice, most business cases are written to justify decisions that have already been made. The executive has already decided to pursue the acquisition, enter the market, or fund the project — and the business case is assembled after the fact to create the appearance of analytical rigour. The assumptions are selected to support the conclusion. The risk section is included but toothless. The financial model shows a positive return under all scenarios because the scenarios were designed to be positive. This is not analysis. It is theatre.
The diagnostic for distinguishing a genuine business case from a justification document is the treatment of assumptions. A genuine business case identifies the assumptions that would kill the initiative if they proved wrong and describes how those assumptions will be tested. A justification document buries assumptions in the financial model, selects only favourable ones, and never mentions testing. When I review business cases, I skip the executive summary and the financial projections entirely. I go straight to the assumptions section. If the assumptions are vague, untested, and uniformly optimistic, the document is advocacy. If the assumptions are specific, falsifiable, and honestly uncertain, the document is analysis.
The second pattern worth naming is the "cost of inaction" gap. Most business cases compare the proposed initiative against a static baseline — the implicit assumption that doing nothing preserves the current state. This is almost never true. Markets move. Competitors invest. Customers evolve. The business that does nothing is not standing still — it is falling behind at a rate that the business case should quantify. The strongest cases I've seen model the "do nothing" scenario as aggressively as the "act" scenario, showing the decision-maker that both paths carry risk and cost.
The third observation: the best business cases are short. Amazon's six-page limit is instructive. Bezos understood that length is not rigour. A thirty-page business case with appendices and sensitivity tables can obscure weak thinking behind volume. A six-page case that must cover problem, solution, return, risks, and assumptions in complete prose has no room to hide. Every sentence must carry weight. The constraint forces clarity — and clarity is what the decision-maker actually needs.
Section 10
Test Yourself
The scenarios below test whether you can distinguish a genuine business case — a structured argument that surfaces assumptions and confronts trade-offs — from the common substitutes: advocacy documents, financial models without logic, and gut-feel decisions dressed in analytical language. The key question: does the argument make its assumptions explicit and falsifiable?
Is this mental model at work here?
Scenario 1
A VP of Engineering submits a proposal for a $2 million infrastructure migration. The document includes a problem statement (growing reliability issues), a proposed solution (migrate to a new cloud provider), projected cost savings over three years, and a section identifying three risks — migration downtime, team bandwidth constraints, and vendor lock-in. The critical assumption is stated: 'The reliability issues are caused by our current infrastructure, not by our application architecture.'
Scenario 2
A startup CEO presents a pitch deck to investors showing a $40 billion TAM, a product demo, customer testimonials, and a revenue projection reaching $500 million in five years. When asked about the critical assumptions behind the revenue projection, the CEO says: 'We've validated demand through our early customers. The market is massive and growing.'
Scenario 3
A product team writes a one-page memo proposing a new feature. The memo states: 'We believe adding collaborative editing will increase team-plan adoption by 15%. The critical assumption is that the adoption gap is caused by the absence of real-time collaboration, not by pricing. We propose a 4-week beta with 200 teams to test this assumption before full development. If beta results show less than 5% adoption lift, we will not proceed.'
Section 11
Top Resources
The business case literature spans corporate finance, strategic planning, and decision science. Start with Bezos's shareholder letters for the philosophy, move to Hammond for the decision-making framework, and use the HM Treasury Green Book for the most rigorous structural template. The Amazon narratives resources explain the format that has become the gold standard in technology companies.
The most concentrated education in business case thinking available in public writing. Bezos's annual letters document the assumptions behind Amazon's largest bets — AWS, Prime, Marketplace, Alexa — and explain why he committed resources despite massive uncertainty. The 1997 letter, included with every subsequent letter, lays out the meta-business-case for Amazon's entire strategy: prioritise long-term value creation over short-term profitability.
The clearest framework for structuring decisions under uncertainty — the core skill the business case requires. Hammond, Keeney, and Raiffa's PrOACT framework (Problem, Objectives, Alternatives, Consequences, Trade-offs) maps directly onto the business case structure and provides the analytical rigour that most business case templates lack. Particularly strong on identifying objectives and evaluating trade-offs.
The British government's standard for evaluating public spending proposals. The five-case model — strategic, economic, commercial, financial, and management — is the most rigorous business case template in widespread use. Designed for public sector decisions but directly applicable to corporate resource allocation. The framework's insistence on modelling the "do nothing" scenario as a distinct case is its most valuable contribution.
The definitive account of Amazon's narrative memo process — the format that replaced PowerPoint with structured prose and transformed how Amazon makes resource allocation decisions. Bryar and Carr, both former Amazon VPs, explain how the six-page memo forces rigorous thinking, how the silent reading period works in practice, and why the format produces better decisions than presentations. Essential for anyone building a business case culture.
Duke, a former professional poker player, applies probabilistic thinking to business decisions — the same mental shift the business case requires. Her framework for separating decision quality from outcome quality is directly relevant: a good business case can lead to a bad outcome if the assumptions prove wrong, and a bad business case can lead to a good outcome through luck. The discipline is in the process, not the result.
Business Case — A structured argument that connects problem identification through solution design to resource commitment, with explicit assumptions and risk assessment at every stage.
Scenario analysis provides the analytical engine for the business case's treatment of uncertainty. Rather than presenting a single projected outcome, scenario analysis models base, upside, and downside cases — each built on a different set of assumptions. The business case that presents three scenarios is more honest than the one that presents one, because it acknowledges that the future is uncertain and the decision must be robust across multiple possibilities.
Reinforces
Amazon Narratives
Amazon's six-page narrative memo is the business case format optimised for intellectual rigour. By requiring complete prose rather than bullet points, the narrative forces logical connections between assumptions and conclusions. The format makes gaps in reasoning visible because prose cannot hide behind formatting the way a slide deck can. The Amazon narrative is what happens when the business case discipline meets a culture that values clarity over presentation.
Tension
Discounted Cash Flow
DCF analysis is the financial engine most commonly embedded in business cases — and it is also the component most likely to create false confidence. A DCF model can produce a precise net present value from wildly speculative inputs. The tension: the business case uses DCF to quantify expected returns, but the precision of the output disguises the uncertainty of the inputs. The best business cases use DCF as one input, not as the answer.
