heyparsadev/claude-venture-plugin / venture/skills/gtm
gtm
VerifiedThis skill should be used when the user asks for go-to-market strategy, positioning, launch planning, channel strategy, pricing strategy, or messaging — e.g. "build a GTM strategy", "how should we launch", "which channels should we use", "positioning for my product", "pricing strategy", "استراتژی ورود به بازار", "گوتومارکت", "پلن لانچ", "از چه کانالی مشتری بیاریم", "قیمتگذاری", "پوزیشنینگ". Produces a positioning canvas, messaging house, channel plan, pricing strategy, and launch plan in the venture workspace.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| references/channel-playbook.md | markdown | 2.5 KB |
| references/launch-checklist.md | markdown | 1.8 KB |
| references/messaging-house.md | markdown | 1.5 KB |
| references/positioning-canvas.md | markdown | 1.6 KB |
references/channel-playbook.md
View on GitHub# Channel Playbook — Bullseye Selection
## Channel menu (brainstorm across ALL before narrowing)
| Channel | Works best when | Watch out |
|---|---|---|
| Founder-led outbound (DM/email/calls) | B2B, price >$1k/yr, identifiable ICP | doesn't scale past founder; that's fine early |
| SEO / content | problem is actively searched; 6–12mo patience | slow signal; check search volume first |
| Paid search | high-intent queries exist; price supports CAC | bid costs vs LTV; needs landing page + tracking |
| Paid social (IG/TikTok/local equivalents) | visual/consumer; impulse-friendly price | creative treadmill; weak for niche B2B |
| Marketplaces & app stores | category browsed there (apps, plugins, templates) | platform tax + ranking dependence |
| Partnerships / resellers | partner already owns your ICP's trust | slow to start; revenue share |
| Communities & social proof (forums, Telegram/LinkedIn groups, local associations) | tight-knit ICP that talks to itself | give-before-ask; ban risk for spam |
| Events / webinars / local meetups | high-touch B2B; local-market trust building | time-expensive per lead |
| Referral / viral loops | product is visible or collaborative by nature | needs existing happy users — not a cold-start channel |
| PR / launch platforms (Product Hunt, local tech media) | novelty story; one-time spike | spike ≠ channel; harvest emails from it |
Local-market note: map to local equivalents (Iran: Telegram channels/groups, Instagram, Cafe Bazaar/Myket, اتحادیهها و انجمنهای صنفی, local tech media like Digiato/Zoomit).
## Scoring (fill for every plausible channel)
| Channel | ICP density (1–5) | Expected CAC vs price (1–5) | Speed to signal (1–5) | Founder fit (1–5) | Total |
|---|---|---|---|---|---|
Pick **1–2 core + 1 experimental**. Spreading across 5 channels = learning nothing about any.
## Experiment card (one per chosen channel)
```markdown
### Channel: <name>
- Hypothesis: <ICP X is reachable here at CAC ≤ Y>
- First experiment: <concrete: "50 personalized DMs to clinic owners in Tehran via Instagram, message variant A/B">
- Budget cap: <money + hours>
- Success metric: <e.g. ≥10% reply, ≥2 demos booked>
- Kill criterion: <e.g. <2% reply after 100 sends → stop, write down why>
- Review date: <+2–4 weeks>
```
## Economics sanity check
CAC ceiling ≈ first-year gross profit per customer (early stage). Channel can't plausibly hit that → don't pick it, note why. Mark every CAC figure as estimate (confidence) until real data replaces it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |