MODULE 01 · MARKET INTELLIGENCE

Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters

TAM can show the theoretical boundary of demand. It cannot tell an exporter which accounts use the product, whether they can be reached, how they buy, or whether the supplier can enter and support the market.

DEFINITION

What is this about?

For B2B exporters, define TAM as the full relevant demand or account universe under stated product and application boundaries; SAM as the part that fits your geography, customer relationship, application, entry, and service constraints; and SOM as the named account scope your team can credibly reach and support during a defined period. Treat SOM as an execution boundary, not a sales forecast.

KEY TAKEAWAYS

  1. Begin with a precise product-application market definition, not a report headline.
  2. Use trade classifications to study goods and NAICS to study establishments; neither alone identifies qualified buyers.
  3. Derive SAM by applying evidence-based filters, not by taking an unsupported percentage of TAM.
  4. Build SOM from verified accounts, reachable buying paths, and actual sales and service capacity.
  5. Keep units, periods, currency, classifications, sources, calculations, and unknowns visible.
  6. A large TAM can coexist with a poor first market.

Who this explainer is for

This explainer is for manufacturers and industrial exporters preparing a market-entry case, budget, investor narrative, account plan, or outreach program and needing a market size that can be reconciled with real companies and operating constraints.

Contents

1 Define TAM, SAM, and SOM for B2B export decisions 2 Choose the right unit 3 Build an evidence-led market funnel 4 Use the SellersGPT Account-Based Market Scope 5 Test readiness beyond size 6 Illustrative example 7 Common mistakes 8 What this explainer does not mean 9 Common questions 10 Sources and methodology

1. Define TAM, SAM, and SOM for B2B export decisions

The labels are widely used but inconsistently defined. For this Knowledge framework, use the following operational definitions. Total addressable market - TAM The complete demand, spend, unit, establishment, or account universe that falls inside a stated product, application, geography, and period boundary, assuming the relevant need exists and without yet applying your company's route and capacity constraints. TAM must still be relevant. "All manufacturing in North America" is not TAM for one specialized component unless every included establishment could plausibly use it under the defined application. Serviceable available market - SAM The portion of TAM that fits the company's actual product, application, customer relationship, geographic coverage, certification, regulatory, delivery, channel, and service conditions. SAM is where a theoretical category becomes a business-specific opportunity space. Serviceable obtainable market - SOM The named, reachable account scope that the company can credibly cover, qualify, deliver, and support during a defined execution period, given sales capacity, route to market, proof, budget, and constraints. SellersGPT recommendation: SOM should not mean "the share we expect to win." Call that a forecast and disclose its separate assumptions. SOM is the bounded arena in which execution can occur.

2. Choose the right unit

Market-sizing errors often begin when incompatible units are mixed. Unit Useful for Main limitation Trade value Product flow and change by classification Not buyer revenue, end demand, or reachable spend Trade quantity Physical flow when quantity units are valid Units may be missing, suppressed, mixed, or unsuitable Establishments Geographic and industry activity density One company may have multiple establishments; not all fit the application Companies or parent accounts Account strategy and commercial coverage Requires deduplication and facility mapping Relevant facilities Plant-level application and service planning Data assembly is more demanding Unit Useful for Main limitation Potential annual units Product planning and capacity scenarios Depends on penetration, replacement, and usage assumptions Revenue Economic potential Sensitive to price, mix, channel, and timing assumptions Official fact: BLS distinguishes an establishment - typically one physical economic unit - from a firm or company that may contain multiple establishments. U.S. Bureau of Labor Statistics - QCEW Concepts For industrial GTM, use at least two views: a market-flow view and an account or facility view. Reconcile them instead of forcing one dataset to produce both.

3. Build an evidence-led market funnel

