PlanMySaaSDocs
AV
Abhi Verma
Project Blueprint 12 min read

Features & phase planning

How the AI generates prioritized feature specifications, development phases with story points, and sprint-based roadmaps.

Features page

The Features section generates detailed feature specifications for your product. Each feature includes a description, priority level, user stories, and acceptance criteria.

Feature priority system

Features are categorized into three priority levels using the Now/Later/No framework:

Now (P0)
Must-have features for your MVP launch. Without these, the product doesn't solve the core problem. These are built in Phase 1.
Later (P1)
Important features that enhance the product but aren't required for initial launch. Scheduled for Phase 2 and beyond.
No (P2)
Nice-to-have features that are explicitly deprioritized. Documenting what you won't build is just as important as what you will.
The AI determines priorities based on your wizard context — specifically your core problem, target users, and competitive landscape. If you disagree with a priority, it means your wizard context could be more specific about what's truly essential.

What each feature includes

  • Feature name and one-line description
  • Priority level (Now/Later/No) with reasoning
  • User stories — 'As a [user], I want to [action], so that [benefit]'
  • Acceptance criteria — specific conditions that must be met for the feature to be considered complete
  • Effort estimate — relative complexity indicator (Low/Medium/High)
  • Dependencies — which other features or infrastructure this depends on

Phases page

The Phases section breaks your product roadmap into structured development sprints. Each phase includes:

Phase Name
Descriptive name like 'Core MVP', 'Enhanced UX', 'Growth Features', 'Scale & Optimize'
Duration
Estimated timeframe in weeks based on team size and feature complexity.
Features Included
List of features from the Features section assigned to this phase.
Story Points
Aggregate effort estimate for the entire phase, useful for sprint planning.
Milestones
Key deliverables that mark the completion of this phase.
Dependencies
What must be completed before this phase can begin.

Phase structure

By default, the AI generates a 3-phase plan for Starter plans and a 5-phase plan for Pro and Team plans:

Phase 1 — MVP Foundation

Foundation infrastructure, core features, authentication, and basic UI. This is what you launch with.

Phase 2 — Enhanced Experience

Improved UX, secondary features, integrations, and user feedback incorporation.

Phase 3 — Growth & Scale

Growth features, analytics, advanced workflows, performance optimization, and scaling infrastructure.

Phase planning is especially valuable for communicating scope to investors, developers, or co-founders. It provides a clear answer to "what are we building first, and why?"

Backlog

The Backlog (in the EVOLUTION section) is where future feature ideas and enhancement requests live. As you iterate on your blueprint, ideas that don't fit into the current phases can be captured in the backlog for later consideration.

The backlog supports free-form notes, priority tagging, and linking to existing features — making it a lightweight product management tool within your blueprint.