

Picture a prospect at their desk with two proposals in front of them. Yours is on the left, the other MSP's is on the right. Both say managed IT, both list a help desk and monitoring and patching and backups, and one of them costs a lot less than the other.
Which one would you pick if you were them? Most people go with the cheaper one, and I don't blame them. They're not dumb, from where they're sitting the two quotes look pretty much the same so price ends up being the only thing left to compare.
You might have real security people, a trained team, a process that works and none of it shows up on the page.
In our experience working with MSPs this happens for two reasons.
First, most MSPs blend security into the monthly fee without ever calling it out, or they leave it off the quote and plan to bring it up later once the client is signed. Either way the client can't see where the real expertise is.
Second, most MSPs only show a client what the client asked about or what they're ready to buy right now, so the client never finds out how deep the offering goes. Meanwhile the cheap guy down the street, who usually isn't delivering much security at all, looks like the same thing for less money.
Fix number one, pull your security services out and give them their own name, their own scope and their own line on the proposal. Once a prospect sees security laid out by itself with real work attached to it, they can finally see what the cheaper quote is missing. It protects your margin too, because you're no longer burying a skilled service inside a price that's getting compared to someone who doesn't offer it. And it makes the quarterly security briefing easier since the client already knows security is something you do on purpose.
Fix number two is showing them everything you offer, not only what they want today. I know that sounds backwards, we were all taught to quote what the customer asked for and not overwhelm them. But clients can't put a value on something they don't know exists. When the whole menu is in front of them they can see how much expertise you've got, and they can see where they might grow into over the next few years. It also cuts down on the "I didn't know you guys did that" comment that always seems to show up at renewal time. Your competition isn't doing this at all, so it's one of the easiest ways to stand out. And showing everything doesn't mean selling everything, you're just making sure nobody has to guess.
Then there's the three year agreement, which a lot of owners flinch at asking for but I think is one of the best things you can offer a client.
On your side it gives you predictable revenue, so you can invest in onboarding and standardization and good people without wondering if the client is gone in twelve months. It also makes the business worth more when it's time to sell, since anybody looking at your company wants revenue they can count on.
On the client's side it locks in a standard rate with inflation already built in, instead of a market adjusted increase every single year. They know what they're paying and they can budget around it. It also makes planning bigger projects easier.
Three years is about a normal lifecycle in IT, so the term lines up with when hardware gets replaced and when the larger projects come due. Instead of getting surprised by a firewall that's end of life, you sit down together and map out what's coming, spread it out, and plan for it. Those conversations get a lot better too, because you're not selling something every year to justify being at the table. You're planning with them.
A three year term only works if the client can see the value from month one though. That means clear service levels, a way out if you keep missing them, and a review every year so nobody feels stuck. If you ask for three years and can't show them anything for it, that's just wishful thinking.
One more thing, and it's about your team. When your packages are written down clearly your technicians know what's included and what isn't and what to do when a request falls outside the line. Fewer arguments about whether something's covered, cleaner escalations, and something your service manager can coach to. When the offering is vague your team feels it every single day.
If you want to check your own packaging, here are some quick questions. Could a prospect tell in a minute or so which part of your offering is security and which part is help desk? Does your proposal show everything you do or just what they asked for? Put your quote next to the cheapest one in town, would a stranger see the difference? Is your term short enough that the client reopens the whole decision every year? And would your techs know what's covered in each package without asking you? If you missed more than one of those, you've got some work to do, and you're in good company because most MSPs do.
All of this belongs in your field guide, the packages and the pricing logic and the term structure, written down so every proposal gets built the same way no matter who's writing it. That's the kind of thing we help with at www.builttorunmsp.com.
Frequently Asked Questions
Should MSPs separate security services from their managed services offering?
Usually, yes. Giving security its own name and scope makes the value easy to see, protects your margin, and helps explain the difference between you and a lower priced MSP that isn't delivering real security.
Why show clients services they aren't buying yet?
Clients can't value what they don't know exists. Showing the full set of services shows the depth of your expertise and gives them a path to grow into, without you having to sell all of it at once.
Are three-year agreements good for MSP clients?
They can be when the value is clear from the start. A three-year term locks in a standard rate with inflation built in instead of a market adjusted increase each year, and it matches the typical three-year IT lifecycle, which makes planning bigger projects and hardware refreshes easier.
What makes a three-year MSP agreement fair to both sides?
Clear service levels, a defined way out if the MSP keeps missing them, and a review every year. Without those, a long term can feel like a trap.
Adam Kuester
Adam Kuester has a PhD in genetics and a career built inside managed services, an unusual combination that shapes how he works. He spent time designing operations at an MSP before joining Bruce McCully to build Galactic Advisors, where he's served as VP of Special Projects. His focus has been operational: finding gaps, building systems, and turning expertise into tools MSP owners can use across a partner base of nearly 1,000 companies. Built to Run MSP is that same work in a different form, practical frameworks for MSP owners who are good at winning business and want to get equally good at running it.