Four ways to track prototypes

Pick the lightest approach that gives your client confidence. This app supports all of them.

Option 1 — Prototype Registry

Every feature has a problem, prototype link, and status. Once approved, build exactly that.

Recommended ▼
Purchase Request Problem: Users currently submit Excel forms. Prototype: https://v0.dev/purchase-request-v2 Status: Approved
Prototype Tracker → Purchase Request
Purchase Request
Approved
Problem Excel forms, no audit trail
Prototype v3 — Added attachments
Approved by Jane (Finance) · 12 May

Statuses: Idea → Prototype → Approved → Built → Deployed

Option 2 — Screenshot Approval

Even simpler for SMEs — they understand screenshots better than requirements documents.

▼
Feature: Leave Application Screenshot: /Screenshots/leave-v2.png Notes: Manager approval step added Approved By: HR Manager Approved: 2026-05-15
Screenshots/leave-v2.png
🖼
Leave Application — v2
Manager approval workflow

Store screenshots in the Screenshots/ folder and reference the path in Prototype Version.

Option 3 — Build Ledger

An audit trail for when someone asks: "Was this included in the release?"

▼
2026-05-30 Feature: Purchase Request Prototype: v3 Production: v1.0 Remarks: Approved during client meeting ───────────────────── 2026-06-14 Feature: Purchase Request Prototype: v4 Production: v1.1 Remarks: Attachment upload added post-release

Use Deployments to link each release to the exact prototype version that shipped.

Option 4 — Scope Wallet

Prevents every conversation from becoming new scope — essential for consultant engagements.

▼

Approved Features

  • Login
  • Dashboard
  • Purchase Request

Pending Ideas

  • WhatsApp Integration
  • Mobile App
  • BI Dashboard

Approved features = status Approved or Deployed. Pending ideas = Change Requests with status Proposed.

What we'd personally use for vibe-coding consultancy: Project → Feature → Prototype Link → Approval → Deployment → Change Requests. That's it. No user stories. No epics. The prototype is the contract.