Skip to main content

Runbook: Startup MVP Build

Mode: NEXUS-Sprint | Duration: 4-6 weeks | Agents: 18-22

Scenario

You’re building a startup MVP — a new product that needs to validate product-market fit quickly. Speed matters, but so does quality. You need to go from idea to live product with real users in 4-6 weeks.

Agent Roster

Core Team (Always Active)

Pipeline & PM

  • Agents Orchestrator
  • Senior Project Manager
  • Sprint Prioritizer

Engineering

  • UX Architect
  • Frontend Developer
  • Backend Architect
  • DevOps Automator

QA

  • Evidence Collector
  • Reality Checker

Growth Team (Activated Week 3+)

  • Growth Hacker
  • Content Creator
  • Social Media Strategist

Support Team (As Needed)

  • Brand Guardian
  • Analytics Reporter
  • Rapid Prototyper
  • AI Engineer (if product includes AI features)
  • Performance Benchmarker
  • Infrastructure Maintainer

Week-by-Week Execution

Week 1: Discovery + Architecture

1

Day 1-2: Compressed Discovery

  • Trend Researcher → Quick competitive scan (1 day, not full report)
  • UX Architect → Wireframe key user flows
  • Senior Project Manager → Convert spec to task list
2

Day 3-4: Architecture

  • UX Architect → CSS design system + component architecture
  • Backend Architect → System architecture + database schema
  • Brand Guardian → Quick brand foundation (colors, typography, voice)
  • Sprint Prioritizer → RICE-scored backlog + sprint plan
3

Day 5: Foundation Setup

  • DevOps Automator → CI/CD pipeline + environments
  • Frontend Developer → Project scaffolding
  • Backend Architect → Database + API scaffold
  • Quality Gate: Architecture Package approved

Week 2-3: Core Build (Phase 2 + Phase 3)

  • Agents Orchestrator manages Dev↔QA loop
  • Frontend Developer → Core UI (auth, main views, navigation)
  • Backend Architect → Core API (auth, CRUD, business logic)
  • Evidence Collector → QA every completed task
  • AI Engineer → ML features if applicable
  • Sprint Review at end of week

Week 4: Polish + Hardening (Phase 4)

1

Day 1-2: Quality Sprint

  • Evidence Collector → Full screenshot suite
  • Performance Benchmarker → Load testing
  • Frontend Developer → Fix QA issues
  • Backend Architect → Fix API issues
  • Brand Guardian → Brand consistency audit
2

Day 3-4: Reality Check

  • Reality Checker → Final integration testing
  • Infrastructure Maintainer → Production readiness
  • DevOps Automator → Production deployment prep
3

Day 5: Gate Decision

  • Reality Checker verdict
  • IF NEEDS WORK: Quick fix cycle (2-3 days)
  • IF READY: Proceed to launch
  • Executive Summary Generator → Stakeholder briefing

Week 5-6: Launch + Growth (Phase 5)

  • DevOps Automator → Production deployment
  • Growth Hacker → Activate acquisition channels
  • Content Creator → Publish launch content
  • Social Media Strategist → Cross-platform campaign
  • Analytics Reporter → Real-time monitoring
  • Support Responder → User support active

Key Decisions

Decision PointWhenWho Decides
Go/No-Go on conceptEnd of Day 2Studio Producer
Architecture approvalEnd of Day 4Senior Project Manager
Feature scope for MVPSprint planningSprint Prioritizer
Production readinessWeek 4 Day 5Reality Checker
Launch timingAfter Reality Checker READYStudio Producer

Success Criteria

MetricTarget
Time to live product≤ 6 weeks
Core features complete100% of MVP scope
First users onboardedWithin 48 hours of launch
System uptime> 99% in first week
User feedback collected≥ 50 responses in first 2 weeks

Common Pitfalls & Mitigations

Scope Creep During BuildMitigation: Sprint Prioritizer enforces MoSCoW — “Won’t” means won’t
Over-Engineering for ScaleMitigation: Rapid Prototyper mindset — validate first, scale later
Skipping QA for SpeedMitigation: Evidence Collector runs on EVERY task — no exceptions
Launching Without MonitoringMitigation: Infrastructure Maintainer sets up monitoring in Week 1
No Feedback MechanismMitigation: Analytics + feedback collection built into Sprint 1

Build docs developers (and LLMs) love