ankit.kapoor /
← All work

Project 01

Growth strategy

Market Entry War Room

Where should we play?

A decision system that turns a business strategy into measurable assumptions, ranks US metropolitan markets using public data, and tests whether the recommendation survives different strategic priorities.

Status: PrototypeEvidence: Measured, partialA working demo runs. Results are reported by the evidence label.

Live-system schematic

Live-system schematic — the War Room after its built-in premium-fitness example was run on 14 September 2026. The visible ranking belongs only to that scenario and those weights; it is not a universal market recommendation.

Drawn wider than this screen — scroll the figure sideways, or read it in words below.

What this figure shows, in words
  • The left rail shows editable assumptions for market size, affluence, growth, customer fit, competition, and cost. Competition carries an entered weight but has no data, so the system redistributes that weight and shows a warning.
  • The main area states that Austin–Round Rock ranks first for this premium-fitness scenario, 0.3 points ahead of Raleigh–Cary. Dallas–Fort Worth appears third. These are the actual results of the built-in example inspected on 14 September 2026, not a general recommendation.
  • The selected market shows an attractiveness score of 90.5 and factor contributions from customer fit, market size, affluence, and growth. Cost is scored but unweighted in this scenario.
  • The raw-evidence area cites US Census ACS 2024 observations and explains that growth compares the 2024 and 2019 vintages, while residential gross rent is only a proxy for operating cost.

Original SVG redrawn faithfully from the running Market Entry War Room deployment and its public repository on 14 September 2026. It is labelled as a schematic, preserves the inspected scenario context, and is not a manipulated dashboard screenshot.

Growth strategy

System at a glance

The decision
A business wants to expand into a new US metropolitan market. Where should it open next, given its customer, price positioning, growth priorities, and cost tolerance?
Why it matters
Market-entry recommendations are often presented as point answers even though the result depends on assumptions about customer fit, growth, affordability, scale, and cost. The system makes those assumptions visible and lets the user see which ones are actually driving the decision.
The system
A decision system that turns a business strategy into measurable assumptions, ranks US metropolitan markets using public data, and tests whether the recommendation survives different strategic priorities.

How it works

  1. Describe the business and target customer.

  2. Translate the strategy into editable measurable assumptions.

  3. Score metropolitan markets using public data and explicit factor weights.

  4. Adjust priorities and compare candidate markets in the War Room.

  5. Perturb the assumptions through sensitivity analysis.

  6. Evaluate the ranking together with its robustness.

Decision output

A ranked set of metropolitan markets with factor-level explanations, direct comparisons, and evidence showing how robust each ranking is to plausible changes in strategic priorities.

Decision record

Evidence: Measured, partial

Decision
A business wants to expand into a new US metropolitan market. Where should it open next, given its customer, price positioning, growth priorities, and cost tolerance?
Position
No universal market recommendation. The system is designed to produce a scenario-specific ranking whose assumptions, factor contributions, missing data, and sensitivity can be inspected before anyone acts on it.
Evidence
Measured in part. The running system scores 393 metropolitan areas using configured 2024 and 2019 Census ACS vintages, explicit metric directions, percentile normalization, weighted factor scores, and Monte Carlo perturbation. The ranking is reproducible from the data and settings, but its commercial coverage is deliberately incomplete.
Trade-off
Transparency and consistency are prioritized over pretending to have perfect market data. Missing factors are dropped and their weights redistributed with a warning instead of being silently scored as zero.
Uncertainty
Competition coverage is absent, residential rent stands in for commercial occupancy cost, and the growth measure is a five-year change rather than a predictive market forecast.

Context and decision

Market-entry advice often arrives as a city name backed by a polished scorecard. The recommendation looks objective even when its result depends on unspoken judgments about who the customer is, how much they can pay, whether scale or growth matters more, and which costs the business can tolerate.

The War Room starts one level earlier. A user describes the business and target customer, then inspects the structured assumptions the parser produced before the model runs. That separation matters: AI helps interpret the description, while public data and deterministic scoring decide how each metro ranks.

The decision is not whether one metropolitan area is universally best. It is whether a candidate is attractive for this business under these priorities, why it reached that position, and whether the position survives a reasonable change in the assumptions.

Alternatives considered

  • Ask a language model which city to enter

    ForIt would be fast, flexible, and able to absorb a nuanced description of the business.

    AgainstIt is rejected as the decision engine because the recommendation would not be reconstructible from explicit evidence and arithmetic.

  • Use one fixed consulting-style scorecard

    ForA single scorecard is easy to communicate and keeps every market on one consistent scale.

    AgainstIt is rejected as the only interface because it hides how subjective weighting changes the answer and can make a fragile winner look definitive.

  • Add every possible commercial dataset

    ForMore sources could improve category-specific competition and operating-cost coverage.

    AgainstIt is rejected for the MVP because inconsistent proprietary coverage can create false precision and make the model harder to audit or reproduce.

Method and model

The running system uses the US Census American Community Survey at the metropolitan level. Its current configuration compares the 2024 ACS 1-year vintage with 2019, producing observations for market size, affluence, growth, customer fit, and a residential-rent proxy for cost.

