The Kit Flow

How aiorg kits work together to take you from idea to successful product.

The Journey

┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
│          │   │          │   │          │   │          │   │          │
│  IDEA    │──▶│  BUILD   │──▶│  PMF     │──▶│  SCALE   │──▶│  RETAIN  │
│          │   │          │   │          │   │          │   │          │
└──────────┘   └──────────┘   └──────────┘   └──────────┘   └──────────┘
   Idea OS       Templates      PMF OS       Marketing     Success OS
                                               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 — Landing page (Coming Soon)

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 PMF OS


Stage 3: PMF

Kit: PMF 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 Success OS for retention


Stage 5: RETAIN

Kit: Success OS

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
  • PMF OS reads that score and adapts advice
  • Marketing OS knows your target customer
  • Success OS knows your PMF status

No re-explaining. Each kit picks up where the last one left off.


Data Ownership

Each kit owns specific data:

KitOwns
Idea OSvalidation.ideaScore, validation.targetCustomer, validation.valueProp
PMF OSpmf.score, pmf.status, pmf.seanEllisScore, pmf.activationRate
Marketing OSRead-only (consumes context from others)
Success OSRead-only (consumes context from others)

Handoff Triggers

Kits automatically recommend the next step:

FromTriggerRecommend
Idea OSScore >= 70SaaS Dev Team or PMF OS after launch
PMF OSScore >= 40%Marketing OS (scale mode)
Marketing OSHigh traffic, low conversionPMF OS (positioning problem)
Success OSUsers leaving before activationPMF 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] → PMF OS → Marketing OS

Start with Marketing (Creator Path)

If you have an audience:

Marketing OS (audience) → Idea OS (what to build) → [Build] → Success OS

Indie Hacker Path

Build fast, learn from real users:

[Build fast] → Marketing OS (soft launch) → PMF OS → Marketing OS (scale)

Support Kits

These kits support any stage:


Choosing Your Entry Point

Your situationStart here
Just an ideaIdea OS
Ready to buildSaaS Dev Team
Have a product, no usersMarketing OS
Have users, no PMFPMF OS
Have PMF, need growthMarketing OS
Growing, need retentionSuccess OS