AI-Native Launch Stage
Goal
Help founders turn a working MVP into a focused launch motion that creates customers, feedback, revenue signals, and repeatable learning.
Required Inputs
If the founder provides a structured brief, use these inputs:
Product/MVP status:
Ideal customer profile:
Positioning hypothesis:
Current users or pipeline:
Pricing hypothesis:
Onboarding flow:
Acquisition channel:
Feedback signals:
Desired output:
Guided Intake
Do not require the founder to provide a full launch brief. If the request is vague, ask up to five questions first:
1. What product or MVP can users try now?
2. Who is the narrowest ideal customer for the first launch motion?
3. How are you currently reaching users or buyers?
4. What launch problem is most urgent: positioning, sales, pricing, onboarding, or feedback?
5. What evidence do you have from users, demos, pilots, or sales conversations?
After the user answers, choose the narrowest useful launch artifact and state assumptions. Ask follow-ups only if the launch audience or available product is still impossible to infer.
Workflow
- Clarify the launch audience and buying/user trigger.
- Use
references/positioning.md to convert product capability into customer value.
- Use
references/founder-led-sales.md to plan outreach, discovery, demos, follow-up, and close/learn loops.
- Use
references/pricing-and-onboarding.md to design a simple offer and activation path.
- Use
references/launch-operating-system.md to replace repetitive founder attention with AI-assisted workflows.
- Return a launch plan with messaging, target list, sales motion, onboarding, feedback loops, and decision points.
AI-Native Workflows
Use generic AI roles:
- Research assistant: build account lists and summarize buyer context.
- Sales copilot: draft outreach, discovery guides, demo scripts, and follow-ups.
- Customer-success assistant: create onboarding, FAQs, and activation nudges.
- Feedback analyst: cluster objections, usage notes, churn risks, and feature requests.
- Workflow agent: automate repeatable launch operations with human review.
Exit Criteria
The Launch stage is complete when:
- a narrow ICP responds consistently;
- customers understand the positioning;
- onboarding reaches the promised outcome;
- pricing has evidence from real conversations or transactions;
- feedback loops identify what to improve next.
Common Failure Modes
- Launching to everyone instead of a narrow ICP.
- Mistaking attention for demand.
- Automating sales before the founder understands the buyer.
- Pricing without value or urgency evidence.
- Collecting feedback without a decision process.
Recommended Outputs
Return the most useful artifact for the request:
- launch plan;
- positioning brief;
- founder-led sales script;
- pricing and onboarding plan;
- launch operating system.
1---2name: ai-native-launch-stage3description: Launch an AI-native product and learn from the first customers. Use when a founder has an MVP or beta and needs positioning, ICP, first users, founder-led sales, pricing, onboarding, launch plan, customer feedback loops, or an AI-assisted operating system for early growth.4---56# AI-Native Launch Stage78## Goal910Help founders turn a working MVP into a focused launch motion that creates customers, feedback, revenue signals, and repeatable learning.1112## Required Inputs1314If the founder provides a structured brief, use these inputs:1516```text17Product/MVP status:18Ideal customer profile:19Positioning hypothesis:20Current users or pipeline:21Pricing hypothesis:22Onboarding flow:23Acquisition channel:24Feedback signals:25Desired output:26```2728## Guided Intake2930Do not require the founder to provide a full launch brief. If the request is vague, ask up to five questions first:3132```text331. What product or MVP can users try now?342. Who is the narrowest ideal customer for the first launch motion?353. How are you currently reaching users or buyers?364. What launch problem is most urgent: positioning, sales, pricing, onboarding, or feedback?375. What evidence do you have from users, demos, pilots, or sales conversations?38```3940After the user answers, choose the narrowest useful launch artifact and state assumptions. Ask follow-ups only if the launch audience or available product is still impossible to infer.4142## Workflow43441. Clarify the launch audience and buying/user trigger.452. Use `references/positioning.md` to convert product capability into customer value.463. Use `references/founder-led-sales.md` to plan outreach, discovery, demos, follow-up, and close/learn loops.474. Use `references/pricing-and-onboarding.md` to design a simple offer and activation path.485. Use `references/launch-operating-system.md` to replace repetitive founder attention with AI-assisted workflows.496. Return a launch plan with messaging, target list, sales motion, onboarding, feedback loops, and decision points.5051## AI-Native Workflows5253Use generic AI roles:5455- Research assistant: build account lists and summarize buyer context.56- Sales copilot: draft outreach, discovery guides, demo scripts, and follow-ups.57- Customer-success assistant: create onboarding, FAQs, and activation nudges.58- Feedback analyst: cluster objections, usage notes, churn risks, and feature requests.59- Workflow agent: automate repeatable launch operations with human review.6061## Exit Criteria6263The Launch stage is complete when:6465- a narrow ICP responds consistently;66- customers understand the positioning;67- onboarding reaches the promised outcome;68- pricing has evidence from real conversations or transactions;69- feedback loops identify what to improve next.7071## Common Failure Modes7273- Launching to everyone instead of a narrow ICP.74- Mistaking attention for demand.75- Automating sales before the founder understands the buyer.76- Pricing without value or urgency evidence.77- Collecting feedback without a decision process.7879## Recommended Outputs8081Return the most useful artifact for the request:8283- launch plan;84- positioning brief;85- founder-led sales script;86- pricing and onboarding plan;87- launch operating system.
Hades-HY-LI