Skip to content

DesignQA

An AI devtool, from zero to one through 50+ user interviews, with paying customers before launch.

Role
Founder and product designer
Team
Solo from zero to one, then three engineers and a video producer
Timeline
2024
  1. Discovery2024
  2. V1/V2
  3. V3
  4. V4
2026
Problem
Design QA is manual, slow and inconsistent: 10-15 minutes to report each bug, then a guessing game to fix it.
Solution
One-click bug capture in a Chrome extension, then the fix as a real pull request.
Results

30 s

Before · 15 minAfter · 30 s

Time to report a bug

70+

Waitlist signups in a few weeks

3

Paying customers before the MVP shipped


V1: a Chrome extension

Chosen over a Figma plugin, a VS Code extension and a SaaS app: it works wherever the bug is.

V1, the extension menu

The prototype that closed three customers

I demoed this Figma prototype in sales calls, before writing any production code.

From 15 minutes to 30 seconds

Click an element, type a line. The rest is captured automatically.

The V1 promo video

I storyboarded every scene, then hired a producer to shoot it.

V2 and V3: the full issue view

What nobody used came out, and every report got a shareable link.

V2 and V3, the full issue view

V3: can it just fix it?

Reporting isn't the bottleneck; fixing is. Customers kept asking: can it just fix it for me?

V4: edit any website

People weren't reporting bugs; they were redesigning their sites. V4 edits any live site and pushes real code.

Design, describe, and apply

Edit visually, describe changes in plain language, then ship them as one pull request.

V4, the Design tab
V4, the Describe tab
V4, the Changes tab

The bet

Had paying customers, dropped the paywall. I saw the shift to V4 early but moved too late.

Read the full story

Password protected. Ask for access at [email protected]