Industries/ Startups/ Metrics your board trusts
A SaaS metrics dashboard that ends the weekend board pack.
We pull signups, activation, retention, revenue and churn straight from your product database and payment provider into one live view. Every number has one written definition, so the board pack and the investor update tell the same story.

- Used by
- Founders, the board, investors and the finance lead
- Takes the place of
- Weekend spreadsheet exports and three versions of revenue
- Connects to
- Your product database, payment provider and accounting software
- Built with
- Our live dashboards service
Where it hurts today
A normal week, before it exists
It is the last weekend of the month and the investor update is due on Monday. A founder exports subscriptions from the payment provider, signups from the product database and invoices from the accounting software, then pastes them into a spreadsheet only they understand. Formulas break when a column moves. By Sunday evening there is a number, and a quiet worry about whether it is the right one.
Different people get different answers. The payment provider's dashboard shows one figure for monthly recurring revenue and the spreadsheet another, because one spreads annual plans across the year and the other does not. Churn is counted as accounts in one place and as revenue in another. The board meeting spends more time on which number is correct than on what to do about it.
The questions get harder as the company grows. A new investor wants retention by signup month. A potential acquirer's adviser asks how revenue per customer has moved by plan. A due diligence checklist wants the definition behind every metric in the deck. Answering any of these from the spreadsheet means another weekend, and a founder's weekends are not a renewable resource.
What it does
Metrics your board trusts, feature by feature
A short list of the numbers your company actually steers by, each defined once and kept current without anyone exporting anything.
- 01
One definition per SaaS metric
Monthly recurring revenue, activation, churn and the rest are each defined once in plain words, with what they include and exclude and who owns them. The dashboard, the board pack and the investor update all read from that definition, so the same question always gets the same answer.
- 02
MRR straight from your billing system
Subscriptions, plan changes, refunds and failed payments come from your payment provider. Signups and product usage come from your own database or analytics tool. Nothing is typed in by hand, and each figure can be traced back to the records behind it.
- 03
Cohort retention and churn
Customers grouped by the month they signed up, so you can see whether spring's accounts stayed longer than winter's, and whether a pricing or onboarding change made any difference. These are the charts investors ask for and spreadsheets handle badly.
- 04
A board pack that builds itself
A fixed set of pages for the board and a shorter one for the monthly investor update, laid out in your brand and exportable as a PDF. The founder adds commentary on top rather than rebuilding the charts from scratch each time.
- 05
Different views for different people
The board and investors see company-level figures. The team sees activation and product usage. Only the founders and finance lead see revenue per named customer. Permissions apply to the data itself, so a filter cannot be removed to show more than someone should see.
- 06
Honest about freshness
Every panel shows when its data last refreshed. If the payment provider's feed fails overnight, the dashboard says so instead of quietly showing yesterday. Checks also flag numbers that jump in ways that usually mean a data problem rather than a good month.
A day with it
How the day runs instead
How a normal month runs once the metrics are live.
- Monday, 8amFounder
The founder opens the dashboard on a phone before stand-up. Activation dipped last week, and the panel shows the dip began the day the new onboarding screen shipped. It goes on the morning's agenda instead of being noticed at month end.
- Mid-monthProduct lead
The product lead compares the last three signup cohorts. Accounts that invited a colleague in their first week stayed longer. That becomes the target for the next onboarding change, and the team will be able to see whether it moves.
- Last working dayFinance lead
The finance lead checks the revenue page against the accounting software. The two agree because both read the same subscription records, and the one difference, a refund issued by hand, is visible and explained in a note on the panel.
- First MondayFounder
The monthly investor update starts from finished charts. The founder exports the update pages as a PDF, writes three paragraphs about what happened and why, and sends it. The numbers match last month's update because the definitions did not move.
- Board meetingInvestor director
An investor director asks how retention on annual plans compares with monthly. The founder filters the retention page in the meeting, the answer is on screen, and the conversation moves on to what to do about it.
What it connects to
Works with what you already run
Most early-stage metrics already exist somewhere. The work is joining them, once, in a way everyone trusts.
Payment provider
Subscriptions, plan changes, trials, refunds and failed payments read from your payment provider, for example Stripe, Paddle or Chargebee where it offers an API, so revenue figures come from the system that actually charges customers.
Your product database
Signups, accounts, seats and the events that define activation, read from a copy of your product data rather than the live database itself, so a heavy report cannot slow the product down.
Product analytics
Feature usage and funnel steps from an analytics tool your team already uses, joined to accounts so usage can be compared with plan, revenue and retention for the same customers.
Accounting software
Invoices and recognised revenue from your accounting software, for example Xero or QuickBooks where it offers an API, so the finance view and the board view can be reconciled rather than argued over.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- A written definition for each metric the board reviews
- Live connections to your payment provider and product database
- A company overview with signups, activation, revenue and churn
- Monthly signup cohorts showing retention and churn over time
- A board pack and investor update view, exportable as a PDF
Once it is in use
- Revenue by plan and segment once pricing has settled
- Cost to serve per customer, drawn from your cloud bill
- A data room export with definitions, ready for due diligence
- Early warnings for accounts whose usage suggests they may cancel
Buyer's guide
Before you commission one
Four decisions worth making before you commission a metrics dashboard.
- 01
Analytics tool or custom dashboard
If your revenue lives in one billing system and the board mainly wants MRR, churn and cohorts, a subscription analytics tool such as ChartMogul or Baremetrics may be the right buy, and we will say so. A custom view earns its place when you need product usage, billing and accounting joined, your own definitions, or metrics inside your own product.
- 02
What to prepare first
The last two board packs and investor updates, the spreadsheet behind them, and a list of every system holding a number you report: payment provider, product database, analytics, accounting and CRM. Note which figures you have already reported externally, and any questions the board asked that you could not answer.
- 03
Who should own it
The CEO usually owns what goes to the board, but each metric needs a named owner who agrees its definition, often the finance lead for revenue and churn and the product lead for activation. An engineer or analyst should own the data connections, so a broken feed is someone's job on the day it happens.
- 04
How you will know it is working
The board pack is assembled from the dashboard rather than rebuilt by hand, meetings stop debating which number is right, the team opens the dashboard between meetings without being reminded, and investor questions are answered with a filter rather than a promise to come back next week. A new hire can read the definitions and explain a number on their first day.
Terms worth knowing
The words you will meet
- MRR and ARR
- Monthly recurring revenue is the subscription revenue you can expect each month, with annual plans spread across their twelve months. Annual recurring revenue is usually that figure times twelve. Both need written rules for trials, discounts, pauses and usage charges, or two people will calculate them differently.
- Net revenue retention
- Revenue from a group of existing customers at the end of a period, after upgrades, downgrades and cancellations, compared with what the same customers paid at the start. New customers are left out. It shows whether existing accounts grow or shrink, which investors read as a sign of product value.
- Recognised revenue
- Revenue counted as the service is delivered, not when the card is charged, so an annual plan paid upfront is recognised month by month. ASC 606 sets the rules in the US and IFRS 15 in many other countries. In the UK, FRS 102 moved to a similar five-step model for periods starting on or after 1 January 2026.
Handled with care
The details that matter here
Numbers that go in front of investors need more care than a chart on the office screen.
Definitions agreed before charts
We sit down with the founders and the finance lead and agree each definition in writing before building anything: what counts as active, how annual plans are spread, when a cancelled account counts as churned. Definitions can change later, and each change is recorded with a date and a reason.
Who sees which customer
Revenue per named customer, payment failures and contract values are restricted to the people who need them, and the board sees company totals. We set this up with whoever owns data protection for you under UK GDPR or EU GDPR, and keep a short record of who can see what.
A read-only copy, never the live system
The dashboard reads from a separate copy of your data, refreshed on a schedule, so analysis cannot change customer records or slow the product. Connections to your payment provider and accounting software use read-only keys under your company's own accounts.
The numbers investors already saw
When the dashboard replaces the spreadsheet, figures can differ from what was reported before. We reconcile the two, explain each difference in writing and help you decide how to describe any change in the next update, rather than letting a new number appear without explanation.
Guides
Worth reading first
Questions
What buyers ask first
Is Stripe's dashboard enough for board reporting?
For a while, often yes, and we will say so if it covers what your board needs. Payment provider dashboards are good at revenue. They know nothing about activation, product usage or which features keep customers, and their definitions may not match how you report. Once the board asks questions that need billing and product data together, a joined-up view starts to earn its place.
Which SaaS metrics should a startup report to its board?
Fewer than most founders expect. A board usually needs a handful that describe growth, activation, retention, revenue and cash, plus one or two particular to your product. We start from the decisions your board and team actually make and work back from there. A metric nobody would act on gets cut, even if it is easy to chart, and every metric that stays gets a written definition.
Will our metrics stand up to investor due diligence?
We cannot say how any investor will judge them. What we can do is make sure every figure has a written definition, traces back to source records, and either matches what you reported before or comes with an explanation. That makes the numbers easier to check, which is most of what financial due diligence on early metrics involves.
Can board members and investors have their own login?
Yes. Each person signs in with their own account and sees the pages their role allows, usually company-level figures without named customers. Access can be removed in one step when someone leaves the board. If some investors prefer a monthly PDF, it can be emailed on a schedule from the same pages, so everyone still reads the same definitions.
Who maintains the dashboard when our pricing changes?
Pricing changes are the most common reason a metrics view needs work, because new plans, discounts or usage charges change what revenue means. We document how each metric is built so your own engineer or analyst can adjust it. If you would rather we kept it current, that can sit inside a monthly support allowance.
Still building the board pack on a Sunday night?
Send us last quarter's board pack and tell us where each number comes from today. We will tell you what a live view would involve, and we reply within 48 hours.
More for startups
What else we build for startups
Pitch-ready brand identity
A mark, colours, type and a pitch-deck template sized for where you are now, with room to extend later. Investors, first hires and early customers judge credibility on thin evidence, so give them a company that looks as considered as the product.
A narrow first release
One workflow, real accounts and real billing, built on foundations that will not need replacing. Small enough to ship early and put in front of paying customers, so what you build next is decided by what they actually do.
Finishing a stalled build
An honest assessment of the half-finished product you were left with, then the parts that matter stabilised, tested and completed. Rebuilding by reflex is expensive, and often the existing code needs finishing rather than replacing. We will tell you which.
AI inside your product
Smart search, recommendations, summaries or document reading built into your own product, each scoped to do one job well, with the cost per customer measured before the feature goes anywhere near your pricing page.
Phone apps and store launch
When your product needs an app, we build for iPhone and Android together and handle the store side in parallel: developer accounts, testing tracks, privacy declarations and reviewer notes, so submission never holds up a launch date you have announced.
Everything we build for startups
The same idea, in other sectors

