If you run an MSP, the odds are high that sales sits in your head as a separate, slightly unpleasant job that you tolerate because somebody has to do it. Your real work, the thing you got into the business to do, is fixing technical problems and keeping clients running. Making people care about that work, in your mental model, is a nice-to-have.
I want to argue that model is the single biggest reason your pipeline is inconsistent, your close rate feels flat, and every sales conversation drains you more than it should. Sales belongs inside the same culture you’re already building on the service side, as a pre-delivery extension of that culture rather than a bolt-on function tacked on beside it.
This post is for MSP owners, MSSP leaders, and service provider sellers who feel stuck between running the business and growing it. The move you need to make is mental before it’s tactical.
The Restaurant in Your Head
Here’s the picture I use when I coach technical founders on this. Think about a restaurant where the waiters and the cooks hate each other. The waiters are mad because the cooks are slow. The cooks are mad because the waiters keep putting the orders in wrong. Meanwhile, the customer has been sitting at a table for forty minutes waiting on a salad, and when it arrives, half the toppings are wrong. Everybody is pointing at each other, the customer leaves, the review gets written, and nobody in the building makes any money.
That is what sales and operations look like in most MSPs. One team is trying to close business. The other team is trying to deliver it. They talk past each other. They blame each other when things go sideways. And the client sits in the middle, waiting for a salad.
The fix isn’t cross-training or a better ticketing system. The fix is recognizing that sales and operations are playing different positions on the same team. They’re working from the same culture, the same promise, and the same definition of what a good client outcome looks like. Once you see it that way, the adversarial dynamic between front of house and back of house goes away, because nobody wastes energy on the interdepartmental fight.
Mindset Beats Tactics by an Order of Magnitude
When technical founders bring me in to fix their sales motion, the first thing they expect is a script. A better discovery framework. A new closing line. Words they can parrot in a meeting that will finally get the results they want.
I disappoint them early. The biggest problem in our industry around sales is a mindset problem rather than a tactical one, and by my reckoning it’s about an order of magnitude more important than anything you might do on the surface. You can read a whole book that tells you exactly what to say. You can memorize the words. If your underlying belief about sales is that it’s adversarial, or that selling is slightly beneath you, or that you hate doing it, those words will come out of your mouth and land flat. The prospect hears it. They always hear it.
Case in point: how many sales experts are out in the world right now beating people over the head with advice? And then how many MSP owners are parroting that advice back to prospects without any conviction behind it, losing the deal, and getting more frustrated? Almost all of them. The words were fine. The mindset behind the words was broken.
The Most Common Tactical Mistake
Once the mindset is right, tactics start to matter, so let me give you one that I see everywhere and that is almost always a symptom of the bigger issue. MSP sellers send proposals in blind emails. They take a first meeting, do a little discovery, go back to their office, guess what the prospect wants, guess what the prospect will pay, build a proposal, and email it over.
Then they wait. Then they wait some more. Then they chase, maybe once a month for six or twelve months, until they give up and wonder why the pipeline feels broken.
I would never email somebody a proposal and hope they called me back. That’s insane. A proposal is a collaborative document. It should get reviewed with the prospect, live, on a call or in a meeting, so that every number and every line item can be discussed in context. The moment you drop a proposal into an inbox and retreat to your desk, you have handed the entire sales process back to the buyer. You’ve abdicated your role as the Sherpa. And the buyer, who is already running their own version of fake, take, escape, now has everything they need to ghost you.
The reason most MSP owners send proposals that way is conflict avoidance dressed up as efficiency. Sitting in the room while somebody reviews your price feels like a fight, so they mail it in instead. The tactical fix, in other words, is downstream of the mindset fix.
Front of House, Back of House, One Team
The reframe I ask MSP owners to sit with is this: your salesperson is on the same team as you, just playing a different position. When they close a deal, they’re running a miniature business inside your business, and every success they have lands in your retirement account. That is a noble setup. It deserves respect.
So when you think about your next hire, your next comp plan, your next pipeline review, ask yourself whether you’re treating sales as an extension of the service you already provide, or as a separate and vaguely suspect function. If it’s the second, your service team is going to inherit a mess every time a new client lands, and your sales team is going to burn out defending promises they never should have had to make.
One Thing to Do This Week
Pick your next sales meeting and change one thing. Whatever proposal you were going to email out, don’t. Book a thirty-minute call specifically to walk through it. Tell the prospect that’s how you work, because proposals are collaborative, and you want to make sure everything on the page is right before you walk away from the conversation.
Then notice, on that call, how differently it goes from the ones where you emailed and waited.
Cynomi’s GTM Academy Sales Kit includes discovery and proposal-review playbooks, team-alignment frameworks, and tools designed to bring sales and operations under one culture. If you want structured support for this shift, you can pick up the kit here.
Table of contents
