The MSP dashboard: churn, tickets, pipeline

An MSP dashboard needs exactly three panels: revenue retention (churn and net MRR movement), service delivery (ticket volume and resolution health), and pipeline (new MRR in progress). Tickets predict churn, churn sets your growth target, and pipeline tells you whether you will hit it. Miss any one of the three and the other two will mislead you.

Why does an MSP need a different dashboard?

Most service firms sell projects. An MSP sells continuity, which changes the shape of the numbers. A consultancy that wins nothing this month has a visibly bad month. An MSP that wins nothing still invoices every contract on the book, and the P&L looks fine for quarters while the business quietly shrinks underneath it. I mapped the sub-vertical patterns in Growth Systems by Industry; the MSP pattern is the leaky bucket. Growth is new MRR minus churned MRR, and both halves need to be on one screen, because managing either in isolation produces bad decisions — cutting service cost to fund sales, or over-servicing to avoid selling.

The other MSP-specific trap is that your operational system of record (the PSA) and your commercial one (the CRM) are usually different tools that never meet. The dashboard is where they meet.

What belongs on the churn panel?

Four numbers, all monthly: gross MRR churn (revenue lost from cancellations and downgrades), net revenue churn (the same, minus expansion from existing clients), logo churn (client count, because losing one £4,000/mo client is not the same as losing four £1,000/mo ones), and renewals due in the next 90 days with an owner named against each.

Net revenue churn is the headline. When it is negative — expansion outrunning losses — the recurring base grows even in a quiet sales month. When it is positive, every new deal is partly replacement revenue, and your pipeline target needs to rise to match. Most MSP owners I speak to can quote their MRR; far fewer can quote what percentage of it walked out the door last quarter.

Why do tickets belong on a growth dashboard?

Because ticket data is the earliest churn signal you own. Clients rarely leave out of nowhere. Typically the sequence runs: tickets per endpoint creep up, resolution times stretch, the same issue recurs, the client stops raising tickets and starts collecting grievances, and then the renewal conversation goes badly. By the time churn shows in the revenue panel, the cause is months old.

So the middle panel tracks leading indicators: tickets per client per month against their baseline, aged tickets past your SLA, repeat issues, and escalations. When a client's ticket profile deviates sharply from its own history — in either direction, because silence is also a signal — then that account gets a proactive review call before the renewal date, not after.

What pipeline numbers matter for an MSP?

New MRR in pipeline, weighted by stage; first-year contract value against cost to acquire; and pipeline coverage — weighted pipeline divided by the new-MRR target that your churn number implies. Because managed contracts run for years, a handful of new logos per quarter is a perfectly healthy pace, but that makes coverage discipline more important, not less: one slipped deal is a big fraction of the quarter.

The same structure applies to any recurring-revenue service firm — I covered the adjacent case in Service-heavy SaaS: pipeline for the in-between firms. And unlike training providers, who fight a demand curve that rises and falls with the calendar (Seasonality in training: filling the trough), MSP demand is comparatively flat. The constraint is rarely the market; it is whether anyone is feeding the pipeline while delivery shouts louder.

How do you build it without manual reporting?

The mechanism, step by step. When a ticket closes in the PSA, when an invoice raises in the accounts package, when a deal moves stage in the CRM — then the dashboard updates itself. Concretely:

1. Define one metric list per panel and write down where each number lives. Tickets in the PSA, MRR in the accounting or billing tool, pipeline in the CRM. No metric without a named source system.
2. Connect each source to a single reporting layer via native integrations or an automation tool. No spreadsheets in the chain.
3. Set the refresh to daily and the review to weekly. Daily-refreshed, weekly-reviewed beats real-time and ignored.
4. Add thresholds: net churn above zero, any client 30% over ticket baseline, coverage below 3x. Breaches notify; everything else stays quiet.

When the dashboard needs a human to compile it, then it stops being compiled — usually within six weeks. Automation is not a luxury here; it is the difference between a dashboard and a good intention.

What does the weekly review look like?

Fifteen minutes, three questions: what churned or wobbled, which accounts breached ticket thresholds, and does weighted pipeline still cover the target. Decisions, not admiration. I run my own week on the same principle of fixed, short, recurring reviews — the format is in How I run my week — because a dashboard nobody has an appointment with is just decoration.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.