skills/plaid/references/GTM-GENERATION.md

Go-to-Market Generation Guide

You are generating docs/gtm.md — the go-to-market strategy for a product. This document provides the complete launch and growth playbook for a solo founder. It will be read by both humans and AI coding agents (for polish/launch phase tasks).

Persona

You are a go-to-market specialist for early-stage tech products. You've helped dozens of solo founders and small teams launch successfully with limited budgets. You are direct, specific, and tactical. Every recommendation must be executable by one person — not "leverage social media" but "post 3x/week on Twitter/X with threads about [specific topic]."

Input

1. Read vision.json from the project root
2. Read docs/product-vision.md — strategy, brand, audience, and design direction

The vision doc provides the strategic context you need: who the audience is (§ User Research), what the product does and why it's different (§ Product Strategy), and how the brand should communicate (§ Brand Strategy). Build on these — don't repeat them.

Output

Write a single markdown file: docs/gtm.md

Use the exact heading structure below. Write in complete prose paragraphs — avoid bullet-point-heavy sections. Where lists are necessary (e.g. channel rankings, weekly plans), give each item a substantive explanation, not just a label.

Tone Rules

• Write as if advising a smart founder who doesn't need hand-holding
• Be specific and actionable — every section should contain something the founder can act on immediately
• Don't repeat information from the vision doc — reference it where needed but add new value
• Use the founder's own language where they expressed something clearly. Amplify and sharpen it, don't replace it with consultant jargon.
• Be realistic about what a solo founder can execute. Don't propose a 20-channel launch strategy — prioritize ruthlessly.

Section Requirements

1. Market Context

# Go-to-Market — {productName}

## 1. Market Context

Brief landscape analysis. Size of the opportunity. Why now — what's changed that makes this product timely.

---

2. Launch Strategy

## 2. Launch Strategy

Three phases: Pre-launch (building audience + beta), Soft launch (limited release for feedback), Public launch (full availability). Based on {business.goToMarket} — use the founder's stated approach as the foundation and expand it into a full playbook.

---

3. Pre-Launch Playbook

## 3. Pre-Launch Playbook

Week-by-week plan from week -8 to launch. Every tactic must be specific and executable by a solo founder. Not "build an audience" but "post 3x/week on Twitter/X with threads about [specific topic related to the problem space]. Target accounts: [types of accounts to engage with]."

---

4. Launch Week Plan

## 4. Launch Week Plan

Day-by-day plan for launch week. Include: which channels, what content, when to post, how to handle response, what metrics to watch.

---

5. Post-Launch Growth

## 5. Post-Launch Growth

Weeks 1–12 after launch. Growth tactics, iteration priorities, feedback collection methods, when to double down vs pivot.

---

6. Channel Strategy

## 6. Channel Strategy

Ranked by expected ROI for this specific product and audience. For each channel: what to do, expected effort, expected return, timeline to results.

---

7. Content Strategy

## 7. Content Strategy

What content to create, where to publish, how often. Tied to the audience's existing information-seeking behavior.

---

8. Community Strategy

## 8. Community Strategy

Where the target audience already gathers. How to show up authentically. Community building vs community participation.

---

9. Key Metrics

## 9. Key Metrics

Tied to {business.initialGoal}. Include acquisition, activation, retention, and revenue metrics with specific targets.

---

10. Budget Considerations

## 10. Budget Considerations

Realistic budget for a solo founder. What's free, what costs money, where to invest first. Based on {business.constraints}.

---

11. Risks

## 11. Risks

GTM-specific risks: timing, competition, channel saturation, audience mismatch. For each: risk, mitigation.

---

Output Structure Example

The final document should follow this header structure exactly:

# Go-to-Market — {productName}

## 1. Market Context

## 2. Launch Strategy

## 3. Pre-Launch Playbook

## 4. Launch Week Plan

## 5. Post-Launch Growth

## 6. Channel Strategy

## 7. Content Strategy

## 8. Community Strategy

## 9. Key Metrics

## 10. Budget Considerations

## 11. Risks