Initial ICP market audit

# Initial ICP Market Audit

## Goal

Use the completed ICP analysis in `docs/gtm/icp.md` and `docs/gtm/icp.yaml` to determine the real market for the selected initial ICP and beachhead.

Treat the ICP as a hypothesis to be measured, not a conclusion to be defended. Translate its operating conditions, painful job, prerequisites, triggering events, qualification signals and disqualifiers into a reproducible market definition.

Determine:

1. How many organizations plausibly experience the problem.
2. How many the currently implemented product can serve successfully.
3. How many are identifiable and reachable through a realistic initial sales motion.
4. How many are likely to enter an active buying window each year.
5. How many could realistically become activated and retained customers within 12, 24 and 36 months.
6. What customer expenditure or economic loss surrounds the problem.
7. What conditional vendor-revenue opportunity exists at defensible pricing scenarios.
8. Whether the market can support a repeatable business and at what scale.

Complete the analysis autonomously. Do not stop to ask clarifying questions. When exact evidence is unavailable, make the narrowest defensible estimate, show the calculation, label the uncertainty and state what evidence would resolve it.

Do not modify application code or overwrite the existing ICP files.

## Prerequisites and source inputs

Begin by reading all applicable `AGENTS.md` files and repository guidance.

Then read:

* `docs/gtm/icp.md`
* `docs/gtm/icp.yaml`
* every repository file cited as material evidence in those files
* locally available pricing, billing, usage, customer, support, interview, sales or financial evidence relevant to market analysis

If the ICP files do not yet exist, first execute the preceding codebase-to-ICP prompt in full.

Treat `icp.yaml` as the structured hypothesis and `icp.md` as its reasoning and evidence record. If they conflict, inspect the cited repository evidence and document the conflict rather than silently choosing one.

Extract:

* primary ICP
* beachhead ICP
* organization type
* operating state
* user
* champion
* economic buyer and approvers
* painful jobs
* triggering events
* current alternatives
* customer and product prerequisites
* qualification signals
* initial use case
* value metric
* retention mechanisms
* expansion paths
* disqualifiers
* YELLOW and RED segments
* assumptions, unknowns and falsification conditions
* ICP version, status and confidence

Do not broaden the ICP merely to produce a more attractive market estimate. Adjacent segments must be analyzed separately and excluded from the initial-ICP market total.

## External research

Use current web research extensively because the repository cannot establish external demand or population size.

Prefer sources in this order:

1. Government datasets, regulatory records, official registries and public procurement data.
2. Official company disclosures, filings, product pages, pricing pages and job postings.
3. Industry associations, accreditation bodies and professional directories.
4. Public datasets with documented methodology.
5. Reputable research institutions and trade publications.
6. Commercial datasets or market reports whose definitions and methods are visible.
7. Search-result counts, SEO pages and unsourced aggregations only as discovery aids.

For every external source record:

* title
* publisher
* URL
* publication date or data period
* retrieval date
* geography
* population definition
* exact input used
* limitations
* reliability

Do not cite search-result snippets as evidence. Do not substitute a broad analyst-defined software category for bottom-up market sizing.

Keep repository evidence, external market evidence and calculations separate so the ICP analysis does not become circular proof of market demand.

## Evidence standard

Label every material claim as:

* `REPOSITORY-PROVEN`: Directly established by implementation, documentation or repository data.
* `MARKET-OBSERVED`: Directly supported by a current external primary source, actual customer behavior or organization-level evidence.
* `DERIVED`: A reproducible calculation from cited inputs.
* `INFERRED`: Reasonably implied by multiple observations but not directly verified.
* `ASSUMED`: A necessary scenario input without sufficient direct evidence.
* `UNKNOWN`: Cannot currently be estimated responsibly.

A source proves only what it directly observes. For example, a job posting can prove that an organization is hiring for a workflow; it does not prove that the organization would buy this product.

Every quantitative input must specify:

* value or low/base/high range
* unit
* denominator
* geography
* time period
* source
* definition
* filters applied
* formula in which it is used
* confidence
* material overlaps or dependencies

Do not manufacture precision. When the evidence supports only an order-of-magnitude range, report that range.

