What is total addressable market?

When a gaming platform talks about reaching a billion people each day, the useful question is not whether that many humans exist with screens. It is whether total addressable market describes a real path to adoption or just a very large ceiling.

Why this matters now

Total addressable market, or TAM, is one of the most common numbers in strategy decks, fundraising plans, and product roadmaps. It estimates the maximum demand a product could capture if every plausible customer in the defined market adopted it. That makes it useful for sizing ambition, but dangerous when treated as proof of momentum.

For professionals working in AI and technology, TAM matters because many products now claim extremely broad reach: every knowledge worker, every developer, every mobile user, every enterprise. Generative AI tools, agent platforms, cloud services, and developer ecosystems can all look massive when the market is defined broadly enough. But strategy depends on narrowing the question from who could use this to who has the problem, access, budget, trust, and habit required to use it repeatedly.

How it works

TAM starts with a market boundary. You define the customer group, the use case, and the value unit, then estimate how much demand exists if adoption were unconstrained. From there, good market sizing narrows the view into serviceable market and reachable market before comparing it with actual active users or revenue.

  Potential market ·············
     │
     ▼
  Serviceable market ···········
     │
     ▼
  Reachable market ·············
     │
     ▼
  Active users ·················

The key distinction is that TAM is not a forecast. It is a ceiling under stated assumptions. A serviceable market asks which part of that ceiling your product can actually serve given geography, platform support, language, compliance, device requirements, or distribution channels. A reachable market asks which portion you can realistically acquire with your current product, brand, partnerships, pricing, and sales motion.

This is where many technology strategies break down. They count possible users but underweight friction. Friction can be technical, such as needing compatible hardware or a supported operating system. It can be behavioral, such as switching from an existing workflow. It can be economic, such as budget ownership. It can also be social, such as whether colleagues, friends, or partners are already in the same ecosystem.

Real-world applications