You came for a product brief template: one page, seven headings, something to paste in and fill out before anyone writes a full PRD. It's right below — take it. A good brief is the cheapest alignment a team ever buys, because it's short enough to read and early enough to change. But here's the catch nobody warns you about: a brief is true for about a week. The PRD grows past it, decisions get made that contradict it, and the one page that was supposed to be the source of truth becomes the first thing that's wrong. Draftlize keeps the brief one page — and makes the decisions inside it cards that link to the PRD downstream and flag themselves stale the moment a dependency moves.
This is the whole product brief. It fits on a page on purpose — a brief you have to scroll is a PRD wearing a smaller name tag. Use it in a doc, a wiki, or a markdown file for early alignment, before the idea earns a full spec. The section after this one is about what changes when the brief stops being frozen text and starts staying current on its own.
The pain, in one or two plain sentences — who hurts and how often. Not the solution wearing a problem costume. If you can't state the problem without naming your feature, you're briefing a solution looking for a justification.
The specific person this is for. "Solo founders shipping with an AI agent," not "users." A brief that's for everyone is for no one, and every later trade-off gets easier the narrower this is.
What changed that makes this worth doing this quarter and not last year — a new capability, a shift in the market, a cost that finally dropped. The section that separates a real bet from a someday-list item.
The approach in a paragraph, not a spec. Enough that a reader pictures the same thing you do, vague enough that you haven't pre-committed every detail before you've decided it's worth building.
The one number that tells you this worked, with a target. "40% of new projects seed a brief in week one." If you can't name the metric, you can't tell shipped from succeeded.
What's in for v1, and — more importantly — what you are deliberately not doing. Non-goals are where briefs earn their keep: they end the "while we're at it" conversations before they start.
The decisions you haven't made yet, named honestly. A brief that pretends everything is settled is lying. These are the items that graduate into real decisions — and, downstream, into the PRD.
That's the brief. Below: why the page goes out of date the week after you write it — and what we do about it.
A brief captures the idea at its earliest, fuzziest moment — which is exactly its job. But it's a photograph, not a feed. The product keeps moving; the brief doesn't. By the time the PRD exists, half the brief is the team's first guess, and nobody goes back to mark which half.
The brief is supposed to be the seed the PRD grows from. But once the PRD takes over, the two drift: a scope call changes in the spec, the brief still says the old thing, and a new teammate reads the brief, builds the wrong mental model, and only finds out in review. Nothing connects the page to what came after it.
Open questions get answered — in a Slack thread, in someone's head, in a meeting nobody minuted. The decision happens; the brief never hears about it. So the one document meant to hold the early thinking quietly stops reflecting what the team actually decided, and stops being worth opening.
In Draftlize the brief isn't a blank page — it's the same seven sections as typed cards: Problem, Target user, Why now, Proposed solution, Success metric, Scope & non-goals, Open questions. Each is addressable by ID and citable from a PRD or a thread, so the brief stays the front door instead of becoming a relic.
An open question becomes a decision; the decision feeds the PRD; the PRD cites the brief. They're one connected graph, not three documents that fell out of touch. Change a scope decision and every card that rested on it — in the brief and in the PRD template below it — flags itself stale automatically, the way a build system invalidates everything downstream of a changed file.
Claude Code or Cursor, over MCP, reads the brief before it drafts the PRD and writes resolved questions back into the same shape. The brief stops being a doc a human skims once at kickoff and becomes context an agent reads on every turn — so the one page stays one page, and stays true.
A brief's whole value is being short and early. Its whole problem is that short, early documents are the first to fall out of date.Keep the one page. Let the substrate keep it current.
A product brief is a one-page summary written before a full PRD — the problem, the target user, the goal, the rough scope, and the key risks. It is the cheapest alignment a team buys, because it is short enough to read and early enough to change before anyone invests in a detailed spec.
A brief is one page and comes first: it aligns everyone on the problem and the bet before the work is scoped. A PRD comes after and goes deep: the requirements, the behavior, the details. The brief earns the PRD — if the one page does not convince anyone, the idea is not ready for a full document.
Usually seven parts: a one-line summary, the problem, the target user, the goal or success metric, the proposed approach, the scope and non-goals, and the open questions or risks. Keep it to a page — a brief you have to scroll is a PRD wearing a smaller name tag.
A brief is usually true for about a week: the PRD grows past it and decisions contradict it. Draftlize keeps the brief one page but makes the decisions inside it cards that link to the PRD downstream — so when a scope decision changes, the brief and everything built on it auto-flag stale instead of silently going wrong.
Take the template above, or spin up a project and let the agent draft the brief from a paragraph of your idea — then carry it into the PRD and keep every decision, and everything that depends on it, current for you.
Start free with $5One click creates a project with these exact sections as typed, linked cards. Answer them with the agent — and when a decision changes later, every dependent section flags stale instead of silently drifting. $5 free credit on signup, no card required.