The Peacock came back in January, which is when these offers arrive, because January is when budgets reopen and everyone is briefly optimistic.

The offer was good. I want to be clear about that, because the easy version of this story is that the vendor was trying something and got caught, and that is not what happened. Commit to a volume floor for two years, receive a substantial discount against what the jungle was currently paying, with the floor set slightly below current consumption so there was headroom before it bit.

The arithmetic was sound. Against last year’s usage it was straightforwardly cheaper. The Fox ran it three ways and it came out ahead every time.

The Sloth had been reading the term sheet for most of the meeting, at his own speed, which is the speed at which sloths do everything. He looked up when the room had more or less concluded.

“What is the engineering roadmap for this workload,” he asked, “for the next two years?”

Nobody had brought it, because nobody had thought it was relevant to a commercial discussion.

It contained, among other things, everything from Act III of this series. Routing. Context restructuring. Retrieval tuning. Caching. All of it targeted, quite deliberately, at reducing consumption on precisely this workload, by a proportion the Crocodile had estimated as substantial.

The jungle had been about to commit to a volume floor and simultaneously fund a program designed to fall below it.

“You would have paid the discount,” said the Sloth, “for the privilege of buying something you had arranged not to need.”

Sloths are slow. Occasionally slow and careful are the same thing, and this was the meeting where the jungle stopped finding him funny.

Why commitments are harder to evaluate here

Capacity commitments are old and well understood. You trade flexibility for price on a resource with stable characteristics, you forecast your volume, and you commit somewhat below it. Organizations have done this competently with every kind of infrastructure for decades.

What is different is that in this domain the resource itself does not hold still. Within a typical commitment term, the unit price will move, the capability level will move, and your own efficiency will move if anybody in your organization is doing the work in Act III.

So you are not only betting on your volume. You are betting on the state of the field, on the trajectory of prices you do not control, and on your own engineering team failing to improve things. That last one is the strange part and it is the part that catches people.

Three things a commitment locks

Volume. Visible, discussed, negotiated. Everyone understands this one.

Price. Also visible, and usually the only thing anybody negotiates.

A capability tier. Rarely on the term sheet and the one that hurts. A commitment is generally made against a particular class of capability. If the field moves and something materially better becomes available, you are holding a volume obligation against the previous generation, and the value of your discount has to be weighed against the cost of not moving.

That third lock is the one to raise in the negotiation, because it is the one nobody will raise for you.

Pricing the option you are selling

The structural problem with these decisions is that the discount is visible and precise, and the thing you are giving up is invisible and vague. Human beings are extremely bad at that trade and it is not a failure of intelligence, it is a failure of presentation.

The framing that helps: what would you pay today for the ability to move this workload entirely in six months with no stranded cost?

Put a number on it. Any number, arrived at honestly. That number is the hurdle the discount has to clear. In a stable market it is small and most commitments comfortably clear it. In a market where capability and price are both moving, it is considerably larger than people assume, and a fair number of commitments do not clear it once it is written down.

The point is not that commitments are bad. It is that you are selling an option and it should appear somewhere in the analysis as a thing with a value, rather than as an unpriced side effect.

Optimizing into a floor

The Sloth’s question deserves its own section because it is the most common own goal in this area and it is entirely preventable.

Two workstreams, running in parallel, in most organizations that are taking this seriously. Procurement is negotiating a volume commitment. Engineering is executing an efficiency roadmap. Neither has ever been in a meeting with the other, because one is commercial and one is technical and they report through different structures.

If engineering succeeds, consumption falls. If consumption falls below the committed floor, you pay for volume you are not using, and your best engineering quarter has converted directly into a stranded contractual cost.

I have seen this happen. The people involved were competent and the outcome was absurd, and the entire cause was that two calendars never intersected.

What to commit on

Baseline. Never peak, and never the growth forecast.

