Craig Stanley
Home / Cost / Underspend pooling

Set the budget weekly, move the underspend on Friday

A simple routine for AI consumption budgets. Set allowances weekly and move unused allowance to people who hit their limits.

10 October 2026 · 2 min read · Craig Stanley
In short, explained

Every week, everyone gets some AI to use. On Friday, if someone hasn't used theirs, it goes to someone who ran out.

Instead of giving everyone a fixed AI allowance for the year, set it each week. On Friday, look at who didn't use theirs and who ran out, and move the spare allowance to the people who need it.

Allocate consumption allowances weekly, not annually. Run a fixed Friday review: reclaim unused allowance above a floor, reallocate to users at their cap, and flag sustained heavy users for a licence-versus-metered review. Money follows the work.

Why weekly

Annual and monthly budgets assume use is steady. It isn't. A finance team's use spikes at month end. A project team's use spikes before a deadline. With fixed allowances, some people run out while others' allowances go unused.

A weekly cycle is short enough to respond to that and long enough not to become admin.

The Friday routine

A 20-minute review with the same agenda every week:

  1. Spend against budget. Total consumption this week compared with the weekly budget.
  2. Who's at the cap? People who hit their limit, and what they were doing.
  3. Who's well under? People who used little of their allowance.
  4. Move it. Reclaim unused allowance above a small floor and give it to the people at the cap for next week.
  5. Flag patterns. Anyone at the cap three weeks running may be better off on a licence than on metered use, or the reverse.

Making it fair

Publish the rules. Everyone keeps a floor so nobody's allowance is taken entirely. Reallocation is based on use, not seniority. Anyone can ask for more with a one-line reason.

Automating it

Most of this can run on the usage reports you already have. A Power Automate flow can pull the week's figures, draft the reallocation and post it to a Teams channel for the budget holder to approve. The meeting then becomes a quick check rather than a spreadsheet exercise.

Read next

A question to take awayIf you moved last week's unused AI allowance to the people who ran out, who would get it?

About me

Craig Stanley

Microsoft AI consultant and technical architect, based in Whitley Bay. Over the last few years I've delivered Microsoft 365 Copilot, Copilot Studio agents, Azure AI Foundry work and governance for UK public sector and financial services organisations.

What interests me is the decision underneath the tool: what it costs, what it risks, and whether a small, transparent model can make it better. I write the methods up here and on Substack so anyone can use them.

Find me