accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels.
$ npx -y skills add shawnpang/startup-founder-skills --skill launch-strategy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/launch-strategyContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels.
name: launch-strategy description: When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels. related: [content-strategy, social-content, email-marketing, landing-page] reads: [startup-context]
1. **Define the offer** — Clarify exactly what is being sold, the transformation it provides, the price point, and the offer stack (main product + bonuses). Total perceived value should be 10x+ the price. 2. **Select the launch type** — Based on audience size, product maturity, and goals:
3. **Build the launch list** — Create a dedicated opt-in to identify the most interested prospects. This is your hottest segment. Build this list before creating pre-launch content. 4. **Create pre-launch content (PLC)** — Develop 3-4 pieces of high-value content using the Sideways Sales Letter structure (see framework below). Each piece delivers standalone value while advancing the sale. 5. **Write the launch email sequence** — Plan emails for every phase: PLC releases, cart open announcement, mid-launch social proof, final push urgency, and cart close deadline. 6. **Build the sales page** — Create the sales page with offer stack, testimonials, guarantee, and countdown timer. The page should make the buying decision feel obvious. 7. **Recruit JV partners (if applicable)** — Reach out to potential affiliates 4-6 weeks before launch. Provide swipe files, tracking links, and leaderboard incentives. 8. **Execute the launch** — Release PLCs on schedule, open cart, send emails, engage with prospects in real time. Most sales happen in the last 24 hours. 9. **Close the cart and debrief** — When the cart closes, it closes. Follow up with non-buyers. Analyze results and plan improvements for the next launch.
Instead of one long sales letter, spread the sales message across 3-4 pieces of pre-launch content over 7-14 days. Each piece delivers value while building desire:
Give away your best material for free during pre-launch. When you deliver massive value before asking for the sale, you build reciprocity and prove competence. Do not hold back your best content out of fear — generosity in pre-launch drives sales at cart open.
| Phase | Timing | Activities | |-------|--------|------------| | Pre-Pre-Launch | 4-6 weeks before | Seed the idea, build launch list, survey audience | | PLC 1 | 10-14 days before | Release Opportunity content | | PLC 2 | 7-10 days before | Release Transformation content | | PLC 3 | 4-7 days before | Release Ownership content | | PLC 4 / Cart Open | Launch day | Release Offer, open cart | | Cart Open | Days 1-3 | Daily emails, testimonials, FAQ | | Final Push | Days 4-5 | Multiple daily emails, urgency, countdown | | Cart Close | Days 5-7 | Final call emails, cart closes (for real) | | Post-Launch | Days 8-14 | Thank buyers, follow up non-buyers, debrief |
1. **Create 3-4 pieces of pre-launch content.** Do not just announce the product. Build desire over 7-14 days. 2. **Build a launch list before launching.** A dedicated opt-in identifies your hottest leads. 3. **Create real scarcity.** Use a genuine cart close date. When it closes, it closes. Fake deadlines destroy trust permanentl
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…