The Watering Hole question had been open since Lesson 7. It was settled in about eleven minutes, in the second budget season, by the last animal anyone expected to propose the answer.

The Crow proposed it herself.

“I am going to stop asking you to forecast this,” she said. “The forecast has been wrong twice and I have concluded that is not your fault. The thing does not hold still long enough to be forecast, so I am going to fund it differently and take back the control somewhere else.”

What she proposed was a standing allocation, reviewed quarterly, with the review holding real authority to increase it, hold it, or cut it. A fixed floor for the shared foundation, funded centrally as infrastructure, and a variable band above it that moved with consumption and with evidence from the value ledger.

The Sloth had been working on precisely this for some time. He put his framework on the table, and for the first occasion in this entire story it was exactly what was needed at exactly the moment it was needed.

Nobody said anything about the timing. The Sloth did not appear to find it remarkable.

“The destination,” he said, “was always correct.”

Why annual budgeting fails specifically here

Annual budgeting is not a bad process. It is a very good process, refined over a century, for allocating money to things whose demand you can estimate a year ahead.

It fails here for a specific structural reason, and it is worth being precise about it because the reason is not poor forecasting.

The demand for an AI capability is created by its own existence. Nobody knows they want it until it is there and somebody shows them what it does. So you are being asked to forecast twelve months of demand for something whose demand does not exist yet and will be generated by the thing you are forecasting. That is not estimation. That is invention with a spreadsheet attached.

On top of which, within the same twelve months, the unit price will move, the capability level will move, and the efficiency of your own implementation will move if anyone reads Act III. Three of the four variables in your forecast are unstable and the fourth is circular.

The failure is not that people forecast badly. It is that the object does not hold still long enough for forecasting to be the right tool.

What persistent funding actually means

A standing allocation to a capability, not a use case and not a project. It continues by default. Nobody resubmits a case for it to exist.

It is reviewed on a published cadence, quarterly for most organizations, against the value ledger from Lesson 10. The review has authority to move money in both directions, and it exercises that authority.

The critical word is both. A reallocation process that only ever increases funding is a request process with a nicer name. A reallocation process that only ever cuts is a budget exercise. It has to genuinely do both, visibly, or the mechanism decays into an annual budget with three extra meetings.

What makes reallocation real

Four things, and I would say all four are necessary.

A published cadence. Fixed dates, known a year ahead, so teams prepare rather than react. An irregular review is an inspection.

Actual authority. The body holding the review can move money without escalating. If every decision goes somewhere else for approval, the review is a recommendation meeting and everyone will treat it as one within two cycles.

Evidence requirements defined in advance. What you must bring, in what form, at what evidence grade. Defined ahead of time so nobody can construct the case backwards from the answer they want.

One visible cut in the first year. This is the one that matters most and the one organizations avoid. Until money has actually moved away from something in front of witnesses, nobody believes the review is real, and preparation for it will be performative. One genuine reduction, publicly, and every subsequent cycle becomes serious.

The floor and the band

Two components, which is the resolution to the argument that ran for four meetings and three lessons.

The floor covers the cost of the capability existing. Platform, people, the shared foundation from Lesson 7, the fixed portion of the stack from Lesson 3. This is infrastructure, funded centrally, not consumption split, and it is reviewed annually rather than quarterly because it does not move quickly.

The variable band sits above it and tracks consumption and evidence. This is where quarterly reallocation actually happens. This is what gets shown back and eventually charged back. This is the part that responds to whether something is working.

Three lessons of argument, one paragraph of answer, which is roughly the real ratio in my experience. The hard part was never the design. It was getting the organization to accept that two different mechanisms were needed for two different problems.

What finance gives up and what it gets

Worth stating plainly, because this has to be sold to a CFO as a trade rather than presented as a modernization.

What finance gives up is annual predictability. The number in September will not be the number in March, and there is no version of this where it is.

What finance gets is quarterly control. Evidence-based reallocation four times a year instead of one act of faith. The ability to stop funding something in April rather than discovering in December that it stopped being worthwhile in February. And a portfolio where money moves toward what is working on a timescale that matters.

For most finance functions that is a good trade and it should be pitched as one. Predictability is worth less than control, particularly for a category of spend where the predictable number was never accurate anyway.

The real cost of this model

Governance load, and it is not trivial.

Quarterly reallocation is four times the review effort of an annual cycle. Four sets of evidence to prepare, four forums to run, four rounds of decisions to communicate. If your organization is already struggling to run one budget process well, running four will not go better.

Which is the honest counterargument to everything in this post, and the reason I would say: start with one capability, not the whole estate. Run the cadence on the largest thing you have, learn what it costs in effort, and expand from there. An organization that attempts this across forty initiatives simultaneously will produce four ceremonies a year and no decisions.

Three ways this goes wrong

Reallocation theater. Quarterly meetings that have never moved money. Teams work this out by the third cycle and stop preparing seriously, and the whole thing becomes a status update with a budget attached.

The floor that only grows. Everything gradually reclassified as fixed, because fixed is safer for whoever owns it, until the variable band is a rounding error and quarterly reallocation has nothing left to reallocate.

Persistent funding without a ledger. Quarterly decisions made on anecdote, enthusiasm and whoever presented most confidently. This is genuinely worse than annual decisions made on a plan, because it is four times as fast at being wrong.

The Field Kit

Concrete things to do this week.

If you sit in the Crow’s chair, cut something visible in the first year. One real reduction, in front of people, makes every subsequent review credible, and nothing else does. Not a memo, not a policy, a cut.

If you sit in the Crocodile’s chair, report against the ledger on the reallocation cadence rather than your own release cadence. The rhythm has to be the finance rhythm or the two conversations never meet.

If you sit in the Mandrill’s chair, stop treating a quarterly reduction as a defeat. Money moves in both directions in this model, and the territories that take reductions gracefully are the ones that get increases fastest, because they are the ones the review body trusts.

For everyone: define the floor and the variable band in writing, and review where the boundary sits once a year. Left alone it drifts upward, permanently, in the direction of everything being fixed.

Jungle Lesson 17

An annual budget asks you to forecast demand for something whose demand is created by its own existence, which is not forecasting, it is fiction with a spreadsheet. Fund the capability persistently and reallocate quarterly, and cut something visible in the first year, because a review that has never moved money is not a review, it is a recurring meeting.

Next time: a quiet one. No crisis, no confrontation, nothing on fire. The jungle has an ordinary working week for the first time in this entire story, and the Fox notices that nobody has asked him for an emergency number in six weeks and does not entirely know what to do with himself. Lesson 18 is about the operating rhythm.

If your organization runs a quarterly review that has never once moved money away from anything, it is worth asking what the meeting is actually for. The answer is usually reassurance, which is a real need, but it should not be confused with governance.