---
title: "Comment by Mohan on \"Don't build an admin panel yet. Save five SQL queries instead.\" | Hashnode"
description: "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"
url: "https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039/comment/6ac7cfecefd59633bc29d10b"
---

[Discussion](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039)

Comment [Don't build an admin panel yet. Save five SQL queries instead.](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039)

[Mohan](https://hashnode.com/@resumeorbitz)

[Oct 8](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039/comment/6ac7cfecefd59633bc29d10b)

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?

[Praneet Brar](https://hashnode.com/@praneetbrar)

[Oct 12](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039/comment/6ac7cfecefd59633bc29d10b#reply-6acc87aa7a388c300a54105e)

Works fine in Supabase's SQL editor if you run it as a role that only has SELECT. Easiest path I've seen: create the read-only role in the SQL editor, grant it SELECT on the tables you need, then open a second connection (TablePlus or psql) as that role when you're poking around. You can also stay in the dashboard editor and just be careful not to run writes — but the separate role makes the "oops" harder.

[Mohan](https://hashnode.com/@resumeorbitz)

[Oct 14](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039/comment/6ac7cfecefd59633bc29d10b#reply-6acf8d19dad2652f499ac47b)

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!

[Praneet Brar](https://hashnode.com/@praneetbrar)

[Oct 19](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039/comment/6ac7cfecefd59633bc29d10b#reply-6ad60af5abb48c964c5077e3)

"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?

[Mohan](https://hashnode.com/@resumeorbitz)

[Oct 22](https://hashnode.com/posts/don-t-build-an-admin-panel-yet-save-five-sql-queries-instead/6ac34c744b60c95f65222039/comment/6ac7cfecefd59633bc29d10b#reply-6ada4efd106819373ed525d2)

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.
