The Kit Flow
How aiorg kits work together to take you from idea to successful product.
All kits require Claude Code to work.
The Journey
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ │ │ │ │ │ │ │ │ │
│ IDEA │──▶│ BUILD │──▶│ PMF │──▶│ SCALE │──▶│ RETAIN │
│ │ │ │ │ │ │ │ │ │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
Idea OS Templates Product OS Marketing Support Team
OS
Note: Not everyone follows this exact path. See Founder Paths for different journeys.
Stage 1: IDEA
Kit: Idea OS (Free)
What happens:
- Define your idea, problem, customer
- Research competitors automatically
- Generate Mom Test interview questions
- Talk to potential customers
- Get a PMF score (0-100)
Output: GO / CONDITIONAL GO / STOP decision
Handoff: When score >= 70, Idea OS recommends moving to Build
Stage 2: BUILD
Kits:
- SaaS Dev Team — Full-stack web app
- Landing Page — High-converting landing pages (Free)
What happens:
- Set up local development
- Configure auth, database, payments
- Build your first features
- Deploy to production
Output: Working product in production
Handoff: Once live with users, move to Product OS
Stage 3: PMF
Kit: Product OS
What happens:
- Diagnose why users leave
- Find the "magic number" (action that predicts retention)
- Run experiments
- Measure PMF (Sean Ellis test)
Output: PMF score. 40%+ "very disappointed" = PMF achieved
Handoff: When PMF achieved, move to Marketing OS (scale mode)
Stage 4: SCALE
Kit: Marketing OS
What happens:
- Scale user acquisition
- Paid ads, aggressive SEO
- Product launches
- Community building
- Viral loops
Output: Growing user base
Handoff: At 1000+ users, add Support Team for retention
Stage 5: RETAIN
Kit: Support Team
What happens:
- Identify at-risk users
- Lifecycle email campaigns
- Engagement campaigns
- Testimonials and reviews
Output: Lower churn, higher LTV
How Kits Share Context
Kits share information through a shared context layer (~/.aiorg/).
~/.aiorg/projects/taskflow/
├── context.json # Business context
└── learnings.json # Cross-kit learnings
This means:
- Idea OS records your validation score
- Product OS reads that score and adapts advice
- Marketing OS knows your target customer
- Support Team knows your PMF status
No re-explaining. Each kit picks up where the last one left off.
Data Ownership
Each kit owns specific data:
| Kit | Owns |
|---|---|
| Idea OS | validation.ideaScore, validation.targetCustomer, validation.valueProp |
| Product OS | pmf.score, pmf.status, pmf.seanEllisScore, pmf.activationRate |
| Marketing OS | Read-only (consumes context from others) |
| Support Team | Read-only (consumes context from others) |
Handoff Triggers
Kits automatically recommend the next step:
| From | Trigger | Recommend |
|---|---|---|
| Idea OS | Score >= 70 | SaaS Dev Team or Product OS after launch |
| Product OS | Score >= 40% | Marketing OS (scale mode) |
| Marketing OS | High traffic, low conversion | Product OS (positioning problem) |
| Support Team | Users leaving before activation | Product OS (not a retention problem) |
Alternative Paths
Skip Idea OS (AI Builder Path)
If building costs a weekend, you might skip validation:
[Build with AI] → Product OS → Marketing OS
Start with Marketing (Creator Path)
If you have an audience:
Marketing OS (audience) → Idea OS (what to build) → [Build] → Support Team
Indie Hacker Path
Build fast, learn from real users:
[Build fast] → Marketing OS (soft launch) → Product OS → Marketing OS (scale)
Support Kits
These kits support any stage:
- QA Team — Test your app at any stage
Choosing Your Entry Point
| Your situation | Start here |
|---|---|
| Just an idea | Idea OS |
| Ready to build | SaaS Dev Team |
| Have a product, no users | Marketing OS |
| Have users, no PMF | Product OS |
| Have PMF, need growth | Marketing OS |
| Growing, need retention | Support Team |