If pricing is unvalidated, make account and workload counts the primary result. Label dollar estimates as `conditional revenue at assumed ACV`, not observed market demand.

## Step 1: Operationalize the ICP

Convert the primary and beachhead ICPs into explicit inclusion and exclusion predicates.

For every predicate identify:

* whether it is required, favorable or disqualifying
* whether it is stable or trigger-dependent
* whether it can be externally observed
* the best observable proxy
* the available data source
* expected false positives
* expected false negatives
* whether it can be applied at scale
* whether it has independent market evidence or only repository support

Distinguish:

* structural qualification: what the organization is
* operational qualification: how it currently performs the work
* problem qualification: whether the consequential pressure exists
* readiness qualification: whether it can adopt the current product
* economic qualification: whether the problem is large enough to fund
* trigger qualification: whether the need is active now
* reachability qualification: whether the buyer can be identified and accessed
* disqualification: what makes the organization unsuitable despite superficial fit

Define the unit being counted:

* parent organization
* subsidiary
* business unit
* location
* team
* practitioner
* workflow
* transaction

Select the unit that most closely corresponds to a purchasing decision. Explain how parent companies, subsidiaries, franchises, locations and shared-service teams will be treated to avoid double-counting.

If an important condition cannot be externally observed, label it hidden and define the narrowest defensible proxy.

## Step 2: Define the market layers

State the scope explicitly:

* product and initial use case
* current-product boundary
* organization and operating condition
* counting unit
* geography
* currency
* measurement date
* maturity requirements
* technical and integration prerequisites
* regulatory or language limitations
* economic buyer
* pricing unit
* whether demand is recurring, event-driven or both

Separate the market into these layers before mapping them to TAM, SAM and SOM:

1. **Structural universe**
   Organizations that meet the stable organizational and operational filters.

2. **Problem-bearing population**
   Structural-universe organizations that plausibly experience the consequential painful job at the required severity and frequency.

3. **Current-product serviceable market**
   Problem-bearing organizations that meet the prerequisites and can obtain value from the implemented product without substantial custom development or a different delivery model.

4. **Trigger-active annual market**
   Serviceable organizations currently experiencing an observable buying trigger or entering the relevant operating state during the year.

5. **Beachhead market**
   The narrower initial cohort selected in the ICP analysis.

6. **Reachable qualified market**
   Beachhead accounts whose qualification signals, champion or buyer can be identified through channels realistically available now.

7. **Obtainable market**
   Customers and revenue realistically winnable within 12, 24 and 36 months after accounting for sales capacity, conversion, implementation capacity, activation and retention.

8. **Adjacent market**
   YELLOW segments considered future options and excluded from all core totals.

Distinguish the installed base from the annual flow of newly triggered organizations. Estimate how long a trigger remains active so accounts are not treated as permanently in-market.

Use TAM, SAM and SOM only after defining the corresponding plain-language layer. State the exact definition used for each acronym.

## Step 3: Build a bottom-up account census

Find the best available enumerations of organizations that could satisfy the ICP.

Possible sources include:

* official business statistics
* licensing and accreditation lists
* regulatory databases
* industry directories
* technology-installation data
* integration marketplaces
* public customer and partner directories
* job postings
* public procurement notices
* company filings
* association memberships
* operational or compliance records
* conference exhibitor lists

For every enumeration determine:

* what population it covers
* whether it counts organizations, establishments, teams or people
* how closely it matches the ICP
* necessary filters
* recency
* geographic coverage
* duplicate risk
* likely omissions

Prefer a direct account census:

`N_serviceable = Σ I(org type AND operating state AND painful job AND prerequisites AND current-product fit AND NOT disqualified)`

Where a census is unavailable, use a transparent prevalence model:

`N_serviceable = N_base × p_operating_state × p_pain_threshold × p_prerequisites × p_product_fit`

Do not assume these probabilities are independent. Use joint observations where available and show low/base/high scenarios where overlap is uncertain.

Where sampling is required:

* define the sampling frame
* explain the selection method
* inspect a sufficiently large sample
* calculate the observed qualification rate
* show the extrapolation
* quantify uncertainty
* discuss selection and coverage bias

