Up to 70% off kits30% off services
PRD Template
A product requirements document you fill in on the page. Each field has a hint and a worked example, eight checks flag what would make it hard to build or price, and it downloads for Word or Google Docs, or copies as Markdown for Notion. Everything stays in your browser.
1.Overview
One paragraph anyone in the company can repeat. If you cannot write it, the product is not clear yet.
A working name is fine.
Who it is for and what it lets them do.
What happens today, and what it costs.
2.Users and roles
Every role you list here needs screens, permissions and tests. Fewer roles, faster launch.
One line per user type, with what they need. One per line.
As a [user], I want to [do something] so that [result]. One per line.
3.Goals and success metrics
How you will know launch worked. Pick numbers you can measure in the first 90 days.
One per line. One per line.
What this version will not do. As important as the goals. One per line.
4.Requirements
Every feature needs a priority. "Must" means launch is pointless without it, not that someone wants it badly.
Launch is pointless without these. One per line. One per line.
Important, but launch works without them for a few weeks. One per line.
Nice to have if time allows. One per line.
How you will check the most important feature works. One per line.
5.Technical notes
Integrations and constraints change the price more than screen count does. Name them early.
Web, iOS, Android, desktop.
Every outside system it talks to. One per line.
Compliance, accessibility, data location, performance. One per line.
6.Plan
A date and a budget turn a wish list into decisions about what to cut.
A date or a number of weeks.
Optional, but it shapes the scope.
What still needs a decision, and who decides. One per line.
Want it turned into a fixed price?30% OFF
Our $349$499 Product Scope turns your PRD into a full spec, a screen list, a clickable flow and one fixed build price in about 5 business days. The fee comes off the build.
How to write a PRD that developers can price
Most PRDs fail in the same few places. When we scope a product, these are the gaps that turn a two-week estimate into a two-month one:
- Start with the problem, not the features. "Shippers email us for every status update" tells a developer more than "add a tracking page".
- Name every user type. Each one needs its own screens, permissions and tests. Three roles cost noticeably more than two.
- Write non-goals. What the first version will not do is the line that protects your budget.
- Keep must haves short. A must have is a feature launch is pointless without. If there are more than eight, some are shoulds.
- Add acceptance criteria to the core flow. "A new shipper can request a quote in under two minutes" is testable. "Easy quoting" is not.
- Name the integrations. Payments, email, a CRM or an ERP each add real work. They move the price more than the number of screens.
- Write down the open questions. With an owner for each, so nobody guesses during the build.
Then sort the requirements with the free MoSCoW prioritization tool. Already have code? Run the code audit checklist before you plan the next version.
Frequently asked questions
What a PRD is, what to include, how long it should be and how to use it.
A product requirements document says what a product or feature has to do, for whom, and how you will know it works, before anyone designs or codes it. A good one is short: the problem, the users, the goals and non-goals, the requirements with priorities, acceptance criteria, and the constraints that shape the build.
At minimum: an overview and the problem, users and roles, user stories, goals with measurable success metrics, non-goals, requirements sorted into must, should and could, acceptance criteria for the core flow, platforms, integrations, constraints, a target date and open questions. This template has a field for each, with a worked example.
Two to four pages. If the must-have list runs past eight items, it is usually not an MVP yet. The checks on this page flag that, along with missing non-goals, unmeasurable goals and a core flow without acceptance criteria.
The PRD says what and why, in words a founder, designer and developer all understand. The technical spec says how: the data model, APIs, services and architecture. Write the PRD first; a developer writes the spec from it.
Yes. Download the Word file to open it in Word or Google Docs, or copy the Markdown and paste it into Notion, Confluence, GitHub or Linear. Headings and bullet lists carry over.
No. The template runs in your browser and nothing is stored or sent. Download or copy your PRD before closing the tab.
Sort the requirements with the MoSCoW prioritization tool, then get it priced. Our $499 Product Scope turns a PRD like this into a full spec with a screen list, a clickable flow and one fixed build price in about 5 business days, and the fee comes off the build.