Use case · Context Board

SaaS Dashboard for MRR, Signups and Errors

MRR, signups, product use, errors and deploys on one live board, with the tool behind each number named.

Free for 3 days · then $12 a month · one plan, every connection
MRRStripenow
$12,4806.1%vs last month
90 days agoToday
VisitorsPlausiblenow
18,240
4.7%
UsersSupabasenow
1,312
4.2%vs last week
Newest customersStripenow
  • TallyworksPro, monthly$49
  • Fieldnote LabsTeam, yearly$490
  • QuillmarkPro, monthly$49
  • Orbit DentalStarter, monthly$19
Weekly active usersPostHognow
2,104
3.9%vs last week
Road to $15kStripenow
83%$12,480 of $15k
MRR goal
Unresolved issuesSentrynow
  • Webhook timeout on billingapi212 events
  • Null plan in onboardingweb37 events
  • Export job hit a rate limitworker9 events
DeploymentsVercelnow
  • Annual plan togglewebReady
  • Retry failed webhooksapiBuilding
  • New onboarding copywebReady
This week
  • Ship annual pricing
  • Fix the billing webhook timeout
  • Email last month's cancels
  • Write the November update
An example Context Board named SaaS HQ. Every number on it is example data.
ON ONE BOARD

What changes with Context Board

Today

Your MRR is in Stripe, signups are in your database, weekly actives are in PostHog and last night's errors are in Sentry. Checking how the product is doing means four logins before coffee. The number you most need, churn, is the one you look at least, because it takes the longest to find.

With Context Board

Context Board puts your SaaS numbers on one live board. Connect Stripe or Lemon Squeezy for revenue, Plausible, Google Analytics or PostHog for traffic and product use, Supabase for signups, and Sentry and Vercel for errors and deploys. Each connects once and only reads. For a number no tool sends as one, like churn, Claude or Codex works it out and puts it on the board.

How it works for SaaS founders

  1. Start from Founder HQ Sign in at board.contextbolt.com and pick the Founder HQ template. It lays out MRR, visitors, an MRR chart, a revenue goal and today's tasks. No template ships a number, so each widget waits for its source.
  2. Connect revenue Save a Stripe restricted key with Read on Balance and Subscriptions for MRR, or sign in with Stripe's own MCP server so your agent can read revenue, customers and subscriptions. On Lemon Squeezy, save an API key and pick your store.
  3. Connect product and traffic Sign in to PostHog for your saved insights, or save a Plausible key for visitors. Point Supabase at your users table for signups. Sign in to Sentry and Vercel for errors and deploys.
  4. Ask for the rest Connect Claude or Codex to the board and ask for what no tool sends as one number, like churned subscriptions this month. The agent builds the widget, and its name is on the change.

What Context Board gets you

  • MRR from a Stripe restricted key or Lemon Squeezy, counted from active and past due subscriptions
  • Newest customers and subscriptions through Stripe's own sign-in
  • Visitors from Plausible, Google Analytics or PostHog, and signups from Supabase
  • Saved PostHog trends and funnels, run again while the board is open
  • Unresolved Sentry issues beside the Vercel deploy that shipped them
  • The board only reads Stripe and your database, so nothing there changes

SaaS Dashboard for MRR, Signups and Errors: the full story

A SaaS dashboard is one screen with the numbers that say whether your product is growing: MRR, new customers, signups, how many people use it, and what’s broken. For a solo founder those numbers live in five tools, so the dashboard is usually five tabs.

Context Board’s Dashboard board puts them on one live screen, like the example above. Every number on it is example data, but each tile shows a real source: MRR from Stripe, visitors from Plausible, users from Supabase, weekly actives from PostHog, errors from Sentry and deploys from Vercel.

Before you connect anything, it helps to know which tool can give which number. So we made a table of it. On November 12, 2026 we read Context Board’s own product notes and our ten integration pages and marked, for ten SaaS numbers, which of ten sources hands the board that number with no code. Eight of the ten come ready-made from at least one source. Churn needs your agent to count it. Failed payments come from none of them yet.

Quick answer
  • A SaaS dashboard needs five numbers to start: MRR, new customers, signups, one product number like weekly active users, and unresolved errors.
  • Our count: of ten SaaS numbers, eight come ready-made from at least one of the ten sources Context Board connects. Churn needs your agent to count it from Stripe’s subscriptions. Failed payments come from none yet.
  • Context Board reads Stripe, Lemon Squeezy, PostHog, Plausible, Google Analytics, Supabase, Sentry and Vercel, and only reads. Numbers refresh while the board is open.
  • Definitions follow Stripe’s own: MRR is the monthly value of active and past due subscriptions. Subscriber churn is churned subscribers over the last 30 days divided by subscribers at the start plus new ones.
  • Price: free for 3 days, then $12 a month, one plan with every connection.

What a SaaS dashboard shows

