Skip to main content

Step two: test the story for plausibility

Once you have written a narrative, the next step is to pressure-test it. Not mathematically—that comes later. But logically and empirically. Does the story make sense? Has anything like it happened before? Are you asking the company to do something that no competitor has achieved? Is the narrative asking for miracles, or is it based on plausible market dynamics?

This step separates rigorous investing from hope-driven speculation. A narrative that feels good is not the same as a narrative that is plausible. Testing forces you to confront your assumptions and decide whether you are making a bet on business fundamentals or betting that you know something the market does not.

Quick definition: Plausibility testing is the process of checking a narrative against base rates, competitive dynamics, market history, and logical consistency to verify that the story is grounded in reality.

Key takeaways​

  • A plausible narrative is not necessarily true—it is one that has happened before in similar contexts or that is logically defensible given what we know.
  • Base-rate thinking is the core of plausibility testing: does this company have attributes similar to companies that have succeeded with this strategy before?
  • The narrative must be internally consistent (no logical contradictions), consistent with the business model (no claimed advantages that contradict historical performance), and consistent with competitive dynamics.
  • Testing does not require perfection; it requires honesty. If your narrative requires the company to violate physical laws or market dynamics, you know it is speculative.
  • The testing phase often reveals that your narrative is either too conservative, too optimistic, or incomplete.
  • Plausibility testing is qualitative, not quantitative, but it is systematic and rigorous.

Four dimensions of plausibility testing​

Plausibility testing operates along four dimensions: internal consistency, competitive reality, base rates, and management capability.

Dimension 1: Internal consistency​

A narrative is internally inconsistent if it contains logical contradictions. These contradictions are not always obvious, but they destroy the narrative if left unaddressed.

Example: Growth and market saturation. A narrative says: "The company will grow revenue 30% annually for 10 years, reaching $8B in revenue, by capturing 40% of a $20B total addressable market." Do the math. If the TAM is $20B and the company reaches 40% share ($8B), then every other competitor combined has $12B. If the company is growing at 30% and gaining share, other competitors must be shrinking or the TAM must be growing. The narrative must explain how this is possible.

Is the TAM growing? That would make the math work: if the TAM grows 8% annually (from $20B to $45B), and the company reaches 18% share, it would have $8B revenue at 30% growth. Is the company pulling share from competitors who are shrinking? That must be explained explicitly. A consistent narrative accounts for market dynamics.

Example: Margin expansion and competitive dynamics. A narrative says: "The company will expand gross margin from 40% to 55% as it scales, while maintaining 35% annual growth." This is suspicious. How is the company expanding margins while competitors see the opportunity and enter? Either:

  • The company is developing proprietary cost advantages (e.g., owning manufacturing, achieving procurement scale) that are difficult to replicate. This must be stated.
  • The company is expanding into higher-margin products or geographies. This must be explained.
  • The company is raising prices. This must be justified by value creation or brand strength.

A narrative that claims margin expansion without explaining the source is internally inconsistent. Do not let vagueness masquerade as strategy.

Example: Investment and return. A narrative says: "We will invest heavily in R&D to maintain competitive advantage, but operating margin will expand from 10% to 30%." If R&D is a fixed amount, this works as the company scales. If R&D is a percentage of revenue, and the company is investing heavily to maintain advantage, then operating margin does not expand; it stays flat. The narrative must clarify the investment trajectory.

To test internal consistency:

  • Write down the key assumptions (growth rate, TAM, market share, margins).
  • Check whether they are mathematically consistent. Can a company grow 30% in a $20B market without hitting saturation?
  • Identify the implicit mechanics: How does this work? If margin expands, why? If growth accelerates, what changes?
  • Ask whether the mechanics are logical. Do they require new business model innovations, or are they relying on market dynamics that contradict the company's competitive position?

A narrative that passes internal consistency is not proven true; it is just not internally broken.

Dimension 2: Competitive dynamics and market reality​

A plausible narrative accounts for competitive responses. Many investors write narratives that assume competitors will be passive. A strong narrative accounts for how competitors will respond and why the company can defend against that response.

Example: Stripe's narrative and competitive entry. The narrative says Stripe will grow 25% annually and capture share from legacy processors. This narrative assumes that legacy processors (FDC, Global Payments) will not simply copy Stripe's API and compete. A plausible narrative accounts for this. What if Stripe says: "Stripe will win because it was first to market with a developer-friendly API, and it has built network effects through the ecosystem (hundreds of thousands of apps and integrations on Stripe's ecosystem). By the time legacy processors launch similar products, Stripe has such a deep ecosystem that switching is expensive. Stripe maintains advantage through product velocity, ecosystem lock-in, and brand."

