2-Founder Training App Startup Playbook
Principles
- Optimize for learning speed, not engineering quality.
- Every sprint should answer one product question.
- Keep process minimal since both founders are busy.
- Prioritize user feedback over internal discussion.
- Build the smallest thing that tests the idea.
Phases
1. Problem Discovery
Goal: Confirm a real problem exists. Time: 2–4 weeks
Actions
- Talk to 10–20 potential users
- Understand current training workflows
- Identify frustrations with existing apps
- Explore early ideas in Figma
Outputs
- Clear problem statement
- Defined target user
- Initial prototype flows
Success signal
Users strongly relate to the problem.
2. Solution Prototyping (Figma)
Goal: Validate that the solution makes sense. Time: 4–8 weeks
Actions
- Build interactive Figma prototypes
- Test with 3–5 users per sprint
- Observe users using the prototype
- Iterate quickly
Typical prototype flows
- Create training plan
- Log workout
- View progress
Outputs
- Refined UX
- Validated core user flow
Success signal
Users say “When can I use this?”
3. MVP Build
Goal: Build the smallest usable product.
Time: 6–12 weeks
Rules
- Only build core workflow
- Avoid scaling architecture
- Avoid complex features
Example MVP scope
- Create account
- Create training plan
- Log workouts
- View progress
Outputs
Working app for 10–50 users
4. Early User Testing
Goal: Validate engagement.
Time: 1–3 months
Focus
- Watch how users actually behave
- Identify friction points
Metrics
- Workouts logged
- Weekly active users
- User retention
Outcome
Refine product direction.
5. Product Refinement
Goal: Turn MVP into a strong product. Time: 3–6 months
Focus
- Improve UX
- Remove friction
- Add essential features
- Improve onboarding
6. Growth Phase
Goal: Scale users and business.
Focus
- User acquisition
- Monetization
- Retention
Team Operating System
Sprint Structure
Length: 2 weeks
Each sprint defines one outcome.
Example:
“User can log a workout in under 30 seconds.”
Tasks support the outcome.
Weekly Meeting (30–45 min)
- Wins
- Blockers
- Progress vs sprint goal
- Adjustments
Biweekly Meeting (Sprint Review)
1. Demo
Show what was built.
2. Retrospective
- What worked well?
- What slowed us down?
- What should change?
3. Sprint Planning
- Choose next sprint outcome
- Define 3–6 tasks
- Assign ownership
Backlog Structure
Keep backlog small.
Now
- Current sprint tasks
Next
- Next sprint candidate
Later
- Ideas and experiments
Delete items that stay in Later for months.
Decision Ownership
Avoid decision paralysis.
Example split:
CS Founder
- Architecture
- Infrastructure
- Implementation
Engineering Maths Founder
- Training logic
- Algorithms
- Training science
Shared
- UX
- Product strategy
Monthly Founder Check-In
Once per month (1–2 hours):
Discuss:
- Are we still excited about the idea?
- What have we learned about users?
- Should we change direction?
- Are we solving a real problem?
Key Rule
Every sprint should answer:
What exists in the product in two weeks that doesn’t exist today?
or
What did we learn about users?