How can I apply the example to my own product?

Identify the matching customer situation, verify the required capability and run a bounded test. Record the differences between your case and the example before adopting the approach.

Are numerical scenarios measured customer results?

Constructed scenarios and illustrative numbers are labelled as such. Public-site observations describe visible material and do not establish internal budgets, conversion rates or causal revenue outcomes.

A SaaS TAM slide: a worked review

Use this example alongside the saas market guide. The purpose is to make a decision inspectable, not to promise that copying an asset will reproduce another company’s results.

The situation

An illustrative product estimates 10,000 eligible accounts and $5,000 annual spending per account.

Work through the decisions

Arithmetic

The theoretical annual opportunity is $50 million.

Serviceability

The team must remove accounts it cannot currently serve.

Obtainability

Expected company sales require a separate distribution and competition model.

Review point	Observation or decision
Arithmetic	The theoretical annual opportunity is $50 million.
Serviceability	The team must remove accounts it cannot currently serve.
Obtainability	Expected company sales require a separate distribution and competition model.

The useful lesson

A readable model is more useful than a large unsupported market total.

Before applying the pattern, write down which part of your customer situation is similar and which part is different. A tactic that helps one segment can create friction for another when buying complexity, product readiness or implementation work changes.

The limit of the example

The numbers are constructed for the example and are not drawn from a public filing or market study.

An example can demonstrate a mechanism or a presentation choice without proving commercial performance. Keep that distinction when sharing it with colleagues. If a numerical result is important to the decision, obtain the original evidence and preserve the population, time period and method used to calculate it.

Adapt the pattern

Choose one relevant customer task and define the outcome you want to improve.
Use the working resource to describe the proposed change and required evidence.
Confirm that the product and operating team can deliver the promise in the actual customer path.
Review a representative case, record the result and decide whether another test or a wider rollout is justified.

Keep the initial scope bounded. A useful exercise ends with a clearer decision and an owner for the next action, even when the conclusion is that the pattern does not fit your business.

Browse more worked examples and the resource library for adjacent tasks.

Apply a saas tam slide: a worked review in a working review

Separate the observed or constructed situation from the inference you draw from it. Identify the mechanism, the conditions that made it relevant and the circumstances in which it would not transfer. A useful example helps a reader reason about their own case; it does not promise that copying the surface appearance will reproduce the same outcome.

For this topic, involve the research owner and the person using the estimate for a decision and work from source method, market boundary and assumption table. The relevant unit is a clearly defined population, period and value measure. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

Read the original definition before combining figures. Publication date, collection period and forecast horizon answer different questions. A market estimate can be useful without being directly comparable to another publisher’s number.

Review field	What to record
Topic	A SaaS TAM slide: a worked review
Decision	The specific action this explanation should help you choose
Working evidence	source method, market boundary and assumption table
Unit and scope	a clearly defined population, period and value measure
Responsible people	research owner and the person using the estimate for a decision
Remaining uncertainty	The missing fact that could change the decision

Two situations that can change the interpretation

When TAM has no eligible-account rule

Not every company in an industry needs or can adopt a particular operational workflow.

Use this check: Define the customer workflow, geography, supported requirements and exclusion criteria. A large addressable market is not evidence of obtainable demand.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When competitor count is treated as demand

A crowded category may contain many small tools serving different jobs rather than one homogeneous market.

Use this check: Separate evidence of supply from evidence of customer problems, spending and switching behavior. Few competitors can indicate opportunity or lack of demand; the count alone does not decide.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

A software-revenue estimate and a broader customer-spending estimate may both be credible within their own definitions. Averaging them does not create a better answer. Explain the boundary and choose the measure that matches the decision being made.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.