The removability test
If the supplier leaves and the work stops running, you did not buy capability. You bought access.
Most companies ask the wrong question when they buy customer intelligence. They ask what the system can do while the supplier is in the room. The better question is what still works when the supplier leaves. That is the removability test. It is the line between access and ownership.
Access is not capability
Access is the right to use something while a relationship lasts. Capability is something your team holds and can run on its own. They feel the same in a demo. They are not the same the day the contract ends, the renewal price doubles, or the people who built it move on.
Most customer intelligence is sold as access. You log in, you get results, and the work lives somewhere you cannot see. While the supplier is in the room, everything runs. The question that matters is what happens when they are not. Ownership is not a feeling. It is a list. If you cannot name what you hold, you hold access.
The six things that must stay
A customer intelligence capability is not one thing. It is a small stack of layers, and you can own each one or rent it. When the supplier leaves, six of those layers have to stay behind, in your hands, in a form your team can use.
- customer_record
The customer record
The cleaned, governed first-party data the whole capability sits on. If it lives only in the supplier's account, the capability leaves with them.
- signals
The signals
The behaviour the record gives off over time, the intent and lifecycle cues the model reads. This is what makes the capability compound, so it has to keep accruing on your side, not the supplier's.
- model_logic
The model
The scoring, segmentation, or propensity logic that turns the record into a judgement. You need to be able to read it, not just trust the output.
- decisions
The decisions
The triggers, rules, and next-best actions the model drives. The decision path should be something your team can follow and explain.
- workflows
The workflows
The lifecycle, CRM, sales, and service flows that put decisions to work in the tools your team already uses. They have to run without a login you do not control.
- measurement
The measurement
The reporting that tells you whether any of it is working. Without your own measurement you cannot improve the capability, only ask the supplier how it is going.
Six layers, one rule: each has to be inspectable, reproducible, and runnable by your team. The seventh thing, the handover, is what carries the other six across. That is the next section.
Why handover cannot wait until the end
Most contracts treat handover as a closing step. A folder of documents, a final call, a login passed across. By then the knowledge that mattered has already walked out the door, and the documents describe a system nobody on your side has ever run.
Handover is not a deliverable at the end. It is the way the work is done from the start. Your team should be reading the model, reproducing the workflows, and reading the measurement while the build is live, not after it. The test of a good handover is simple. The supplier could leave next week and the work would keep running, because your people have already been running it.
If handover is the last line item, it is the first thing to get cut when the timeline slips. Make it the spine, and removability is built in rather than bolted on.
What to ask before signing another platform contract
The sales conversation is built to show you what the system can do. It is not built to show you what you would keep. So you have to ask. The questions are not technical. They are questions of ownership, and any honest supplier can answer them plainly.
Where does the customer record live, and can we hold a copy in our own environment? Can we read the model and the decision logic, or only the results? If we left, what would we walk away with, and what would stop working? Who runs this in twelve months, your team or ours?
A supplier who is building you a capability will welcome these. A supplier who is selling you access will reach for the word convenience. Quiet intelligence beats loud platforms. The quiet kind is the kind you can still run when the room empties out.
The practical test
Here is the test in a form you can use this week. Run it against any customer intelligence you already have, or any you are about to buy. Removability is the test. It is a list, and your team either can or cannot answer yes to each line.
A customer intelligence capability is ownable if your team can answer yes to these:
- Do we hold the customer record?
- Do the signals keep accruing on our side?
- Can we inspect the model or decision logic?
- Can we reproduce the workflow?
- Can we explain the decision path?
- Can another team run it?
- Can the supplier leave without the system collapsing?
Seven yeses is ownership. Anything less is a gap worth naming before you sign or renew.
RUN THE TEST
Want to run the removability test on your own customer stack?
Book a 30-minute fit call and we will help you find the first gap.