Launch & Growth

Disclaimer

Launch and growth tactics should be adapted to your specific market, product stage, and regulatory environment. Test assumptions before scaling.

Go-to-Market

A go-to-market (GTM) plan answers three questions: Who are we selling to? How will they learn about us? What does the buying process look like? The complexity of the plan scales with the complexity of the product and organization. A two-person startup does not need a 40-page GTM brief. An enterprise launching into a new market does.

Startup Mode: Lean GTM

For early-stage products, your GTM strategy is simple: find the people who have the problem most urgently, get the product in front of them, and learn as fast as possible. You do not need a marketing department. You need hustle, specificity, and speed.

Identify Early Adopters

Early adopters are not "everyone who might use this." They are the people whose pain is so acute that they will tolerate a buggy, incomplete product to get relief. To find them, answer these questions:

Who has the problem most urgently? Look for people currently using spreadsheets, manual workarounds, or cobbled-together tool stacks to solve the problem your product addresses. They are actively investing time and effort, which means they will pay to save it.
Where do they already gather? Identify 3-5 communities: Slack groups, Discord servers, subreddits, Twitter/X circles, LinkedIn groups, niche forums, industry meetups. Your first 50 users are already in these places.
What language do they use? Listen to how they describe the problem. Use their words in your messaging, not your product jargon.

Launch Channels for Startups

Product Hunt launch playbook:

Build a "hunter" relationship 2-4 weeks before launch. Reach out to top hunters in your category.
Prepare assets: tagline (under 60 characters), description (under 260 characters), 4-6 images/GIFs showing the product, a 1-minute demo video, a maker comment with your backstory.
Launch on a Tuesday or Wednesday. Avoid Mondays (competition from weekend builders) and Fridays (lower traffic).
Have your team, advisors, and early users ready to upvote and comment in the first 2 hours. Authentic comments matter more than vote count.
Respond to every comment personally. Engage for the full 24-hour cycle.

Hacker News (Show HN) playbook:

Title format: "Show HN: [Product Name] -- [One sentence describing what it does]."
Lead with the technical or design insight, not the marketing pitch. HN rewards substance over hype.
Include a text body explaining: what problem it solves, how it works (technical details appreciated), what you learned building it, what feedback you want.
Post between 8-10 AM ET on weekdays. Avoid weekends.
Respond to every comment thoughtfully. Engage with criticism gracefully -- it builds credibility.

Beta waitlist strategy:

Create a landing page with a clear value proposition, one email capture field, and a short explainer (video or 3 bullet points).
Add a referral mechanic: "Move up the waitlist by sharing with friends." Tools like Viral Loops or custom referral codes work.
Send a welcome email immediately on signup. Include expected timeline and what makes this product different.
Email the waitlist weekly with progress updates. Build anticipation and trust.
Invite in small batches (10-25 at a time). This lets you manage support load and iterate between batches.

Founder-led sales (the first 10 customers): Your first 10 customers should not come from inbound marketing. They should come from you personally reaching out to people who fit your ideal customer profile. This is not scalable. It is not supposed to be. The goal is to learn, not to grow.

Identify 50 potential customers by name. Use LinkedIn, community directories, conference attendee lists.
Send personalized outreach (not templates). Reference something specific about their work or pain point.
Offer a 30-minute call to understand their workflow. Do not pitch. Listen.
After the call, offer free access to the product in exchange for 2 feedback sessions over the next month.
Close the loop: Did the product solve their problem? What is missing? Would they pay? How much?

Community seeding: Find 3-5 communities where your target users already spend time. Contribute value before promoting anything. Answer questions. Share insights. Build a reputation. Only after you have established credibility should you mention your product -- and even then, frame it as "I built something to solve this problem" rather than "check out my product."

Content marketing basics:

Write 2-3 blog posts that address the specific pain points your product solves. Optimize for the search terms your customers use.
Create Twitter/X threads that break down industry problems, share data, or tell your building-in-public story.
Write a "Show HN" or "Indie Hackers" post about your journey, lessons, or technical decisions.

Lean GTM Checklist

LEAN GTM CHECKLIST
===================
Product: _______________
Target launch date: _______________
Owner: _______________

BEFORE LAUNCH:
[ ] Early adopters identified (names, not personas)
[ ] 3-5 communities where users gather identified and joined
[ ] Landing page live with email capture
[ ] Waitlist has 50+ signups (or 10+ warm intros scheduled)
[ ] Product Hunt assets prepared (if applicable)
[ ] Show HN post drafted (if applicable)
[ ] 3 blog posts or content pieces published or scheduled
[ ] Founder outreach list of 50 names prepared
[ ] Personal outreach sent to first 20 prospects
[ ] Pricing page live (even if "free during beta")
[ ] Analytics instrumented (signup, activation, key actions)

LAUNCH WEEK:
[ ] Product Hunt / HN launch executed
[ ] All comments and feedback responded to within 2 hours
[ ] Waitlist invites sent in first batch (10-25 users)
[ ] Daily check-in on analytics (signups, activation, drop-off)
[ ] Founder available for same-day support

