There is a failure pattern that shows up repeatedly in traders who review their own decisions honestly: they formed a strong view on a business — bullish or bearish, cheap or expensive — before they could plainly describe how that business makes money. They knew the ticker, the chart, the ratio. They could not answer, in plain language, who the customer is or what would have to break for the revenue to collapse. This article teaches a five-question business-model map that corrects that gap. By the end, you will be able to complete a structured map for any business — and, more importantly, to notice which dependency you could not fill in.

One clarification before the framework: this map produces comprehension, not a valuation and not a recommendation. Understanding how a business earns money is a prerequisite to forming a useful view. It is not itself a verdict on price. A business can be structurally elegant and priced so that nothing is left for future buyers. It can be structurally vulnerable and priced for that vulnerability already. The map tells you what the engine looks like. It does not tell you what to do.

Why Map Before You Read Anything Else

When you read an earnings release, an analyst note, or a news headline before you can describe the business model yourself, you are borrowing someone else's framing. Their framing decides which numbers they present, which risks they emphasize, and which dependencies they leave in the footnotes. You absorb their conclusion and later mistake it for your own analysis.

The five-question map forces you to form your own description first. You fill in what you know and — this is the more valuable output — you locate what you do not know. A box you cannot fill is not a failure; it is a signal that you need a primary source (an annual report, a 10-K, an earnings call transcript) before any opinion has a stable foundation. For an explanation of what primary sources are and how to trace them, see Source Hygiene.

The Five Questions

1. Who Is the Customer?

Name the customer segment as specifically as possible. Not "consumers" — individual households in a specific income bracket buying a specific thing. Not "businesses" — which type, at what scale, in which geography. A business that serves many distinct customer segments is more complex, and the map should reflect that: different customers may pay differently, churn differently, and depend on different delivery mechanisms. When you cannot specify the customer beyond a vague category, you do not yet understand the model.

A good answer is concrete and verifiable. If you need to check, the "Customers" or "Revenue" sections of an annual report or 10-K filing will usually state this directly.

2. What Do They Pay For?

This is the exchange at the center of the model. Customers pay for a physical product they take ownership of. Or for access to a service they use over time. Or for the completion of a transaction they could not arrange themselves. Or for attention — their own, rented to an advertiser. Each of these payment structures has different economics, different competitive dynamics, and different fragilities. Two companies with identical revenue lines on a chart can be utterly different depending on what that revenue represents.

Map the payment type precisely. "Software" is not enough — is it licensed once, subscribed to monthly, or billed per use? The distinction changes every downstream number.

3. Is the Revenue Recurring or One-Off?

Recurring revenue flows without the business needing to re-acquire the customer for each period. A subscription model, a contract with automatic renewal, a utility relationship — these produce revenue that compounds as the customer base grows, because existing customers stay while new ones are added. One-off revenue requires the business to find and close a new customer for each revenue event. The same gross revenue figure means something structurally different depending on which type is producing it.

This question also surfaces churn: how fast do recurring customers leave? A business with high nominal recurring revenue but 30% annual churn is on a treadmill. A business with low churn is building a compounding base. Neither shows up in a single year's revenue line. See the glossary entry on revenue recurrence for the mechanics of how this compounds over time.

4. What Does It Cost to Deliver?

Cost structure determines how much of the revenue reaches the business as something usable. More importantly for this map, it determines how costs behave as volume changes. A business where most costs are fixed — staff, infrastructure, licenses — has high operating leverage: costs do not grow proportionally when revenue grows, but they also do not shrink proportionally when revenue falls. A business where most costs scale with each unit sold or delivered has lower leverage in both directions. Neither is inherently better; the implications differ depending on growth rate and demand stability.

Map this as a rough split: mostly fixed, mostly variable, or a meaningful mix. The annual report's cost-of-revenue and operating-expense breakdown will show this. The purpose here is not precision — it is knowing which direction the business moves under pressure. This connects to the concept of unit economics: what does it cost to serve one additional customer, and does that cost fall as scale increases?

5. What Is the Single Key Dependency That Could Break the Model?

Every business has a load-bearing assumption — something the model requires to be true for the other four boxes to keep working. It might be a distribution channel that brings in the majority of customers. It might be a regulatory structure that makes the pricing possible. It might be a technology platform on which the product runs. It might be a single large customer whose contract, if lost, would restructure the revenue entirely.

This is the most important box, and it is the one most often left empty. It does not appear as a line item in revenue. It sometimes surfaces in the "Risk Factors" section of a 10-K, but it is often buried in language designed to satisfy disclosure requirements rather than to communicate clearly. The discipline of forcing yourself to name a single biggest dependency — not a list, one — sharpens the question considerably. If you cannot name it, you do not yet understand what the model is depending on.

How to Find the Answers

