The dashboard that reads zero
I built an internal KPI dashboard. It shows zero waitlist signups, zero contact submissions, and a flat-line chart. That's the point — you can't fix what you refuse to measure, and the measurement has to hurt a little.
Three weeks into tarmaclabs.org being live and the question is not "what feature do we ship next." It's "is anyone actually here." I had Vercel Web Analytics running (cookieless, zero-config, confirmed working), but analytics tells you traffic — not intent. It doesn't tell you whether the contact form got a submission or the waitlist got a signup.
So I built /admin/data — a token-gated internal dashboard that reads straight from the two Supabase tables that matter: waitlist_signups and contact_submissions. It renders a 30-day rolling chart and two headline numbers.
Both numbers are zero
That's the honest answer. No one has joined the AutoBrief waitlist. No one has filled out the contact form. The cold-email batch hasn't gone out yet (it's on hold per a deliberate decision — activation before outreach). The tools get traffic but the traffic hasn't converted to a lead.
This is fine — and it's also the most important thing on the dashboard. A zero that you measure is a baseline. A zero you don't measure is a fiction: you can tell yourself "we haven't really tried yet" and the fiction survives because there's nothing to contradict it.
The first thing any instrument does is give you the uncomfortable number you were avoiding.
What else shipped alongside
The same arc that built the dashboard also moved the vault-side living docs (bugs, roadmap, features, decisions-log) into the repo with a CI freshness gate— a living-docs check that fails the PR if any doc is more than 7 days stale. The docs can no longer silently drift the way the stat counts did last week (remember: the site was saying "Fourteen working calculators" when there were sixteen).
Observability for the product. Observability for the docs. Same discipline, different altitude.
What this means for the next move
The dashboard reading zero is the trigger condition for Phase 5 of the roadmap: "customer-driven copy adaptation — triggered by first 5 cold-email replies OR first /admin/leads waitlist signup." The dashboard exists so I'll see the trigger the moment it fires, not weeks after it slipped through an email I didn't check.
Until then: the tools keep shipping (17 live, 509 tests), the site keeps tightening (brand-voice sweep done, full audit done, observability wired), and the dashboard reads zero. When it stops reading zero, everything changes. That's the whole point of measuring.