10 templates included free. Pick one and start.
Every template shapes the AI interview, the document structure, and the level of detail so you get exactly the document your team needs. All templates included on every plan.
Templates aren't just formatting. They're smarter interviews.
Templates don't just change the output format. They change the entire interview.
Focused interviews
Each template defines the questions the AI asks. A Lean interview skips formal risk analysis; a Technical spec skips business strategy. You only answer what's relevant.
Consistent structure
Every document generated from the same template has the same section layout, making it easy for your team to review and compare documents across projects.
Best-practice prompts
Templates include tailored AI prompts that guide the generation. The AI knows what "good" looks like for each section and writes accordingly.
Right-sized output
A Lean document is concise. A Comprehensive document is thorough. Templates ensure the depth of the document matches the needs of your project.
Explore our templates
Ten purpose-built templates available today. Each one is designed for a specific workflow and team.
Project Charter
Establish authority, scope, and governance
A formal project charter that establishes authority, scope, stakeholders, and success criteria. Built for project kickoffs and executive approvals where governance and clarity matter. Defines who is responsible, what is in and out of scope, and how success is measured.
Best for:
Project kickoffs, executive approvals, cross-functional initiatives, PMO governance
- Clear scope boundaries with explicit in/out of scope sections
- Stakeholder mapping with roles, concerns, and governance
- Risk assessment with mitigation strategies and hard constraints
- Formal approval section to authorize project kickoff
Feature Request
From idea to actionable request in minutes
A structured feature request document with business justification, user impact analysis, and testable acceptance criteria. Built for internal IT requests and product feature proposals. Give your engineering team everything they need to evaluate, prioritize, and implement.
Best for:
Internal IT requests, product feature proposals, enhancement tracking, stakeholder submissions
- Fastest template, typically complete in about 10 minutes
- Quantified user impact with benefit analysis
- Clear, testable acceptance criteria for each feature
- Built for handoff to technical teams who need actionable specs
RFC / Design Decision
Document, evaluate, and align on technical choices
A request for comments or design decision record that documents the problem, proposed solution, alternatives considered, trade-offs, and rollout plan. Built for engineering teams making architectural decisions that need team alignment and a permanent record of reasoning.
Best for:
Architecture decisions, design proposals, technical RFCs, ADRs, team alignment on approach
- Documents alternatives considered with honest trade-off analysis
- Includes migration strategy and rollback planning
- Open questions section drives productive team reviews
- Creates a permanent record of architectural decisions
Lean Canvas
Move fast, validate faster
Inspired by Lean Startup methodology, this template focuses on hypotheses, experiments, and minimum viable features. It strips away the formality and zeroes in on what matters most: the problem, the solution, and how you'll know if it works.
Best for:
Startups, MVPs, rapid prototyping, agile development
- Fastest template, complete in under 20 minutes
- Built around testable hypotheses, not assumptions
- Defines clear MVP scope to prevent scope creep
- Perfect for pitch decks and investor conversations
Technical Specification
Architecture-first, engineer-ready
A deep-dive technical document for engineering teams. Covers system architecture, API design, data models, infrastructure, performance requirements, and security considerations. The output reads like a real tech spec your team can implement from.
Best for:
Technical projects, API development, system architecture, engineering handoffs
- Generates detailed architecture descriptions
- Includes API endpoints, data models, and schemas
- Covers non-functional requirements (performance, security, scaling)
- Engineers can start implementing directly from the output
User Story Focus
Epics, stories, and acceptance criteria
Built for agile teams running Scrum or Kanban. Organizes requirements as epics and user stories in standard "As a... I want... So that..." format, each with acceptance criteria, priority, and story point estimates. Drop the output straight into Jira or Linear.
Best for:
Agile teams, sprint planning, feature development, Scrum projects
- Stories follow the standard As a / I want / So that format
- Includes Gherkin-style acceptance criteria for each story
- MoSCoW prioritization built in
- Output maps directly to sprint backlog items
Marketing Requirements Document
Market context, buyer personas, and positioning
A strategic marketing document that defines the target market, competitive landscape, product positioning, and go-to-market themes. Built for product marketing teams who need to align product strategy with market opportunity and craft messaging that resonates with buyers.
Best for:
Product marketing, go-to-market planning, competitive positioning, launch strategy
- Detailed buyer persona and segment analysis
- Competitive matrix with differentiation insights
- Structured positioning and messaging framework
- GTM strategy with phased launch approach
Business Requirements Document
Business objectives, stakeholders, and ROI
An enterprise-grade business document that justifies an initiative with clear objectives, stakeholder mapping, process analysis, and financial justification. The go-to format when you need executive buy-in and cross-functional alignment before starting a project.
Best for:
Enterprise initiatives, business process changes, investment decisions, stakeholder alignment
- Stakeholder mapping with influence and engagement strategies
- Current-state / future-state process analysis
- Financial justification with ROI and payback period
- Risk assessment with mitigation strategies
Functional Requirements Document
Detailed specs, system flows, and UI behavior
A precise functional specification that describes exactly what the system must do: inputs, processing, outputs, screen behavior, and error handling. Bridges the gap between business requirements and technical implementation, giving developers and QA engineers everything they need.
Best for:
System design handoffs, BA-to-dev communication, detailed feature specs, QA test planning
- Numbered functional requirements with input/output specs
- Process flows with alternate and exception paths
- Screen-level behavior specs with field validations
- Complete error handling catalog
Software Requirements Specification
Formal IEEE 830 specification with traceability
A formal requirements specification following IEEE 830 / ISO 29148 standards. Uses precise "shall" language, numbered requirement IDs, verification methods, and a traceability matrix. The standard for regulated industries, government contracts, and safety-critical systems where every requirement must be auditable.
Best for:
Regulated industries, government contracts, safety-critical systems, formal verification processes
- IEEE 830 / ISO 29148 compliant structure
- Formal "shall" / "should" / "may" requirement language
- Traceability matrix linking requirements to objectives and tests
- Built-in verification and validation methods
Quick comparison
Not sure which template to pick? Here's a side-by-side look.
Build your own templates
Need a format we don't cover? Upload a .docx or Markdown file and our AI will analyze its structure, extract sections, and generate tailored interview prompts, giving you a fully custom template in minutes. Available on Pro and Enterprise plans.
Every template. Every format. Start free.
Create your first document free, no credit card required. Upgrade to Pro when you're ready for unlimited docs.