The Onboarding Process That Decides an MSP's Margin on Every New Client

The client signed. Now the expensive part starts.

You have just closed a new managed services client. The proposal was priced per user or per device, the contract is signed, and somebody on your team is about to spend the next several weeks inside an environment they have never seen. They will find the domain admin account shared by four people, the backup job that reports success and restores nothing, and the firewall configured by a nephew in 2019.

Search for how to run that process and page one gives you checklists. Every one of them is organised around the first 90 days, and nearly every one is written from the client's side of the table: here is what to expect, here is when you will meet your account manager, here is when the business review happens. They are useful documents. They are also answering the wrong question for the person who owns the MSP.

The owner's question is not how to onboard smoothly. It is how much margin this client will produce, and the uncomfortable answer is that most of it was decided during onboarding, by what you agreed to accept.

The one hard number, and where it sits

The checklists do agree on one figure. Flamingo, an MSP tooling vendor, puts onboarding at 40 to 80 hours for a single new client, and ITPortal quotes the same range. Flamingo then does the arithmetic most articles skip: at a 65 dollar blended rate, a 70-hour onboarding is about 4,550 dollars of labour before the client has opened a normal ticket.

Now look at what typically pays for it. Intelligent Technical Solutions, an MSP that publishes its own pricing logic, tells prospective clients to expect an onboarding fee equal to one month of service. That fee covers getting users into your systems, adding servers, setting security protocols and bringing workstations up to standard. It does not cover remediation. Their own wording is that remediation hours depend on the state of the network, "so there's no fixed price."

That is an honest sentence, and it contains the whole problem. The work with a fixed price is the work you can predict. The work you cannot predict is the work that determines whether the client is profitable, and it is exactly the work that sits outside the fee.

Onboarding is a project priced before anyone saw the site

Consider the order of operations in the standard 30-60-90 plan. Datapath's version is typical: month one is discovery, validation and risk control; month two is where security hardening and remediation happen "in waves"; month three is a leadership review and the transition to steady state. Integritech's plan has the same shape, with migrations and security fixes in days 31 to 60 and the first strategic business review in the final month.

Put the commercial timeline next to that. The contract, and with it the monthly price, was fixed before day one. Discovery happens after the price. Remediation happens after discovery. So the MSP learns what it has actually agreed to support at the exact moment it has the least room to charge for it.

We see the same structure in private equity, where a deal is priced on the data room and the operational problems surface after close. We wrote about that gap in what operational diligence finds that a quality of earnings report cannot. An MSP onboarding is a small acquisition. You are taking on someone else's technical decisions, and you are doing it without diligence rights, because the diligence is scheduled for after the signature.

Flamingo's checklist says the quiet part plainly: if the assessment turns up problems outside the signed scope, say so in writing before you touch them, "or you have just volunteered for a remediation project nobody is paying for." That warning is correct, and in our experience it is routinely ignored. Not out of carelessness. Out of a very reasonable fear of opening a new relationship with a change order.

Why the bill arrives in month four

The cost of an unremediated environment does not show up during onboarding. During onboarding your best people are on site, the client is patient, and everyone is in project mode. Tickets are low because the environment is being looked at.

It shows up after the handoff to the service desk, somewhere around month four, as ticket volume. The backups that nobody fixed produce a restore request that becomes a weekend. The shared admin account produces a security incident, or at least a very long afternoon. The unsupported hardware that was noted in the assessment and deferred "to next quarter" produces the same ticket every other week. We described that pattern from the service desk's side in what MSP ticket triage really costs: a large share of a queue traces back to causes the MSP already knows about. Onboarding is where most of those causes were first written down and then accepted.

By month four the contract has been signed for a quarter. Sequentur, an MSP, writes that onboarding is "where the MSP relationship is built or broken," and it is right, but not only about the relationship. The per-client margin is built or broken there too, and nobody looks at it until the renewal.

This is the part of the story where somebody usually suggests an onboarding automation tool.

What automation fixes, and what it does not

There are good products for this. Flamingo claims modern tooling cuts onboarding time by 30 to 40 percent, which on their own example is roughly 1,600 dollars of labour saved per client. Scripted agent deployment, automated documentation capture and templated access provisioning are real improvements, and an MSP onboarding more than a few clients a quarter should have them.

Notice what they speed up. They shorten discovery. They do not change what happens after discovery. A faster assessment of an environment you have already agreed to support at a price you have already set is still an assessment you cannot act on commercially. If anything, automated discovery makes the problem easier to ignore, because a tool that produces a clean 40-page report creates the feeling that the environment has been dealt with. It has been described. That is not the same thing.

The savings are also on the wrong side of the ledger. Saving 1,600 dollars of onboarding labour on a client whose unremediated environment generates two extra tickets a week for three years is a rounding error against the thing you did not price. We make the same argument about agencies in why time tracking is a pricing problem disguised as an admin problem: when the hours are running over on a fixed fee, the hours are rarely the problem. The price was.

The margin question is what you refuse to accept

In our experience, the MSPs whose per-client margin holds up share one habit, and it is not a faster checklist. It is a clear, written position on which environments they will support as found, which they will support only after remediation, and which they will not take at all.

That position changes where things sit in the process. The assessment moves in front of the price, either as a paid engagement or as a condition of the final quote. Remediation becomes a line item the client can see and decline, and a decision to decline it is recorded with a consequence attached, such as a different service tier or an exclusion from the flat fee. The onboarding fee stops being a month of service by convention and starts reflecting the environment it is paying to bring up to standard.

None of this is exotic, and yet the pricing of onboarding is visibly contested inside the industry. The written material barely mentions it. Search video instead and the practitioner content is asking the question directly, under titles like "What Is MSP Onboarding and Should You Charge For It?" When operators are still debating on camera whether to charge for 40 to 80 hours of work, the written checklists are not where the answer lives.

It is also the hardest part to get right on your own, because the thresholds are specific to your stack, your client mix and your sales motion. Which findings are dealbreakers. Which are priced in. Which you can tolerate for a quarter and which will cost you by month four. Where your current contracts already give you room to reprice and where they do not. An article can tell you those are the questions. It cannot tell you your answers.

Before you onboard the next one

If you have a client in onboarding right now, there are two things worth doing this week. Pull the discovery findings and mark each one as remediated, scheduled with a named owner, or accepted. Then look at the accepted column and ask whether anyone told the client, in writing, what accepting it means for them.

For the clients already past month four, the same exercise works in reverse. Their ticket history will tell you which onboarding findings turned into support cost. That list is the most useful input you have for the next renewal conversation, and for the next proposal you write.

If your newest clients are the least profitable ones on the books, and the onboarding checklist looked fine every time, talk to us. We would start with what your last five onboardings found and what happened to each finding after the price was already set.