PRD library

The PRD template, section by section

What each section should answer, with a worked example (SplitKaro, a UPI bill-split app).

How to frame a PRD like top PMs

Use this order of thinking before you write a single requirement.

• 1. Problem before solution. Who is hurting, how often, how do you know? Add data or quotes.
• 2. One clear goal. A North Star metric with baseline and target, plus guardrails.
• 3. Say what you won't do. Non-goals stop scope creep.
• 4. Stories with acceptance criteria. "As a…, I want…, so that…" + Given / When / Then.
• 5. Edge cases and states. Empty, error, offline, slow network, accessibility.
• 6. Measure and launch. Experiment design, rollout %, what success looks like in 30/60/90 days.
• 7. Risks and open questions. Each with an owner and a date.
• 8. Keep it short and alive. 2–5 pages, link designs and research, update as decisions change.

120 PRD ideas across 15 industries

Practise framing PRDs for interviews and portfolios. Click Write this PRD with AI to get a full draft, then improve it yourself.

Common PRD mistakes

• ❌ Starting with the solution instead of the user problem and evidence.
• ❌ No measurable goals: 'improve engagement' instead of 'raise D30 retention from 18% to 25%'.
• ❌ Missing non-goals, so scope keeps growing.
• ❌ User stories without acceptance criteria, so engineers and QA guess.
• ❌ Ignoring edge cases, error states, accessibility and privacy (DPDP).
• ❌ Writing a 40-page document nobody reads: keep it skimmable and link details.
• ❌ Not updating the PRD after decisions change; it should be a living document.
• ❌ No owner or date for open questions.

Learn from the best

Trusted guides, real templates and the apps product teams use to write PRDs.

Guides and templates

Apps to write and manage PRDs