Attempt at least two independent account-sizing approaches. Reconcile disagreements through definitions and evidence; do not average incompatible estimates.

## Step 4: Build the prospect universe

Create an evidence-backed list of testable organizations.

Include at least 25 organizations when 25 defensible candidates exist. If fewer than 25 survive the filters, enumerate the smaller universe and treat the inability to find 25 as potentially falsifying evidence. Never loosen the ICP or pad the list.

For every organization record:

* organization name
* parent organization
* website
* geography
* counted purchasing unit
* structural qualification evidence
* operating-state evidence
* prerequisite evidence
* observable trigger
* current alternative, if observable
* likely champion role
* likely economic-buyer role
* supporting source URLs
* source dates
* confidence
* missing evidence
* possible disqualifiers
* recommended tier
* concise rationale

Use roles rather than inventing individual contacts.

Classify organizations as:

* `TIER 1`: Multiple strong qualification signals and a visible trigger.
* `TIER 2`: Strong structural fit, but trigger or readiness remains unverified.
* `WATCH`: Potential future fit with a specific missing condition.
* `EXCLUDED`: Superficial fit but a known disqualifier or missing prerequisite.

A publicly qualified organization is a testable prospect, not a validated customer.

Deduplicate parents, subsidiaries and operating units using the selected counting rule. Report what portion of the estimated market the named list covers.

## Step 5: Measure demand and the economic pool

Determine what the market currently does about the painful job.

Measure, where evidence permits:

* internal labor devoted to the workflow
* software expenditure
* services, agencies or consulting expenditure
* additional hiring
* delay cost
* error or compliance cost
* expected risk loss
* missed-revenue or conversion cost
* workflow frequency and volume
* cost of doing nothing
* switching and implementation cost
* buyer and budget ownership
* whether the budget already exists or must be created
* whether the economic benefit accrues to the buyer’s department

Rank demand evidence in this order:

1. Repeated purchases, renewals, realized outcomes and expansion.
2. Paid pilots involving real workflows or data.
3. Existing recurring expenditure on competitors, contractors, labor or a defined workaround.
4. Active procurement, hiring, migration, compliance or other trigger behavior.
5. Credible reports of repeated pain or active solution search.
6. Search volume, clicks, survey interest and hypothetical willingness to pay.

Lower-ranked signals may support a hypothesis but must not establish demand.

Keep these quantities separate:

* customer economic loss or opportunity
* value the product could create
* value that can be credibly measured
* existing addressable expenditure
* available departmental budget
* willingness to pay
* plausible vendor price
* conditional vendor-revenue pool

A value ceiling may be estimated as:

`annual customer value = labor avoided + incremental gross profit + expected risk loss avoided − incremental operating cost`

Do not present that value ceiling as willingness to pay.

## Step 6: Analyze competitors and the status quo

Map every meaningful way the customer currently handles the economic job:

* direct software competitors
* adjacent products
* incumbent platforms
* internal software
* spreadsheets and manual operations
* agencies and consultants
* outsourcing
* additional hiring
* avoidance or doing nothing

For each alternative determine:

* target customer
* economic job
* user and buyer
* delivery model
* public pricing or pricing basis
* implementation requirements
* strengths
* weaknesses
* switching cost
* why customers choose it
* why customers abandon or supplement it
* overlap with the implemented product
* budget line
* adoption evidence
* source and retrieval date

Determine:

* whether an established purchasing category exists
* which budget funds the work today
* whether the product replaces, consolidates or creates a budget
* whether an incumbent can bundle the capability
* whether internal construction is economically rational
* where the current product has a defensible wedge
* where it is inferior
* whether the market is crowded, fragmented, emerging or category-less
* whether apparent whitespace indicates opportunity or absence of demand

Competitor existence is not itself proof of demand. Look for expenditure, adoption, retention and switching behavior.

## Step 7: Calculate the market

Use at least two and preferably three sizing methods:

1. **Account method**
   Qualifying purchasing units × plausible annual contract value.

2. **Workflow method**
   Annual addressable workflow volume × price or value captured per workflow.