POST-LAUNCH (first 2 weeks):
[ ] 10+ user conversations completed
[ ] Key learnings documented
[ ] Top 3 product issues identified and triaged
[ ] Second batch of waitlist invites sent
[ ] Follow-up content published (learnings, traction, updates)

Enterprise Mode: Cross-Functional GTM

For established products launching new capabilities, entering new markets, or releasing major versions, GTM requires coordination across sales, marketing, customer success, product, and sometimes legal and compliance. The risk is not obscurity -- it is misalignment.

Sales Enablement

Sales teams need four things to sell effectively:

Battle cards (one per major competitor):

| Section | Content | |---|---| | Competitor overview | Who they are, what they sell, pricing, target market | | Where we win | 3-5 specific advantages with proof points (customer quotes, benchmark data, feature comparisons) | | Where they win | 2-3 areas where the competitor is stronger. Honest assessment -- sales reps will be asked about these. Equip them with responses, not denial. | | Objection handling matrix | Top 5 objections buyers raise when comparing, with scripted responses | | Demo talking points | Which features to highlight, which to avoid, recommended demo flow for competitive deals | | Pricing talk track | How to position your pricing vs. the competitor's. When to discount (rarely), when to hold firm, how to reframe value. |

Objection handling matrix template:

| Objection | Why They Say It | Response | Proof Point | |---|---|---|---| | "Competitor X is cheaper" | They are comparing sticker price, not TCO | "When you factor in implementation, maintenance, and the integrations you will need to add, the total cost over 2 years is actually 20% lower with us. Here is a TCO comparison..." | [Customer name] saved $45K/yr after switching from Competitor X | | "We already use Competitor Y" | Switching cost concern | "We integrate with Y and most customers run both during a 90-day transition. Here is a migration guide..." | Average migration time: 3 weeks with zero downtime | | "You do not have Feature Z" | Feature gap, real or perceived | "We approach that differently. Instead of Z, we offer [alternative] which achieves the same outcome with less configuration..." | 85% of customers who asked about Z found our approach sufficient |

Demo scripts: Structure every demo as Problem, Solution, Proof. Open with the customer's stated pain point (from the discovery call), show the product solving it (live, not slides), close with a proof point (customer story, metric, case study). Demos should be under 20 minutes. Save 10 minutes for questions.

Pricing talk tracks: Train sales on value framing: "The question is not whether $X/month is expensive. The question is whether saving Y hours per week and reducing Z% errors is worth $X/month to your team." Provide a calculator that quantifies ROI based on the customer's inputs.

Marketing Launch Plan

| Activity | Owner | Timeline | Status | |---|---|---|---| | Press release drafted and approved | Comms | T-4 weeks | | | Analyst briefing scheduled (Gartner, Forrester, or relevant) | AR | T-3 weeks | | | Webinar content created and landing page live | Demand Gen | T-2 weeks | | | Email campaign sequence built (announcement, feature deep-dive, case study) | Email Marketing | T-2 weeks | | | Blog post (announcement) published | Content | Launch day | | | Blog post (deep-dive / technical) published | Content | T+1 week | | | Social media posts scheduled (LinkedIn, Twitter/X, relevant platforms) | Social | Launch day through T+2 weeks | | | Landing page live with CTA (demo request, free trial, contact sales) | Web | T-1 week | | | Customer case study or testimonial ready | Customer Marketing | T-1 week | | | Paid advertising campaigns launched (if applicable) | Demand Gen | Launch day | |

Customer Success Readiness

| Deliverable | Owner | Description | |---|---|---| | Training plan | CS Enablement | Internal: train all CSMs on new capabilities (hands-on, not slides). External: create customer-facing training (videos, docs, webinar). | | Documentation | Technical Writing | User guides, API docs (if applicable), FAQ, migration guides (if changing existing behavior). Published before launch. | | Support runbooks | Support Ops | Step-by-step troubleshooting for the top 10 expected issues. Include escalation criteria: when to escalate to engineering. | | Escalation paths | Support Ops | Severity definitions (P1-P4), response time SLAs, who owns each severity level, communication templates for customer updates. | | Known issues list | Product/Eng | Documented limitations, workarounds, and planned fix timelines. CS and Support must know these before customers discover them. |

Partner Channel Activation

If you sell through partners (resellers, system integrators, technology partners):

Partner onboarding: Provide partners with product training, demo environments, and sales materials 2-4 weeks before GA.
Co-marketing: Joint webinars, co-branded case studies, partner blog posts. Agree on messaging and approval process upfront.
Deal registration: Ensure the partner portal is updated with the new product/SKU. Clarify margin structure and discount authority.
Technical certification: If partners implement or support the product, require certification before they can sell or support it.

Enterprise GTM Checklist

ENTERPRISE GTM CHECKLIST
==========================
Product / Feature: _______________
Launch date: _______________
GTM Owner: _______________

