In short: Your next piece of billable work is probably already sitting in a client's environment. Across 450+ client subscriptions, cost came to under 4% of the work worth doing. Security, compliance and reliability made up 92.4% of it. Two things stop that work getting done: seeing it across a whole book of clients, and helping the client see what it is worth to them. A roadmap solves the second one better than a list ever will.
I co-founded and exited a cloud managed services business. The P&L was mine.
Your next piece of billable work is probably already sitting in a client's environment. Not something anyone dropped. It's simply there, waiting for someone to spot it and turn it into a conversation. Some idle spend. A workload that could be reserved. A service heading for end of life. Every one of those is a project, and a reason to walk into the client already knowing what matters to them.
Let me show you one real environment rather than lead with a big headline number. In a single client tenant we looked at, the security and resilience work alone came to a genuine project: on the order of 96 hours of scoped, billable work, sitting there, ready to sequence and take to the client.
And it wasn't a one-off. Across 450+ client subscriptions we looked at, cost came to under 4% of the work worth doing. Security, compliance and reliability made up 92.4% of it. Usually a set of quiet, worthwhile improvements: tightening how a workload is reached, making sure a system is backed up, keeping a client's cloud resilient as it grows. Each modest on its own. Together, a roadmap of valuable work already in the environment.
The first challenge is simply seeing it
So why doesn't more of it get done? Two honest reasons, and neither is a failing.
The first is seeing it at all. A cloud estate is enormous and it shifts every week. Surfacing what's worth doing, by hand, across a whole book of clients, takes time your best people rarely have. They're the last people you want spending their week trawling for it. It was never that the work wasn't there. Finding it, and working out what's worth raising, is slow, careful work.
"There are project people: design it, build it, hand over the keys, walk away. And there are operators: feed it, water it, optimize it, react when it breaks. Managed services lives or dies on finding disciplined operators, and they are hard to find."
Free those people from the trawling and you get them back for the work that moves a client forward. One provider did exactly that, handing a few days of an architect's time back each month and putting it onto services work instead.
The second is helping the client see the value
Some of it the MSP already knows about. There the gap isn't seeing it. It's getting the client to understand the value, and the outcomes it achieves for them. A client doesn't say yes to "resize these VMs" or "turn on backup." They say yes when they can see what it's worth to them, and often they simply aren't ready to commit yet. That conversation, helping a client understand why the work matters, is the valuable part, and a genuine growth lever.
"We moved away from time-for-money to a value metric. Here's the outcome, here's the price. It meant we never had to have the 'I don't want to pay for that' conversation at all."
Put it on a roadmap, not a list
The way you make the value legible is to hand a client a roadmap instead of a list. Take what's in the environment and sequence it: what's worth doing now, what comes next, what can wait. Then put a rough shape of effort and time against each. This one's an afternoon, this one's a small project, this one's a quarter's work. Now the client isn't staring at a wall of findings. They're looking at a plan they can walk through with you, and commit to a step at a time.
That sequencing and scoping is the part that used to take an architect's evenings: turning a finding into "here's what it is, here's roughly what it takes, here's the order I'd do it in." Most of that can be produced for you now, so your people spend their time on the judgment rather than the write-up.
A roadmap does two things a list never will. It gives the client something they can say yes to in stages instead of all at once. And it makes you the provider who has clearly thought about their cloud, which is worth as much as any single project on it.
Spotting the work is a craft. So is getting a yes.
Seeing what's worth doing across a client's estate is a real skill, and it's one your team has. Packaging it so the client approves it is a skill of its own, and it's the one most of us learned on the job rather than being taught.
If that second half is where your findings tend to stall, we wrote up the four moves the best MSPs use to get from a technical finding to approved work: how MSPs turn a finding into work the client approves.
Start with one client
The opportunity is already in the accounts you've won. It just needs someone to spot it, and a way to walk the client through it.
Start with one client. Look at what's actually in the environment. Pick the handful worth doing, put them in an order with an ROI and timeline against each, and take that roadmap to the client.
So when you look at a client's cloud, are you looking at what it costs, or at what it's ready for?
Disclosure: this is the thinking behind Spotto, the company I co-founded, built to help MSPs surface and package exactly this kind of work. But the shift matters whether you ever use it or not.