The Value Creation Protocol

Part III — The Core Framework Traps

Chapter 12

The Managed Services Trap → Value-First Delivery


We've built an entire industry around keeping clients dependent on us. The more complex we make things, the more they need us. The more they need us, the more we can charge.

Erin Wiggers and I talked about this trap in June 2025. I was hosting a series of ten conversations, one for each of the ten Core Framework Traps, and this trap was hers.

Notice who that first sentence is talking about. "We." "Us." It isn't describing some other firm down the road. That is what makes this one hard to see from the inside. Nobody sets out to hold a client back. You do good work, they renew, and one renewal at a time your income comes to rest on what they can't do.

You may be reading this as someone who sells a service or as someone who buys one. Most of us are both, so this chapter is written for both seats.

What this is

The Managed Services Trap, in one line:

Building business models on client dependency rather than client capability.

It begins as a fair trade. A company needs something done that it doesn't know how to do, and somebody who does know offers to do it. The trap closes later, when the provider's income depends on the client never learning. From then on every incentive points the same way: keep the knowledge on our side, keep the setup complicated enough to need us, renew. The methodology's longer description says it in one sentence: "When dependency becomes the business model, transformation becomes impossible."

The belief it breaks is Empowerment over Learned Helplessness, one of the Five Core Beliefs. That belief describes the shift it asks for in two sentences: "From creating dependency to building capability. Success means people need us less for routine matters while engaging more for strategic evolution."

Read the second sentence slowly. It doesn't say the relationship ends. It says the routine work moves to them, and what you do together gets more interesting.

The way out is called Value-First Delivery:

Build client capability rather than dependency. Transfer expertise rather than hoard it. Measure success by client independence, not contract length. Create value that compounds for clients beyond the engagement.

How to tell where you are

If you provide the service, look at this week's work.

  • The same request came in again, you handled it again, and nobody has ever shown the person asking how to do it.
  • Your client's people can tell you who to call about the system. They can't tell you how it works.
  • The setup is more complicated than it was a year ago, and nobody on their side asked for that.
  • The renewal conversation is about term and price. What their team learned doesn't come up.
  • Nothing in the agreement says what they will be running on their own, or what finished would look like.

If you buy the service, look at your own team.

  • When your contact at the provider is out, something of yours stops.
  • You have paid for a year, and the list of things your own people can do hasn't grown.
  • You couldn't say whether the last invoice was fair, because you couldn't describe the work.
  • A new hire asks how something works and is told it belongs to the agency.
  • Somebody on your team once asked to learn it, and the request went nowhere.

Any one of these on its own is ordinary. When they stack up, dependency has stopped being a side effect. It is the arrangement.

What to do

The order is the same from either seat. I'll write it from the provider's side and mark the buyer's part.

  1. Write the starting line. List what the client's people can do today without you. Use names and tasks: who can do what. No ratings.
  2. Sort the work into two piles, together. One pile is work the client should own. The other is work they have chosen to leave with you. The client picks the piles. If you pick for them, you will pick the one that renews.
  3. Name an owner for everything in the first pile. One person on the client's side for each item. This is the buyer's move. A handover with nobody to receive it is only a document.
  4. Simplify before you teach. If it takes a specialist to run, it isn't ready to hand over. Take parts out until the owner can run it.
  5. Do the next one with them. Then watch them do one. Then stay reachable while they do one alone. The teaching happens inside the real work, on the real request, not in a training session scheduled for later.
  6. Put the finish line in the agreement. Write down what they will be running on their own, and what the two of you will still do together after that.
  7. Look at what you are paid for. If the invoice only ever counts hours of doing, the pull toward dependency hasn't gone anywhere. I'm not going to hand you a pricing model. I'll only say that a provider who gets paid when the client can't will feel that pull every month, good intentions or not.

If you are the buyer, be honest about your half. Some of this trap gets built by clients whose whole instruction was to just handle it. Before the next renewal, ask your provider one question: what will my people be able to do on their own when this agreement ends?

How you know it worked

Not by anything you delivered. The handover document, the training session and the recorded walkthrough are all things you did.

All five of these books use one definition of value. It belongs to The Value Era, and here it is word for word:

What a person or organization can now do that they could not before. Not what they were sold, not what was produced for them, not a promise about the future — value is the real change in what someone can do, and only the person who received it can say it happened.

So the proof is on their side of the table.

  • Their person does the task with you out of the room, and you hear about it afterward. The methodology's own example of a change like this is "the ops lead builds her own workflows without us in the room."
  • They explain the system to their new hire in their words, not yours.
  • They change something you built without asking you first, and it is better for it.
  • The questions they bring you get harder. Fewer requests to do a thing for them. More accounts of what they tried and what happened.
  • You ask what they can do now that they couldn't before, and they have an answer of their own.

A falling hours number is not on that list. Hours can drop because they learned, or because they gave up on you. The number can't tell you which. Ask them.

Writing down what they tell you, and having them confirm it, is a practice of its own. Value Accounting (Book 4) is the handbook for that.

Where it goes wrong

The binder. You hand over a thick document and call it knowledge transfer. A document isn't a capability. If nobody on their side has done the work with their own hands, nothing was handed over.

The early exit. You walk away and call it independence. Capability gets built alongside someone. If you leave before move 5 has happened a few times, you haven't freed them. You have dropped them.

One indispensable person. The client stops depending on you and starts depending on a single employee who learned everything. That is the same dependency with a shorter commute. Hand over to more than one person.

The same trap with a machine in it. Chapter 1 of this book teaches five claims, and one of them, Configuration Over Customization, names this exactly: custom architecture creates "dependency on capability you don't have — whether that's outside consultants, external resources, or AI you can't direct yourself." Trading an agency you can't see into for an AI system you can't see into is still renting.

The trap beside this one is the Authority Trap (Chapter 16). It is the same dependency, inside the building. You can teach a client's team everything and still leave them unable to act, if every decision waits on one manager. Managed Services keeps the capability outside the company. Authority keeps the decision away from the people who have the capability. Check for both.

And watch the ERP Trap (Chapter 13). A rigid system that only the provider can change locks the dependency in place, however much the client's people have learned.

Read further

Stop 1 of 6: What this is

Back to contents