Product Roadmap
Decision Tree: After the MVP
The roadmap is divided into three phases: Audience Discovery (Pre-MVP), MVP Validation Phase, and Post-MVP Platform Investment. Audience discovery selects the MVP audience. The MVP phase is time-bound and signal-gated, not feature-driven. Post-MVP work depends on what we learn from validation.
Phase 1: Audience Discovery (Pre-MVP)
This phase uses surveys, interviews, and content-led outreach to answer: Who has the strongest pain today? Who shows urgency, not curiosity? Who describes the problem in their own words?
At this stage, there is no MVP per audience. There is no product differentiation yet. The output of this phase is a decision, not a product.
Decision Gate: "This is the audience we will test first."
Decision Gate: Select MVP Audience
Phase 2: MVP Validation (March 2026)
Once an audience is selected, the MVP becomes intentionally narrow. The MVP is not designed to serve every surveyed audience. It is designed to test one audience deeply.
Single end-to-end use case per audience (workplace communication for non-English speakers, pitching/fundraising for founders). Minimal content to trigger practice, AI feedback, optional paid human practice sessions. Direct payment, simple scheduling, basic feedback collection.
What we validate: Will this selected audience pay for live human practice?
This phase uses validation-first language: we observe, learn, and decide based on signals. The MVP is time-bound and signal-gated, not feature-driven. Engineering effort increases only after learning reduces risk.
MVP Validation Results
Phase 3: Post-MVP Platform Investment
If validated, the following can be layered on as conditional next steps. This phase uses build-first language: we build, integrate, scale, and optimize. These features belong to post-MVP platform investment, not the validation phase.
If Validated: Platform Expansion
Platform Integration & Expansion
- Build additional practice scenarios (presentations, negotiations, team meetings)
- Integrate multiple session types and lengths
- Scale enhanced feedback and progress tracking
- Build coach profiles and matching systems
- Optimize repeat user features and retention tools
- Integrate with existing writing system
Builds on validated core: paid human practice works for professional communication.
Full Platform Vision
- Scale to broader audiences (K-12, casual learners, academic prep)
- Build subscription models and pricing tiers
- Optimize marketplace and coach network
- Build high-production instructional content libraries
- Integrate advanced analytics and personalized learning paths
- Scale cohort-based programs and long-form courses
Full platform vision, built on validated foundation. These are conditional next steps that depend on what we learn from the MVP validation phase.
If Not Validated: Learn and Pivot
If the MVP shows people won't pay for live human practice, that's valuable learning. It tells us:
- Maybe the audience needs to be different
- Maybe the value proposition needs adjustment
- Maybe the format or pricing needs to change
- Maybe AI-only tools are preferred
The MVP is designed to give clear signals, whether positive or negative. Both outcomes inform next steps.
Key Principle
The MVP Validation Phase exists to reduce uncertainty. We observe, learn, and decide based on signals. Every feature in Post-MVP Platform Investment depends on what we learn from validation.
We can't plan platform expansion in detail until we know whether the foundation works. That's why the MVP is so focused: it needs to give us clear, actionable answers. Engineering effort increases only after learning reduces risk.