borghei/Claude-Skills / project-management/gtm/gtm-strategy
gtm-strategy
VerifiedBuilds and audits a go-to-market plan: beachhead, motion matched to ACV, funded channels, tested messaging, owned metrics and a T-90 launch sequence. Use when launching a product, entering a segment or fixing a stalled GTM.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.3 KB |
| assets/gtm_strategy_template.md | markdown | 3.4 KB |
| assets/sample_gtm.json | config | 1.8 KB |
| assets/sample_gtm_flawed.json | config | 580 B |
| references/gtm-anti-patterns.md | markdown | 6.4 KB |
| references/gtm-components-deep.md | markdown | 10.6 KB |
| references/launch-sequence-playbook.md | markdown | 6.0 KB |
| scripts/gtm_strategy_validator.py | script | 10.8 KB |
references/launch-sequence-playbook.md
View on GitHub# Launch Sequence Playbook
T-90 to T+90, role by role.
## T-90 — Lock the foundations
### PM
- ICP locked + documented
- Positioning v1
- Pricing + packaging finalized
- Feature scope locked for launch
- Roadmap post-launch sketched
### Marketing
- Launch theme / narrative
- Hero message + 3 supporting messages
- Channel strategy (which to invest)
- Content plan (blog, video, social)
- Analyst targets identified
### Sales
- Sales playbook outline
- Lighthouse customer targets
- Sales kickoff date booked
- Compensation plan updated for new offering
### CS
- Customer success playbook outline
- Onboarding flow
- Support training plan
### CEO
- Investor / board narrative
- Executive sponsorship for launch
- Major partnerships engaged
### Finance
- Launch budget approved
- Success metrics + targets
- Forecast model
## T-60 — Build the assets
### PM
- Demo scripts
- Customer feedback from beta
- Product-market fit signal review
- Documentation in user-facing channels
### Marketing
- Landing page live (gated)
- Press kit drafted
- Analyst briefings scheduled
- Influencer outreach started
- Webinar (if planned) scheduled
- Social calendar drafted
### Sales
- Sales deck v1
- Battle cards (vs alternatives)
- ROI calculator
- 1-pager + case-study skeletons
- Lighthouse customers signed up
### CS
- Onboarding sequence
- Customer training materials
- Health-check rubric
### Press / analysts
- Embargoed briefings
- Spokesperson prepped
## T-30 — Train + rehearse
### Internal
- Sales kickoff (full team)
- All-hands launch preview
- CS + support training
- Engineering on-call ready for spike
### External
- Lighthouse customers public-OK confirmed
- Analyst pre-briefings complete
- Press embargoes signed
- Pre-launch email to existing customers (heads-up)
## T-7 — Final prep
### All teams
- Final comms reviewed (legal sign-off)
- Launch dashboards live
- War-room set up
- Crisis comms drafted (in case of bad press)
- Backup plans (server capacity, etc.)
### Final list
- [ ] Press release approved
- [ ] Blog post scheduled
- [ ] Email queued
- [ ] Social posts queued
- [ ] Lighthouse customer quotes confirmed
- [ ] Sales team ready to take inquiries
- [ ] Support team ready for support tickets
- [ ] On-call eng ready for spike
- [ ] Analyst day-of contact info ready
## T-0 — Launch day
### Hour 0
- Press release goes live
- Blog post live
- Social posts go live
- Email goes out
- Sales team ready for inbound
- Support team ready
### Hours 1-8
- Monitor real-time:
- Site traffic
- Sales inquiries
- Support tickets
- Social mentions
- Press pickup
- Quick wins: re-share early positive press
- Address issues immediately
### End of day
- Daily standup with all teams
- Top issues triaged
- Next-day priorities set
## T+1 to T+7 — Triage + iterate
### Track
- Channel performance: which delivered?
- Customer questions: patterns?
- Sales early-stage: where are deals stalling?
- Demo conversion: requested vs converted?
- Lighthouse customer happiness: maintain trust
### Act
- Fix messaging that confuses
- Add FAQs to address common questions
- Adjust paid channel investment based on signal
- Push early wins (case studies, testimonials)
- Brief sales on common objections + responses
## T+30 — First learning wave
### Review
- Pipeline generated vs target
- Demo → opportunity → close rates (early signal)
- Customer satisfaction (new customers)
- Channel attribution
- Competitive response
### Adjust
- Messaging refinement based on what sticks
- Channel reallocation (double down what works; cut what doesn't)
- Sales playbook v2
- Pricing tweaks (rare; only if needed)
## T+90 — GTM v2
### Review
- Beachhead success metrics
- ICP refinement based on actual customers
- Motion economics (CAC payback, LTV/CAC)
- Channel mix optimization
- Sales rep performance + ramp curves
### Plan
- Next beachhead segment
- Expansion plan (geography / vertical / persona)
- GTM v2 with learnings incorporated
- Roadmap updates based on customer feedback
## Common launch failures
### "Launched into silence"
**Symptom:** Press release goes out; nobody notices.
**Cause:** No press relationships; no analyst briefings; no narrative.
**Fix:** PR / analyst engagement begins T-90 minimum.
### "Sales team unprepared"
**Symptom:** Inquiries come; sales doesn't know how to handle.
**Cause:** Sales kickoff was day-of; not weeks before.
**Fix:** Sales trained T-30; playbook + battle cards in hand.
### "Spike then silence"
**Symptom:** Launch day is huge; week 2 is nothing.
**Cause:** Launch was a moment, not a campaign.
**Fix:** Campaign continues T+30 with content, customer stories, integration partner activity.
### "Customer pile-up"
**Symptom:** Tons of signups; CS can't onboard them all.
**Cause:** Demand exceeded CS capacity.
**Fix:** Either gate signups or scale CS capacity pre-launch.
### "Press / analyst silence"
**Symptom:** No coverage from major outlets / analysts.
**Cause:** Embargoes were too tight; story didn't differentiate; relationships not built.
**Fix:** Start press / analyst relationships months in advance.
### "Launched the wrong message"
**Symptom:** Messaging doesn't resonate; bounce rate high; demos low.
**Cause:** Messaging wasn't customer-tested.
**Fix:** A/B test messaging T-30 with beta customers + paid traffic.
## Cadence per audience after launch
| Audience | Cadence |
|----------|---------|
| Customers (existing) | Email at T-7, T-0, T+30 |
| Prospects (in pipeline) | AE-led; weekly cadence |
| Press | T-30 embargoed; T-0 release; T+30 follow-ups |
| Analysts | T-30 pre-brief; T-0 brief; T+90 update |
| Partners | T-30 enablement; T-0 announce; T+30 reflection |
| Investors | T-7 heads-up; T+30 update; T+90 results |
| Internal | T-30 kickoff; T-0 launch; T+30 retro |
## Launch budget allocation (rough)
For a meaningful product launch:
- PR / analyst: 15-25%
- Paid acquisition (initial spike): 30-40%
- Content (case studies, video, blog): 15-20%
- Events (if any): 10-15%
- Sales enablement: 5-10%
- Tooling (dashboards, automation): 5-10%
Total often $200K-$2M depending on company stage + launch importance.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |