Building in Public #6: Measure, reject, keep
By Peter Coppinger
This week I found the metric I'd been missing, and it reframes everything: how often does a user have to ask twice?
Build time matters, polish matters, but the moment that decides whether someone trusts Vorx is when they ask for a change. If the change lands first time, magic. If they have to repeat themselves, the spell breaks. So I instrumented it: every edit, did a follow-up request come in about the same thing? That repeat rate is now the update-quality number on my wall, and it's already caught its first lie: an attribution bug that made silent misses look twice as common as they were.
Even your measurements need measuring.
The experiments that said no
In the same spirit, I ran a set of speed experiments this week and rejected most of them. A model swap for the escalation path: measured, worse, rejected. The expensive model earns its latency by breaking loops the fast one can't. Fast-model routing for a corrective pass: rejected. It's oddly satisfying writing 'REJECTED' in the log.
Every no is a yes to the system you already have, now with receipts.
Payments in generated apps
The big feature ship: payments in generated apps. Connect Stripe, and Vorx suggests plans, creates them, wires up checkout and subscriptions, and tells the build where the payment screens belong. Testing it end to end, a generated app charging a real test card, was this week's grin moment. 'Build me a business' inches closer to being literal.
Also a proper mobile pass (generated apps and the editor itself: dynamic viewport heights, focus-zoom fixes, all the iOS Safari folklore), and a rebuilt build-status card: I designed ten variants, wired them into a live cycler, and picked a winner. A bounded six-phase rail instead of an endless scrolling step list. Watching a build should feel like progress, not like scrolling a log file.
Next week: a testing push that I suspect will be humbling. The plan is to hammer the builder with real-world builds until the defect list stops growing. I'll report the numbers, whatever they say.
Stay updated: one founder, an army of AI agents, building this in public.
Get each new diary entry by email: the wins, the failures, and the one number we're chasing. No spam, unsubscribe any time.
Shipped this week 8 Aug – 14 Aug
- Payments: Payments setup panel
- Platform: Forms that collect real submissions
Comments