π 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)
| Agent |
Role |
| Agents Orchestrator |
Pipeline controller |
| Senior Project Manager |
Spec-to-task conversion |
| Sprint Prioritizer |
Backlog management |
| UX Architect |
Technical foundation |
| Frontend Developer |
UI implementation |
| Backend Architect |
API and database |
| DevOps Automator |
CI/CD and deployment |
| Evidence Collector |
QA for every task |
| Reality Checker |
Final quality gate |
Growth Team (Activated Week 3+)
| Agent |
Role |
| Growth Hacker |
Acquisition strategy |
| Content Creator |
Launch content |
| Social Media Strategist |
Social campaign |
Support Team (As Needed)
| Agent |
Role |
| Brand Guardian |
Brand identity |
| Analytics Reporter |
Metrics and dashboards |
| Rapid Prototyper |
Quick validation experiments |
| AI Engineer |
If product includes AI features |
| Performance Benchmarker |
Load testing before launch |
| Infrastructure Maintainer |
Production setup |
Week-by-Week Execution
Week 1: Discovery + Architecture (Phase 0 + Phase 1 compressed)
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
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
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)
Sprint 1 (Week 2):
βββ 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
Sprint 2 (Week 3):
βββ Continue DevβQA loop for remaining features
βββ Growth Hacker β Design viral mechanics + referral system
βββ Content Creator β Begin launch content creation
βββ Analytics Reporter β Set up tracking and dashboards
βββ Sprint Review at end of week
Week 4: Polish + Hardening (Phase 4)
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
Day 3-4: Reality Check
βββ Reality Checker β Final integration testing
βββ Infrastructure Maintainer β Production readiness
βββ DevOps Automator β Production deployment prep
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)
Week 5: Launch
βββ 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
Week 6: Optimize
βββ Growth Hacker β Analyze and optimize channels
βββ Feedback Synthesizer β Collect early user feedback
βββ Experiment Tracker β Launch A/B tests
βββ Analytics Reporter β Week 1 analysis
βββ Sprint Prioritizer β Plan iteration sprint
Key Decisions
| Decision Point |
When |
Who Decides |
| Go/No-Go on concept |
End of Day 2 |
Studio Producer |
| Architecture approval |
End of Day 4 |
Senior Project Manager |
| Feature scope for MVP |
Sprint planning |
Sprint Prioritizer |
| Production readiness |
Week 4 Day 5 |
Reality Checker |
| Launch timing |
After Reality Checker READY |
Studio Producer |
Success Criteria
| Metric |
Target |
| Time to live product |
β€ 6 weeks |
| Core features complete |
100% of MVP scope |
| First users onboarded |
Within 48 hours of launch |
| System uptime |
> 99% in first week |
| User feedback collected |
β₯ 50 responses in first 2 weeks |
Common Pitfalls & Mitigations
| Pitfall |
Mitigation |
| Scope creep during build |
Sprint Prioritizer enforces MoSCoW β "Won't" means won't |
| Over-engineering for scale |
Rapid Prototyper mindset β validate first, scale later |
| Skipping QA for speed |
Evidence Collector runs on EVERY task β no exceptions |
| Launching without monitoring |
Infrastructure Maintainer sets up monitoring in Week 1 |
| No feedback mechanism |
Analytics + feedback collection built into Sprint 1 |