Your baseline is the volume you would consume even if nothing went well, even if adoption stalled, even if the efficiency roadmap delivered everything it promised. That is the portion you can safely commit, because you will consume it under essentially every scenario.

Everything above the baseline stays variable, and paying the standard rate on it is correct rather than wasteful. The uncommitted band is what your flexibility costs and it is buying you something real.

The most common error is committing on the forecast, because the forecast is the number in the plan and committing on it makes the discount look bigger. The forecast has never once been right in any organization I have worked with, and it is a considerably more expensive place to be wrong when there is a contract attached to it.

Ladder the terms

The practical technique that most organizations skip.

Rather than a single long commitment, use several shorter overlapping ones with staggered end dates. Your headline discount is lower. Your position when something changes is dramatically better, because at any given moment only a portion of your volume is locked and something is always coming up for renewal.

This is how mature organizations handle every other volatile input they buy. It is not a novel idea. It is simply that AI procurement is often being done by people running their first cycle in this category, and the single long commitment is what gets offered first.

And negotiate more than the discount. Portability between capability tiers, so committed volume can move as your needs change. Term flexibility. Notice periods on behavioral change, which connects directly to the version pinning question from Lesson 14. All of these are frequently available and almost never asked for, because the conversation stops at the number.

The self-hosted parallel

Worth closing the loop with Lesson 11.

Buying hardware is a commitment. It is a longer commitment than any contract you would sign, with no exit clause, no portability terms and no renegotiation. Every argument in this post applies to it with more force, not less.

Which means the crossover analysis from Lesson 11 should include the optionality framing from this one. The self-hosting case that looked marginal on unit cost usually looks worse once you price the option you are giving up, and that is worth doing explicitly rather than leaving as an unarticulated discomfort.

Three ways this goes wrong

Committing on the forecast. Locking to the aspiration rather than the floor, then paying for volume that never arrived, for two years, in a line item nobody wants to discuss.

Optimizing into a commitment. Act III succeeding and turning into stranded cost because the technical and commercial workstreams never spoke.

Negotiating only the discount. Headline price improved, portability and term structure given away for free because nobody knew they were negotiable.

The Field Kit

Concrete things to do this week.

If you sit in the Crow’s chair, commit on the baseline only, and require the engineering efficiency roadmap on the table before you sign anything with a volume floor in it. Two documents, one meeting.

If you sit in the Crocodile’s chair, tell procurement what your efficiency roadmap will do to consumption, in numbers, before they negotiate. This conversation almost never happens and it is the single largest source of stranded commitment cost in the discipline.

If you sit in the Mandrill’s chair, resist committing on your own growth forecast. You have never been right about one, nobody has, and this is a far more expensive place to be wrong than a planning document.

For everyone: ladder the terms and negotiate portability alongside price. A few points of discount is worth considerably less than the ability to move.

Jungle Lesson 20

A commitment locks your volume, your price and, quietly, your capability tier, and only two of those are on the term sheet. Commit on the baseline you would spend anyway, ladder the terms, and remember that if your own efficiency work succeeds, a volume floor turns your best engineering quarter into a stranded cost.

That closes the fourth act. The jungle now has an operating model. Capabilities funded persistently rather than projects funded to end. A floor and a variable band. Quarterly reallocation with authority to move money in both directions. A rhythm that runs at five cadences with a name against each. Guardrails that separate the runaway loop from the animal doing good work. And a commercial posture that does not accidentally bet against its own engineers.

What it has not yet faced is time. Everything in the first four acts describes building something. The fifth act is about what happens to it, and it opens somewhere uncomfortable: with somebody finding the Fox’s original slide, the one titled Conservative Estimate, in an archive, and reading it aloud. Lesson 21 is about the second year, and why the programs that die are usually the ones that were working.

The question the Sloth asked is worth stealing verbatim. Before any volume commitment, ask for the engineering roadmap for the same workload over the same term. If the two documents have never been in the same room, that is the finding, and it takes one meeting to discover.