Post five in our series on gross margin compression looks at one of the most deadly killers of margin: scope creep.
Most IT service providers have made the shift from break-fix to managed services over the last decade or so. That shift moved billing from post-work to pre-work. Instead of billing by the hour after the work is complete, managed services requires you to price and scope the work up front. This is fantastic for revenue predictability, but it puts a new burden on the business. The business now needs to price the work correctly up front and protect it. The business now needs to deliver exactly what was agreed to, without quietly giving away more. That process of doing more for the client than what is in the service agreement is called scope creep.
The scope you’ve agreed to with your client defines the revenue coming in. The more you deliver outside of that scope, the more your gross margin shrinks. Unlike pricing or client grading, scope creep never shows up as a line item on your P&L. It quietly eats the hours and capacity of your team.
“Just This Once”: How Small Favors Become the Norm
The problem is your company has agreed to a price and scope usually based on a set number of seats. Then the client needs something outside of that. The person who sold the work isn’t in the room anymore; it’s the techs who are there. It is much easier and less confrontational for a tech to just do the (alleged) extra five or ten minutes of work than to push back and upset the client. After all, techs receive most of their training to manage technical work, not client behavior.
The “just this once” work is never flagged as out of scope, even when the tech knows it should be. Over time, what’s on paper and what is delivered drift to form a small chasm. This happens for a couple of reasons. First, nobody references the clearly defined scope boundary in the contract (it is there, but forgotten before the digital signature is archived). There’s a breakdown between the salesperson who signed the agreement and the technical team who delivers it.
Second, even when techs do know what’s in scope, they’re often not trained or empowered to say so. Techs are frequently compensated on NPS scores and fast ticket resolution. That creates a negative incentive to say no. Saying no feels like bad customer service, and for a tech being measured on customer satisfaction, pushing back on a “victimless” small favor just isn’t worth the friction.
Your Client is Training Your Techs
This problem is perpetuated because there’s no mechanism to catch the drift and revenue looks completely consistent. Top-line numbers stay the same while the actual time and efficiency behind each client quietly erode. One small favor here and there is fine, until it isn’t. The more the tech gives in, the more requests they receive, and this is where it gets ironic: the client starts training your company how to deliver service, instead of you training them how to be a great client.
This compounds from one client to the next, and it’s invisible in the P&L. Revenue looks exactly like what you agreed to, but the time spent serving each client keeps growing. This ties directly back to the grading conversation from a few posts ago. Chronic scope creep is often the hidden driver that turns a decent client into a C or D. The client is, without realizing it, training your company to lower their own rating.
Managing Scope Clarity is Kindness
Managing scope creep will improve your gross margin. It’s not about being punitive or nickel-and-dimming your clients. Your company exists to take care of your clients, and that’s a good, symbiotic relationship when it works. This isn’t about fee-ing clients to death. It’s about clarity.
Since you’re not billing time and materials, everything relies on a well-documented scope of work, one that both your team and your client can actually reference. The more that document gets used, and the more clearly each service is written, the better this functions for everyone.
The approach with your techs should be educational, not confrontational. The better your team understands exactly what’s included in each service level, the better prepared they are to recognize and flag what’s out of scope. Those flagged requests should go to your service manager, who can track how often a client is asking for free work outside the agreement. That log becomes either a scope conversation or a change order, instead of just being absorbed for free.
If a client insists on services outside of scope, they can pay for it. If they insist on getting it for free, that’s a client who probably needs a conversation about re-scoping, or possibly needs to move on. You don’t have to wait for renewal to have that conversation. Start by auditing a sample of recent tickets against the contracted scope to see how much drift already exists. Build a process for techs to flag scope questions in a way that feels like teaching, not conflict.
Clarity is Kindness
Scope definitions should be consistently incorporated in the relationship, not just at the start of the relationship. They need to be part of your culture, revisited at renewal and beyond. There’s a lot of emotion and excitement on both sides when a new relationship begins, but that excitement can blur the boundaries you actually need in place long term.
One of the best parts of the managed services industry is that you’re paid up front to serve a client on a defined scope of services. Protecting that scope is what keeps your margin where it should be.
Clarity is kindness here. This all ties back to grading and to the renegotiate-or-exit conversation. These are hard discussions to have, but too often, scope creep is the quiet driver behind a client’s declining grade, and behind the gross margin your company is trying to protect.