GTM Strategy
Position in workflow: v0.8 Monitoring Setup → v0.9 GTM Strategy → v0.9 Launch Metrics
Purpose
Define how the product reaches its target users—the channels, messaging, timing, and coordination required for a successful launch.
Core Concept: Launch as Campaign
A launch is not "making the product available." It is a coordinated campaign that creates awareness, drives activation, and captures feedback. Every touchpoint should move users toward value.
GTM Components
| Component |
Purpose |
Output |
| Messaging |
What we say |
GTM- (value props, headlines) |
| Channels |
Where we say it |
GTM- (channel strategy) |
| Timing |
When we launch |
GTM- (timeline, phases) |
| Coordination |
Who does what |
GTM- (RACI, tasks) |
Execution
Review target personas
- Pull PER- from v0.4
- Understand where they spend time
- Know what messages resonate
Define core messaging
- Value proposition (from CFD- value hypotheses)
- Positioning (from BR- product type)
- Key differentiators (from v0.2 competitive landscape)
Select launch channels
- Match channels to personas
- Prioritize by reach and conversion potential
- Consider owned, earned, and paid media
Plan launch timeline
- Pre-launch: Build anticipation
- Launch day: Maximum impact
- Post-launch: Sustain momentum
Assign ownership
- Who creates content?
- Who monitors channels?
- Who handles support surge?
Create GTM- entries with full traceability
GTM- Output Template
GTM-XXX: [GTM Item Title]
Type: [Messaging | Channel | Timeline | Task | Asset]
Owner: [Person or team responsible]
Status: [Planned | In Progress | Ready | Live]
For Messaging Type:
Audience: [PER-XXX targeted]
Format: [Headline | Value Prop | Tagline | Elevator Pitch]
Message: [The actual copy]
Supporting Evidence: [CFD-XXX value hypothesis it's based on]
Where Used: [GTM-YYY channels, assets]
For Channel Type:
Channel: [Specific platform or medium]
Audience Fit: [Why this channel reaches PER-XXX]
Strategy: [How we'll use this channel]
Content Plan: [What content goes here]
Success Metric: [How we measure effectiveness]
Linked Assets: [GTM-YYY assets for this channel]
For Timeline Type:
Phase: [Pre-launch | Launch Day | Week 1 | Month 1]
Date: [Specific date or relative timing]
Activities: [What happens in this phase]
Dependencies: [What must be ready]
Milestones: [Key checkpoints]
For Task Type:
Task: [What needs to be done]
Owner: [Who is responsible]
Due: [When it's due]
Dependency: [What it depends on]
Deliverable: [What's produced]
For Asset Type:
Asset: [What this is — landing page, email, video]
Purpose: [What it accomplishes]
Channel: [GTM-YYY where it's used]
Copy: [GTM-YYY messaging used]
Status: [Draft | Review | Approved | Live]
Linked IDs: [PER-XXX, CFD-XXX, KPI-XXX related]
Example GTM- entries:
GTM-001: Primary Value Proposition
Type: Messaging
Owner: Product Marketing
Status: Ready
Audience: PER-001 (Startup Founder)
Format: Value Prop
Message: "Ship faster with AI that understands your codebase.
Context-aware coding assistance that reduces debugging
time by 40%."
Supporting Evidence: CFD-010 (time savings validated in interviews)
Where Used: GTM-005 (Landing Page), GTM-010 (Product Hunt)
Linked IDs: PER-001, CFD-010, KPI-001
GTM-002: Product Hunt Launch
Type: Channel
Owner: Growth Team
Status: Planned
Channel: Product Hunt
Audience Fit: PER-001 (Startup Founder) frequents PH for tools
Strategy:
- Launch on Tuesday 12:01 AM PT
- Engage with comments first 24 hours
- Share maker story
- Prepare demo video
Content Plan:
- Tagline: GTM-001 (Primary Value Prop)
- Maker comment: GTM-003 (Founder Story)
- Demo video: GTM-006 (Product Demo)
Success Metric: Top 5 product of the day, 500+ upvotes
Linked IDs: PER-001, GTM-001, GTM-003, GTM-006, KPI-005
GTM-003: Launch Week Timeline
Type: Timeline
Owner: Launch Coordinator
Status: Planned
Phase: Launch Week
Day -7 (Pre-launch):
- [ ] Email list teaser
- [ ] Social media hints
- [ ] Press outreach
Day -1:
- [ ] Final staging verification
- [ ] Launch assets approved
- [ ] Team roles confirmed
Day 0 (Launch):
- [ ] Product Hunt live at 12:01 AM PT
- [ ] Social media posts scheduled
- [ ] Email to waitlist
- [ ] Monitor and engage
Day 1-3:
- [ ] Respond to all feedback
- [ ] Fix any critical issues
- [ ] Share early wins
Day 4-7:
- [ ] Publish case study
- [ ] Analyze metrics
- [ ] Plan iteration
Dependencies: DEP- release criteria met, MON- monitoring active
Milestones: 1000 signups (Day 3), First paying customer (Day 7)
Linked IDs: DEP-002, MON-005, KPI-001
GTM-004: Landing Page Hero Section
Type: Asset
Owner: Design + Marketing
Status: In Progress
Asset: Landing page hero section
Purpose: Convert visitors to signups
Channel: GTM-007 (Website), GTM-002 (Product Hunt referrals)
Copy: GTM-001 (Primary Value Prop)
Status: Review
Components:
- Headline: "Ship faster with AI that understands your codebase"
- Subhead: "Context-aware coding assistance that reduces
debugging time by 40%"
- CTA: "Start Free Trial" → /signup
- Social proof: "Trusted by 500+ developers"
- Demo video thumbnail: GTM-006
Linked IDs: GTM-001, GTM-006, SCR-001
Channel Selection Framework
Match channels to product type (from v0.2 BR-):
| Product Type |
Primary Channels |
Strategy |
| Fast Follow |
SEO, Paid, Aggregators |
"We're the better [competitor]" |
| Slice |
Community, Integrations, Partnerships |
"Best [thing] for [ecosystem]" |
| Innovation |
Content, PR, Events |
"Here's why this matters" |
Channel Categories
| Category |
Examples |
Best For |
| Owned |
Website, Blog, Email, Product |
Control message, build audience |
| Earned |
PR, Reviews, Word-of-mouth |
Credibility, reach |
| Paid |
Ads, Sponsorships, Influencers |
Scale, targeting |
| Community |
Forums, Discord, Twitter |
Engagement, feedback |
Messaging Hierarchy
| Level |
Purpose |
Example |
| Mission |
Why we exist |
"Make developers 10x more productive" |
| Value Prop |
What we offer |
"AI that understands your codebase" |
| Differentiator |
Why us vs others |
"Context-aware, not just autocomplete" |
| Proof Point |
Why believe us |
"40% reduction in debugging time" |
| CTA |
What to do next |
"Start your free trial" |
Launch Phases
| Phase |
Duration |
Focus |
Success Metric |
| Teaser |
2 weeks pre |
Build anticipation |
Waitlist signups |
| Launch |
Day 0-3 |
Maximum impact |
Traffic, signups |
| Momentum |
Week 1-4 |
Sustain interest |
Activation, feedback |
| Steady State |
Month 2+ |
Optimize funnel |
Conversion, retention |
Anti-Patterns
| Pattern |
Signal |
Fix |
| Launch and leave |
Big launch day, then silence |
Plan 30 days of post-launch activity |
| Everything everywhere |
All channels, no focus |
Pick 2-3 channels, do them well |
| Features not benefits |
"We have X, Y, Z" |
"You can achieve X, Y, Z" |
| No measurement |
"The launch went well (I think)" |
Define KPI- before launch |
| Ignoring personas |
Generic messaging for everyone |
Tailor by PER- |
| Over-promising |
"Revolutionary AI" without proof |
Ground in CFD- evidence |
Quality Gates
Before proceeding to Launch Metrics:
Downstream Connections
| Consumer |
What It Uses |
Example |
| Launch Metrics |
GTM- channels inform tracking |
GTM-002 (PH) → KPI-005 (PH upvotes) |
| Feedback Loop Setup |
GTM- channels become feedback sources |
GTM-002 comments → CFD-100 |
| Content Creation |
GTM- messaging guides content |
GTM-001 → blog post theme |
| Sales |
GTM- messaging for outreach |
GTM-001 → sales email template |
Detailed References
- Messaging framework examples: See
references/messaging-examples.md
- GTM- entry template: See
assets/gtm-template.md
- Channel evaluation guide: See
references/channel-guide.md
- Launch timeline template: See
references/timeline-template.md
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: nicepkg-ai-workflow-prd-v09-gtm-strategy3description: GTM Strategy4---56# GTM Strategy78Position in workflow: v0.8 Monitoring Setup → **v0.9 GTM Strategy** → v0.9 Launch Metrics910## Purpose1112Define how the product reaches its target users—the channels, messaging, timing, and coordination required for a successful launch.1314## Core Concept: Launch as Campaign1516> A launch is not "making the product available." It is a **coordinated campaign** that creates awareness, drives activation, and captures feedback. Every touchpoint should move users toward value.1718## GTM Components1920| Component | Purpose | Output |21|-----------|---------|--------|22| **Messaging** | What we say | GTM- (value props, headlines) |23| **Channels** | Where we say it | GTM- (channel strategy) |24| **Timing** | When we launch | GTM- (timeline, phases) |25| **Coordination** | Who does what | GTM- (RACI, tasks) |2627## Execution28291. **Review target personas**30 - Pull PER- from v0.431 - Understand where they spend time32 - Know what messages resonate33342. **Define core messaging**35 - Value proposition (from CFD- value hypotheses)36 - Positioning (from BR- product type)37 - Key differentiators (from v0.2 competitive landscape)38393. **Select launch channels**40 - Match channels to personas41 - Prioritize by reach and conversion potential42 - Consider owned, earned, and paid media43444. **Plan launch timeline**45 - Pre-launch: Build anticipation46 - Launch day: Maximum impact47 - Post-launch: Sustain momentum48495. **Assign ownership**50 - Who creates content?51 - Who monitors channels?52 - Who handles support surge?53546. **Create GTM- entries** with full traceability5556## GTM- Output Template5758```59GTM-XXX: [GTM Item Title]60Type: [Messaging | Channel | Timeline | Task | Asset]61Owner: [Person or team responsible]62Status: [Planned | In Progress | Ready | Live]6364For Messaging Type:65 Audience: [PER-XXX targeted]66 Format: [Headline | Value Prop | Tagline | Elevator Pitch]67 Message: [The actual copy]68 Supporting Evidence: [CFD-XXX value hypothesis it's based on]69 Where Used: [GTM-YYY channels, assets]7071For Channel Type:72 Channel: [Specific platform or medium]73 Audience Fit: [Why this channel reaches PER-XXX]74 Strategy: [How we'll use this channel]75 Content Plan: [What content goes here]76 Success Metric: [How we measure effectiveness]77 Linked Assets: [GTM-YYY assets for this channel]7879For Timeline Type:80 Phase: [Pre-launch | Launch Day | Week 1 | Month 1]81 Date: [Specific date or relative timing]82 Activities: [What happens in this phase]83 Dependencies: [What must be ready]84 Milestones: [Key checkpoints]8586For Task Type:87 Task: [What needs to be done]88 Owner: [Who is responsible]89 Due: [When it's due]90 Dependency: [What it depends on]91 Deliverable: [What's produced]9293For Asset Type:94 Asset: [What this is — landing page, email, video]95 Purpose: [What it accomplishes]96 Channel: [GTM-YYY where it's used]97 Copy: [GTM-YYY messaging used]98 Status: [Draft | Review | Approved | Live]99100Linked IDs: [PER-XXX, CFD-XXX, KPI-XXX related]101```102103**Example GTM- entries:**104105```106GTM-001: Primary Value Proposition107Type: Messaging108Owner: Product Marketing109Status: Ready110111Audience: PER-001 (Startup Founder)112Format: Value Prop113Message: "Ship faster with AI that understands your codebase.114 Context-aware coding assistance that reduces debugging115 time by 40%."116Supporting Evidence: CFD-010 (time savings validated in interviews)117Where Used: GTM-005 (Landing Page), GTM-010 (Product Hunt)118119Linked IDs: PER-001, CFD-010, KPI-001120```121122```123GTM-002: Product Hunt Launch124Type: Channel125Owner: Growth Team126Status: Planned127128Channel: Product Hunt129Audience Fit: PER-001 (Startup Founder) frequents PH for tools130Strategy:131 - Launch on Tuesday 12:01 AM PT132 - Engage with comments first 24 hours133 - Share maker story134 - Prepare demo video135Content Plan:136 - Tagline: GTM-001 (Primary Value Prop)137 - Maker comment: GTM-003 (Founder Story)138 - Demo video: GTM-006 (Product Demo)139Success Metric: Top 5 product of the day, 500+ upvotes140141Linked IDs: PER-001, GTM-001, GTM-003, GTM-006, KPI-005142```143144```145GTM-003: Launch Week Timeline146Type: Timeline147Owner: Launch Coordinator148Status: Planned149150Phase: Launch Week151152Day -7 (Pre-launch):153 - [ ] Email list teaser154 - [ ] Social media hints155 - [ ] Press outreach156157Day -1:158 - [ ] Final staging verification159 - [ ] Launch assets approved160 - [ ] Team roles confirmed161162Day 0 (Launch):163 - [ ] Product Hunt live at 12:01 AM PT164 - [ ] Social media posts scheduled165 - [ ] Email to waitlist166 - [ ] Monitor and engage167168Day 1-3:169 - [ ] Respond to all feedback170 - [ ] Fix any critical issues171 - [ ] Share early wins172173Day 4-7:174 - [ ] Publish case study175 - [ ] Analyze metrics176 - [ ] Plan iteration177178Dependencies: DEP- release criteria met, MON- monitoring active179Milestones: 1000 signups (Day 3), First paying customer (Day 7)180181Linked IDs: DEP-002, MON-005, KPI-001182```183184```185GTM-004: Landing Page Hero Section186Type: Asset187Owner: Design + Marketing188Status: In Progress189190Asset: Landing page hero section191Purpose: Convert visitors to signups192Channel: GTM-007 (Website), GTM-002 (Product Hunt referrals)193Copy: GTM-001 (Primary Value Prop)194Status: Review195196Components:197 - Headline: "Ship faster with AI that understands your codebase"198 - Subhead: "Context-aware coding assistance that reduces199 debugging time by 40%"200 - CTA: "Start Free Trial" → /signup201 - Social proof: "Trusted by 500+ developers"202 - Demo video thumbnail: GTM-006203204Linked IDs: GTM-001, GTM-006, SCR-001205```206207## Channel Selection Framework208209Match channels to product type (from v0.2 BR-):210211| Product Type | Primary Channels | Strategy |212|--------------|------------------|----------|213| **Fast Follow** | SEO, Paid, Aggregators | "We're the better [competitor]" |214| **Slice** | Community, Integrations, Partnerships | "Best [thing] for [ecosystem]" |215| **Innovation** | Content, PR, Events | "Here's why this matters" |216217## Channel Categories218219| Category | Examples | Best For |220|----------|----------|----------|221| **Owned** | Website, Blog, Email, Product | Control message, build audience |222| **Earned** | PR, Reviews, Word-of-mouth | Credibility, reach |223| **Paid** | Ads, Sponsorships, Influencers | Scale, targeting |224| **Community** | Forums, Discord, Twitter | Engagement, feedback |225226## Messaging Hierarchy227228| Level | Purpose | Example |229|-------|---------|---------|230| **Mission** | Why we exist | "Make developers 10x more productive" |231| **Value Prop** | What we offer | "AI that understands your codebase" |232| **Differentiator** | Why us vs others | "Context-aware, not just autocomplete" |233| **Proof Point** | Why believe us | "40% reduction in debugging time" |234| **CTA** | What to do next | "Start your free trial" |235236## Launch Phases237238| Phase | Duration | Focus | Success Metric |239|-------|----------|-------|----------------|240| **Teaser** | 2 weeks pre | Build anticipation | Waitlist signups |241| **Launch** | Day 0-3 | Maximum impact | Traffic, signups |242| **Momentum** | Week 1-4 | Sustain interest | Activation, feedback |243| **Steady State** | Month 2+ | Optimize funnel | Conversion, retention |244245## Anti-Patterns246247| Pattern | Signal | Fix |248|---------|--------|-----|249| **Launch and leave** | Big launch day, then silence | Plan 30 days of post-launch activity |250| **Everything everywhere** | All channels, no focus | Pick 2-3 channels, do them well |251| **Features not benefits** | "We have X, Y, Z" | "You can achieve X, Y, Z" |252| **No measurement** | "The launch went well (I think)" | Define KPI- before launch |253| **Ignoring personas** | Generic messaging for everyone | Tailor by PER- |254| **Over-promising** | "Revolutionary AI" without proof | Ground in CFD- evidence |255256## Quality Gates257258Before proceeding to Launch Metrics:259260- [ ] Core messaging defined (GTM- Messaging type)261- [ ] Primary channels selected (GTM- Channel type)262- [ ] Launch timeline created (GTM- Timeline type)263- [ ] All tasks assigned owners (GTM- Task type)264- [ ] Key assets identified (GTM- Asset type)265- [ ] Messaging traces to CFD- evidence266- [ ] Channel selection matches PER- personas267268## Downstream Connections269270| Consumer | What It Uses | Example |271|----------|--------------|---------|272| **Launch Metrics** | GTM- channels inform tracking | GTM-002 (PH) → KPI-005 (PH upvotes) |273| **Feedback Loop Setup** | GTM- channels become feedback sources | GTM-002 comments → CFD-100 |274| **Content Creation** | GTM- messaging guides content | GTM-001 → blog post theme |275| **Sales** | GTM- messaging for outreach | GTM-001 → sales email template |276277## Detailed References278279- **Messaging framework examples**: See `references/messaging-examples.md`280- **GTM- entry template**: See `assets/gtm-template.md`281- **Channel evaluation guide**: See `references/channel-guide.md`282- **Launch timeline template**: See `references/timeline-template.md`283284---285> Converted and distributed by [TomeVault](https://tomevault.io/claim/nicepkg) — claim your Tome and manage your conversions.286<!-- tomevault:4.0:skill_md:2026-04-11 -->