Every publicly listed company is required to file periodic reports with its securities regulator. In the United States, this is primarily the annual 10-K and quarterly 10-Q filings, available on the SEC's EDGAR database. The 10-K's "Business" section describes the model in plain language. The "Risk Factors" section names the dependencies the company is legally required to disclose. The financial statements show cost structure. These documents are primary sources — they come from the company itself, under disclosure obligations, with auditor oversight.

Reading a 10-K's first 20 pages before reading any secondary commentary about a company is the single most reliable way to complete a business-model map from primary evidence. For a structured approach to distinguishing primary from secondary sources, see Source Hygiene. For how to identify when a narrative about a company is being constructed selectively, see Auditing a Market Narrative.

A Structural Illustration: Blockbuster and Netflix, 1997–2010

This is a closed historical case used strictly to show how the five-question map surfaces a key dependency that headline numbers do not. It is not a commentary on any current business or security.

Netflix was founded in 1997 as a DVD-by-mail rental service and introduced its subscription, no-late-fee model in 1999 — a deliberate structural contrast to the prevailing retail video rental model. By 2004, Blockbuster, then the dominant physical video rental chain, had a business-model structure that any analyst running the five-question map would have found legible from public filings.

On Question 5 — the key dependency — Blockbuster's model contained a structurally important revenue source that would not have survived the map unchallenged. Blockbuster's "extended viewing fees" (commonly called late fees) were structurally central: per Blockbuster's Q4 2004 earnings 8-K, the company projected that ending them would forgo on the order of $400–450 million in revenue and $250–300 million in operating income for full-year 2005 — a measure of how much of the business rested on that single dependency. (For fiscal 2004 itself, extended-viewing-fee revenue was reported at about $622 million.) Those are approximate figures drawn from the filing — but the directional point is clear: a material portion of operating income in that period depended on customers returning physical media late. That revenue was not incidental. It was a load-bearing dependency in the cost structure.

Under Question 5, a rigorous map would have named this plainly: the model depends on customers incurring late fees at a predictable rate, and that dependency is threatened by any competitor who removes the fee structure. Netflix's subscription model was precisely that competitor. Netflix did not need to be large to be threatening at the structural level — it needed only to demonstrate that customers preferred a no-late-fee experience, which it did from its founding year.

Blockbuster attempted to eliminate late fees around 2005. The structural pressure this created on operating income was a direct consequence of the dependency that had been visible in the map. Blockbuster filed for Chapter 11 bankruptcy in September 2010.

The lesson here is not about the video rental industry or about any specific company. It is about the map: the key dependency — Question 5 — was visible in public filings years before the disruption became an observable market event. Analysts focused on revenue growth or market share figures were reading a different set of numbers than the ones that mattered most. The map would have foregrounded the right question earlier. This is how comprehension precedes and improves analysis. For a framework on how prior evidence shapes probability estimates, see Base Rates and Priors.

What the Map Does Not Tell You

A clear business-model map is not a buy signal. It is not a valuation. It does not tell you that a business is attractively priced or that any outcome is predictable.

A business can be structurally sound — recurring revenue, low cost-to-serve, no concentrated dependencies — and still be priced so that all of that quality is already reflected and then some in the current price. A business can have an obvious dependency and be priced at a level that more than accounts for the risk. Comprehension of the model is a prerequisite for forming a useful view. It is not itself a verdict.

The discipline of completing a map before reading any narrative about a business is also a partial antidote to one of the more reliable process failures in market analysis: arriving at a strong view because you encountered a compelling story, and then reverse-engineering reasons to support it. Forming your own description first gives you something to compare against the narrative you later encounter. For the specific mechanics of how narrative shapes interpretation, see Confirmation Bias at the Chart.

Simulator Exercise

Open Abu Terminal's Speed Run and choose an era that contains a company you recognize by name but have never read a filing for — a retailer, a technology company, or an industrial from a decade you did not trade through. Before you read any narrative description of what happened to that company, pause and attempt to fill in all five mapping questions from memory or general knowledge alone.

Write your five answers down — one line each — before proceeding. Then notice which box you could not fill in, or filled in with a vague placeholder. That blank is the signal: you are about to encounter a scenario about a business you have not yet described. The narrative the Speed Run provides will be more useful, and more critically receivable, if you know in advance which dependency you did not understand before the scenario began.

After the session, open the replay debrief and ask: was the key dependency you named in Question 5 the one that actually drove the outcome you were scored on? If it was not — if the scenario turned on something you left blank — that gap is exactly the kind of incompleteness a business-model map is designed to surface before it costs anything. Running this drill across several Speed Run eras builds a calibration for how often your prior comprehension of a business matches the structural reality that determined its outcomes.

Business Model Mapping: Five Questions Before You Form a View