This is plausible. Legacy competitors can enter, and the narrative acknowledges it. It then claims that Stripe has defensibility. Reasonable investors can believe this or not, but the narrative is honest about competitive dynamics.

Example: A SaaS company's narrative in a crowded space. Narrative: "Our product will grow 40% annually in a market with 50+ competitors." This is suspicious. Why? Because 50 competitors suggest the market is mature or crowded. If the market were young and growing, there would be fewer players. A plausible narrative explains why a new entrant succeeds in a crowded market. Is it a better product? Lower price? Serving an underserved segment? The narrative must name the advantage.

To test competitive dynamics:

  • Identify who the competitors are: direct competitors (same product, same customer), indirect competitors (different product, same customer need), and disruptive threats (new entrants or business models).
  • Ask: What will they do in response to the company's growth? Will they cut prices? Invest in product? Copy the model?
  • Test whether the narrative's defensibility claims are plausible given competitive response. If the narrative says the company will maintain 30% gross margin while competitors cut prices, that is suspicious.
  • Compare to history: Have other companies in similar industries maintained market share and margins against competitive entry? If not, why is this company different?

A narrative that acknowledges competitive response is more credible than one that assumes the market will wait politely for the company to win.

Dimension 3: Base rates and historical comparables​

Base-rate thinking is the discipline of comparing your narrative to historical outcomes. Have companies achieved the growth rates, margin profiles, and market positions your narrative describes? If not, why will this company be different?

Base rate: Company growth rates. The narrative says the company will grow 35% annually for 10 years, reaching $5B in revenue. How many public companies have achieved this? Amazon reached ~$50B by growing ~25% for 20+ years, sustained by re-investment and market expansion. Microsoft grew 25%+ for 20+ years due to relentless domination of enterprise software. Netflix, Apple, Facebook—all achieved long-term high growth, but it typically required unique positioning and market dynamics.

If you are projecting 35% growth for 10 years, you are predicting that the company will join a very small list. That does not mean it is wrong, but you should acknowledge that you are betting against base rates.

Base rate: Gross margins. The narrative says gross margin will expand from 40% to 60% as the company scales. In what industries is 60% gross margin common? Software (yes), hardware (no), e-commerce (no), financial services (varies), biotech (yes). Is the company in an industry where high gross margins are possible? If your company is in retail and you are projecting 60% margin, you are predicting something no comparable retailer has achieved.

Base rate: Operating margins. The narrative says operating margin will reach 35% at scale. How many companies actually achieve this? Most mature companies operate at 15–25% operating margin. If you are projecting 35%, you need a specific reason (software company with AI-powered automation, high switching costs, network effects). Vague optimism does not justify the projection.

To test base rates:

  • Identify 3–5 historical comparables: companies that attempted a similar strategy or occupied a similar market position.
  • Look at their growth rates, margin profiles, and outcomes. Did they succeed or fail?
  • Ask: What is different about the company you are analyzing? Is it better positioned, or are you overestimating its advantage?
  • Be honest: if no comparable company has achieved the financial outcome your narrative predicts, you are speculating. You might still be right, but own it.

Base rate: Market expansion. The narrative claims the company will expand from a $10B market to a $50B market by expanding into adjacent uses. Can markets actually expand by 5x? Yes: smartphones expanded the mobile market from $10B to $300B+. Cloud computing expanded IT infrastructure from $100B to $500B+. But most markets do not expand this much. A narrative that requires market expansion should test whether the expansion is plausible.

