The MSP sales process: seven stages from first call to signed client
The MSP sales process is a set of steps a managed service provider follows to turn a business owner who might need IT support into a signed client. In a small MSP, sales often depend on the owner’s free time, because the process lives in one person’s head. Writing it down as stages, each with a clear test to move on, makes sales repeatable. This guide sets out seven stages, from choosing who to target to handing a new client to the service desk, with what to do and what "done" looks like at each one.
It is written for MSPs selling to small and mid-sized businesses, roughly the 10–50 staff range, in the UK and the US.
What are the stages of an MSP sales process?
| Stage | Goal | Exit test |
|---|---|---|
| Target | Choose businesses you can serve well | A named list with a reason to contact each |
| First call | Understand the business and its pain | A clear problem and the decision-maker identified |
| Assessment | See the real state of their IT | Findings written up in plain language |
| Findings meeting | Agree what matters most | The owner agrees on priorities |
| Proposal | Offer a scope, a price and a start date | Proposal sent and walked through |
| Decision | Answer concerns and agree terms | Signed agreement, or a dated "not now" |
| Handover | Move the client to onboarding | Onboarding plan accepted by the client |
A deal moves to the next stage only when the exit test is met. That one rule keeps your pipeline honest: no more "proposals" that were never discussed, or "hot leads" nobody has spoken to.
Target: who should you approach?
Pick a type of business you understand and can support from your current team: a sector, a size and an area. The tighter the focus, the easier everything later becomes, from the first email to the proposal.
Look for a reason to contact each business now: a move, new hires, a new contract that asks for security standards, or an IT person who has just left. Our guide on how MSPs get new clients covers channels and triggers in detail, and our MSP cold email templates give you wording for the first message. If you write your own, our guide on how to write a cold email explains the structure.
First call: what should you find out?
The first call is for listening. Ask about the business before the technology: what they do, how many people, what has gone wrong recently, who looks after IT today and what they would change. Our list of discovery call questions for MSPs gives you a full set.
By the end of the call, you should know two things: the problem in the owner’s words, and who makes the decision. If you cannot name both, the deal is not ready for an assessment.
Assessment: how should you run it?
The assessment is where an MSP earns trust. Keep it structured, so the owner sees a method rather than a sales pitch.
Two public frameworks give you a neutral structure:
- NIST Cybersecurity Framework 2.0. NIST says CSF 2.0 "is designed for all audiences, industry sectors and organization types, from the smallest schools and nonprofits to the largest agencies and corporations". Its core is "organized around six key functions: Identify, Protect, Detect, Respond and Recover, along with CSF 2.0’s newly added Govern function". NIST also offers quick-start guides for specific users, "such as small businesses". See the NIST Cybersecurity Framework.
- Cyber Essentials (UK). The NCSC calls it "the minimum standard of cyber security recommended by the Government for organisations of all sizes". It is built on five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. See the NCSC Cyber Essentials overview.
You can use the six functions as headings for your findings, and the five controls as a practical baseline for UK clients. For a lighter first look, the NCSC’s Small organisations guide to cyber security covers email, important online accounts, devices, backups and spotting attacks.
Agree the scope of the assessment in advance: what you will look at, what access you need, how long it takes and whether it is free or paid. Write it down in one short email.
Findings meeting: how do you present what you found?
Present findings in a meeting, not just a report. Owners act on what they understand.
A simple structure:
- What we looked at. One line on the scope.
- What is working. Start with the good news; it shows you are fair.
- What needs attention. Three to five issues at most, each in business terms: what could happen and what it would affect.
- What we suggest first. The two or three actions that matter most.
- Questions. Let the owner react before you talk about price.
Avoid fear. The facts are usually enough. If a UK client tells you their customers have started asking about security, you can quote the NCSC: "a growing number of organisations require suppliers to be certified to bid for work". Offer to help them prepare, and never promise that they will pass.
Proposal: what should it include?
A good proposal follows from the findings meeting. If the owner is surprised by anything in it, the meeting did not do its job.
Include:
- The problem in their words, from the first call.
- The scope: users, devices, sites and services covered, and what is not covered.
- Service levels: how they contact you, how quickly you respond and when you are available.
- The first projects from the findings, with a rough order.
- Price and how it changes when they add users or sites.
- Start date and onboarding steps.
- Term and notice.
Walk the owner through the proposal on a call rather than sending it cold. Agree a date for the decision before you hang up.
Decision: how do you keep the deal moving?
A deal can stall here, not because the owner says no but because nobody agreed what happens next. Ask directly: "What do you need to decide?" and "Who else needs to see this?"
Expect objections such as "we already have an IT person" or "it’s too expensive". Our guide to MSP sales objections gives honest answers for each. If the answer is "not now", agree a date to check in and record it in your pipeline.
Handover: how do you pass the client to onboarding?
The sale is not finished when the agreement is signed. A poor first month can undo a good sales process.
- Brief the service team on what was promised, including anything said on calls.
- Share the findings so the first projects start from what the client already agreed.
- Introduce one named contact for the first weeks.
- Book a review at the end of the first month or quarter.
MSP sales process checklist
- Target type of business defined (sector, size, area)
- A reason to contact each business noted
- First call held; problem and decision-maker recorded
- Assessment scope agreed in writing
- Findings presented in a meeting, in business terms
- Proposal walked through on a call; decision date agreed
- Objections answered or a dated "not now" recorded
- Handover brief shared with the service team
- First review booked
How do you measure the process?
Track a few numbers per stage: how many businesses reach each stage, how long they stay and how many move on. The stage where most deals stop is where to improve first. To set a monthly target, our guide on how many sales meetings you need per month works backwards from your revenue goal.
Where does Arbyn Partners fit?
Arbyn Partners books meetings for B2B firms in the UK and the US, including MSPs, with business owners or decision-makers who have a real need, not a competitor or an existing client of yours. We fill your diary with first calls; you run the rest of the process. You pay only for qualified meetings that take place: £150 in the UK and $200 in the US. The first qualified meeting is free, one per company, and there is no retainer. See our page on lead generation for MSPs.
More about Arbyn Partners is on our homepage.
The handover starts the next job: keeping the client. Our client retention checklist covers the first month, quarterly reviews and the warning signs to watch.
Two templates help at the later stages: our IT services proposal template for the proposal, and our onboarding checklist for new MSP clients for the handover. To decide how you charge, see MSP pricing models explained.
FAQ
What are the stages of an MSP sales process?
Target, first call, IT assessment, findings meeting, proposal, decision and handover to onboarding. Each stage has a clear test that must be met before a deal moves on.
Should an MSP charge for an IT assessment?
It is your choice. What matters is that the scope, access needed, timing and any cost are agreed in writing before you start.
Which framework should I use to structure an assessment?
You can use the six functions of the NIST Cybersecurity Framework 2.0 as headings, and the five Cyber Essentials technical controls as a practical baseline for UK clients.
How many issues should a findings meeting cover?
Keep it short: what is working, a handful of issues in business terms, and the two or three actions that matter most.
Why do MSP deals stall after the proposal?
Usually because no decision date or next step was agreed. Walk the owner through the proposal on a call and ask who else needs to see it.
Can Arbyn Partners book first calls for MSPs?
Yes. We book qualified meetings with owners or decision-makers who have a real need. You pay £150 in the UK or $200 in the US per qualified meeting held, and the first one is free.