TAM, SAM, and SOM for product managers
TAM, SAM, and SOM are three ways to frame market size. Total addressable market, or TAM, is the broadest opportunity if the relevant problem could be served without today’s constraints. Serviceable available market, or SAM, narrows that opportunity to the customers and use cases a product can realistically target. Serviceable obtainable market, or SOM, is the portion I could plausibly reach and win over a defined period.
I use the framework to clarify assumptions, not to decorate a strategy document with a very large number. Market sizing is useful when it helps me choose a segment, test demand, plan capacity, or decide whether an opportunity is worth pursuing. It is weak when the categories are vague or the arithmetic hides uncertainty.
Define the market before calculating it
I start with the customer, problem, geography, time period, and buying unit. “The software market” is not a usable market definition. “Organizations in a specified region that need to coordinate a defined workflow and have a budget owner for that problem” is closer, though it still needs evidence.
I describe the job and the alternative. Customers may solve the problem with another product, an internal process, a spreadsheet, a service provider, or nothing at all. If I count only direct competitors, I may understate the alternatives. If I count everyone who could theoretically benefit, I may overstate the market.
I also distinguish users from buyers, accounts from seats, and revenue from customer count. A product sold per account should not use individual users as its only denominator. The unit must match the business model and the decision I am making.
Estimate TAM as a boundary, not a forecast
TAM is a way to describe the broad boundary of a problem. I can estimate it top-down using credible industry, economic, or public data, or bottom-up using a count of relevant customers multiplied by a plausible annual value. I prefer bottom-up reasoning when I can define the population and pricing logic clearly.
A bottom-up example might be: number of organizations that meet the problem definition multiplied by an annual contract value range. The result is not a promise that every organization will buy. It is a transparent estimate of the opportunity under stated assumptions.
I show a range when the inputs are uncertain and explain what would move it. I do not combine unrelated sources just to reach a larger figure, and I do not treat a vendor’s market estimate as independent proof without checking definitions and incentives.
Narrow to SAM with real constraints
SAM reflects where the product can serve customers given its capabilities, geography, language, compliance requirements, integrations, pricing model, distribution, and support model. I narrow TAM by explicit filters rather than applying an unexplained percentage.
For example, a product may serve only certain industries because of workflow fit, only certain countries because of data or support requirements, or only a subset of company sizes because the implementation model requires specialist help. Those constraints are not defects in the analysis; they make the target more actionable.
I list each filter and ask whether it is a current constraint, a deliberate choice, or a hypothesis that could change. If the product roadmap can expand the market, I show the current SAM separately from a potential future SAM. That keeps strategy from treating future capability as present revenue.
Make SOM a plan with evidence
SOM is the most decision-oriented layer. I define the period, route to market, capacity, competitive position, and expected adoption path. I ask how many customers the team can reach, onboard, support, and retain—not only how many might be interested.
I build SOM from operating assumptions such as qualified opportunities, conversion, sales cycle, onboarding capacity, product readiness, and retention. For a self-serve product, I may use qualified traffic, activation, conversion, and support capacity. For an enterprise motion, I may use target accounts, reachable buying groups, pipeline, win rate, implementation limits, and expansion assumptions.
I label these as scenarios, not facts. A base case, upside case, and downside case can show which assumptions matter most. I then identify the fastest evidence to collect: interviews, pricing conversations, a landing-page test, a prototype test, a design-partner commitment, or a small paid pilot where appropriate.
Connect market size to product strategy
A market estimate becomes useful when it changes a product decision. I use it to choose an initial segment, evaluate whether a roadmap expands serviceable demand, compare distribution options, or decide what evidence is needed before scaling. I do not use TAM to justify building a feature without customer evidence.
I connect the sizing model to a product strategy framework and to competitive analysis. The market can be large while the product’s wedge is weak. A smaller segment with urgent needs, reachable buyers, and strong retention may be a better starting point than a broad category with expensive acquisition and low differentiation.
I revisit the model when pricing changes, the target customer changes, a new competitor enters, regulations shift, or research changes the problem definition. Versioning prevents old assumptions from becoming invisible facts.
Common mistakes
The most common mistake is confusing TAM with revenue potential in the next year. TAM describes a broad opportunity; it does not account for access, competition, product fit, or execution capacity. Another mistake is using a top-down percentage for SAM or SOM without explaining the filter.
I also watch for double counting, mismatched time periods, inflated pricing assumptions, and market reports that define the category differently from the product. A forecast with precise decimals can still be fragile if the underlying customer count is uncertain.
Finally, I avoid treating a market-size slide as validation. Customers’ willingness to pay, ability to adopt, and continued use are separate questions. The market model helps me decide what to test next.
A practical market-sizing worksheet
I create a table with these columns: customer definition, buying unit, geography, problem evidence, population source, value or price assumption, inclusion filter, confidence, and next validation step. I calculate a range rather than a single heroic number. I then write three sentences: what the market includes, what it excludes, and which assumption could most change the decision.
I review the worksheet with sales, marketing, finance, data, and customer-facing teammates when possible. Their questions often expose constraints that a product-only model misses. After that review, I convert the most important uncertainty into a research or go-to-market test.
TAM, SAM, and SOM are most valuable when they make a strategy more honest. I use them to show where the opportunity might be, where I can serve now, and what evidence would justify reaching further.
Next step
Build stronger product strategy, market research, and decision-making skills in the Product Manager Certification. Subscribe to the Product HQ newsletter for practical frameworks and career-ready product lessons.