The board at the top of this page is a SaaS dashboard for one founder. Read it left to right, top to bottom.

  • MRR is the number, its change against last month, and 90 days of history. A ring beside it fills toward a goal of $15k.
  • Visitors and Users show the top of the funnel. Plausible counts visitors, and Supabase counts the rows in your users table.
  • Newest customers comes from Stripe’s own sign-in, with the plan and price of each.
  • Weekly active users is a saved PostHog insight, run again while the board is open.
  • Unresolved issues and Deployments sit side by side, so a new error lines up with the deploy that shipped it.
  • This week is a plain to-do list, because a number is only worth watching if it changes what you do.

The design galleries for “SaaS dashboard” show what a product’s own admin screen could look like. This is the other kind: the screen the founder looks at to run the business. It’s yours, you arrange it, and the numbers are live.

Which SaaS numbers each tool gives your board with no code

This is the table we made. Rows are ten numbers a SaaS dashboard usually carries. Columns are the ten sources. “Yes” means our pages name that number for that source as a widget or a read the board makes itself. “Agent” means the source sends the records the number is made from, and your agent, like Claude or Codex, turns them into the number. “No” means not from this source.

NumberStripe sign-inStripe keyLemon SqueezyPayPalPlausibleGA4PostHogSentryVercelSupabase
MRRNoYesYesNoNoNoNoNoNoNo
RevenueYesNoYesAgentNoNoNoNoNoNo
New customersYesNoNoNoNoNoNoNoNoNo
Churned subscriptionsAgentNoNoNoNoNoNoNoNoNo
Failed paymentsNoNoNoNoNoNoNoNoNoNo
VisitorsNoNoNoNoYesYesYesNoNoNo
SignupsNoNoNoNoNoAgentYesNoNoYes
Product eventsNoNoNoNoNoAgentYesNoNoNo
ErrorsNoNoNoNoNoNoNoYesYesNo
DeploysNoNoNoNoNoNoNoNoYesNo

How we made it: we read Context Board’s product notes (the list of sources the board pulls itself) and our own integration pages for each source on November 12, 2026. A cell says Yes or Agent only where one of those says so in words. Where they say nothing, the cell says No, even if the tool’s own API might reach the number. Your agent can often go further than this table, so read it as the floor.

Ready-madeYour agent works it outMRR2Revenue3New customers1Churned subs1Failed paymentsnone yetVisitors3Signups3Product events2Errors2Deploys1Out of 10 sources. Our own pages, Nov 12, 2026.
How many of the ten sources give each SaaS number. Visitors and signups are the easiest to fill. Churn and failed payments need your agent or your own script.

A few things the table shows that are easy to miss:

  • Stripe connects two ways, and they give different numbers. A restricted key with Read on Balance and Subscriptions gives the board MRR and your balance. Stripe’s own sign-in gives your agent revenue, customers and subscriptions. If you bill with Stripe, connect both. See the Stripe dashboard page for the setup.
  • Lemon Squeezy gives MRR and revenue from one key. Revenue for the last 30 days, orders, payments and MRR, all from one API key. The Lemon Squeezy dashboard page explains why orders and payments differ when you sell subscriptions.
  • PostHog covers the product half. The board runs your saved insights, so a trend like weekly active users or a signup funnel lands as its own widget. The PostHog dashboard page shows how. PostHog runs its own MCP server, and that is what the board signs in to.
  • Plausible needs one key. Visitors today, the last 30 days, top pages and sources, from one Stats API key, which Plausible lists as a Business plan feature. The Plausible dashboard page has the steps.
  • Paddle isn’t in the table because it has no ready-made connection on the board. A Paddle number can still come in through the push API, below.

For failed payments, and for any number no source sends, have your own script send it with the push API, POST /v1/push/:stream, from a cron job or a GitHub Action. A push key can send data and nothing else. If Claude or Codex already has the number from somewhere you connected it, ask it to put the number on the board.

The SaaS metrics, defined

The definitions below are Stripe’s, from its Billing analytics docs and its guides. If you bill with Stripe, its Billing overview uses the same definitions for MRR and churn.

MetricStripe’s definitionOn the board
MRRThe monthly value of all active and past due subscriptions, leaving out taxes, free plans and usage-based productsStripe key or Lemon Squeezy
Subscriber churn rateSubscribers churned in the last 30 days, divided by active subscribers 30 days ago plus new subscribers in the last 30 daysYour agent, from Stripe’s subscriptions
Churned revenueChurned MRR plus contraction MRR (downgrades) in the periodYour agent or the push API
ARPUMRR divided by active subscribersYour agent or the push API
Subscriber LTVARPU divided by the subscriber churn rateYour agent or the push API
Net revenue retentionStarting recurring revenue, minus MRR lost to churn and downgrades, plus revenue from upgrades, divided by starting recurring revenue, times 100The push API
CAC paybackCustomer acquisition cost divided by monthly profit per customer (monthly revenue per customer minus monthly cost per customer)The push API

Stripe’s own examples make these concrete:

  • MRR: 100 subscribers on a $100 monthly plan and 50 on a $600 yearly plan is (100 × $100) + (50 × $600 / 12) = $12,500.
  • Churn: start the month with 1,000 subscribers, add 100, lose 100. Churn is 100 / 1,100 = 9.1%. A subscriber counts as churned when all their subscriptions are canceled or marked unpaid.
  • LTV: an ARPU of $500 and a churn rate of 9% gives $500 / 9% = $5,555.

