Individual skill
build-and-fill-a-tam
Use this skill when a team needs a defensible total addressable market and a governed plan to cover it over time. Produces a sourced account estimate, revenue model, contact target, CRM coverage baseline, and measured population plan.
skills/ryan-iyengar/build-and-fill-a-tam/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- sales Declared skill tag
- revops Declared skill tag
- leadership Declared skill tag
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,204 bytesSKILL.mdcore · 5,204 bytesSKILL.mdcore · 5,204 bytesreferences/tam-model.mddoc · 793 bytesreferences/worked-tam.mddoc · 818 bytes
Read excerpt
Use this when the team needs to size a market and turn that estimate into an executable account-coverage program. Produce labeled assumptions, real account counts where possible, and a burn-up plan that never confuses loaded records with valid TAM coverage.
## Freeze the ICP definition
Write the account inclusion and exclusion rules before counting. Specify industry, company size, geography, business model, technology or operating conditions, and disqualifiers. Separate required filters from preferences and mark which filters can actually be measured by each source.
Define the unit of analysis. Count companies, not people, when estimating account TAM. Decide how subsidiaries, franchises, agencies, parent companies, and multi-brand groups are treated. Preserve one canonical domain per operating account and document exceptions.
## Estimate the account universe
Prefer a bottom-up count from a source capable of returning the matching companies. Record the source, query date, applied filters, omitted filters, caps, sampling, and estimated duplication. If the source exposes only a count, label the result as a count estimate rather than a verified account list.
Cross-check with a second method: industry registry, known-account sample, CRM classification, or another data source. Investigate large differences instead of averaging incompatible populations. A provider cap is a floor, not the size of the market.