TAM Diligence Checklist
Quick definition: TAM diligence is the systematic investigation and validation of Total Addressable Market claims, comparing management estimates against independent research, comparable company data, and bottom-up market analysis.
TAM assessment is central to growth investing analysis, yet many investors perform TAM diligence superficially—accepting management-provided estimates at face value or conducting cursory top-down calculations. Rigorous TAM diligence requires systematic investigation across multiple dimensions, explicitly questioning assumptions and validating claims against independent evidence.
This checklist provides framework for disciplined TAM diligence applicable across different market types and company stages.
Market Definition and Scope
Define the market precisely. Begin by articulating exactly what problem the company addresses and which customers face that problem. "HR software for mid-market companies" is more precise than "HR technology." Vague market definitions enable inflated TAM estimates and obscure critical assumptions. Write down the specific customer segment, problem addressed, and geographic scope before estimating TAM.
Verify market definition consistency with company product. Sometimes companies claim larger TAMs than their product addresses. A payroll processing company might claim a "total HR software TAM" but actually address only payroll. The claimed TAM should match the company's current product scope. Adjacent expansion potential should be addressed separately as TAM expansion opportunity, not core TAM.
Confirm customer spending in the defined market. Validate that customers currently spend money addressing this problem. Some nascent markets might eventually be large, but if customers don't yet spend on solutions, TAM is zero today regardless of future potential. If customers do spend, identify what they spend on today—that spending is the minimum credible TAM anchor.
Distinguish between TAM and total spending on related problems. A payment processing company might claim TAM encompassing "all payment and commerce infrastructure," which overstates the company's addressable market. TAM should be limited to payments processing specifically, not all commerce infrastructure.
Top-Down Validation
Identify credible top-down TAM estimates from industry analysts. Gartner, IDC, Forrester, and similar analysts publish spending estimates for major software categories. Do these published estimates align with management TAM claims? Significant divergence requires explanation. If management claims $100 billion TAM but industry analysts project $20 billion, the gap indicates either analyst underestimation or management overestimation requiring investigation.
Cross-reference multiple analyst sources. Different analysts often publish different TAM estimates. Compare Gartner, IDC, and Forrester estimates. If estimates diverge by 50%+, understand the source of divergence—different market scope, different geographic coverage, or different time horizons.
Validate GDP/industry spending allocation percentages. If top-down TAM estimation depends on claims that "15% of enterprise software spending flows to HR platforms," validate that percentage against historical data. Analyst reports often project spending allocations; compare management assumptions to published analyst projections.
Apply conservative percentages. If management claims TAM from top-down estimation, apply deliberately conservative percentages at each cascade step. If management assumes 20% penetration, model both 10% conservative and 20% base case penetration. This range-based thinking acknowledges uncertainty.
Bottom-Up Validation
Count addressable customer units independently. Don't accept management customer count estimates at face value. Use census data, company databases, industry registries, and analyst reports to independently estimate customer counts. For "mid-market software companies in North America," what does census and company databases tell you about actual counts? How does management count compare to independent counts?
Validate average selling price (ASP) against comparable companies. Pricing is critical to TAM. If management claims ASP of $200,000 for mid-market HR software, what do comparable companies charge? If Workday charges $300,000 for comparable functionality, why would customers pay $200,000 to a smaller, less-proven vendor? ASP assumptions should account for competitive positioning.
Review pricing tiers and feature-based pricing. TAM based on single ASP often oversimplifies. Sophisticated vendors price different customer segments differently. A bottom-up TAM should incorporate different ASPs by customer segment—large customers paying $500,000, mid-market customers paying $100,000, small customers paying $20,000. This segmented approach is more credible.
Estimate penetration rates against historical adoption curves. What do historical adoption curves show for comparable markets? If comparable markets achieved 20% penetration over 10 years despite established vendors addressing the category, why would a newer market achieve 30% penetration? Look to precedent for penetration rate reasonableness.
Model multiple penetration scenarios. Rather than accepting single penetration estimate, model conservative, base, and aggressive penetration scenarios. This range captures uncertainty and makes critical assumptions explicit.
Comparable Company Analysis
Identify comparable companies and their stated TAM estimates. Salesforce, Workday, Adobe, and other public software companies publish addressable market estimates in investor presentations. These provide reference points for your market. If Salesforce claims a $50 billion TAM in sales automation and similar functionality, and your company targets a $100 billion TAM in HR, what explains the difference?
Compare revenue as percentage of claimed TAM. A company claiming $50 billion TAM while generating $200 million revenue (0.4% share) is either massively underperforming or has inflated TAM. Compare revenue to TAM ratio against comparable companies. If comparable companies generate 2-5% of their claimed TAM as revenue, and your company generates 0.2%, reconcile the difference.
Analyze customer acquisition patterns and penetration rates. Public companies publish customer counts and customer acquisition rates. If a market leader acquired 500 customers annually at peak growth, and a new entrant claims it will acquire 2,000 customers annually in the same market, understand why—is the market significantly larger than evident from market leader growth? Have conditions changed that enable faster acquisition? Or is the forecast unrealistic?
Review guidance progression. Compare how comparable companies' TAM estimates have evolved over time. Did early TAM estimates prove accurate? Did they expand as companies discovered new use cases? Understanding historical precedent informs assessment of current TAM expansion claims.
Management Quality Assessment
Evaluate track record of management TAM estimates. Has management previously made TAM estimates in other roles or companies? Have those estimates proven accurate? Investors often accept TAM estimates from experienced operators while discounting estimates from first-time entrepreneurs. This heuristic captures a real tendency—experienced managers internalize market disciplines while novices often overestimate.
Cross-examine management TAM methodology. Ask management explicitly: How did you estimate this TAM? Request documentation of top-down and bottom-up approaches. Does management provide one number or a range? Sophisticated management typically provides ranges acknowledging uncertainty. Management providing a single point estimate may reflect overconfidence.
Identify management conflicts. Management incentives favor large TAM estimates—they justify aggressive growth targets and premium valuations. Evaluate how internal incentives might bias TAM estimates. Independent TAM validation provides check on these incentives.
Assess market knowledge depth. Does management demonstrate deep customer knowledge through specific customer examples, use case understanding, and pricing discussion? Or does management present generic market information applicable to many TAMs? Deep market knowledge suggests credible TAM understanding.
Market Structure and Competitive Dynamics
Document existing competitors and their market positions. If the market is mature and competitive, competitors' market shares and positioning indicate realistic TAM. If Zendesk and Salesforce capture 40% of CRM market combined, a new entrant's TAM estimate should account for entrenched competition. Substantial portion of TAM may be uncapturable due to switching costs and network effects.
Identify barriers to entry and switching costs. Low-barrier markets enable rapid competition, limiting pricing and expanding TAM. High-barrier markets enable premium pricing and sustainable positioning. TAM estimates should account for competitive dynamics.
Assess regulatory constraints. Some TAMs are constrained by regulatory barriers that limit competition and protect incumbents. Healthcare software, financial services software, and regulated industries often have regulatory protection that constrains addressable TAMs. Understanding regulatory landscape refines TAM estimates.
Evaluate network effects and switching costs. TAMs with strong network effects and switching costs are more defensible—competitors find it harder to capture share even in large markets. TAMs with weak network effects see more competition and commoditization. This affects long-term TAM value.
Red Flags
Watch for circular reasoning. "Our TAM is $100 billion because we'll capture $5 billion in revenue at 5% share." This inverts correct logic. TAM should be estimated independently of revenue projections.
Be skeptical of TAM claims that require behavior change. TAMs that depend on assuming customers will radically change behavior ("everyone will move from on-premise to cloud") are less credible than TAMs based on existing customer spending patterns.
Question TAM expansion claims without execution evidence. Companies often claim TAMs expanding into adjacent markets. If the company has zero revenue in the adjacent market yet large portion of TAM depends on capturing that adjacent market, be skeptical of execution capability.
Verify whether claimed TAM growth reflects market growth or scope expansion. Management might claim "TAM grew 20% year-over-year" when the growth reflects expanding product scope, not growing existing market. Distinguish market growth (positive) from TAM scope expansion (neutral to negative—larger TAM often indicates competitive positioning challenges).
Distrust single-source TAM estimates. If TAM estimate comes only from management, industry analyst, or company research, validate against other sources. Triangulation across sources reduces probability of missing critical issues.
Documentation Template
For each TAM analysis, document:
- Market Definition: Specific problem, customer segment, geographic scope
- TAM Estimate (Base/Conservative/Aggressive): Three-scenario TAM range
- Top-Down Estimate: Starting category, cascade assumptions, source validation
- Bottom-Up Estimate: Customer counts, penetration assumptions, ACV assumptions
- Comparable Company Analysis: Reference companies, their TAM estimates, revenue capture percentages
- Saturation Assessment: Current penetration, growth trends, saturation timeline
- Expansion Opportunity: Adjacent markets, expansion timeline and credibility
- Key Risks: Critical assumptions, validation gaps, competitive threats
This documentation forces explicit thinking and enables later review when outcomes diverge from estimates.
Key Takeaways
- Precise market definition prevents scope inflation, requiring explicit agreement on problem addressed, customer segment, and geographic boundaries rather than vague category claims.
- Independent validation across multiple sources (analysts, comparable companies, bottom-up research) identifies divergences that reveal hidden TAM inflation risks.
- Comparable company reference points constrain estimates, preventing outlier TAM claims by comparing revenue capture percentages to historical precedent in similar markets.
- Penetration rate assumptions should anchor to historical adoption patterns, limiting overoptimistic claims by grounding forecasts in comparable market precedent.
- Documentation forces rigor and enables later assessment of whether TAM estimates reflected reality, enabling investment learning and improving TAM assessment quality over time.