Working Surfacelink · 30 Oct 2026
03
A large gas meter with a clear round dial fixed to a pipe that feeds a row of engines of different sizes, each with its own small valve, while a figure seen from behind writes the dial reading in a notebook, the whole scene drawn with wide empty margins on every side.
LeadDev

Cheap AI tokens are running out

James Stanier · 29 October 2026

Company story · roles · decisions · Changing roles

Read the original
Takeaway

James Stanier, chief technology officer of Nordhealth, tells engineering leaders to make AI usage visible and match AI models to tasks before per-token billing raises costs about tenfold.

Summary

James Stanier, chief technology officer of the software company Nordhealth, writes that the flat-rate AI plans many engineering teams use are subsidised and may end. His own team is on such a plan, but he estimates the same usage would cost about ten times as much at per-token prices. He sets out habits a team can build now so that a metered bill does not arrive as a shock.

Key points
  • Engineers frustrated by company usage limits often switch to personal plans, which sends company code through accounts the company does not control.
  • Every engineer should know how to see their own usage and limits and which AI model suits which kind of task, with a shared chat channel for examples.
  • Managers see their own team's usage, while engineers see department-wide figures without names; Stanier warns that ranking people by usage leads them to use AI for its own sake.
  • He suggests using the most expensive AI models for large exploratory tasks that produce plans, then giving the plans to smaller models. He notes that the effort setting changes cost as much as model size.
Implication

An engineering manager can start sharing usage figures and model-choice guidance while costs are still predictable. The article was metered on the publisher's site and was read in full.

Plays
Engineering

Use the most expensive AI models for large exploratory tasks that produce a plan, and give the plan to smaller AI models to carry out.

Engineering

Share department-wide AI usage figures with every engineer, show names only to each engineer's own manager, and never rank engineers by usage.

Derived by Working Surface from the article; more in the Playbook. Source line: One thing to avoid is ranking people by tokens, because you get tokenmaxxing, usage chased for its own sake, which is the opposite of what you want.

Source issue

30 October 2026: as AI agents do more of the building, teams decide on purpose which work people keep and set up tests, usage figures and baselines before handing over more.