Why I built Duetpad.
I’m a designer. For a year I built things with AI builders — Lovable, Bolt, v0, Cursor — and got back work that was “close but wrong” about sixty percent of the time. The honest reason: my briefs were vibes. Personas, journeys, jobs-to-be-done lived in Notion docs the AI builders never saw.
I started writing structured briefs by hand. The output got measurably better. But the structured thinking lived in one place and the AI builders read another. I copy-pasted. I lost details. The thinking died on the way over.
So I built Duetpad. It’s a canvas with thirteen typed templates — the ones I reach for most are Problem Statement, Persona, Jobs to be Done, Customer Journey, and Acceptance Criteria. You answer six framing questions; you pair Claude Code; you let Claude Code do the reasoning while the canvas keeps an editable record of every artefact. When you’re ready to ship, you hand the resulting brief to your AI builder — the structure stays intact.
That’s the whole product. It’s small on purpose.