<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
The Simple PRD template is for a focused feature or Epic that fits in one or two sprints in a single product area. When in doubt, start here. If your feature spans multiple screens, phased releases, or branching user paths, use the Detailed PRD instead.
How to use this template: Duplicate this page to get started. The headers, callouts, and section structure are the template — each section is filled in with a worked example: a lightweight invite-by-email flow for a fictional Tasklight SaaS product. Replace the example content with your own as you go.
</aside>
What we're building and what success looks like. Include 2-3 measurable objectives.
Ship a lightweight "invite by email" flow to allow end users to add members to their team. This minimum-viable version captures most of the impact in one to two sprints. Workspace owners can paste up to 50 teammate emails right after signing up, see which invites delivered, and track pending acceptances from Settings. Roles, shareable links, and a Google Workspace contact picker are intentionally deferred to later phases of work.
Objectives
What problem are we solving, and what evidence tells us it's worth solving?
Workspace owners can't easily get their team into Tasklight. The current invite UI is buried in Settings, accepts one email at a time, and gives no delivery confirmation. Result: 42% of workspaces are still single-user at Day 30, and single-user workspaces churn at 2.5× the rate of 3+ member workspaces.
[link to Product Discovery Doc]
What's in v1 and what's intentionally deferred. The Out of Scope list should anticipate questions stakeholders will actually ask.
In Scope