How to write an evidence-backed PRD (the Cursor-for-PMs way)

Why most PRDs are broken

Most PRDs are written as if confident.

They state the problem. Propose a solution. List scope.

They rarely show their work.

Six months later nobody can reconstruct why the bet was made.

An evidence-backed PRD inverts that.

The artefact is downstream of the evidence. If the evidence shifts, the PRD knows.

The four layers

• Layer 1 — The bet. One paragraph. Plain language.
• Layer 2 — Supporting evidence. Every event, ticket cluster, interview quote, and behavioural signal that points toward the bet.
• Layer 3 — Challenging evidence. Counter-signal that argues against the bet, listed honestly.
• Layer 4 — Explicit gaps. The evidence you do not yet have and what would close it.

How Synchronise generates it

As the Cursor for Product Managers, Synchronise reads your live signal and generates each layer with claim-level references back to source.

Layer 2 quotes link to the Intercom ticket.

Layer 3 challenges link to the PostHog cohort that argues the other way.

Layer 4 names the missing study.

The PRD becomes a living object.

When the signal moves, the PRD flags as stale and offers a regenerated version.

A template you can copy today

• Bet — one paragraph.
• Why we believe it — 3–5 evidence cards, each with source.
• Why we might be wrong — 2–3 challenges, each with source.
• Gaps — unknowns and how we would close them.
• Scope and PBIs — inherits the same evidence chain.