← ClaudeAtlas

market-gap-micrositelisted

Recruitment pipeline — turn foot-traffic / market data into a market-gap analysis map and a branded recruitment microsite that shows a target brand its footprint, your market's gap, and demand proof. Use when the user wants to pitch a new retail/restaurant brand, work with trade-area data, or update the gap-analysis template.
DanielOnPurpose/danielonpurpose-skills · ★ 0 · Data & Documents · score 57
Install: claude install-skill DanielOnPurpose/danielonpurpose-skills
# Market-Gap Microsite Pipeline A recruitment pipeline: show a target brand its regional footprint, your market's gap, and the anchor-demand proof that the catchment is real. ## The building blocks - A **template** map + guide (edit only a clearly marked BRAND DATA section of the HTML). - One **worked example** folder to clone from. - Trade-area **source data** (foot-traffic reports, visit counts). - A **target note** per brand. ## Design rules (hard-won — never break) 1. **No straight-line distance rings.** They never match road-mile labels and discredit the map. Show distance as connecting lines + a sidebar instead. 2. **Road miles + drive times everywhere**, never straight-line distance. 3. **Keep a constant anchor** (e.g. a major retailer) across brands — it's the proof the catchment is real. Only the brand's locations and projection change per pitch. 4. The map must show **region-wide location density** so the gap is visually obvious — a zoomed-in map that hides the pattern misses the point. 5. Verify pin alignment and the anchor cross-reference data before showing anyone. 6. Keep the map a **single static HTML file** (no framework/build) so it drops into any microsite. 7. A star icon marks your target location. ## Pipeline steps 1. **Ingest** the brand's trade-area report(s) → extract locations, visit counts, catchment data. 2. **Clone** the template to a new brand folder; fill the BRAND DATA section per the guide. 3. **Verify** the map locally (serve over HTTP,