Step 1 - freeze the definition Write: Product + application + buyer relationship + industry + geography + operating condition + period Example: hygienic liquid-transfer equipment for mid-sized food-processing facilities in Ontario and selected Great Lakes states, bought by end users with local installation support, over the next 12 months. Step 2 - verify classifications Record the HS or HTS code used for product-flow research and the NAICS code used for establishment research. Document code level, descriptions, exclusions, version, and any concordance across years. Official fact: NAICS classifies business establishments for statistical purposes. It is not a product classification. U.S. Census Bureau - NAICS Step 3 - build the broad evidence boundary Use official trade data to understand relevant product flow and official establishment data to locate industry activity. Official fact: USITC DataWeb provides official U.S. import and export statistics with selectable trade flow, classification, measure, period, country, and commodity dimensions. USITC - DataWeb Official fact: County Business Patterns provides annual statistics for employer businesses at detailed NAICS and geographic levels; QCEW provides establishment, employment, and wage data. These sources screen where activity exists but do not identify all buyers. U.S. Census Bureau - CBP API and BLS - QCEW Overview Step 4 - apply SAM filters Apply each filter with a documented rule:

• relevant application or production process;

• facility scale or operating condition;

• OEM, distributor, end-user, or contractor relationship;

• product specification and compatibility;

• certification and regulatory eligibility;

• deliverable geography and lead time;

• installation, warranty, spare parts, and support coverage;

• workable route to specification and purchase;

• economics above the company's minimum threshold. Avoid a shortcut such as "SAM equals 10 percent of TAM" unless that 10 percent is calculated from disclosed evidence. Step 5 - build the SOM account universe For each candidate account, record:

• parent company and relevant facility;

• evidence of application fit;

• relationship type;

• likely buying roles;

• route-to-market path;

• entry or service requirement;

• reachable business contact path;

• inclusion, exclusion, or research-needed status;

• evidence source and date. Apply capacity limits: how many accounts can be researched, contacted, followed up, technically supported, visited, quoted, fulfilled, and serviced during the decision period?

4. Use the SellersGPT Account-Based Market Scope

Maintain five counts rather than one impressive number: Layer Definition Output Statistical universe Establishments or product flow inside the broad boundary Source-led screening total Application-fit universe Facilities or accounts plausibly using the product Evidence-based estimate or list Serviceable universe Application-fit accounts meeting entry, geography, route, and support conditions SAM Reachable universe Serviceable accounts with a valid business access path Reachable SAM Execution scope Named accounts the team can responsibly cover in the period SOM For every transition, publish the inclusion rule, exclusion rule, number removed, unknown count, source, and calculation. An unknown should not be silently counted as fit or excluded as unimportant. Revenue scenarios belong beside, not inside, the account scope If revenue potential is useful, calculate scenarios after the account scope is visible: eligible accounts x assumed purchase incidence x assumed units x assumed realized price Label every non-official input as an assumption. Use ranges. Do not describe the output as an official market fact or SellersGPT forecast.

5. Test readiness beyond size

After sizing, ask:

• Is the need urgent enough to trigger evaluation?

• Can the team identify and reach relevant buying roles?

• Are incumbents protected by approval, integration, service, or switching cost?

• Can the product legally enter and operate as sold?

• Can the supplier quote, deliver, install, warrant, and support?

• Does margin support acquisition and route-specific costs?

• Is proof strong enough for the buyer's risk level? These questions explain why market size is not market readiness.

6. Illustrative example

Illustrative example. All figures are fictional and show method only. They are not market estimates, customer data, or forecasts. An exporter begins with 1,800 employer establishments in selected industry-geography cells. Manual and secondary screening indicates that 420 may operate the relevant application. Product, certification, geography, delivery, and service filters reduce the serviceable universe to 160 accounts. Valid business access paths exist for 95. Given research, outreach, follow-up, and technical capacity, the team selects 60 named accounts for a 90-day execution scope. Layer Fictional count Meaning Statistical universe 1,800 Screening count, not prospects Application-fit universe 420 Requires continuing verification Serviceable universe 160 Meets current SAM rules Reachable universe 95 Valid access path identified Execution scope 60 Bounded SOM for the period The company does not claim it will win 60 accounts. It has defined which 60 accounts can be responsibly tested and what evidence will update the next market decision.

7. Common mistakes

