Step 2 of 3
The regional map.
A regional map answers a planning question: in which applications and regions are the products your line could go into, and where is the incumbent displaceable? It is built bottom-up from screened product records, not top-down from market-size reports.
It uses the screen's records. A map without a screen underneath it would be a list of company names, which is what you already have.
Products first, then regions.
Each screened product carries its maker and the maker's location. Records are aggregated by application class and region: how many products, which routes they took, which incumbents appear in the evidence, and where the review queue is deepest.
- Named products and their makers
- Shortlist, exclusion and review counts
- Incumbent parts seen in the evidence, with the source
Volumes and revenue are estimates, and say so.
Public documentation rarely states volumes. Where a figure is given it is derived from what is public and from your own knowledge of the application, and it is labelled as an estimate with its basis. It is there to support a decision, not to be quoted as a fact.
- Every estimate carries its basis
- Facts and estimates are kept apart in the record
- A region with many unknowns is shown as such, not smoothed over
Where to enter, and where to send the field team.
Which applications and regions hold enough products your line could serve to be worth entering. Where a distributor or representative would need a brief. Where displacement is plausible because the incumbent appears often in the evidence.
A region with many fitting products is a technical finding. Whether any of them is deciding now is a timing question, and it is answered per product, only from evidence.
Next steps.
- Start with a screen; the map is built from its records
- Add application classes or regions in later runs
- The subscription keeps the map current
The service · Step 1: the screen · Step 3: the subscription · How the system works
Discuss the regions you are weighing