Raw metrics are converted to percentiles across the metros in the run. Metrics whose lower values are preferable are inverted, metrics roll into factor scores, and the final attractiveness score is a weighted sum. The requested weights must sum to one; when a factor is unavailable, its weight is redistributed proportionally and the interface states that explicitly.

Sensitivity analysis perturbs the effective weights within a configured band, renormalizes them, and recomputes the ranking across repeated runs. This turns the finding from a single rank into a distribution: which markets stay near the top when the user's priorities move?

Evidence and results

The system is deployed and the full path from business description to assumptions, ranking, comparison, and sensitivity can be inspected. A built-in premium-fitness example currently scores all 393 loaded metros and exposes every factor contribution and raw observation behind the ordering.

That example is evidence that the workflow and arithmetic run, not a universal market conclusion. Changing the business, customer, or weights can change the ordering, which is the behavior the product is built to reveal rather than suppress.

The strongest current evidence is the sourced metro dataset, the deterministic score calculation, and the sensitivity mechanism. Evidence about category-level competition, actual commercial occupancy costs, or realized market-entry outcomes remains outside the MVP.

  • Census market dataset

    Measured, partialThe running system exposes 393 metro-level observations from the US Census ACS, with 2024 as the current configured vintage and 2019 as the comparison vintage. Each metric retains its source and vintage, and missing prior observations remain missing rather than becoming zero.

    Sources: src-market-entry-census, src-market-entry-demo

  • Explicit scoring model

    Measured, partialMetric direction, percentile normalization, within-factor aggregation, and user-visible factor weights produce the ranking deterministically. Unavailable factors are excluded and their weight is redistributed across the factors that remain.

    Sources: src-market-entry-readme, src-market-entry-demo

  • Sensitivity analysis

    Measured, partialMonte Carlo runs perturb the effective factor weights within a disclosed band, renormalize them, and report rank stability so the apparent leader is evaluated across plausible changes in priorities rather than at one point estimate.

    Sources: src-market-entry-readme

Interpretation

The most useful output is not 'Market X ranks first.' It is 'Market X ranks first under these assumptions, for these reasons, and remains near the top across this range of plausible assumption changes.'

That framing changes the conversation from defending one answer to examining what drives it. A weight that flips the ranking is not a nuisance; it identifies the strategic judgment the team actually needs to debate.

  • Trade-offTransparent coverage over false completeness

    The MVP drops competition when no comparable public measure exists. That narrows the answer, but it keeps the missing evidence visible instead of filling the gap with an opaque estimate.

  • Trade-offRelative ranks over absolute truth

    A percentile says where one metro stands against the others in this run. It does not say that a high-scoring market is intrinsically good or that the business will succeed there.

  • Trade-offEditable priorities over one official answer

    Allowing weights to move makes the judgment inspectable, but it also means the model cannot offer a context-free winner. The output is useful only with the scenario attached.

Limitations

Competition is unmeasured in the current MVP because no public source covers every business category consistently. The factor is dropped and its weight redistributed rather than scored as zero.

Median residential gross rent is used as a proxy for operating cost. It is not commercial lease data and should not be presented as such.

Growth is a multi-year historical delta between configured Census vintages, not a predictive market forecast. A high rank establishes fit under the model, not the probability of a successful launch.

  • OpenCategory-specific competition

    No broad public source covers competing establishments consistently across every business category, so competition is currently absent from the ranking and its weight is redistributed.

  • OpenOperating-cost proxy

    Median residential gross rent is available consistently, but it is only a proxy for commercial occupancy cost and may point in a different direction for a particular format.

  • OpenGrowth is historical

    The growth factor is the change between the 2019 and 2024 ACS vintages. It is not annualized and it is not a forecast of the next five years.

Next test

Add a bounded, category-specific competition source for one business type and test whether its inclusion materially changes the top tier without making coverage inconsistent across markets.

Run structured decision reviews with strategy practitioners: ask them to state a recommendation before and after sensitivity analysis, then record which assumption changes their conclusion and why.

Sources

  • src-market-entry-readme Market Entry War Room — public repository documentation

    Public repository documentation describing the strategy parser, scoring model, Census integration, factor weighting, missing-data handling, comparison workflow, and Monte Carlo sensitivity analysis.

  • src-market-entry-census US Census American Community Survey

    Metro-level ACS observations used by the running system. The inspected application and repository are configured for the 2024 ACS 1-year vintage with 2019 as the prior comparison vintage.

  • src-market-entry-demo Market Entry War Room — production deployment

    Running production deployment inspected on 14 September 2026 to verify the end-to-end workflow and the representative premium-fitness scenario used by the product schematic.

Authorship and review

Ankit's contribution
I framed the market-selection decision, specified how a business description becomes editable assumptions, designed the scoring and sensitivity workflow, and set the evidence and limitation rules that keep a scenario-specific result from being presented as a universal answer.
AI-assisted implementation
The application was implemented with AI coding assistance against an owner-authored specification. AI interprets the business description; Census observations, normalization, factor aggregation, ranking, and sensitivity are produced by deterministic code that can be inspected and tested.
Human review
No external review is claimed. This case is grounded in the public repository documentation and the running production workflow, and it preserves the limitations those sources disclose.
Status
A working demo runs. Results are reported by the evidence label.

Published . Last updated .