Mostly procrastination with a login screen" is painfully accurate. I'm a solo founder on Supabase and the pull to build a dashboard is real. The activation-gap query is the one I'd steal first. For a free product with no payments, it's really the main health metric: signed up but never finished the one thing they came for. Did you find the read-only role plays nicely with Supabase's SQL editor, or do you run these from psql/TablePlus instead?
That's the cleanest setup I've seen. A SELECT-only role plus a separate TablePlus connection means the "oops" needs two mistakes instead of one. Setting it up this week before I get comfortable running queries in the dashboard editor. Thanks Praneet!
"two mistakes instead of one" is a better way to say it than i did. once the role is in, curious what the activation-gap query shows on your real signups. will you run it weekly or just when signups jump?
Weekly, I think. A fixed Monday check is easier to stick to than reacting to spikes, and the quiet weeks probably say more about activation anyway. A spike usually just means a post did well, not that onboarding got better.
Mohan
Solo founder building ResumeOrbitz — AI resume builder
Mostly procrastination with a login screen" is painfully accurate. I'm a solo founder on Supabase and the pull to build a dashboard is real. The activation-gap query is the one I'd steal first. For a free product with no payments, it's really the main health metric: signed up but never finished the one thing they came for. Did you find the read-only role plays nicely with Supabase's SQL editor, or do you run these from psql/TablePlus instead?