If your SaaS metrics live in your database but you need an engineer every time you want to check MRR, something is broken. Not in your product — in your workflow.
This guide shows you how to track MRR, ARR, and expansion revenue directly from your database — no SQL required, no analyst on standby, no waiting three days for a query to run.
Why Most Teams Struggle to Track MRR From Their Database
Your subscription data is already in the database. Stripe webhooks write to it. Your billing tables have everything: plan changes, cancellations, upgrades, trial conversions. The information exists — you just can't get to it easily.
The traditional options are bad. You can hire a data analyst (expensive, slow). You can use a BI tool like Metabase or Looker (requires SQL to set up, then SQL every time you want to tweak a filter). Or you copy data into a spreadsheet manually (that's not tracking, that's archaeology).
The actual problem: SQL is a barrier for most operators. You know what you want to know — 'what's our MRR this month vs last month, broken down by plan' — but writing the JOIN across subscriptions and invoices and plan changes takes someone who knows what they're doing.
What MRR Tracking Actually Requires
To calculate MRR reliably, you need at minimum:
— Active subscriptions at end of each period — Subscription amounts (monthly-normalized if annual) — New MRR (new customers that month) — Expansion MRR (upgrades) — Churned MRR (cancellations) — Contraction MRR (downgrades)
All of this lives in your billing tables. The catch is that querying it correctly requires understanding date logic, handling annual-to-monthly normalization, and aggregating across plan changes mid-period. That's 4–6 JOINs on a good day.
How to Query MRR From Your Database in Plain English
Tools like AI for Database (aifordatabase.com) let you skip the SQL entirely. You connect your database — PostgreSQL, MySQL, Supabase, PlanetScale, whatever you're running — and ask questions directly:
'What was our MRR at the end of last month?'
'Show me new MRR vs churned MRR for each month this year.'
'Which plan has the highest expansion MRR in Q2 2026?'
The tool translates your question into SQL, runs it, and returns the result in plain English or as a table you can work with. No SQL knowledge required on your end.
This matters for two groups: founders who want a quick answer without opening a SQL client, and operators — heads of CS, RevOps, growth — who need to track these metrics daily but aren't engineers.
Build a Self-Refreshing MRR Dashboard
One-off queries are useful. But for MRR tracking, you want a dashboard that updates automatically so your team always has current numbers — not 'MRR as of whenever someone last ran a query.'
With AI for Database, once you've asked your MRR question and confirmed the answer looks right, you can save it as a dashboard widget. The dashboard refreshes on a schedule (hourly, daily, or on-demand), pulling fresh numbers from the live database each time.
A practical SaaS MRR dashboard typically has:
— Total MRR (current month) — MRR growth % vs last month — New MRR, Expansion MRR, Churned MRR (waterfall view) — ARR (MRR × 12) — MRR by plan tier — Top 10 customers by MRR
None of these require writing a single line of SQL to set up or maintain. You describe what you want, the tool generates the query, and the dashboard stays live.
ARR: Derive It From MRR or Track It Directly
For most SaaS companies at early stages, ARR = MRR × 12. If you have annual contracts, it's slightly more nuanced: you want the sum of all active annual subscription amounts (not monthly-normalized) plus monthly subscriptions × 12.
You can ask: 'What is our current ARR including annual subscriptions at their actual contract value?'
If your database has the contract value stored separately from the billing interval, the query needs to handle that split. AI for Database will ask for clarification if it needs to, or you can specify in natural language: 'ARR = sum of annual contract values plus monthly subscriptions times 12.'
Once you have that query working, save it to your dashboard. Done.
Automate MRR Alerts Without Zapier
Beyond tracking, you probably want to know when something changes. MRR drops 10% week-over-week. A high-value customer churns. A customer upgrades from Starter to Pro.
AI for Database supports action workflows: you define a condition based on a database query, and it triggers an action — a Slack message, email, or webhook — when that condition is met.
Example workflow: 'If total MRR this week is more than 8% below last week, send a Slack alert to #revenue-alerts.' No Zapier needed. No middleware. The trigger runs directly against your database.
This is useful for operators who manage revenue health but aren't watching a dashboard all day. Set the alert once, get notified when it matters.
Comparison: How Other Tools Handle MRR Tracking
Metabase
Requires SQL to set up questions. If you know SQL, Metabase works fine for MRR dashboards. If you don't, you need someone to build the questions for you — and they need to be updated every time your schema changes.
Chartmogul / Baremetrics
Dedicated SaaS metrics tools. They pull from Stripe directly (not your database), so they only see what Stripe sees. If your source of truth is your database (e.g., you have custom billing logic, usage-based pricing, or multi-product subscriptions), these tools will give you incomplete numbers.
Looker / Tableau
Enterprise BI tools. Powerful, but require a data model to be built upfront (usually by a data engineer), cost significantly more, and are overkill for a team that needs basic MRR tracking.
aifordatabase.com
Connects directly to your database. No SQL required to query. Dashboards refresh automatically. Supports action workflows for alerts. Works whether your billing data comes from Stripe, Paddle, custom billing, or any combination. Best fit for small-to-mid SaaS teams who want direct database access without the BI overhead.
Frequently Asked Questions
I don't have a data analyst. Can I still build an MRR dashboard?
Yes. That's exactly what AI for Database is built for. You connect your database, ask questions in plain English, and the tool handles the SQL. No analyst required.
My MRR data is in Stripe, not my database. What should I do?
You have two options: use a dedicated Stripe metrics tool (Baremetrics, Chartmogul), or sync your Stripe data to your own database using something like Airbyte or a Stripe webhook handler. Once it's in your database, AI for Database can query it. Keeping MRR data in your own database gives you more flexibility for custom metrics.
What databases does this work with?
AI for Database supports PostgreSQL, MySQL, Supabase, PlanetScale, SQLite, MongoDB, MS SQL Server, BigQuery, and others. If your billing data lives in any of these, you can start tracking MRR today.
Can I share the MRR dashboard with my team?
Yes. Dashboards can be shared with your team so everyone has access to the same live numbers — no need to screenshot and paste into Slack every Monday.
How to Get Started
1. Connect your database at aifordatabase.com. Takes about 2 minutes — you just provide your connection string.
2. Start with one question: 'What is our MRR this month?' See what the tool returns. If the numbers look off, you can clarify in plain English.
3. Build your dashboard. Add MRR, ARR, churn, expansion one widget at a time. Set the refresh schedule.
4. Set up an alert. Define one condition — like MRR dropping week-over-week — and connect it to Slack or email.
The whole setup takes under 30 minutes if your billing tables are reasonably structured. No SQL, no analyst, no waiting.