Prompt for a SaaS dashboard
An example prompt for a SaaS dashboard
A good prompt for a SaaS dashboard names who uses it, the main things they create or manage, the rule that must never break, and what to leave out for now. Here is one you can paste and edit: "Build a churn and revenue dashboard for subscription businesses. It needs: organisations and memberships, roles and permissions, usage metering and limits, audit log, api keys and public api and admin analytics dashboards. Rule that must always hold: every org-owned table carries org_id with a Postgres RLS policy keyed to a per-request setting, and all data access goes through withOrg() which verifies membership first. Leave out for now: no dashboards that query raw event tables and no entitlement changes from client redirects, only from verified webhooks."
Last checked
Starter prompt
Build a churn and revenue dashboard for subscription businesses. It needs: organisations and memberships, roles and permissions, usage metering and limits, audit log, api keys and public api and admin analytics dashboards. Rule that must always hold: every org-owned table carries org_id with a Postgres RLS policy keyed to a per-request setting, and all data access goes through withOrg() which verifies membership first. Leave out for now: no dashboards that query raw event tables and no entitlement changes from client redirects, only from verified webhooks.
Replace the first sentence with your own idea. The list of needs stays useful whatever the niche, because it comes from what a SaaS dashboard has to do.
Two variations
- Build a usage and billing portal for an API product. Start with organisations and memberships and roles and permissions, and add usage metering and limits once those work.
- Build a team analytics workspace for a design agency. People should be able to an immutable who-did-what-when record for security, support and enterprise buyers.
Words that help Forge AI recognise the category
Forge AI picks a reference architecture from how you describe the app. These phrases point to a SaaS dashboard: saas, saas dashboard, saas platform, multi-tenant, multi tenant, b2b saas, admin dashboard and subscription billing.
What the plan decides for you
- Organisation-scoped tenancy enforced by RLS plus one helper.
- Append-only partitioned audit log written in the same transaction.
- Transactional outbox for signed outbound webhooks.
What to ask for in a later prompt
This is a reference design for the category, not a promise that every item is generated today. Built-ins such as email, background jobs, file uploads and search are coming soon, so anything here that needs them is something you add yourself for now.
- Custom roles and fine-grained permissions: four fixed roles cover most teams.
- Dedicated event bus for webhooks and ingest: Postgres queue is simpler and sufficient.
- Read replicas for dashboards and audit: primary handles phase-1 load.
- Columnar analytics store: pre-aggregated rollups are enough early on.
FAQ
- How detailed should a prompt for a SaaS dashboard be?
- Name the users, the main objects, one rule that must always hold and one thing to leave out. The plan fills in the rest, and you can change it before generation.
- Which words tell Forge64 this is a SaaS dashboard?
- Phrases such as saas, saas dashboard, saas platform and multi-tenant point to this category.
- Can I change the app after the first build?
- Yes. Describe the change in plain English and Forge AI edits the app; the quality gate checks the code again.
Build your app with Forge64
One prompt to a running app with auth, database, hosting and payments. Start free, no credit card required.
Start building for free