Balancing Project Work Against Recurring Managed Revenue
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
A big project lands — a full network refresh, a cloud migration, an office move — and it's tempting to say yes without hesitation. The dollar figure is large, it's here now, and it feels like free money on top of your monthly recurring revenue. So the whole team pivots to the project. Then a managed client's server goes down, tickets pile up, response times slip, and the contract base you spent years building starts to feel neglected. The danger isn't project work itself; it's letting the loud, one-time payday quietly consume the capacity your recurring clients are already paying you to keep available.
Managed revenue is the foundation of an MSP — predictable, compounding, and the thing that makes the business worth more than the sum of its hours. Project work is real money too, but it competes for the same finite pool of technician time. When you don't allocate that time on purpose, projects win by default, because they're urgent and visible while managed obligations are quiet until they break.
ONE POOL OF TECH HOURS
managed contracts (paid to be available)
▇▇▇▇▇▇▇▇▇▇▇▇ ← reserved capacity
│
├─ project work fits in the slack → both served
└─ project work eats the reserve → contracts starve
tickets slip · SLAs miss · clients churnOwner symptoms
A large project lands and your managed clients' ticket response times immediately slip.
Techs are always "on a project," so routine maintenance and patching fall behind.
You take every project that comes, then scramble to cover the contracts you already owe.
Why this happens
Project revenue is loud and immediate; managed revenue is quiet and assumed. A $40,000 migration announces itself with a clear deadline and a happy client, while your managed obligations sit in the background making no noise — until a server dies during the week your whole team is heads-down on the project. Because the recurring work rarely screams for attention, it's the easiest thing to borrow capacity from. The problem is that you've already sold that capacity. Managed clients aren't paying for hours; they're paying for availability, and every tech you pull onto a project is availability you promised and quietly withdrew.
Common mistakes
Treating project revenue as pure upside instead of a claim on capacity you've already sold.
Saying yes to every project without checking whether the hours exist to deliver it.
Pulling techs off managed work reactively, so contract quality swings with the project pipeline.
No reserved capacity for the recurring base — projects consume whatever they need.
Judging the mix by revenue alone, ignoring which stream builds enterprise value.
Business consequences
Starving your managed base for a project is a bad trade even when the project pays well. A missed SLA or a stretch of slow response times can cost you a recurring client whose lifetime value dwarfs the one-time job — and that client tells others. You trade compounding, predictable revenue for a single payday, then spend months rebuilding trust. The owner who protects managed capacity keeps churn low, keeps the recurring base healthy and growing, and takes project work as a genuine addition rather than a hidden subtraction. Over years, that discipline is the difference between an MSP that's worth selling and one that's just busy.
How experienced operators think about it
They treat managed capacity as reserved and non-negotiable, and project work as something that fits into the slack around it — not the other way around. Before saying yes to a project, they ask a simple question: do we have the hours to deliver this without borrowing from what our contracts are paying for? If the answer is no, the honest options are to schedule the project later, hire or subcontract the extra capacity, or decline it. They also weigh the two streams differently. A dollar of recurring revenue is worth more than a dollar of project revenue because it compounds and it's what a buyer pays a premium for — so protecting it takes priority over chasing the next big one-off.
Practical actions
Reserve managed capacity first. Decide what share of tech hours your contracts require, and treat that as spoken-for before any project goes on the calendar.
Run project work through a capacity check. Only commit to a project once you've confirmed the hours exist outside the reserve — or that you'll add capacity to cover it.
Schedule projects into the slack, staggering start dates so no single week strips the managed base bare.
Add capacity for real project pipelines through hiring or trusted subcontractors, rather than borrowing from contracts you owe.
Learn to say no or not-yet. A project you can't staff without hurting clients is a project to decline or defer, not squeeze in.
Questions every owner should ask
If a big project landed tomorrow, do I know how many hours I could give it without touching managed work?
When project work spikes, do my managed clients feel it in slower response?
Am I weighing recurring and project revenue as if a dollar of each is worth the same?
Frequently asked questions
How much of my capacity should I reserve for managed work versus projects?
There's no universal split — it depends on your contract load, staffing, and how project-heavy your market is. The point isn't a magic percentage; it's that the number should be decided on purpose and protected, not left to whatever the project pipeline demands. Start by estimating the hours your current contracts actually consume in a normal month, add a buffer for the inevitable emergencies, and treat everything above that line as your true project capacity.
A huge project came in but I'm at capacity. Should I turn it down?
Not necessarily turn it down — but don't take it at the expense of clients you've already committed to. The honest choices are to schedule it for when you have room, add capacity to deliver it (a hire or a subcontractor), or decline it. Taking it and quietly borrowing hours from your managed base is the one option that looks like a win and usually isn't, because a churned recurring client costs more than the project pays.
Related articles
Running a Profitable Managed IT Services Business — the pillar.
Stopping the Small Favors That Quietly Blow Up Your Contracts — protecting the same capacity from scope creep.
Quoting a Managed Services Agreement Before You Know the Mess Inside — pricing the recurring base right.
Why Jobs Take Longer Than You Quoted — the general capacity-drain problem.
Where Time Leaks on a Typical Job — where hours quietly disappear.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.