Total addressable market

A founder once told me her company had a $720 million total addressable market. The number came from multiplying every payments company she could find by the product’s annual price.

That’s not useless. It’s just not the number her sales team could work with.

Total addressable market, or TAM, is the maximum annual revenue available if a company captured every relevant customer for a defined product. It’s a ceiling, not a forecast, quota, or credible year one target.

What total addressable market measures

TAM only means something when the product and customer are specific.

Say a 12-person B2B software company sells automated reconciliation to payments businesses. Its average annual contract value is $18,000. The founder finds an industry report listing 40,000 payments companies worldwide:

40,000 accounts × $18,000 ACV = $720 million TAM

The arithmetic is fine. The market definition isn’t.

Many of those companies are too small to need a dedicated reconciliation process. Others already use an internal tool. Some operate in countries the vendor can’t support. Some won’t buy from a small supplier because procurement requires a longer track record.

A market estimate that ignores those details is mostly category theater. It may look good in a pitch deck, but it won’t tell the founder how many accounts to target, whether the sales team is large enough, or whether the product has room to grow.

How to calculate TAM

The basic formula is:

TAM = total potential customers × annual revenue per customer

For a subscription business, use annual contract value rather than a list price that few customers actually pay.

The payments company might start by identifying 8,000 businesses that process enough volume to need dedicated reconciliation. Then it filters for companies with finance teams large enough to buy software and finds 3,000 qualifying accounts. If the median ACV is $18,000:

3,000 accounts × $18,000 ACV = $54 million

The $720 million estimate describes a broad theoretical category. The $54 million estimate describes a market the company can research and sell into today. Both might be useful, but they answer different questions.

For sales planning, I’d trust the second number every time.

Build that estimate from actual accounts where possible. Use company databases, trade associations, public filings, customer interviews, and your own CRM. Look for the conditions that create a buying case. In this example, transaction volume, finance team size, and processor compatibility matter more than a company’s generic industry label.

A bottom-up model also exposes weak assumptions. If you can’t name the accounts, explain why they qualify, or show what similar customers pay, the number needs more work.

TAM, SAM, and SOM

These terms get mixed together constantly. They shouldn’t.

TAM is the full potential market for the product category.

SAM, or serviceable available market, is the part the company can serve with its current product, geography, integrations, pricing, and distribution.

SOM, or serviceable obtainable market, is the part it can realistically win in a defined period.

Return to the payments company. Its $54 million TAM includes accounts across North America, Europe, and Asia. But the product only supports English language workflows and integrates with three processors used mainly in the United States and Canada.

That leaves 900 viable accounts:

900 accounts × $18,000 ACV = $16.2 million SAM

The company has two account executives, one SDR, and enough implementation capacity to onboard about 40 new customers next year. Based on its sales cycle and historical win rate, the team expects to close 25:

25 accounts × $18,000 ACV = $450,000 SOM

That $450,000 is the useful planning number for the next year. Not $720 million. Not even $16.2 million.

SOM should account for sales capacity, competitors, onboarding limits, pricing, and time. It isn’t just “we’ll take 10% of the market.” A startup claiming 10% of a crowded $100 million SAM in year one has confused ambition with arithmetic.

Three ways to estimate market size

Top-down sizing starts with published industry data, then narrows the figure using segment assumptions. A cybersecurity vendor might begin with total security software spending, remove consumer products and services revenue, then estimate the share spent on compliance monitoring.

This is quick and useful when deciding whether a category deserves more research. But the original report may define the category differently from your product. A polished industry number can hide a lot of guesswork.

Bottom-up sizing starts with identifiable buyers and what they pay. For the payments company, that means building a list of qualifying accounts, grouping them by transaction volume, estimating ACV for each group, and adding the segments together.

Suppose the company finds 1,200 target accounts at an average ACV of $20,000. That segment represents $24 million. It doesn’t matter if a market report claims the broader category is worth $2 billion. The sales team still has 1,200 accounts to work with.

Value-based sizing takes a different route. It estimates the financial value created for customers and uses that to test pricing. If the reconciliation product saves a 30-person finance team 1,500 hours per year and prevents $100,000 in errors, an $18,000 contract may be easy to justify.

But a theoretical benefit isn’t revenue. The customer has to recognize the problem, have budget, trust the solution, and sign the contract. Value-based sizing is useful for pricing a new category. It’s a bad excuse for inventing a huge TAM.

What TAM changes in a go-to-market plan

Market sizing should affect the next operating decision. If the payments company has only 900 serviceable accounts, broad demand generation may be wasteful. A named account approach and targeted cold outreach probably make more sense.

The team could prioritize companies that recently changed processors, hired a CFO, failed an audit, or raised enough funding to replace manual finance work. Those triggers give sales reps something specific to investigate and write about.

If the company’s ideal customer profile includes 3,000 businesses but only 300 are compatible with the current product, hiring another SDR is probably not the first move. An integration may be worth more.

TAM also puts revenue plans under pressure. If the business expects $10 million in annual recurring revenue from a $16.2 million SAM, it needs a very good explanation. It may need higher prices, adjacent products, a larger geography, or a different market definition.

The common mistake is treating every company in an industry as a buyer. A 50-person SaaS vendor selling audit workflow software might claim that every regulated business belongs in its TAM. In reality, its product supports only SOC 2 and ISO 27001 workflows, sells in English, and requires a minimum $25,000 contract.

Those constraints belong in the model.

Keep the assumptions beside the number: account count, pricing basis, geography, product limits, source, and date. Separate facts from guesses. “There are 3,000 qualifying accounts” is a market observation. “Thirty percent will buy this year” is a forecast.

Recalculate when something material changes, such as a new integration, a move into Europe, a price increase, or a new sales channel. TAM changes with the product and the company’s ability to serve customers. A smaller market you can name, segment, and reach is more useful than a billion dollar category nobody can actually sell into.