Don't Neglect "Legacy" Services

There's a lot of noise right now about what's next.

AI-powered this. Autonomous that. New service categories appearing every quarter. Every vendor event you walk into has a "transformation" theme and a slide deck full of things that don't exist yet at scale.

And look — some of that's worth paying attention to. New services keep you relevant. They open new conversations. They stop you from standing still.

But here's what I see happening while everyone's looking forward.

The existing services — the ones that actually pay the bills — are being quietly neglected.

The services nobody's reviewing

The managed firewall offering that's been on the books for years. The endpoint service that's technically still live but nobody's looked at properly in two years. The connectivity bundle built for a customer profile that's since changed completely.

Services that customers are still paying for. Still relying on. Still renewing. But haven't been reviewed since the day they launched.

That's a problem. And it's a more expensive problem than most people realise.

When did you last properly review your legacy services? Not a commercial review. Not a renewal conversation. An actual look at whether the service still does what it says it does. Whether the delivery model still makes sense. Whether the scope matches the contract — or what's quietly crept beyond it.

If the answer is "a while ago" — you're not alone. But you're sitting on a set of risks that compound quietly over time.

What it actually costs you

Customers paying for a service that's drifted away from what they need. Delivery teams running on muscle memory rather than documented process. Scope creep absorbed for free for so long it's now the default expectation. Pricing that made sense three years ago and erodes margin every year it isn't revisited.

None of this shows up as a crisis. It shows up as friction. Churn you can't quite explain. Renewal conversations that feel harder than they should. A delivery team that's stretched but can't tell you exactly why.

The customers most at risk of leaving aren't the unhappy ones. They're the ones who've gone quiet. Paying their invoice, getting their service, not really thinking about it — until a competitor calls and offers them something that looks sharper, more current, more like what they actually need now.

Refreshing isn't the opposite of innovation

New services need headroom to land. If your existing portfolio is inefficient — full of scope creep, ambiguity and underpriced delivery — there's no margin to invest in what's next. Every new service launch is effectively being subsidised by the one you should have fixed two years ago.

The best MSPs treat service refresh as a regular discipline. Not a one-off project. Not something that happens when a customer complains. A scheduled, structured review of what's on the shelf — whether it still works, whether it's priced correctly, and whether it's actually being sold.

Customer retention starts with the services they're already on. Not the ones you're trying to sell them next.

In the next post, I'll walk through five signs that a service offer needs a refresh — and what to do about each one.

Service before technology. Always.