---
name: gtm-map
description: Map a product onto a funnel you can actually measure and call the B2C/B2B fork. Use when the go-to-market plan feels shapeless.
---

Build the user's GTM map. Work from what they actually have, not what a template says they should have.

1. **Read the product.** Look at the repo, the site, the README — whatever exists. Do not ask them to describe it if you can read it.
2. **Sketch the funnel.** Propose the stages that apply to them specifically. B2C tends toward Awareness → Interest → Activation → Revenue → Retention → Referral; B2B toward Awareness → Interest → Evaluation → Decision → Onboarding → Expansion. Pick one and say why.
3. **Mark what's measurable today.** For each stage: is there a number available right now, a number obtainable this week, or nothing? Be blunt about the nothings — those are the gaps that matter.
4. **Call the fork.** B2C or B2B, with reasoning based on who signs, who pays, and how long they take. If it's genuinely ambiguous, say so and name the test that would settle it.
5. **Write it to `01-roadmap/gtm-map.md`** as a short doc: funnel stages, measurable/not, fork call, and the three things to fix first.

Push back if the funnel has stages they'll never measure. A four-stage funnel with real numbers beats a six-stage one that's decoration.