How to sell managed services as a small MSP: pick clients you can serve, qualify them on a short call with a price range, and run discovery before pricing. Sell one monthly package with written edges, ask for a decision on a date, then check actual support against assumed hours.
Below: the stages, six steps that follow one client to a signature, the objections you'll hear, a meetings calculator, and the numbers to watch. They come from the team behind SherpaDesk, a helpdesk and PSA (professional services automation) a small IT team can run alone. Two founders who ran their own MSP have built it since 2001.
Key takeaways
A managed service provider is a third-party company that remotely manages a customer's IT, usually for a flat fee paid on a schedule, often monthly. So you aren't selling a repair or a project. You're selling a monthly promise, and the buyer is betting on how you'll behave for years.
That changes the order of the conversation. In a small MSP, sales is usually the owner's second job, done between tickets. A fixed set of stages, each with a clear exit, keeps that job short.
One widely used marketing textbook, OpenStax's Principles of Marketing, splits personal selling into seven steps. Here's what each looks like when you're selling managed services:
| Stage | What you do | You leave with |
|---|---|---|
| Prospecting and qualifying | Pick the client type; 15-minute call | Fit, budget range, who signs, timing |
| Pre-approach | Read their website, staff count, sites, and industry rules | Three questions only they can answer |
| Approach | First meeting, on site if you can | Their problems in their words |
| Presentation | Discovery findings, then one recommended package | A yes, or the change they need first |
| Handling objections | Price, incumbent, timing, "never had a problem" | Each objection answered, or a clear no |
| Closing | Ask for a decision on a date | Signed agreement and a start date |
| Follow-up | Onboarding and the first 90 days | Support hours checked against the fee, a referral ask |
The right column is the point. If you can't say what a stage left you with, you haven't finished it. When a sale stalls, check the first exit: did anyone ask who signs and what they'd pay?
Five things make the steps below work, and you can build each in an afternoon:
These steps cover how to sell managed services to a business that isn't your client yet. Moving an existing hourly client to a contract is a different conversation.
Six steps, from the first call to the signature. Each ends with something you can check.
Write down the client you want more of: industry, headcount, sites, and what they already run. Then estimate how many exist near you. The Census Bureau's County Business Patterns counts establishments with paid employees by industry and employment size, below the national level. Treat that as a rough market estimate; headcount bands, software, and drive time you check prospect by prospect. In the SBA's 2026 summary of 2022 data, 6.4 million of 36.2 million US small businesses have paid employees; the other 29.8 million have none.
Why it matters: a bad fit costs as much to win as a good one. As one r/msp member put it, "It's as much work to prospect and onboard the right prospects as it is the wrong ones. Wrong ones will sink you eventually."
Example: "Architecture and engineering firms, 10 to 40 staff, one office, Microsoft 365, within 45 minutes' drive." An r/sales member who sells IT services advised: "Spend more time with businesses that have understanding of it but need more help." The rest of the steps follow one such firm, Harbor Architects, with 18 staff.
Common mistake: chasing anyone with a computer. You end up supporting ten different stacks with one set of hands.
Check four things: the problem in their words, a monthly budget range, who signs, and when they could start. Qualifying means narrowing leads to good fits, including whether they can afford it and whether your contact can make the purchase decision. Say your range out loud. One r/msp member does exactly that: "I will frequently do the 15-minute call to qualify a prospect. And I will give them a very realistic monthly number to chew on."
If they already have a provider, don't attack it. "You need to ask how it's going and when their contract is up," as the r/sales member put it. A renewal date is a follow-up date.
Example: Harbor's office manager calls after a bad week with the file server. Say your range is $100 to $150 per user: "For 18 people, that's $1,800 to $2,700 a month. Is that in the range you expected? And who besides you signs off?" She expects that range, the two partners sign together, and they want someone in place before their January deadlines.
Common mistake: a 45-minute walkthrough before you know who signs. Ask in the first five minutes.
Meet on site and bring a technician. One r/msp member's routine: "Short phone call to discuss their needs, and if we're a good fit then a site visit to get the details."
Ask in business terms first: what stops work, what an hour of it costs, and what changes in the next year. Then cover people, sites, admin accounts, backups and the last restore test, devices, key apps, and any insurance or compliance demands. A non-technical sales manager in one r/msp thread wants technicians to "standardize a list of questions that have to be answered on the initial discovery call."
Why it matters: a quote built on the request, not the environment, breaks at kickoff. In the same thread, a manager's team quoted an Intune rollout, then found a messy hybrid setup on the kickoff call and needed a change order. A reply was blunt: "Kickoff isn't where you do discovery, it's before you sign."
Example: at Harbor, project drawings live on one file server in a closet. It stalled for a morning in October, and eight architects couldn't open drawings two days before a client deadline. Backups run, but nobody has ever restored from one. The business problem isn't "the server." It's billable design hours lost before deadlines, with no tested way back.
Common mistake: handing over a full written plan for free. A prospect can take it to a cheaper provider or do the work themselves. Keep the free visit to findings; charge for a plan.
Turn the findings into one recommended package that fixes the problem you found. Write the services, the response times, what's billed separately, and the fee in the unit you quoted on the first call. Bill onboarding as its own line. One r/msp member uses "an assumed onboarding fee, equivalent to one month mrr if things are relatively ok." If the client may want something extra, name it as a separate add-on with its own boundary. Don't blur it into the monthly fee.
Example: for Harbor, helpdesk for 18 users on weekdays, 8 a.m. to 6 p.m. First response within 1 business hour when someone can't work; 4 business hours for the rest. Nightly backup of the file server with a restore test every quarter, patching, and MFA on every account. $2,250 a month ($125 per user), plus onboarding at $2,250 once, one month of the fee.
Not included: new hardware, office moves, and projects such as a server replacement, each quoted separately. Add-on: deadline-week standby after hours, quoted per week when they ask for it.
Common mistake: "unlimited support" with no written edges. The first office move turns into free labor.
Book the meeting with everyone who signs before you leave the discovery visit. Start with their problem in their words, then the package, then the start plan. Bring one client they can call, if you have one. For the written document, use our managed services proposal template with one recommended package in place of its Option A/B section.
Why it matters: the meeting is where the buyer asks questions you can answer on the spot. One r/msp member said it plainly: "If they won't cover the proposal in person and make a decision, it isn't that important to them." If a prospect won't give you 30 minutes, ask why before you send anything. Speed counts too. Another, at a five-person MSP: "We have lost countless, solid leads because we were too slow to get in front of people."
Example: to Harbor's two partners: "In October, eight of your architects lost a morning two days before a deadline. This plan puts a tested restore and a one-business-hour response behind that file server. It's $2,250 a month, plus $2,250 once for onboarding."
Common mistake: emailing the PDF and following up "next week". Nobody explains your recommendation better than you.
For many salespeople, asking for the order is the hardest step. A trial close makes it easier: talk through terms or the start date to see whether they're ready. Then agree the date they'll decide by, and what happens on a yes.
Example: "Can you two decide by Friday, December 4? On a yes, you sign the agreement that day, onboarding starts Monday, December 7, and the monthly fee starts when onboarding ends." One partner wants the first restore test date in writing. You add it, and they sign on the 4th.
Common mistake: leaving a deal open with no decision date. If the answer is "we need to think," ask what's missing and set the date anyway.
Listen, then restate the question before you answer it. Expect price to come up almost every time, and prepare for it. These are common objections for a small MSP. Ask a clarifying question before you answer, and don't reach for a discount:
| They say | Possible reason | Ask first, then |
|---|---|---|
| "It's too expensive." | The spend feels too high, or the result isn't clear yet | Ask: "Is it the monthly amount, or what you get for it?" Then tie the fee back to the problem from discovery |
| "We already have an IT person." | Some tasks are covered, others may have no owner | Ask: "Which tasks does that person handle today?" Then offer to cover only what has no owner |
| "We already have an MSP." | The service may be fine, or a renewal may be close | Ask how it's going and when the contract ends; follow up before that date |
| "We've never had a problem." | No incident has hurt them yet | Ask: "When did you last restore from a backup?" Then show one discovery finding with its cost |
| "We need to think about it." | Information is missing, or someone else decides | Ask: "What would you need to decide?" Then confirm who signs and set a date |
| "Just send me some information." | A polite exit, or it's too early | Ask: "What should it cover?" Then offer the 15-minute call |
"We've never had a problem" deserves facts, not fear. The SBA puts it plainly: "Small businesses in particular may lack the means to protect their digital systems." In 2025, the FBI's IC3 logged 24,768 business email compromise complaints with $3.05 billion in reported losses. Tie that to what you found: shared admin passwords, or a backup nobody has restored.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Selling managed services takes a steady flow of first meetings. Your close rate gives a planning estimate of how many you need for a goal. Enter your own numbers:
Qualified first meetings needed
new clients ÷ close rate, rounded up. A planning estimate: some deals from these meetings may sign next quarter. Your numbers stay in the browser.
Example: you want three new clients this quarter and sign one in four qualified prospects. That's about 12 qualified first meetings, roughly one a week over 13 weeks. If your calendar shows two a month, check targeting and lead flow before you work on your close.
Don't know your close rate? Take one group of qualified first meetings, say last quarter's, and wait until every deal from it has signed or ended. Signatures ÷ meetings in that group is your rate. Track deals still open separately.
Follow-up is where the real work begins: onboarding, repeat business, referrals, and upsells. For a managed services client, the first quarter also shows whether the support effort matches what the fee assumed. That's an effort check, not a profit statement.
Deliver what the agreement promised to set up first; for Harbor, that's the first tested restore. Our MSP onboarding checklist covers each phase. Log onboarding time apart from support, since it's billed separately.
Call the person who signed: what got fixed, what's still open, what surprised them. Compare support hours logged on this client with the hours your fee assumed.
If support hours still run high, find out why before you change anything. Look for onboarding leftovers, a one-off project, one heavy user, or scope discovery missed. Then fix it the way your agreement allows.
Show tickets, fixes, and the plan for next quarter. Ask who else they know who needs the same help.
The hours check is the easiest one to skip. A flat fee can hide an overrun until renewal.
Run this for every prospect. Each item is a yes or no.
Measure your MSP sales process once a month, then change one thing a quarter and watch the numbers. In MSP sales, some deals stay open for weeks, so count open deals apart from finished ones. Test, measure, adjust: a sales process that never changes stops working when your market does.
| Measure | How to count it | When to investigate |
|---|---|---|
| Qualified first meetings | Prospects who passed the 15-minute call: fit, budget, signer, and timing | The count falls: check step 1, your targeting and where leads come from |
| Meetings to discovery visits | Share of qualified first meetings that book a visit | The share falls: check step 2, when you gave the range and who was on the call |
| Close rate | One group of qualified first meetings, once every deal has signed or ended: signatures ÷ meetings | The rate falls: find the stage where most of that group dropped |
| Proposal win rate | One group of presented proposals, once every one has signed or ended: signatures ÷ proposals | The rate falls: check steps 4–5, whether the package matched the problem and which objections went unanswered |
| Days from first call to signature | Median, for agreements signed this month | The number rises: check step 6, whether each deal had a decision date |
| Support hours vs. hours the fee assumed | Per new client, at day 30 and day 60, onboarding excluded | Actual hours run over plan: find the cause first (leftovers, a project, one user, or missed scope) |
| Referrals asked and received | Count, from day-90 reviews | The count falls: check whether the day-90 reviews happened |
Your close rate from one finished group of meetings goes into the calculator above. The hours measure needs support time logged by client from day one. It tells you about effort, and it's the evidence you'll want before any scope or price conversation.
How this works in SherpaDesk
You can import the new client from QuickBooks, Xero, FreshBooks, or an Excel file, and give the account its own rate plan. A contract can carry rate plans, expenses, and prepaid hours. If you sell a flat fee + hourly contract with included hours, alerts fire as it nears or passes them.
Technicians log time with Add Time, a calendar timesheet, or a start/stop timer. For the day-30 look, standard reports include a Time and Cost report, a Time Log Detail report, and a Contract Detail Report with prepaid-pack hours remaining.
A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.
Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever, and the trial is 14 days free with no card.
See Invoicing And Billing In SherpaDesk →
Who this isn't for
MSPs with a sales team that needs pipeline stages, lead scoring, and email sequences: that's CRM software, next to your helpdesk and PSA. MSPs answering a formal RFP, where the buyer sets the format and the steps.
A common textbook model lists prospecting and qualifying, pre-approach, approach, presentation, handling objections, closing, and follow-up. For a small MSP, qualifying is a 15-minute call, the presentation is discovery findings plus one recommended package, and follow-up is onboarding and the first 90 days. The stages table shows what each stage should leave you with.
For managed services: get in front of the buyer quickly, learn their problems before you price, and present one recommendation in a meeting, not by email. Give a price range early so nobody wastes an afternoon. Then ask for a decision on a date. The six steps above put that in order, with an example and a common mistake for each.
Charge when the deliverable is a plan someone could hand to a cheaper provider. Keep the first visit free and limited to findings. One r/msp member charges "a flat $300 for my time and that includes cost for the on-board project proposal." If the prospect signs, you can count the fee toward onboarding.
Most charge a flat fee paid on a schedule, often monthly. The amount should come from the hours your clients take and the hourly rate you need, not from another MSP's price list. For selling, what matters is saying it early: give a per-user or per-device range on the first call. The pricing guide in What You Need Before You Start walks through the math.
Usually the owner, with a technician at discovery. The owner can talk price and sign; the technician spots the hybrid setup or the backup nobody tested before it reaches a quote. In one r/msp thread, a manager whose CEO and sales team ran those calls without a sales engineer described quotes that missed the real environment and needed change orders.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.