3. **Status-quo expenditure method**
   Relevant current labor, software, service or failure cost × realistically replaceable share × plausible vendor capture rate.

If pricing is not validated, use low/base/high scenarios and label their basis as:

* repository-observed
* customer-observed
* competitor-benchmarked
* value-derived
* assumed

For an event-driven market calculate:

`annual triggered accounts = eligible installed base × annual trigger incidence + new eligible entrants`

For an account-priced product calculate:

`conditional ARR pool = serviceable accounts × assumed sustainable ACV`

For a usage-priced product calculate:

`conditional ARR pool = accounts × addressable units per account × assumed price per unit`

Do not add account, seat, workflow and usage estimates together as separate markets.

Calculate:

* structural account universe
* problem-bearing account universe
* current-product serviceable accounts
* annual trigger-active accounts
* primary-ICP account and conditional-revenue range
* beachhead account and conditional-revenue range
* reachable account and conditional-revenue range
* 12-, 24- and 36-month capacity-constrained SOM
* geographic and customer concentration
* recurring versus one-time revenue opportunity

Do not calculate SOM as an arbitrary percentage of TAM.

Use:

`new customers_t = min(reachable accounts remaining, funnel output_t, onboarding capacity_t)`

Where:

`funnel output = valid accounts contacted × response rate × qualification rate × pilot rate × pilot-success rate × paid-conversion rate`

And:

`exit ARR_t = active retained customers_t × ACV_t`

Include sales-cycle length, activation, churn, expansion and implementation capacity. Label unsupported funnel inputs `ASSUMED` or `UNKNOWN`.

Perform sensitivity analysis on the three inputs that most affect the conclusion. Show their break-even values.

Calculate the retained customers and market penetration required to reach:

* $1 million ARR
* $5 million ARR
* $10 million ARR
* $25 million ARR
* $100 million ARR

State whether the evidence supports a small profitable niche, a substantial independent business, a venture-scale opportunity or no commercially credible market. Do not force a large-market conclusion.

## Step 8: Identify the strongest market-entry cohort

Divide the primary ICP into three to five operationally meaningful subsegments that remain inside the ICP.

Differentiate them using factors such as:

* trigger intensity
* workflow volume
* present expenditure
* implementation readiness
* regulatory exposure
* organizational ownership
* buyer accessibility
* current alternative
* concentration in observable channels

Do not create superficial variations based only on geography or headcount.

For each subsegment provide:

* definition
* estimated account count
* annual trigger incidence
* current alternative
* buyer and budget
* plausible pricing basis
* time to value
* implementation burden
* retention mechanism
* discoverability
* channel concentration
* evidence
* unknowns

Score each from 1–5 on:

* problem severity
* problem frequency
* trigger visibility
* current expenditure
* implemented-product fit
* buyer clarity
* buyer reachability
* time to value
* activation likelihood
* retention potential
* expansion potential
* implementation burden
* support burden
* competitive intensity
* prospect density
* evidence strength

Explain every score and select the strongest initial market-entry cohort.

## Step 9: Determine reachability

Identify practical routes to the market:

* professional associations
* role-specific communities
* conferences
* industry publications
* software ecosystems
* consultants and implementation partners
* public procurement systems
* job-posting searches
* regulatory or funding announcements
* relevant directories
* targeted outbound
* founder-led content
* referrals
* channel partnerships

For every route evaluate:

* concentration of ICP accounts
* concentration of champions and buyers
* accessibility
* signal quality
* false-positive risk
* expected sales motion
* trust requirement
* repeatability
* evidence needed to validate the route

Identify the five strongest observable prospecting signals and provide a reproducible method for finding each.

Do not equate discoverability with demand.

## Step 10: Attempt to falsify the market

Challenge every major market assumption:

