Bearings

Positions on shifts in enterprise technology. Each rests on data CIOPages collects and on public records, states its reasoning, and makes dated calls that are scored here when they fall due.

• Your software bill is turning into a meterAs enterprise software moves AI to unit pricing, the budget risk is less a missing control than default terms that favor the vendor, units that expire unused and overage billed until someone sets a cap, so IT should set caps before rollout and negotiate rollover in the contract.Taken October 31, 2026 · Confidence: medium · 2 calls

How a position is built

1. The position, in one sentence, with the date it was taken and a confidence level.
2. The reasoning, step by step, from the evidence to the position.
3. The evidence as it stood that day: figures from AI Footnotes, CIOnomics and other CIOPages data, and from filings and official statistics, each with its source.
4. The evidence that already points the other way, and what would change the position.
5. The moves for this quarter.
6. Calls: dated predictions, checked against named data on the date given.
7. A follow-up about a year later that grades the calls and the reasoning against what happened. The original stays as written.

A position can turn out wrong. The page keeps the evidence and reasoning from the day it was taken, so a reader can judge whether it was reasonable then. Calls are scored on their date, whichever way they fall, on the calls page.