Quoting a Managed Services Agreement Before You Know the Mess Inside
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
A prospect calls, frustrated with their last IT provider, and wants a flat monthly number to take everything off their plate. You've got a headcount, a rough sense of their industry, and a deadline to send the quote. So you price it off seats and hope the environment behind the login screen is roughly normal. Then onboarding starts, and you find failing backups, servers two versions past end-of-life, and a firewall nobody has touched in four years. A flat MSA price is a bet on the condition of an environment you haven't seen yet — and if you bet blind, you inherit someone else's neglect at your own expense.
The trap is that the mess is invisible at quoting time. A twenty-seat company with a clean, patched, documented environment and a twenty-seat company held together with duct tape look identical on a headcount spreadsheet. One is profitable at your standard rate. The other will bleed your techs' hours for the first six months while you fix problems you didn't price for — and the contract you signed doesn't let you charge for any of it.
TWO 20-SEAT CLIENTS, SAME QUOTE
priced on seats ──┬── clean, patched, documented → profitable
│
└── failing backups, EOL servers,
four years of neglect → margin sink
▲
the difference you couldn't see at quoting timeOwner symptoms
New clients look fine on paper, then eat far more labor than the MSA priced for.
Your first ninety days on an account are spent fixing inherited problems for free.
You can't tell profitable prospects from money pits until you're already committed.
Why this happens
Managed services quoting rewards speed and simple numbers — a per-seat or per-device figure the prospect can compare against the last guy. That model works when environments are healthy, but it prices the count of things, not their condition. Neglect, deferred upgrades, and undocumented tangles don't show up in a seat count, so the quote silently assumes a baseline the environment may not meet. The prospect switching providers is often switching because something is wrong — meaning the environments most likely to be a mess are exactly the ones landing on your desk.
Common mistakes
Quoting off headcount alone, treating a seat count as a proxy for the real work.
Skipping assessment to win faster, then discovering the condition after you've signed a flat price.
Assuming a normal baseline, so inherited technical debt becomes your unpaid problem.
Writing no remediation clause, leaving no way to charge for fixing what you didn't cause.
Pricing the honeymoon, not the marriage — quoting steady-state support while ignoring the heavy first-quarter cleanup.
Business consequences
A blind MSA turns your worst-condition clients into your least profitable ones, and it front-loads the loss: the neglected environment costs you the most exactly when you can least afford it, in the onboarding window before the relationship has earned any goodwill. Your techs burn out on someone else's deferred maintenance, your margin on the account may never recover to plan, and you learn the client was unprofitable only after the ink dried. The owner who assesses first prices to reality — separating the one-time cleanup from the ongoing agreement, walking away from the true money pits, and signing steady-state contracts that actually hold their margin.
How experienced operators think about it
They treat the assessment as the product's first deliverable, not a favor. Before a flat number exists, they want to know the condition: backup status, patch levels, hardware age, security posture, documentation quality. They separate two things the naive quote jams together — the current-state remediation (a one-time, scoped project to get the environment to a supportable baseline) and the ongoing managed agreement (priced for a healthy steady state). The MSA assumes the baseline; the remediation earns it. If a prospect won't pay for an assessment or refuses to fix what's broken, that refusal is itself the answer about whether they'll be a good client.
Practical actions
Assess before you price. Run a paid or scoped discovery of the environment's condition before any flat number leaves your office.
Quote two things, not one. Separate the one-time remediation project from the ongoing MSA so cleanup isn't buried in a flat monthly fee.
Define your supportable baseline. Write down the condition an environment must reach — backups, patching, supported hardware — before steady-state pricing applies.
Put a remediation clause in the agreement. Give yourself a contractual way to bill for inherited problems you discover after signing.
Be willing to walk. A prospect who won't fund the assessment or the cleanup is telling you the account will lose money.
Questions every owner should ask
Do I know the condition of an environment before I commit to a flat monthly price?
Is inherited technical debt someone I can bill for, or does my contract make it mine?
Which of my current clients were priced blind, and are they the ones bleeding margin?
Frequently asked questions
A prospect won't pay for an assessment and wants a number now. What do I do?
Give a number, but make it conditional and honest: a range, explicitly contingent on the environment meeting a supportable baseline, with a clear statement that anything below that baseline is scoped and priced separately after discovery. If they refuse both the assessment and the conditional framing, that's a signal — the prospects most resistant to being assessed are often the ones with the most to hide, and the ones most likely to turn into unprofitable accounts.
How do I separate one-time cleanup from the ongoing agreement without scaring the client off?
Frame it as getting their environment to a healthy, supportable state — which is what they're actually paying you for. Most clients understand that a neglected system needs work before it can be maintained affordably, the same way a neglected building needs repairs before a maintenance contract makes sense. Presenting the remediation and the ongoing agreement as two clear line items is more transparent than hiding the cleanup cost in an inflated monthly fee, and it protects your margin without a surprise later.
Related articles
Running a Profitable Managed IT Services Business — the pillar.
Getting Recurring IT Invoices Paid On Time Every Month — protecting the revenue once you've priced it right.
Managing Cash Flow When You Float Client Hardware Purchases — the cash side of onboarding new clients.
Why Jobs Take Longer Than You Quoted — the general estimating problem.
Where Time Leaks on a Typical Job — where hidden hours 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.