* Is the ICP operating condition too rare?
* Are public qualification proxies dominated by false positives?
* Is the problem expensive or merely annoying?
* Does the likely buyer control the resulting economic benefit?
* Does the trigger actually cause purchasing behavior?
* Is the existing workaround sufficient?
* Is expenditure fragmented across departments?
* Can an incumbent bundle the capability?
* Is the opportunity actually consulting rather than repeatable software?
* Is plausible ACV too low relative to sales and implementation cost?
* Are too few organizations newly triggered each year?
* Would success require implausible market penetration?
* Does value disappear after the immediate triggering event?
* Does the named prospect universe survive manual inspection?
* Could the estimate reasonably be wrong by more than 2×?
* Would current-product limitations exclude most apparent prospects?

For every major hypothesis provide:

* supporting evidence
* strongest counterargument
* confirmation evidence
* falsification evidence
* consequence if false

Preserve contradictions between market evidence and the original ICP. Do not silently broaden or rewrite the ICP.

## Step 11: Produce a market-validation plan

Identify what desk research cannot establish.

For every important unknown provide:

* why it matters
* current evidence
* fastest validation method
* target sample
* confirmation threshold
* falsification threshold
* decision if confirmed
* decision if falsified

Include:

1. **Census-validation sprint**
   Manually audit a representative prospect sample and measure false-positive and false-negative rates.

2. **Buyer interviews**
   Focus on actual recent behavior, current expenditure, workarounds, failed attempts, triggers and budget ownership.

3. **Workflow-access test**
   Ask qualified organizations to supply real data, workflow access or a representative case.

4. **Commitment-bearing pilot**
   Use the smallest offer from the ICP analysis. Prefer payment, signed participation, workflow access, implementation effort and decision-maker involvement over stated enthusiasm.

5. **Proof-of-value test**
   Measure the ICP value metric against a baseline within a defined period.

6. **Repeatability test**
   Deliver the same offer across multiple organizations without material customization.

7. **Retention test**
   Determine whether usage and economic value continue beyond the triggering event.

Define evidence that would:

* confirm or reduce the account estimate
* validate or invalidate the pricing range
* confirm the trigger-to-purchase relationship
* promote a subsegment into the beachhead
* remove a subsegment
* demote the primary ICP to YELLOW or RED
* justify investigating an adjacent ICP

Do not use compliments, survey enthusiasm, clicks, waitlist signups or hypothetical willingness to pay as primary validation.

## Step 12: Make the market decision

Conclude with one of:

* `PURSUE`: Evidence supports a sufficiently dense, reachable and economically meaningful initial market.
* `PURSUE CONDITIONALLY`: The market appears plausible, but named validation gates must be passed before substantial investment.
* `NARROW OR REPOSITION`: Demand exists, but the selected ICP, offer or product boundary is misaligned with the economic pool.
* `DO NOT PURSUE`: Account count, economics, reachability, competition or implementation burden does not support a repeatable business.

Lead with this sentence:

“As of [date], within [geography], an estimated [low/base/high account count] organizations fit the current-product ICP, approximately [annual trigger-active range] enter an active buying window annually, and at [pricing basis or ACV range] this represents [conditional revenue range], with [confidence] confidence.”

Then explain the decision using:

* qualifying account count
* annual trigger flow
* plausible pricing basis
* current-product serviceability
* beachhead density
* reachability
* status-quo expenditure
* competitive pressure
* activation and retention logic
* implementation burden
* market penetration required at target ARR levels
* most dangerous unknown

If evidence is insufficient, return `PURSUE CONDITIONALLY`. Do not manufacture certainty.

## Deliverables

Create the following files:

### 1. `docs/gtm/market.md`

Include:

* executive market conclusion
* source ICP and version
* ICP conflicts or revision implications
* operational market definition
* inclusion, proxy and exclusion rules
* counting unit
* source and methodology ledger
* bottom-up account census
* market layers
* low/base/high estimates
* sizing formulas and calculations
* TAM, SAM and capacity-constrained SOM
* annual trigger flow
* economic-pool analysis
* pricing scenarios
* ARR penetration requirements
* sensitivity analysis
* market-entry subsegments and scoring
* competitors and status quo
* buyer and budget analysis
* channel and reachability analysis
* prospect-universe summary
* falsification analysis
* major unknowns
* validation plan
* final decision

### 2. `docs/gtm/market.yaml`

Use a valid machine-readable structure containing:

