After buying an online business, a reliable KPI dashboard helps you separate normal variation from an operational problem. This guide explains which numbers to track for SaaS, ecommerce, content, and service businesses; how to calculate them; how to set practical assumptions; and how to run a monthly review that turns data into operating priorities.
Overview
Your acquisition model determines which metrics deserve the most attention. A SaaS business needs retention, churn, activation, and recurring revenue visibility. An ecommerce business needs contribution margin, inventory performance, conversion rate, fulfillment reliability, and repeat purchasing. A content site needs traffic quality, monetization, search concentration, and revenue per visitor. A service business may rely more heavily on leads, close rate, delivery capacity, and owner hours.
The dashboard should not be a collection of every number available in Analytics, Stripe, Shopify, an advertising platform, or a help desk. It should answer five operating questions:
- Is revenue growing, stable, or declining?
- Is each sale becoming more or less profitable?
- Are customers, visitors, and leads behaving as expected?
- Can the business fulfill demand without damaging quality?
- Is the owner replacing the previous operator with a repeatable system?
Use one reporting period consistently, usually a calendar month. Keep accounting figures on an accrual or cash basis according to the business's established records, but do not mix the two without labeling the difference. For trend analysis, compare the current month with the previous month and with the same period in the prior year when enough history exists.
Before setting growth targets, review the business's pre-acquisition performance. The guide to comparing website traffic and revenue quality can help you distinguish durable performance from a temporary spike. For a SaaS acquisition, pair this dashboard with a technical and customer review using the SaaS due diligence workflow.
How to estimate
Start with a simple monthly model. Record the numerator, denominator, data source, reporting period, and owner for every KPI. A metric is only useful when two people would calculate it the same way.
| Area | KPI | Calculation | Suggested cadence |
|---|---|---|---|
| Revenue | Total revenue | All recognized sales for the period, separated by product or channel | Weekly glance, monthly close |
| Profitability | Gross margin | (Revenue minus direct costs) divided by revenue | Monthly |
| Cash | Operating cash flow | Cash received minus operating cash paid during the period | Weekly and monthly |
| Marketing | Conversion rate | Conversions divided by relevant sessions, leads, or visitors | Weekly, monthly review |
| Retention | Customer retention | Customers remaining at period end, adjusted for new customers, divided by customers at period start | Monthly or cohort-based |
| SaaS | Logo churn | Customers lost during the period divided by customers at the start | Monthly |
| Traffic | Traffic mix | Share of visits or conversions by organic, paid, direct, referral, email, and other channels | Weekly glance, monthly |
| Fulfillment | On-time fulfillment | Orders delivered or completed on time divided by total orders | Weekly and monthly |
| Support | Support volume | Total tickets or requests, segmented by issue type and customer segment | Weekly |
| Capacity | Owner hours | Hours spent by the owner, categorized by operations, support, sales, and growth | Weekly, summarized monthly |
Use the source system closest to the event. Pull revenue and refunds from the payment processor or accounting system, orders from the commerce platform, sessions and channels from the analytics platform, and tickets from the support tool. Reconcile totals rather than assuming platforms will match: payment dates, order dates, refunds, tax treatment, attribution windows, and time zones can all create differences.
For each KPI, calculate both the result and the change. A useful variance formula is:
Percentage variance = (current period minus comparison period) divided by comparison period multiplied by 100.
Choose the comparison period before reviewing the result. Month-over-month comparisons are useful for recent operational changes, while year-over-year comparisons can reduce confusion caused by seasonality. If the comparison value is zero or very small, use an absolute change and explain it instead of presenting a misleading percentage.
Inputs and assumptions
A practical dashboard needs clear definitions more than elaborate software. Create a metric dictionary with these fields:
- Name: for example, gross margin or logo churn.
- Definition: exactly what is included and excluded.
- Formula: including the time period and denominator.
- Source: accounting system, payment processor, analytics platform, CRM, store, or support tool.
- Owner: the person responsible for updating and checking it.
- Target or operating range: a business-specific expectation, not an unsupported universal benchmark.
- Action threshold: the result that triggers investigation.
Avoid importing generic benchmarks without adjusting for business model, price point, geography, acquisition channel, product maturity, and seasonality. Instead, establish an initial baseline from the last six to twelve months where records are reliable. If the business has changed materially since closing, use the most comparable recent period and document why.
Separate leading indicators from lagging indicators. Traffic, trial starts, qualified leads, cart additions, and support backlog can warn of a future revenue issue. Revenue, gross margin, cash flow, churn, and owner hours show what already happened. The dashboard should contain both, but the monthly meeting should connect them. For example, a fall in conversion rate may follow a checkout change, while rising support volume may explain a later increase in refunds.
For ecommerce operations, include inventory and supplier context rather than evaluating revenue alone. The ecommerce operations checklist provides a useful framework for reviewing those dependencies. For content businesses, monitor traffic concentration and revenue by page or channel; strong total traffic can conceal dependence on one source or a small group of pages.
Worked examples
Example 1: Ecommerce gross margin and cash
Assume a store records $40,000 in monthly revenue. Product cost is $18,000, payment fees are $1,200, and shipping paid by the business is $3,000. If all three are treated as direct costs, gross profit is $17,800 and gross margin is 44.5%: ($40,000 - $22,200) divided by $40,000.
The next question is whether the margin is improving for the right reason. Compare product mix, discounts, shipping costs, refunds, and advertising separately. If revenue rises but gross margin falls, the owner may be buying growth at a lower contribution level. Cash flow should then be reviewed alongside inventory purchases, because cash paid for stock can precede the related revenue by several weeks or months.
Example 2: SaaS churn and retention
Assume a subscription product begins the month with 200 paying accounts, loses 8 accounts, and adds 20 new accounts. Logo churn is 4% (8 divided by 200). Ending accounts are 212, but the retention calculation should not treat new accounts as retained customers. Gross logo retention is 96%, before considering expansion or contraction within existing accounts.
Review churn by signup cohort, plan, customer size, and stated cancellation reason. A stable overall rate can hide a deteriorating recent cohort or a problem concentrated in one plan. If revenue retention is available, track it separately from logo retention because losing one small account and losing one large account do not have the same financial effect.
Example 3: Owner hours after acquisition
Suppose the new owner spends 120 hours in a month: 45 on support, 30 on fulfillment, 25 on sales, and 20 on product or growth. The total is more informative when paired with output. Track tickets resolved, orders completed, leads handled, or releases shipped. If revenue is flat while owner hours rise, identify the category causing the increase before adding new initiatives. A recurring task may need documentation, automation, a policy change, or removal.
When to recalculate
Run a short weekly check for cash, orders or signups, conversion, traffic anomalies, fulfillment issues, and support backlog. Run the full dashboard after the monthly close, when refunds, expenses, payroll, and other adjustments are recorded. Hold a variance review within a few business days while the causes are still discoverable.
Use this workflow:
- Confirm the data: check missing days, duplicate transactions, tracking changes, refunds, and time-zone differences.
- Mark material variances: flag results outside the documented operating range or a meaningful change from the comparison period.
- Explain before acting: separate a one-time event, seasonal movement, measurement error, and genuine operating change.
- Choose one owner and action: assign a specific next step, deadline, and expected effect.
- Review the result next month: keep, revise, or stop the action based on evidence.
Recalculate definitions and assumptions whenever pricing, payment processing, analytics tracking, advertising attribution, product packaging, fulfillment, or marketplace reporting changes. Revisit benchmark ranges at least every six months, or sooner after a material business change. Record the old and new definitions so historical comparisons are not silently broken.
Finally, keep a monthly snapshot rather than overwriting the previous dashboard. A clean history lets you identify post-acquisition declines, test improvements, and explain decisions to partners or future buyers. For broader operating context, review the website acquisition due diligence checklist and the guide to valuing an online business. The goal is not to chase every metric; it is to maintain a consistent record that shows what changed, why it changed, and what you will do next.