SALES ENABLEMENT:
[ ] Battle cards created for top 3 competitors
[ ] Objection handling matrix complete
[ ] Demo script and environment ready
[ ] Pricing talk track and ROI calculator ready
[ ] Sales team trained (live session + recorded)
[ ] Sales FAQ document published

MARKETING:
[ ] Press release drafted, approved, and distributed
[ ] Analyst briefings completed
[ ] Launch webinar scheduled and promoted
[ ] Email campaigns built and tested
[ ] Blog posts published (announcement + deep-dive)
[ ] Social media campaign scheduled
[ ] Landing page live with tracking
[ ] Paid campaigns launched (if applicable)
[ ] Customer case study or testimonial ready

CUSTOMER SUCCESS:
[ ] CSM team trained on new capabilities
[ ] Customer-facing documentation published
[ ] Support runbooks created for top 10 expected issues
[ ] Escalation paths documented and communicated
[ ] Known issues and workarounds documented
[ ] Customer-facing training (videos, webinar) scheduled

PARTNER CHANNEL:
[ ] Partner training completed
[ ] Partner portal updated with new SKU/materials
[ ] Co-marketing activities scheduled
[ ] Technical certification program updated (if applicable)

LEGAL / COMPLIANCE:
[ ] Terms of service updated (if applicable)
[ ] Privacy impact assessment completed (if applicable)
[ ] Regulatory approvals obtained (if applicable)

SIGN-OFF:
[ ] Product: _______________  Date: ______
[ ] Engineering: _______________  Date: ______
[ ] Sales: _______________  Date: ______
[ ] Marketing: _______________  Date: ______
[ ] CS: _______________  Date: ______
[ ] Legal: _______________  Date: ______

Pricing Strategy Basics

Pricing is the most underleveraged growth lever. A 1% improvement in pricing yields a larger profit impact than a 1% improvement in customer acquisition or cost reduction. Yet most PMs spend less than an hour on pricing decisions.

Pricing Approaches

Value-based pricing: Price based on the value the customer receives, not what it costs you to deliver. To determine value: quantify the customer's current cost of the problem (time, money, risk), then price your solution as a fraction of that savings. If your product saves a team $100K/year, pricing at $20K/year is easy to justify. This is the recommended approach for software products.

Competitor-based pricing: Set your price relative to the market rate, adjusted for positioning. If you offer more value, price 10-20% above. If you are the challenger with less brand recognition, price 10-30% below. Use this when the market has established price anchors that customers use as reference points.

Cost-plus pricing: Calculate your cost to deliver (COGS, support, infrastructure) and add a margin. Appropriate for hardware, professional services, or commoditized products where the customer is price-shopping. Not recommended for software -- your value to the customer is typically far above your delivery cost.

Freemium vs. Free Trial vs. Paid-Only

| Criteria | Freemium | Free Trial | Paid-Only | |---|---|---|---| | Best when | Product has viral/network effects; large addressable market; low marginal cost per user | Product value is clear but takes time to experience; complex setup | High ACV; small addressable market; requires human onboarding | | CAC tolerance | Low (self-serve acquisition) | Medium (some sales touch) | High (sales-led) | | Product complexity | Low (user can get value without training) | Medium (guided setup acceptable) | High (requires implementation or consultation) | | Time-to-value | Instant or within first session | Within trial period (7-30 days) | Demonstrated during sales process | | Market maturity | Growing market (land-grab phase) | Established market (conversion optimization phase) | Mature market (relationship-driven sales) | | Conversion benchmark | 2-5% free-to-paid | 10-25% trial-to-paid | N/A (100% paid from day 1) | | Risk | Supporting large free user base that never converts | Users not activating during trial window | Missing out on word-of-mouth and organic discovery |

Decision rule: If your product has a clear "aha moment" that users can reach independently within 5 minutes, freemium works. If the aha moment takes days or requires configuration, free trial is better. If the aha moment requires a custom demo or human walkthrough, go paid-only with a strong sales process.

Pricing Page Best Practices

Show 3 tiers. The middle tier should be your target -- most customers anchor on the center option. Name tiers by customer segment (Starter, Professional, Enterprise), not by feature list.
Highlight the recommended plan. Use visual emphasis (color, badge, border) on the tier you want most customers to choose.
Annual vs. monthly toggle. Show the annual price by default with the monthly savings percentage. Annual billing improves cash flow and retention.
Feature comparison table below the tiers. Let customers self-serve the comparison. Bold the differentiating features between tiers.
Include social proof. Logos of recognizable customers, a testimonial, or "Trusted by X teams" near the pricing.
Enterprise tier should say "Contact Sales." Do not show enterprise pricing publicly. This allows value-based negotiation and prevents anchoring.
Address objections on the page. FAQ section: "Can I switch plans?" "What happens if I cancel?" "Is there a setup fee?" "Do you offer discounts for nonprofits/education?"

References

For detailed templates, frameworks, and field-level guidance, read:

references/launch-growth-reference.md — Complete framework details, templates, and examples

Read this file when the task requires:

Launch Management
A/B Testing
Growth Experiments
Output Formats