Proofavo — build in public, week of Aug 17

Shipped this week: review reminders the shop writes in its own words — you set the wording and the timing, and the product tracks reminders sent and reminders spared. Behind that, the operator back-office, so when a shop writes in I can actually answer them instead of staring at a database. And I got the product listed on the first directories: BetaList, AlternativeTo, Smol Launch, Capterra, Crunchbase.

Numbers this week:

Waitlist: 0
Beta workspaces: 0
Reviews completed: 0
First-ever Google impressions: 3. Clicks: 0.

That's the whole scoreboard. The product works; nobody has arrived yet.

What went wrong: a change I made four days ago quietly widened who could record an approval. It's fixed, and with zero workspaces live, nobody was exposed — but the thing that stings isn't the mistake. It's that my own test suite had been failing about it since the moment I made it, and I didn't run it for four days. A test nobody runs isn't a test.

What I learned: it turns out I'd already "closed" that same hole once before — with a one-line fix I was certain about, and never checked whether it did anything. It didn't. Being sure and having checked feel identical from the inside, and only one of them is worth anything.

The founding offer still stands: 50% off the list price for the first 50 waitlist places, for as long as the subscription stands. All fifty places are, at time of writing, available.

Demo if you want to poke around: https://proofavo.com/demo

For those of you doing client review workflows: what's the one step your clients always get stuck on?