A codebase is not a paragraph. Neither is a litigation folder, a clinical case file, a customer-support history, a policy archive, or the slow-motion disaster known as “all meeting notes since March.” Yet many enterprise AI systems still treat long context as a heroic prompt-engineering problem: push more text into the model, pray the key detail survives attention, and call the bill “innovation.” ...
Thinking is expensive. That sounds obvious when the thinker is a human consultant billing by the hour. It sounds less obvious when the thinker is a large reasoning model producing long chains of thought, checking itself, trying another route, doubting the first answer, then generously spending another few thousand tokens to arrive at the same wrong place with better punctuation. ...
A familiar business scene: a team has already tried the standard AI improvement kit. Better prompts. More examples. Chain-of-thought. Self-consistency. A small agent wrapper. Maybe even a heroic tree-of-thought workflow that burns compute like a startup burns runway. The model improves, but not in the way the team hoped. It can explain more. It can sample more. It can retry more. Yet when the task requires a new abstraction — a hidden rule in a grid, a nested logical constraint, a multi-step scientific relation, a variable-binding trick in math — the model still behaves like someone confidently rearranging old furniture in a room that needs a new door. ...
Budget meetings have a useful cruelty. They make vague AI strategy sound ridiculous. A team may begin with the familiar story: the model is not reasoning well enough, so the company needs a larger model, a longer context window, more inference-time search, and probably a procurement conversation involving GPUs. Very modern. Very expensive. Also not always the right diagnosis. ...
Budget. Not the inspirational kind that appears in founder decks as “disciplined growth.” The real kind: GPU invoices, latency targets, queueing delays, memory ceilings, unhappy users, and the quiet discovery that a model can be brilliant in a benchmark and still economically annoying in production. That is the useful tension behind Scaling Laws Meet Model Architecture: Toward Inference-Efficient LLMs.1 The paper does not merely repeat the familiar lesson that large language models become expensive when they get larger. Everyone with a cloud bill has already enjoyed that seminar. Its sharper point is that the usual scaling-law conversation leaves out a design variable that businesses eventually pay for: architecture. ...
Tokens are tiny invoices. One reasoning model writes a long chain-of-thought, checks itself, circles back, restates the same conclusion in a slightly more spiritual tone, and then finally prints an answer. Another model reaches the same answer halfway through but keeps talking because nobody told it that the meter is still running. This is not philosophy. This is unit economics with better typography. ...