format: apply repo prettier (3.8.1) to the folded skills tree
963 markdown files reformatted with the repository's pinned prettier so pnpm format:check covers the folded tree like every other repo file. The formatter's embedded-language pass also normalized code fences (TS semicolons, closed HTML tags in examples, lowercased CSS hex colors, one renumbered list that skipped an index). Alphanumeric token deltas vs the fold commit were audited file-by-file; all are formatter-equivalent markup normalizations plus the four sanitized skills.
This commit is contained in:
@@ -20,6 +20,7 @@ If `.mosaic/product-marketing-context.md` exists, read it before asking question
|
||||
The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
|
||||
|
||||
A strong launch isn't about a single moment. It's about:
|
||||
|
||||
- Getting your product into users' hands early
|
||||
- Learning from real feedback
|
||||
- Making a splash at every stage
|
||||
@@ -32,9 +33,11 @@ A strong launch isn't about a single moment. It's about:
|
||||
Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
|
||||
|
||||
### Owned Channels
|
||||
|
||||
You own the channel (though not the audience). Direct access without algorithms or platform rules.
|
||||
|
||||
**Examples:**
|
||||
|
||||
- Email list
|
||||
- Blog
|
||||
- Podcast
|
||||
@@ -42,12 +45,14 @@ You own the channel (though not the audience). Direct access without algorithms
|
||||
- Website/product
|
||||
|
||||
**Why they matter:**
|
||||
|
||||
- Get more effective over time
|
||||
- No algorithm changes or pay-to-play
|
||||
- Direct relationship with audience
|
||||
- Compound value from content
|
||||
|
||||
**Start with 1-2 based on audience:**
|
||||
|
||||
- Industry lacks quality content → Start a blog
|
||||
- People want direct updates → Focus on email
|
||||
- Engagement matters → Build a community
|
||||
@@ -56,15 +61,18 @@ You own the channel (though not the audience). Direct access without algorithms
|
||||
Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.
|
||||
|
||||
### Rented Channels
|
||||
|
||||
Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
|
||||
|
||||
**Examples:**
|
||||
|
||||
- Social media (Twitter/X, LinkedIn, Instagram)
|
||||
- App stores and marketplaces
|
||||
- YouTube
|
||||
- Reddit
|
||||
|
||||
**How to use correctly:**
|
||||
|
||||
- Pick 1-2 platforms where your audience is active
|
||||
- Use them to drive traffic to owned channels
|
||||
- Don't rely on them as your only strategy
|
||||
@@ -73,6 +81,7 @@ Platforms that provide visibility but you don't control. Algorithms shift, rules
|
||||
Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.
|
||||
|
||||
**Platform-specific tactics:**
|
||||
|
||||
- Twitter/X: Threads that spark conversation → link to newsletter
|
||||
- LinkedIn: High-value posts → lead to gated content or email signup
|
||||
- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more
|
||||
@@ -80,15 +89,18 @@ Hacked virality through Twitter, YouTube, and Reddit where productivity enthusia
|
||||
Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
|
||||
|
||||
### Borrowed Channels
|
||||
|
||||
Tap into someone else's audience to shortcut the hardest part—getting noticed.
|
||||
|
||||
**Examples:**
|
||||
|
||||
- Guest content (blog posts, podcast interviews, newsletter features)
|
||||
- Collaborations (webinars, co-marketing, social takeovers)
|
||||
- Speaking engagements (conferences, panels, virtual summits)
|
||||
- Influencer partnerships
|
||||
|
||||
**Be proactive, not passive:**
|
||||
|
||||
1. List industry leaders your audience follows
|
||||
2. Pitch win-win collaborations
|
||||
3. Use tools like SparkToro or Listen Notes to find audience overlap
|
||||
@@ -106,9 +118,11 @@ Borrowed channels give instant credibility, but only work if you convert borrowe
|
||||
Launching isn't a one-day event. It's a phased process that builds momentum.
|
||||
|
||||
### Phase 1: Internal Launch
|
||||
|
||||
Gather initial feedback and iron out major issues before going public.
|
||||
|
||||
**Actions:**
|
||||
|
||||
- Recruit early users one-on-one to test for free
|
||||
- Collect feedback on usability gaps and missing features
|
||||
- Ensure prototype is functional enough to demo (doesn't need to be production-ready)
|
||||
@@ -116,9 +130,11 @@ Gather initial feedback and iron out major issues before going public.
|
||||
**Goal:** Validate core functionality with friendly users.
|
||||
|
||||
### Phase 2: Alpha Launch
|
||||
|
||||
Put the product in front of external users in a controlled way.
|
||||
|
||||
**Actions:**
|
||||
|
||||
- Create landing page with early access signup form
|
||||
- Announce the product exists
|
||||
- Invite users individually to start testing
|
||||
@@ -127,14 +143,17 @@ Put the product in front of external users in a controlled way.
|
||||
**Goal:** First external validation and initial waitlist building.
|
||||
|
||||
### Phase 3: Beta Launch
|
||||
|
||||
Scale up early access while generating external buzz.
|
||||
|
||||
**Actions:**
|
||||
|
||||
- Work through early access list (some free, some paid)
|
||||
- Start marketing with teasers about problems you solve
|
||||
- Recruit friends, investors, and influencers to test and share
|
||||
|
||||
**Consider adding:**
|
||||
|
||||
- Coming soon landing page or waitlist
|
||||
- "Beta" sticker in dashboard navigation
|
||||
- Email invites to early access list
|
||||
@@ -143,29 +162,35 @@ Scale up early access while generating external buzz.
|
||||
**Goal:** Build buzz and refine product with broader feedback.
|
||||
|
||||
### Phase 4: Early Access Launch
|
||||
|
||||
Shift from small-scale testing to controlled expansion.
|
||||
|
||||
**Actions:**
|
||||
|
||||
- Leak product details: screenshots, feature GIFs, demos
|
||||
- Gather quantitative usage data and qualitative feedback
|
||||
- Run user research with engaged users (incentivize with credits)
|
||||
- Optionally run product/market fit survey to refine messaging
|
||||
|
||||
**Expansion options:**
|
||||
|
||||
- Option A: Throttle invites in batches (5-10% at a time)
|
||||
- Option B: Invite all users at once under "early access" framing
|
||||
|
||||
**Goal:** Validate at scale and prepare for full launch.
|
||||
|
||||
### Phase 5: Full Launch
|
||||
|
||||
Open the floodgates.
|
||||
|
||||
**Actions:**
|
||||
|
||||
- Open self-serve signups
|
||||
- Start charging (if not already)
|
||||
- Announce general availability across all channels
|
||||
|
||||
**Launch touchpoints:**
|
||||
|
||||
- Customer emails
|
||||
- In-app popups and product tours
|
||||
- Website banner linking to launch assets
|
||||
@@ -183,11 +208,13 @@ Open the floodgates.
|
||||
Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.
|
||||
|
||||
### Pros
|
||||
|
||||
- Exposure to tech-savvy early adopter audience
|
||||
- Credibility bump (especially if Product of the Day)
|
||||
- Potential PR coverage and backlinks
|
||||
|
||||
### Cons
|
||||
|
||||
- Very competitive to rank well
|
||||
- Short-lived traffic spikes
|
||||
- Requires significant pre-launch planning
|
||||
@@ -195,6 +222,7 @@ Product Hunt can be powerful for reaching early adopters, but it's not magic—i
|
||||
### How to Launch Successfully
|
||||
|
||||
**Before launch day:**
|
||||
|
||||
1. Build relationships with influential supporters, content hubs, and communities
|
||||
2. Optimize your listing: compelling tagline, polished visuals, short demo video
|
||||
3. Study successful launches to identify what worked
|
||||
@@ -202,6 +230,7 @@ Product Hunt can be powerful for reaching early adopters, but it's not magic—i
|
||||
5. Prepare your team for all-day engagement
|
||||
|
||||
**On launch day:**
|
||||
|
||||
1. Treat it as an all-day event
|
||||
2. Respond to every comment in real-time
|
||||
3. Answer questions and spark discussions
|
||||
@@ -209,6 +238,7 @@ Product Hunt can be powerful for reaching early adopters, but it's not magic—i
|
||||
5. Direct traffic back to your site to capture signups
|
||||
|
||||
**After launch day:**
|
||||
|
||||
1. Follow up with everyone who engaged
|
||||
2. Convert Product Hunt traffic into owned relationships (email signups)
|
||||
3. Continue momentum with post-launch content
|
||||
@@ -216,12 +246,14 @@ Product Hunt can be powerful for reaching early adopters, but it's not magic—i
|
||||
### Case Studies
|
||||
|
||||
**SavvyCal** (Scheduling tool):
|
||||
|
||||
- Optimized landing page and onboarding before launch
|
||||
- Built relationships with productivity/SaaS influencers in advance
|
||||
- Responded to every comment on launch day
|
||||
- Result: #2 Product of the Month
|
||||
|
||||
**Reform** (Form builder):
|
||||
|
||||
- Studied successful launches and applied insights
|
||||
- Crafted clear tagline, polished visuals, demo video
|
||||
- Engaged in communities before launch (provided value first)
|
||||
@@ -253,6 +285,7 @@ Add dedicated sections about the new feature/product across your site.
|
||||
Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
|
||||
|
||||
### Keep Momentum Going
|
||||
|
||||
It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
|
||||
|
||||
---
|
||||
@@ -266,16 +299,19 @@ Don't rely on a single launch event. Regular updates and feature rollouts sustai
|
||||
Use this matrix to decide how much marketing each update deserves:
|
||||
|
||||
**Major updates** (new features, product overhauls):
|
||||
|
||||
- Full campaign across multiple channels
|
||||
- Blog post, email campaign, in-app messages, social media
|
||||
- Maximize exposure
|
||||
|
||||
**Medium updates** (new integrations, UI enhancements):
|
||||
|
||||
- Targeted announcement
|
||||
- Email to relevant segments, in-app banner
|
||||
- Don't need full fanfare
|
||||
|
||||
**Minor updates** (bug fixes, small tweaks):
|
||||
|
||||
- Changelog and release notes
|
||||
- Signal that product is improving
|
||||
- Don't dominate marketing
|
||||
@@ -299,6 +335,7 @@ Even small changelog updates remind customers your product is evolving. This bui
|
||||
## Launch Checklist
|
||||
|
||||
### Pre-Launch
|
||||
|
||||
- [ ] Landing page with clear value proposition
|
||||
- [ ] Email capture / waitlist signup
|
||||
- [ ] Early access list built
|
||||
@@ -311,6 +348,7 @@ Even small changelog updates remind customers your product is evolving. This bui
|
||||
- [ ] Analytics/tracking in place
|
||||
|
||||
### Launch Day
|
||||
|
||||
- [ ] Announcement email to list
|
||||
- [ ] Blog post published
|
||||
- [ ] Social posts scheduled and posted
|
||||
@@ -321,6 +359,7 @@ Even small changelog updates remind customers your product is evolving. This bui
|
||||
- [ ] Monitor for issues and feedback
|
||||
|
||||
### Post-Launch
|
||||
|
||||
- [ ] Onboarding email sequence active
|
||||
- [ ] Follow-up with engaged prospects
|
||||
- [ ] Roundup email includes announcement
|
||||
|
||||
Reference in New Issue
Block a user