For net revenue retention, Stripe says a figure above 100% points to strong retention and revenue growth. Your existing customers added more revenue than churn and downgrades took away. For CAC payback, Stripe treats 12 months or less as healthy for a SaaS company. CAC needs your ad and sales spend, which none of the ten sources hold, so that one comes from you.

One detail on MRR. The board’s MRR widget counts the way Stripe does, active and past due subscriptions made monthly, but it counts prices before discounts and leaves out metered prices, and the widget says so. If you run coupons, Stripe’s own figure can come in lower. Stripe lets you choose whether discounts come off MRR, from its Billing overview.

Which numbers to put on a startup dashboard first

A startup dashboard for one founder works best small. Start with five tiles and add one only when it would change what you do this week.

  1. MRR, with a goal ring. From a Stripe restricted key or Lemon Squeezy.
  2. New customers. From Stripe’s sign-in, as a list of the newest.
  3. Signups. The row count of your users table in Supabase, or a saved PostHog trend.
  4. One product number. Weekly active users from PostHog is a good default.
  5. Unresolved errors. From Sentry, next to Vercel deploys if you ship often.

Churn goes on the board once you have enough customers for it to move from month to month. Until then, a list of who canceled tells you more than a percentage.

For more boards built around a goal, like a growth board or a launch board, KPI dashboard examples has ten of them, each with the formula and where the number comes from. If you’d rather start in a spreadsheet, how to build a Google Sheets dashboard walks through it with real formulas. A sheet works until the first busy week, when nobody pastes in the new numbers.

Building it with Claude or Codex

You don’t have to lay the board out by hand. Connect Claude or Codex to the board by its address, click Allow, and ask in plain words.

  • “Put my Stripe MRR at the top of this board with a goal of $15k.”
  • “Show my signup funnel from PostHog.”
  • “Count the Stripe subscriptions canceled this month and put the number beside MRR.”
  • “Put unresolved Sentry issues next to my latest Vercel deployments.”

The agent finds what you connected and builds each widget. Every change it makes shows with its name on it and can be undone. When no built-in widget fits, it writes a custom one in the board’s own look, which runs sealed off with no network access.

These connections only read. The board runs no tool that writes in Stripe, PostHog, Supabase, Sentry or Vercel, so nothing there changes. Keys you save are sealed on our server and never sent back to your browser.

When a cofounder or an early investor asks how the month is going, share the board instead of writing the numbers into an email. Share it by email with Can view, which is free for them, or turn on a public read-only link. They see the numbers update as yours do. They never see your sources, your keys or your chats with the agent.

Sources refresh on our server while the board is open in front of someone, every 30 minutes by default, and a widget’s Updated time works as a refresh button when you want the number now. If a read fails, the widget keeps the last good number and says what went wrong and when, so the board never shows a number it didn’t receive.

A SaaS dashboard template or a live board

Much of what you find for “SaaS dashboard” is design: mockups and UI kits for the admin screen inside your product. Those are for building your app. A live board is for running the business around it.

If you’re choosing between tools for that second job, dashboard software for small business prices nine of them, checked on each vendor’s site. Context Board is ours, so weigh the bias, but it’s built for this reader: one founder, the AI agents they already use, and $12 a month.

What it doesn’t do, so you know before you start. Sources refresh while the board is open, not in the background. There’s no team plan or per-seat price. A person you share with can view for free, and editing needs their own subscription. And no source on the board sends failed payments yet, so that one comes from your agent or a script.

For revenue, traffic and search on one screen without the product numbers, the business dashboard is the simpler start. To build this one, start the trial on Context Board, pick Founder HQ, and connect Stripe first.

Frequently asked questions

Something else on your mind? Get in touch.

What should a SaaS dashboard show?

Start with five numbers: MRR, new customers, signups, one product number like weekly active users, and unresolved errors. Add churn once you have enough customers for it to move. On Context Board, MRR comes from Stripe or Lemon Squeezy, signups from Supabase and product use from PostHog.

Does Context Board show churn?

Not as a ready-made widget. Stripe's sign-in gives your agent your subscriptions, so Claude or Codex can count the churned ones and put the number on the board. Or work it out in your own script and send it with the push API.

Is the MRR the same as Stripe's?

It should be close. Both count active and past due subscriptions, made monthly, with a yearly plan counted as a twelfth. The board counts prices before discounts and leaves out metered prices, so if you run coupons, Stripe's figure can come in lower.

Can I use Paddle?

Paddle has no ready-made connection on the board. You can send a Paddle number from your own script with the push API, which takes a push key that can send data and nothing else.

Does it update when the board is closed?

No. Sources refresh on our server while the board is open in front of someone, every 30 minutes by default. If a read fails, the widget keeps the last good number and says what went wrong and when.

What does it cost?

Context Board is free for 3 days, then $12 a month. One plan with every connection, widget and theme.

One workspace for you and all your agents

Free for 3 days, then $12 a month. One plan with every connection, widget and theme.

Start free trial See everything Context Board does