Buying a market report and calling the headline TAM Verify product definition, geography, channel level, currency, period, and whether the figure measures sales, shipments, imports, production, or something else. Multiplying a broad market by an arbitrary percentage Apply observable filters and show the account or facility logic. Treating establishments as companies Deduplicate parent accounts and preserve facility-level applications. Treating imports as total demand Imports exclude domestic production and do not reveal every application or buyer. They can also include inventory, related-party trade, and mixed product categories. Calling SOM a revenue target Separate reachable execution scope from conversion and revenue assumptions. Ignoring fulfillment capacity A market is not serviceable if the team cannot deliver the product experience buyers require.

8. What this explainer does not mean

• It does not establish one universal definition of TAM, SAM, and SOM.

• It does not turn public statistics into a buyer list.

• It does not predict market share, leads, meetings, orders, or revenue.

• It does not replace product classification, customs, regulatory, tax, or certification advice.

• It does not assume every market should be narrowed to a small SOM; the execution scope depends on the sales motion and capacity.

9. Common questions

Should TAM be measured in revenue or accounts? Use the unit that answers the decision, and show both when useful. For account-based GTM, account and facility counts are necessary even when revenue scenarios are also presented. Can trade value be our TAM? Only if you explicitly define TAM as that product-flow measure and disclose its limitations. It is not automatically end-market revenue or addressable spend. How precise should SOM be? Precise enough to identify named accounts, inclusion evidence, route, capacity, and period. False decimal precision does not improve the evidence. What if application fit is unknown for many accounts? Keep a research-needed segment. Report known fit, known exclusion, and unknown separately. Use primary validation to reduce the unknowns.

10. Sources and methodology

Sources 1 U.S. Census Bureau - NAICS. Used for the official purpose of NAICS as an establishment classification. Accessed August 24, 2026. 2 U.S. Census Bureau - County Business Patterns API. Used for employer-establishment statistics by NAICS and geography. Accessed August 24, 2026. 3 U.S. Bureau of Labor Statistics - QCEW Overview and QCEW Concepts. Used for establishment, company, employment, wage, geography, and industry concepts. Accessed August 24, 2026. 4 U.S. International Trade Commission - DataWeb. Used for the dimensions and scope of official U.S. merchandise trade data. Accessed August 24, 2026. 5 Statistics Canada - Canadian Business Counts, Table 33-10-1097-01. Used for Canadian business counts by NAICS and subnational geography. Accessed August 24, 2026. 6 Statistics Canada - Canadian International Merchandise Trade Web Application. Used for official Canadian merchandise trade availability. Accessed August 24, 2026. 7 International Trade Administration - Market Diversification Tool. Used for the official framing of multi-indicator market comparison as a research starting point. Accessed August 24, 2026. SellersGPT framework The operational TAM, SAM, and SOM definitions, five-layer Account-Based Market Scope, filter sequence, and separation of execution scope from forecast are original SellersGPT editorial choices. They are decision tools, not official statistical definitions. Evidence labels

• Official fact: directly supported by a named official source.

• Calculated from official data: derived from a disclosed dataset, code, period, unit, and method.

• SellersGPT recommendation: a framework, filter, or practical interpretation. Update policy Review annually and whenever product scope, classification, market geography, entry requirements, account evidence, route-to-market coverage, service capacity, or the execution period changes.

Sources and Methodology

  1. bls.gov: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  2. census.gov: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  3. dataweb.usitc.gov: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  4. census.gov: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  5. bls.gov: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  6. www150.statcan.gc.ca: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  7. www150.statcan.gc.ca: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)
  8. trade.gov: Market Size Is Not Market Readiness: TAM, SAM, and SOM for B2B Exporters(2026-09-09, accessed 2026-09-09)

Methodology

This article separates cited official or first-party facts from SellersGPT calculations, examples, frameworks, and recommendations. Source links and scope are retained from the publication pack.

Limitations

This material supports planning and decision-making. It is not legal, financial, regulatory, or performance advice, and it does not guarantee leads, meetings, customers, revenue, or return on investment.

Ready to Build Your B2B Sales Pipeline?

Explore SellersGPT

Research your market, compare GTM approaches, and learn how qualified B2B pipeline is built.