How many of your clients are currently on a "legacy" agreement? You know the ones, the clients who signed up in 2018, are still paying 2018 prices, and are running on a 2018 security stack that wouldn’t stop a basic phishing attempt today, let alone a sophisticated ransomware attack.
As a coach to MSPs, I get this question all the time: "Joe, how do I raise my prices without losing my oldest, most loyal customers?"
Conventional wisdom says you should just send out a blanket 5% increase every year and hope nobody notices. But in reality, that doesn’t solve the root problem. The real takeaway isn't just about the price, it's about the product. If you are still supporting a client on an outdated tech stack, you aren't just losing money; you’re carrying a massive amount of operational risk.
The secret to solving this, and a cornerstone of high-level managed services consulting, is a concept I call Agreement Versioning.
The Legacy Client Problem: A Support Nightmare
We’ve all been there. You have a handful of clients who have been with you since the beginning. You love them, and they love you. But because they’ve been with you so long, they are essentially "grandfathered" into a version of your service that no longer exists for new customers.
They might be paying $100 per endpoint while your new clients are at $175. Even worse, they might be using an old antivirus you phased out three years ago because "that’s what’s in their contract."
This creates what we call "technical debt" in your service delivery. When your technicians have to remember that Client A gets one tool while Client B gets another, your efficiency plummets. You can’t automate effectively, your documentation is a mess, and your team is constantly frustrated. This is exactly how beating Parkinson’s Law in MSP service management becomes impossible, the work expands because your environment is too fragmented.
What Exactly is Agreement Versioning?
In the world of msp consulting, we focus heavily on the service delivery framework. Part of that framework is defining exactly what your "product" is at any given moment.
Think of your MSP agreement not as a static document, but as software. Software has versions: v1.0, v2.1, v3.0.
Agreement Versioning is the practice of naming and numbering your specific compilation of tools, software, and service levels. When you change your stack, say, you swap out a legacy firewall for a SASE solution or move from basic AV to a full XDR/SOC offering, you aren't just "updating your tools." You are releasing a new version of your service.
For example:
- v2023.1: Basic RMM, EDR, and Cloud Backups.
- v2025.2: Advanced XDR, SOC Monitoring, AI-driven Phishing Training, and immutable backups.
By treating your agreements as versions, you stop selling "IT Support" and start selling a specific, engineered solution. This allows you to track exactly which clients are on which version of your "firmware."
The Cell Phone Analogy: Why It Works
Think about your last interaction with a cell phone provider like Verizon or AT&T. You walk in wanting the newest iPhone, and the first thing they do is look at your plan.
"I’m sorry," the rep says, "but you’re on the 'Unlimited Choice' plan from 2021. That plan doesn't support 5G speeds or the hotspot features required for this device. To get the new phone, you’ll need to move to our 'Unlimited Ultimate' plan."
They don't ask you for a 5% "cost of living" increase. They tell you that the old plan is no longer compatible with modern technology requirements.
This is exactly how you should approach your MSP clients. Instead of a difficult conversation about inflation, you have a strategic conversation about compatibility and protection. "Mr. Client, you are currently on our v2021 Security Stack. While it was great three years ago, it no longer supports the encryption standards required by your new insurance policy. To maintain your coverage, we need to move you to our v2026 Framework."
Building Your Stack: The Service Delivery Framework
To make this work, you need a rock-solid service delivery framework. This is where many owners get stuck, they try to customize every agreement to what the client thinks they need.
In managed services consulting, we teach that the MSP is the expert. You decide what tools are necessary to keep the client safe and productive.
- Audit Your Current "Versions": Look at your existing clients. Group them by what they are paying and what tools they are receiving. You’ll likely find you have 5 or 6 "accidental" versions running right now.
- Define Your "Current Standard": What is the gold standard you sell to new clients today? That is your current version (e.g., v3.0).
- Draw the Line in the Sand: Decide that you will no longer support v1.0. This doesn't mean you fire the client; it means you set a sunset date.
This approach is a key part of true MSP management and moving the numbers. When everyone is on the same version, your cost of goods sold (COGS) becomes predictable, and your margins expand.
Using Versions to Drive Upgrades and Price Increases
The beauty of versioning is that it removes the "personal" aspect of price increases. It’s no longer about you wanting more money; it’s about the evolution of the industry.
When you release a new version, let's say you've integrated the use of AI in MSP sales and lead generation or enhanced security, you have a reason to reach out to every legacy client.
The Script:
"Hey, we’ve just released our v2026 Service Standards. It includes updated threat hunting and automated remediation that wasn't available when we signed your last agreement. Because we can't guarantee your security on the old version anymore, we’re transitioning all our partners to the new standard over the next six months."
This also allows you to use cross-selling to drive revenue growth naturally. You aren't "selling" a new tool; you are upgrading their "plan" to the current supported version.
The Benefits: Higher Value, Better Margins, Easier Support
Why go through all this trouble? Because the "Referral Trap" (where you keep prices low just because a client was a referral) is a slow death for MSPs. You can read more about avoiding that in our post on the benefits of a referral program for managed service providers.
By implementing agreement versioning, you achieve three things:
- Scalability: Your technicians only have to know one stack. Training becomes easier, and mistakes decrease. This is essential when staffing an MSP with a winning strategy.
- Profitability: You can easily identify which clients are on "low-margin" legacy versions and prioritize them for upgrades.
- Valuation: If you ever want to sell your MSP, a buyer will pay a much higher multiple for a company with 90% of its clients on a standardized, modern versioned agreement than one with 50 different custom contracts.
How to Address Your Legacy Agreements Today
If you’re sitting there thinking, "This sounds great, but my clients will never go for it," remember this: You are the one responsible for their data. If they are on an old version that leads to a breach, they won't remember that they "saved $50 a month." They will only remember that you were their IT provider when they lost everything.
Action Steps:
- Inventory your tools: List every tool in your stack and what version of your service it belongs to.
- Review your Chart of Accounts: Ensure your accounting reflects these stacks so you can see your true margins. (See our guide on aligning your chart of accounts).
- Schedule 'Executive Business Reviews' (EBRs): Don't call them QBRs or technical reviews. Call them EBRs and use them to discuss the 'Version Roadmap' for their business.
- Be prepared to walk away: If a client refuses to move off a version that is no longer safe to support, you have to ask yourself if the liability is worth the monthly check.
Agreement versioning might seem like a lot of work upfront, but it is the only way to break the cycle of stagnant growth and operational chaos. It moves you from being a "utility" (like the power company) to a "strategic partner" (like a consultant).
If you’re struggling to define your versions or your service delivery framework feels more like a "choose your own adventure" book, we can help.
At RedVine Operations, we specialize in helping MSPs professionalize their operations and sales processes. Whether you need help hiring sales people for lead generation or building a scalable service model, let’s talk.