The point of the roadmap is not to predict the future. It is to prevent two common failure modes: overbuilding and stalling.
When a part-time team builds without a phase goal, it drifts into “random progress” and eventually disbands. When a team builds with phase goals, the work becomes legible: each phase ends with a proof point that unlocks the next phase.
The phases
Setup (1 week), Kick-off (2–3 weeks), Proto Dev (8–10 weeks), Product Dev (8–10 weeks), Launch (4–6 weeks). Each phase has one job: produce the smallest visible proof that the team is real and momentum is increasing.
Time commitments (realistic)
The journey is designed around constraints: founders working nights and weekends, contributors donating a few hours per week, and a coach guiding structure.
| Phase | Founder | Coach |
|---|---|---|
| Setup | 3–5 hrs/week | 5–8 hrs/week |
| Kick-off | 5–10 hrs/week | 8–10 hrs/week |
| Proto Dev | 8–10 hrs/week | 5–8 hrs/week |
| Product Dev | 8–10 hrs/week | 3–5 hrs/week |
| Launch | 5–10 hrs/week | 1–3 hrs/week |
If your availability is lower than this, reduce scope. If your availability is higher, keep scope minimal and ship faster instead of expanding complexity.
Run it in SeedStart
The roadmap only works when it is visible. Use the platform to publish roles, track work, run rituals, and recognize contributors.