tam-and-sourcinglisted

# TAM and Sourcing Turn a market definition into a deduplicated, sized, prioritized universe. Sizing first, pulling second, and never the reverse. ## When to use - Standing up a program and nobody knows how many accounts exist - A segment expansion decision needs a denominator - The current list is too small to hit a pipeline number and you need to know whether more exist - Territory planning ## Inputs - Reads: `workspace/data/object-model.md`, `workspace/data/suppression.csv` (both required) - Needs from user: the segment definition in firmographic terms, geography, the exclusions, and the current account list **Do not run this without the object model.** Sourcing into an undefined model produces a universe you cannot dedup. ## Workflow ### 1. Write the segment definition as filters Vague segment definitions produce unusable universes. Convert prose into filters. "Mid-market SaaS in North America" is not a definition. This is: ``` Industry: <specific codes or categories, listed> Employee count: <range> Revenue: <range, or a proxy> Geography: <countries, or regions> Business model: <B2B, subscription, etc.> Technology: <required stack signals, if any> Excluded: <competitors, resellers, staffing, agencies, franchises> ``` If a filter cannot be expressed as a field, it is a qualification criterion for later, not a sourcing filter. Note it and move on. ### 2. Probe the size before pulling anything Run a count-only query first. Sizin