mi-size-tam-sam-somlisted

# TAM, SAM, and SOM ## Purpose Build a market size that survives contact with finance. Bottom-up, cited, and expressed in **both currency and number of customers** — because the customer count is what exposes an unbelievable model fastest. A $400M SOM sounds fine until it implies signing eleven hundred customers in three years with a sales team of nine. The **sensitivity is the deliverable**. The point estimate is decoration. Business cases do not die because a number was wrong; they die because nobody could say what would have to be true for it to be right. This skill consumes a denominator and a capture rate. Where an input has no source, the honest entry is **"no evidence found"** and the layer it feeds is not computed. ## When to Use It Use it before a business case meets finance, before an entry decision, and whenever a sizing number is being quoted that nobody can trace. Do not use it when: - **You do not have a denominator.** Run `mi-collect-geoint-demoint` first. Sizing without a count of the eligible population is arithmetic on a guess. - **You do not have a capture-rate basis.** Run `mi-collect-finint` on a comparable — revenue over claimed customer count is a deal-size reality check that optimism cannot supply. - **The category is too new to be counted.** Say so, size against the nearest adjacent code with the substitution declared, and label the whole model an Assumption. - **The question is where to grow rather than how big it is.** That is `mi-analyze-a