Adaptive solutions, and how to tell if the word means anything.

What does a supplier mean when they call something adaptive?

Adaptive has become a standard modifier in supplier language, sitting alongside flexible, scalable and intelligent. Like those, it survives because it is agreeable and because almost nothing turns on it. A buyer hears a promise. A supplier has usually made none.

This page is written from the buyer’s side, including where it is inconvenient for us, because the fastest way to make the word mean something is to publish the questions that test it.

What the word should commit somebody to

Applied honestly, describing a solution as adaptive is a claim about three specific things, and any one of them missing makes the word decoration:

• It detects change without being told. Something runs continuously and notices when a condition moves. If the trigger for every change is the client raising it, the client is the adaptive component and they are paying somebody else for the property.
• It changes what it does, not just how much. Handling more volume is scale. Handling a different situation is adaptation. Vendors routinely evidence the first when asked about the second.
• Somebody is accountable for the change being right. An adaptive system with no owner produces drift, and drift with a good explanation is still drift.

Four questions, and the answers that mean no

What did you change for a client in the last ninety days that they did not ask for? A genuine answer is specific and slightly boring: a page rewritten because search language shifted, a supplier switched, an approach dropped after it stopped performing. A vague answer means the last ninety days contained no adaptation.

How would you find out this stopped working? Listen for a mechanism with a cadence, not an intention. "We review quarterly" is a calendar. "This is measured weekly and the threshold that triggers a change is stated in advance" is a mechanism.

What have you stopped doing for a client? Suppliers whose work only ever accumulates are not adapting, they are accreting. Every retained hour is defended because it is billed.

Who decides, and what happens if they are wrong? If the answer is that the client decides, the supplier is providing information and calling it adaptation. If nobody can describe what happens when a change fails, nothing is genuinely owned.

The structural problem, which is not dishonesty

Most suppliers who use the word are not lying. They are selling under a commercial model that makes the promise impossible to keep.

Project pricing pays for delivery of a defined scope, so noticing something six weeks after delivery is unpaid work performed by a supplier who has moved on. Hourly retainers pay for time, which makes continuing an activity profitable and stopping it a revenue loss. Neither model rewards the specific behaviour the word promises.

So the useful diagnostic is not the language, it is the contract. Ask what the supplier is paid to be responsible for. If the answer is deliverables or hours, adaptation is something they may do out of professionalism, and it is not what you bought. This is why Digilu sells an ongoing responsibility rather than a deliverable schedule: not because the work is unusual, but because a retainer for output cannot make the promise regardless of who is doing the work.

Why procurement makes this harder, not easier

Formal procurement is supposed to protect a buyer from exactly this, and on adaptive claims it often does the opposite. A tender asks suppliers to describe capabilities, and describing capabilities is free. It scores responses against criteria written before anyone understood the problem well enough to write them. And it selects, structurally, for the supplier with the best proposal writer rather than the best practitioner, because the proposal is the only artefact being compared.

The specific weakness is that procurement evaluates a promise about the future, which is unfalsifiable at the moment of evaluation. The correction is not more criteria. It is to ask for evidence of past behaviour instead: not what the supplier would do, but what they did do, to whom, on what date, and what changed as a result. A supplier who cannot produce that has told you what they are, and they have told you before the contract rather than in month eight.

The test we would want applied to us

Every claim should be answerable with a thing rather than a sentence. Ask to see the record: the finding, the date it was observed, what was done, and the measurement afterwards showing whether it worked. A supplier who adapts has that record as a by product of working. A supplier who does not will offer a case study instead, which is a story told after the fact by the person who benefits from it.

Where a supplier cannot show the after measurement, that is not automatically disqualifying, because plenty of good work is genuinely hard to measure. It should be said out loud rather than covered with a number that was never taken.

Where this test is unfair

Two honest caveats. Small suppliers often adapt constantly and document none of it, and holding them to an evidence standard designed for larger firms can select for the better recordkeeper rather than the better practitioner. And some work genuinely should not change: an accountant, a lawyer and a payroll provider are valuable precisely because they are the same every month, and asking them what they adapted is asking the wrong question.