PM Tooling · Built with Lovable

ProductPilot — AI Product Thinking & PRD Workspace

An AI product documentation and handoff workspace for PMs. ProductPilot forces a raw product idea through discovery and gap-resolution before it's allowed to become a PRD — then auto-generates user flows, wireframes, architecture and cross-functional handoff docs, all tied back to the same PRD with traceability and change-impact tracking.

Role
Solo builder — problem to working prototype
Method
Workflow design, PRD architecture, prompt engineering
Scope
PM tooling — idea-to-PRD workspace
The problem

PRDs get written before the thinking is done

The easiest way to write a weak PRD is to skip straight from an idea to a document. I wanted a workspace that structurally prevents that — one that won't let a product move to "Generate PRD" until assumptions have been challenged and gaps have been named, not just implied.

Solution

A nine-step workflow, in order, every time

Every product in ProductPilot moves through the same sequence — discovery and gap-resolution are gates, not optional steps, before a PRD can be generated.

01 · Idea
Capture — a raw product idea enters the workspace as a seed, not a spec.
02 · Discover
Discovery — structured questions surface who has the problem and why it matters now.
03 · Challenge
Challenge assumptions — the workspace pressure-tests the idea's weakest claims before they get built on.
04 · Identify gaps
Gap identification — missing evidence, success metrics or edge cases are named explicitly.
05 · Resolve gaps
Resolution — each open gap has to be closed or consciously deferred, not silently dropped.
06 · Customize
Customize PRD sections — the PRD's structure is tailored to what this specific product actually needs documented.
07 · Generate
Generate PRD — the PRD is produced from the resolved discovery work, not from a blank template.
08 · Review
Review — a pass to check the generated PRD against the original discovery findings.
09 · Measure
Measure readiness — a live readiness score tracks whether the product is actually ready to leave discovery.
What it produces

More than a document — artifacts, handoffs and a readiness score

ARTIFACTS

User flows, wireframes & architecture, generated together

Each product's artifacts live alongside its PRD instead of scattered across separate tools, so a flow change and a PRD change stay in sync.

HANDOFF

Three handoff views from one PRD

The same PRD reshapes into an Engineering view, a Design view and a GTM/Marketing view — each surfacing what that function actually needs, not the whole document.

READINESS

A readiness score tied to open gaps

Every product carries a live readiness percentage driven by its unresolved gaps — a visible signal for whether a PRD is genuinely ready, not just written.

TRACEABILITY

Change-impact tracking, not a static export

Every flow, wireframe and handoff doc stays tied back to the PRD it came from — so editing a requirement surfaces exactly which downstream artifacts are now out of date.

Prototype

A working workspace, not just a workflow diagram

ProductPilot is built and live — the dashboard, discovery flow, gap resolution, PRD generation and readiness scoring all work end to end in the prototype below, seeded with three demo products.

Live prototype — ProductPilot Open full screen ↗
Open interactive prototype ↗
Process

Designed the workflow before designing the interface

Discovery
Problem discovery — started from watching PRDs skip straight from idea to document, and what breaks downstream when they do.
Flow
Workflow architecture — mapped the nine-step gate sequence so discovery and gap-resolution couldn't be bypassed.
Prompts
Prompt engineering — wrote the prompts that challenge assumptions and surface gaps, then generate the PRD from resolved discovery output.
Output
Build — shipped a working, clickable workspace on Lovable, seeded with three demo products to prove the flow end to end.