Some useful historical comparables to consider:

  • Cloud infrastructure: AWS achieved 30%+ growth for 15+ years. But it had unique positioning (AWS started as Amazon's own infrastructure, then sold to external customers, giving it cost advantage from the start).
  • Mobile payments: Square grew 40%+ annually for 10+ years, then slowed as market matured. Could Stripe achieve similar trajectories? Possible, if it had different end markets.
  • Streaming video: Netflix grew subscribers from 1M to 200M over 15 years. Is streaming a good comp for your SaaS company? Only if the unit economics and market dynamics are similar.

The point is not to use historical comparables as a ceiling; it is to calibrate your expectations. If you are projecting something that has never happened before, you should know that.

Dimension 4: Management capability and alignment​

A narrative can be plausible in the abstract but implausible given the team executing it. Conversely, a mediocre narrative with a superb team is often more promising than a great narrative with a weak team.

To test management capability:

  • Track record: Has the CEO, CFO, or product lead executed a similar strategy before? Have they built a company from this stage to the next stage? If the CEO is a first-time founder, the narrative should account for execution risk.
  • Incentive alignment: Are management's incentives aligned with the narrative? If the narrative says the company will invest for long-term growth but the CEO gets massive bonuses based on near-term profitability, the incentive is misaligned. If the founder owns significant equity, their incentives are aligned with long-term value creation.
  • Track record of honesty: Does management have a track record of providing realistic guidance and meeting it? Or do they consistently over-promise and under-deliver? If they over-promise, narratives are less credible.
  • Hiring: Is the company hiring the right people for the next phase? If the narrative says the company will invest in product, is it hiring top engineers? If it says it will expand internationally, is it hiring regional leaders with emerging-market experience?

A narrative is only as credible as the team executing it.

Testing framework: the four-dimension checklist​

Red flags in plausibility testing​

Several red flags suggest a narrative is not plausible:

The narrative requires multiple miracles. It is not that the company will expand gross margin by 1,000 basis points and grow at 35% and maintain 90% customer retention and enter a new market at scale, all at once. Each of these is difficult; all together is a miracle. A plausible narrative typically requires one or two major things to go right (e.g., the company's superior product leads to market share gains, and gross margin expands due to scale). Multiple independent miracles are a sign the narrative is too optimistic.

The narrative contradicts what management says. You have written a narrative that the company will expand into B2B markets within three years, but management guidance suggests B2B is 3–5 years away. Either your narrative is overoptimistic, or you have information management does not (unlikely). Divergence from management guidance is a red flag.

The narrative is vague about the key assumption. The narrative says "the company will grow faster than competitors due to superior execution," but does not explain what superior execution means. Vagueness is a sign you have not thought through the story.

The narrative requires competitors to be irrational. The company has a 10% cost advantage and will expand market share, but "competitors will not respond by cutting prices." Why would competitors not respond? If they are rational actors, they will. A plausible narrative explains why competitors cannot respond (they lack the cost advantage due to different business models), not that they will not (irrational actors).

The narrative ignores a major risk. You have written about the company's product advantage, but not mentioned that 50% of customers are concentrated in one vertical, which has slowing growth. Ignoring a major risk does not make the narrative plausible; it makes it incomplete.

The plausibility rating scale​

After testing, you should have a sense of plausibility. Use a simple scale:

Highly plausible (4–5/5). The narrative is internally consistent, has been achieved by historical comparables, accounts for competitive response, and requires one major thing to go right. Examples: Apple's ecosystem narrative (achieved before), Netflix's streaming narrative (achieved before), software companies' margin expansion through scale (happens often).

Plausible (3/5). The narrative is internally consistent, mostly aligns with history, but requires something unusual to happen. Examples: A SaaS company growing 30% for 10 years in a crowded market (possible, but requires exceptional execution). A hardware company expanding from 15% to 35% gross margin (possible if achieving manufacturing scale or moving into higher-margin products).

Speculative (2/5). The narrative is internally consistent and accounts for major risks, but requires multiple things to go right or contradicts base rates. Examples: A company projecting to grow 40% annually for 15 years (only a handful of companies have done this). A new entrant taking 30% market share from an entrenched incumbent in 5 years.

Implausible (1/5). The narrative has internal contradictions, contradicts history, or ignores major competitive threats. Examples: A company claiming it will grow 50% annually while operating margin expands to 50% (extremely rare in any industry). A startup claiming it will defeat an incumbent with a 10x scale advantage.

This scale is not absolute; it depends on the industry and context. A 30% growth rate is routine for a biotech company but extremely ambitious for a financial services company. Base your plausibility rating on context.

Real-world examples of plausibility testing​

Tesla (2010). Narrative: "Tesla will scale production from 1,000 vehicles annually to 100,000+ vehicles by 2020, at gross margins of 25%+, becoming a volume manufacturer." Plausibility test: Have startups ever achieved this? No automotive startup had ever scaled to 100,000 vehicles at 25% margins. This was speculative by historical standards. But it was plausible: the EV market was new, manufacturing at scale was proven, Tesla had capital backing. Rating: Speculative (2–3/5), but the narrative was specific enough to track against actual results.

Netflix (2007). Narrative: "Netflix will transition subscribers from DVDs to streaming, eventually generating 80% of revenue from streaming by 2015, at improving margins." Plausibility test: Had any media company successfully transitioned to a new format? Yes, many times (VHS to DVD, broadcast to cable). Was Netflix capable of executing? It had streaming technology and had launched initially. Rating: Highly plausible (4/5). The narrative aligned with precedent and capability.

Amazon Web Services (2007). Narrative: "AWS will grow to $10B+ in revenue by 2020 by expanding from Amazon's internal infrastructure into an external service, with 30%+ operating margins." Plausibility test: Had any company successfully built a high-margin infrastructure business? Yes, many IT services companies had. Did AWS have unique advantage? Yes, it built the service for internal use first, giving it cost structure advantage over competitors. Rating: Highly plausible (4–5/5).

Zoom (2019). Narrative: "Zoom will grow from $600M to $3B+ revenue within two years due to market shift to remote work, maintaining 25%+ gross margin and expanding operating margin as it scales." Plausibility test: The narrative assumed a major market shift to remote work, which was not guaranteed. The growth rate (100%+ annually) was extreme. But the model was in place. Rating: Speculative (2–3/5) before the pandemic, highly plausible (4/5) after it became clear the market shift was happening.

Common mistakes in plausibility testing​

Confusing a narrative you like with a plausible narrative. You like the company's product and think it is cool. But that does not make the financial narrative plausible. Test it rigorously.

Dismissing a narrative because it has not happened before. Every successful company was once a narrative that had not been achieved before. Tesla had never been done, and it worked. The point is not to avoid narratives with no historical precedent, but to acknowledge the additional risk.

Ignoring base rates because "this time is different." This time is always different. But usually not as different as investors think. If you are projecting something that contradicts historical base rates, own it explicitly, do not hide from it.

Testing the narrative once and then moving on. Testing is not a one-time event. New evidence arrives quarterly. Retest the narrative against each quarter's results and new competitive information.

Forgetting to test management capability. A narrative is only as credible as the team executing it. Spend time assessing whether the team can deliver.

FAQ​

Q: What if my narrative passes some tests but not others? A: Then you have a narrative with specific strengths and weaknesses. Own that explicitly. Write a narrative that is "highly plausible in growth, speculative in margin expansion," and be clear about where the risk is.

Q: Should I abandon a narrative if it fails plausibility testing? A: Not necessarily. Speculative narratives can still generate attractive returns. But you should know they are speculative. If you are betting on Tesla in 2010 (speculative), you should size the position accordingly and have a clear trigger for updating if the narrative breaks.

Q: How much time should I spend on plausibility testing? A: As much as it takes to understand the narrative's strengths and weaknesses. For a high-conviction thesis, spend a few days. For a speculative idea, spend less time but be explicit about what you do not know.

Q: Can I plausibility test a narrative I disagree with? A: Yes. Understanding the bull case narrative, even if you do not believe it, is valuable. Test it. Rate its plausibility. Compare your base case to the bull case. This is how you think critically.

Q: What role does base-rate thinking play in plausibility testing? A: Base-rate thinking is central. Before you claim the company will achieve something unprecedented, check whether anything close has been achieved before. If not, acknowledge that you are betting against history.

  • Base-rate fallacy — The tendency to ignore historical frequencies when making predictions.
  • Reference class forecasting — Using comparable historical cases to estimate the likelihood of a narrative.
  • Overconfidence bias — The tendency to overestimate plausibility without rigorous testing.
  • Scenario analysis — Creating bull, base, and bear cases, each with different plausibility ratings.
  • Narrative shifts — When reality contradicts the narrative, it is time to update.

Summary​

Plausibility testing is the discipline of checking a narrative against logic, history, and competitive dynamics. It is not a mathematical exercise; it is a rigorous qualitative assessment. A plausible narrative is not guaranteed to succeed—it is one that has a reasonable chance of occurring given what we know about markets, competition, and human capability.

Testing forces you to separate conviction from hope. You may still invest in a speculative narrative (2–3/5 plausibility), but you should know that is what you are doing. You should size the position accordingly and monitor it closely for signs that the narrative is breaking.

Next​

Proceed to Step three: derive numbers from the story to learn how to translate a plausible narrative into a financial model.

Statistic: Investors who rigorously test narratives against base rates and historical comparables show 40% better accuracy in forecasting long-term business performance than those who rely on intuition alone.