* `version`
* `status`
* `as_of_date`
* `source_icp`
* `confidence`
* `decision`
* `scope`
* `primary_icp`
* `beachhead_icp`
* `counting_unit`
* `eligibility`
* `observable_proxies`
* `hidden_conditions`
* `exclusions`
* `market_layers`
* `demand_evidence`
* `account_estimates`
* `annual_trigger_flow`
* `pricing`
* `economic_value_model`
* `account_sizing_model`
* `workflow_sizing_model`
* `status_quo_sizing_model`
* `tam`
* `sam`
* `beachhead_market`
* `reachable_market`
* `som_12_month`
* `som_24_month`
* `som_36_month`
* `arr_penetration_requirements`
* `subsegments`
* `selected_entry_segment`
* `buyers`
* `budget_sources`
* `competitors`
* `status_quo_options`
* `market_access_channels`
* `assumptions`
* `unknowns`
* `sensitivity`
* `sources`
* `validation_experiments`
* `confirmation_conditions`
* `falsification_conditions`

Use `status: hypothesis` unless actual purchases, outcomes, retention and expansion justify a stronger status. Represent unknown values as `null` with an explanation instead of inventing data.

### 3. `docs/gtm/prospect-universe.csv`

Use these columns:

* `organization_name`
* `parent_organization`
* `website`
* `geography`
* `purchasing_unit`
* `subsegment`
* `structural_fit_evidence`
* `operating_state_evidence`
* `prerequisite_evidence`
* `observable_trigger`
* `current_alternative`
* `champion_role`
* `economic_buyer_role`
* `source_urls`
* `source_dates`
* `qualification_confidence`
* `missing_evidence`
* `disqualification_risk`
* `tier`
* `rationale`

Use one row per purchasing unit. Keep sources directly traceable.

## Boundaries

* Do not modify application code.
* Do not overwrite `docs/gtm/icp.md` or `docs/gtm/icp.yaml`.
* Do not treat claims inherited from the repository-derived ICP as independent market validation.
* Do not silently broaden or redefine the ICP.
* Do not include YELLOW, RED or future-product segments in current market totals.
* Do not use an entire industry or software category as TAM.
* Do not treat industry membership as sufficient qualification.
* Do not invent organizations, signals, budgets, prices, conversion rates or demand.
* Do not confuse economic value, addressable expenditure, willingness to pay and vendor revenue.
* Do not calculate SOM as an arbitrary percentage of TAM.
* Do not mix incompatible years, geographies, denominators or counting units.
* Do not assume conditional filters are independent.
* Do not double-count parents, subsidiaries, locations or overlapping classifications.
* Do not treat funding, hiring, search volume or social attention as purchase demand unless directly tied to the painful job.
* Do not treat the prospect list as proof that its organizations will buy.
* Do not confuse a temporary trigger with recurring demand.
* Do not ignore procurement cycles, switching costs, activation, retention, support burden or onboarding capacity.
* Do not loosen the ICP to manufacture 25 prospects.
* Preserve uncertainty instead of manufacturing confidence.

## Done when

* The original ICP and its evidence have been reviewed.
* Every ICP condition is measurable, proxied or explicitly marked hidden.
* Counting unit, geography, currency, product boundary and time horizon are explicit.
* Primary ICP, beachhead, adjacent segments and exclusions remain separate.
* The market has been estimated bottom-up using at least two independent methods.
* Population size and demand evidence are analyzed separately.
* Structural, problem-bearing, serviceable, trigger-active, beachhead, reachable and obtainable markets are distinguished.
* Every number is traceable to sources, assumptions and formulas.
* Low/base/high estimates are provided.
* The three highest-sensitivity variables and their break-even values are shown.
* The required penetration for $1M, $5M, $10M, $25M and $100M ARR is calculated.
* At least three internal market-entry subsegments have been compared.
* Competitors, indirect alternatives and doing nothing have been analyzed.
* At least 25 defensible testable organizations are documented, or failure to find them is treated as evidence against the hypothesis.
* SOM is constrained by the actual sales motion, implementation capacity, activation and retention.
* A commitment-based validation plan is complete.
* The final market decision is explicit.
* All three deliverables are internally consistent.