A useful startup KPI dashboard does more than collect numbers: it shows whether the business is acquiring the right customers, creating value, retaining demand, and converting activity into cash. This guide provides a repeatable monthly dashboard structure for SaaS companies, marketplaces, and service businesses, including metric definitions, formulas, assumptions, worked examples, and a review process you can adapt as the company changes.
Overview
The right startup metrics to track monthly depend on how the business earns revenue. A subscription software company needs to understand recurring revenue, retention, activation, and customer acquisition. A marketplace must also measure liquidity: whether buyers can find suitable sellers and whether sellers receive enough valuable demand. A service business usually needs to focus on utilization, project margin, pipeline coverage, and cash collection.
Start with a small dashboard rather than attempting to report every available metric. A practical first version might include revenue, gross margin, cash balance, customer acquisition cost, retention, and one operating metric specific to the business model. Add detail only when it helps explain a decision or a change in performance.
Use the dashboard as a period-over-period tool. Monthly figures should normally be compared with the prior month, the same period in the previous year when enough history exists, and the plan or forecast. A single result rarely explains the health of a startup. Trends, definitions, and the relationship between metrics matter more than an isolated target.
| Business model | Core metrics | Useful supporting metrics |
|---|---|---|
| SaaS | Recurring revenue, gross margin, activation, churn, retention | Customer acquisition cost, lifetime value, expansion revenue, cash burn |
| Marketplace | Gross transaction value, take rate, liquidity, repeat usage | Time to match, fill rate, buyer and seller retention, dispute rate |
| Service business | Revenue, gross margin, utilization, pipeline, cash collection | Average project value, win rate, delivery time, accounts receivable |
How to estimate
Build the dashboard from a consistent monthly close. Choose a reporting date, define the period, and record the raw inputs before calculating ratios. The same definitions should be used each month unless you deliberately revise them and preserve the old method for comparison.
1. Record the financial base
Capture recognized revenue, direct costs, operating expenses, cash balance, invoices issued, and cash collected. For a marketplace, record both gross transaction value and the revenue retained by the platform. Do not treat the full value of transactions as platform revenue unless that matches the business's accounting treatment.
- Gross margin: (Revenue minus direct costs) divided by revenue.
- Operating burn: Cash operating outflows minus operating cash inflows for the period. Define whether financing activity is excluded.
- Cash conversion: Cash collected divided by invoiced or recognized revenue, using a clearly stated period.
- Runway: Cash balance divided by an agreed monthly burn measure. See the startup runway calculator guide for a separate review of assumptions.
2. Calculate customer economics
For customer acquisition cost, divide sales and marketing costs included in the calculation by the number of new customers acquired during the same period. State whether founder time, salaries, commissions, advertising, software, and onboarding costs are included. Mixing a broad cost base with a narrow customer count can make the result difficult to interpret.
For a simple lifetime value estimate, multiply average revenue per customer by gross margin and divide by the customer churn rate. This is a directional model, not a promise of future revenue. It is most useful when the revenue base, margin, and churn definitions are stable enough to compare across periods.
3. Add behavior and funnel metrics
Track the event that represents meaningful activation, not just account creation. For example, activation might mean completing a workflow, publishing a listing, inviting a teammate, or completing a first transaction. Calculate activation as activated new users divided by eligible new users.
For retention, define the cohort and period first. Logo retention measures the share of customers still active; revenue retention measures the share of starting revenue retained, including or excluding expansion according to the chosen definition. Gross revenue retention excludes expansion, while net revenue retention includes expansion and contraction. Label the version used in your dashboard.
4. Add model-specific operating metrics
A marketplace dashboard should include liquidity measures such as the percentage of relevant buyer requests that receive a suitable response, the percentage of listings that result in a transaction, or the median time to a match. Pick one or two measures that reflect the marketplace's actual bottleneck.
A service business should track utilization: billable or revenue-generating hours divided by available delivery hours. Also track project-level gross margin and cash collection, because high booked revenue can conceal underpriced work or delayed payment.
Inputs and assumptions
Create an inputs tab or source-of-truth section before building charts. At minimum, include the reporting month, opening and closing customer counts, new customers, churned customers, opening and closing recurring revenue where relevant, revenue, direct costs, sales and marketing costs, cash balance, and the operating metric for your model.
Document each assumption beside the input. Useful notes include:
- Whether revenue is recognized, invoiced, or collected cash.
- Whether taxes, refunds, payment fees, and pass-through costs are included in direct costs.
- Whether customers are counted by account, contract, location, or paying entity.
- Which users, transactions, hours, or listings are considered eligible.
- Whether the period uses calendar months, a four-week cycle, or another reporting convention.
- Whether one-time deals, annual contracts, discounts, and expansion revenue are treated separately.
Avoid forcing every metric into a target. Early-stage data may be too sparse for a dependable churn or lifetime value estimate. In that case, report the raw counts, cohort age, and direction of change. A note such as “insufficient history for a stable estimate” is more useful than a precise-looking number built on weak assumptions.
Keep a metric dictionary with the formula, owner, data source, and last definition change. This prevents a dashboard from silently changing when a new analytics tool, accounting workflow, or customer-counting rule is introduced. For accounting inputs, your startup accounting software comparison can help frame the bookkeeping and invoicing workflow around the reporting process.
Worked examples
SaaS example
Assume a software company ends the month with $48,000 in recurring revenue. It recorded $12,000 in direct hosting and support costs, spent $18,000 on sales and marketing, and acquired 12 new paying customers. Its opening customer count was 120, and four customers churned during the month.
- Gross margin = ($48,000 - $12,000) / $48,000 = 75%.
- Simple acquisition cost = $18,000 / 12 = $1,500 per new customer.
- Monthly logo churn = 4 / 120 = 3.3%, if the opening customer count is the denominator.
These calculations do not establish whether the company is healthy by themselves. The team should examine whether the new customers activated, how much recurring revenue they represent, whether acquisition cost is rising, and whether churn is concentrated in a particular customer segment or product use case.
Marketplace example
Assume a marketplace records $100,000 in completed transaction value during the month and retains a 10% platform share under its chosen revenue model. Platform revenue is therefore $10,000 before considering other adjustments. Of 200 qualified buyer requests, 150 receive at least one suitable response, giving a response-based liquidity rate of 75%.
The team should define “suitable response” in the inputs tab. If the definition changes from any response to a response that meets stated requirements, the rate may fall even if marketplace quality improves. Preserve both the old and new definitions during the transition so the trend is not misread.
Service business example
Assume a service business has 800 available delivery hours and completes 520 billable hours. Utilization is 520 / 800 = 65%. If project revenue is $78,000 and direct delivery costs are $31,200, project gross margin is ($78,000 - $31,200) / $78,000 = 60%.
A monthly review should connect these results. If utilization rises while project margin falls, the business may be filling capacity with underpriced work. If margin is strong but cash collection is weak, the next action may concern invoicing terms or overdue accounts rather than sales volume.
When to recalculate
Refresh the dashboard after each monthly close, but recalculate or review the model more deeply when an underlying input changes. Revisit customer acquisition cost when channel mix, compensation, or campaign spending changes. Revisit lifetime value when pricing, gross margin, contract length, or churn changes. Revisit marketplace liquidity when the category, geography, supply mix, or matching process expands.
Review the metric dictionary at least annually and whenever the reporting system changes. Update benchmark comparisons cautiously: definitions, customer segments, pricing models, and accounting treatments can differ enough to make external targets misleading. Treat benchmarks as context, not as substitutes for your own trend data.
Use this monthly workflow:
- Lock the reporting period and gather raw inputs.
- Check totals against accounting, billing, analytics, and operational records.
- Calculate the dashboard using unchanged definitions.
- Compare actual results with the prior period, plan, and relevant cohorts.
- Write down the two or three largest changes and their likely causes.
- Assign one owner and one next action for each material issue.
- Record any definition or assumption change before the next reporting cycle.
A dashboard earns its place when it changes what the team does. Keep the current version simple, preserve the underlying inputs, and add metrics only when they answer a recurring operating question. For adjacent planning, pair this dashboard with the startup break-even calculator guide, startup tech stack audit template, or startup payroll tools comparison as the company’s cost and reporting needs develop.