🚀 Executive Summary
TL;DR: Trying to boost sales won’t fix an MSP’s underlying operational issues like broken onboarding or lack of standardization, which only leads to increased churn. Sustainable growth requires addressing these fundamental flaws through technical vetoes, rigorous standardization, or even a temporary onboarding freeze to rebuild operational efficiency.
🎯 Key Takeaways
- Implement a ‘Technical Veto’ or ‘Solutions Review Board’ within the sales process to ensure new deals align with operational capabilities and are priced appropriately for non-standard requirements.
- Define and enforce a Standard Operating Environment (SOE) and a clear service catalog to move from custom IT art to scalable, standardized service delivery, improving efficiency and reducing context-switching.
- Consider a ‘Full Stop Onboarding Freeze’ as a strategic investment to re-tool the delivery engine by automating onboarding, consolidating tools, stabilizing existing clients, and training staff for sustainable growth.
Stop trying to sell your way out of an operational crisis. A bigger sales team can’t fix fundamental flaws in service delivery; it only accelerates the burn rate and customer churn.
Sales Can’t Fix a Broken MSP, and I’ve Got the Scars to Prove It
I remember the day we landed the “whale.” The sales team was ringing the bell, high-fives all around. We’d signed a massive new client, a deal that was supposed to change our trajectory. A week later, I was sleeping on a cot in the office, surviving on stale coffee and pizza crusts. The client’s 300+ servers, which we were promised were “standardized,” turned out to be a chaotic menagerie of ancient CentOS, unpatched Windows Server 2008, and a custom billing app held together with Perl scripts and hope. Our onboarding process, a collection of half-documented bash scripts, buckled and then shattered. The monitoring alerts flooded our system, tickets piled up, and our best engineer quit. The sales team sold a dream, and we in operations were living the nightmare. That’s the crux of the issue: you cannot sell a service you are not equipped to deliver.
The Leaky Bucket: Why More Sales Makes It Worse
When your Managed Services Provider (MSP) is struggling, it’s easy for management to think the solution is more revenue. “If we just close more deals, we can hire more people!” The problem is, this treats the symptom, not the disease. The real issue is usually a broken operational foundation. Think of your MSP as a bucket. Your clients are the water.
- Broken Onboarding: A hole in the side. Every new client you pour in causes a frantic scramble, spilling resources and goodwill.
- Lack of Standardization: The bucket is made of porous clay. Supporting dozens of bespoke client environments means your team is constantly re-learning and context-switching, unable to build efficient, scalable solutions.
- Reactive Firefighting: The bottom of the bucket is missing. Your team spends all their time catching the water as it falls, with no time to actually patch the bucket itself.
Pouring more water (sales) into this leaky bucket doesn’t fill it up. It just makes a bigger mess and exhausts the people holding it. The answer isn’t a bigger funnel; it’s fixing the damn bucket.
The Fixes: From Band-Aids to Surgery
Look, I get it. We can’t just shut down the business to re-architect everything from scratch. But you have to do something. Here are three approaches I’ve seen work, ranging from immediate triage to a full-blown reboot.
1. The Quick Fix: The ‘Technical Veto’
This is your immediate stop-gap. You need to insert a technical checkpoint into the sales process. Right now. Create a small, empowered group—call it a “Solutions Review Board” or just “The Sanity Checkers”—composed of senior technical staff. No non-standard deal gets a signature without their sign-off.
The salesperson has to fill out a simple intake form: “How many endpoints? What OS? What are the key applications? Are they asking for anything not in our standard service catalog?” The board’s job is to look at the request and answer one question: “Can we deliver this without setting our hair on fire?” If the answer is no, the deal is either vetoed, re-scoped, or re-priced to reflect the actual cost of bespoke engineering work.
Pro Tip: This isn’t about saying ‘no’ to sales; it’s about saying ‘yes’ responsibly. It forces a conversation about the real cost of a deal, moving the burden from the operations team’s late nights to the client’s invoice, where it belongs.
2. The Permanent Fix: Standardize or Die
This is the real work. You have to stop being a custom IT art studio for every client and start being a factory that produces excellence at scale. This means defining your service catalog in concrete terms.
Get your best technical minds in a room and don’t let them out until you’ve defined your Standard Operating Environment (SOE). What monitoring tools will you use? What’s your approved list of OS versions? What is your standard backup agent and policy? Document it. Build automation around it. Then, build your service tiers around that standard.
| Service Tier | Monitoring | Patching Cadence | Backup |
|---|---|---|---|
| Bronze | Basic Uptime (Ping/HTTP) | Quarterly (Security Only) | Nightly, 3-day retention |
| Silver | Full OS Metrics (CPU/RAM/Disk) | Monthly (All Critical) | Nightly, 14-day retention |
| Gold | Application Performance Monitoring | Weekly (Proactive) | Hourly, 30-day retention + DR Test |
Once you have this, your sales team isn’t selling vague promises anymore. They’re selling well-defined products. The conversation changes from “Can you support our ancient prod-db-01 running Oracle on Solaris?” to “Our Gold package supports these specific database environments. We can offer a custom Professional Services engagement to assess your Solaris box.”
3. The ‘Nuclear’ Option: A Full Stop Onboarding Freeze
Sometimes, the house is so thoroughly on fire that you just have to stop pouring gasoline on it. This is the bravest, and scariest, option: you announce a temporary freeze on all new client onboarding.
Yes, you read that right. Tell the sales team to stop closing deals for 30, 60, or 90 days. This will cause panic in the executive suite, but you have to frame it as a strategic investment. “We are pausing to re-tool our delivery engine so we can grow sustainably and reduce churn.”
Use that time with ferocious intensity:
- Automate your client onboarding process. Turn that 20-page Word doc into an Ansible playbook or a PowerShell DSC script.
- Consolidate your tools. Get rid of the three different monitoring systems you’re barely using.
- Stabilize your existing clients. Show them some love, fix their long-standing issues, and turn them from detractors into fans.
- Train your team. Give them the time and resources to learn the new, standardized way of doing things.
Warning: This move requires immense political capital. You need buy-in from the very top. But if your engineer turnover is high and your client satisfaction is in the toilet, it might be the only thing that can save the company from collapsing under its own weight.
Ultimately, a healthy MSP is a partnership between sales and operations, not a battle. Sales needs something stable and reliable to sell, and operations needs new clients to be aligned with their capabilities. Fixing that alignment is the only path to sustainable growth.
🤖 Frequently Asked Questions
âť“ Why can’t sales fix a broken MSP?
More sales exacerbate operational issues by pouring ‘water’ (clients) into a ‘leaky bucket’ (broken operations), leading to resource drain, customer churn, and exhausted staff without addressing root causes like broken onboarding or lack of standardization.
âť“ How do these operational fixes compare to simply expanding the sales team?
Expanding the sales team treats symptoms by seeking more revenue, while operational fixes address the underlying ‘disease’ of inefficient service delivery, enabling sustainable growth rather than accelerating a crisis by adding more clients to an unstable system.
âť“ What is a common implementation pitfall when standardizing MSP services?
A common pitfall is the failure to rigorously define and enforce a Standard Operating Environment (SOE) and service catalog, leading to continued support for diverse, non-standard client setups that hinder scalability and operational efficiency.
Leave a Reply