Three ways of charging in ten weeks, and a book of business still unproven.
From SaaS-pocalypse to cost-per-completed-task
Watch how the customer was asked to pay, because it changed three times. First the consolidation read: AI would compress the software stack the way every capability wave does, and the labs would push into their customers' businesses to find revenue. Then tokenmaxxing — more tokens looked like more value until the invoice arrived. By midsummer, enterprises were reining in employee AI as metered costs bit; one executive said flatly they had created a monster. Then came the correction in late June and early July: the number that matters is not the token, it is the completed task. Cursor benchmarked Opus at roughly $11 per finished coding job against its own model at 55 cents. The buyer pays for work done, not sticker price.
Under all three sits the read we filed in the first financing window: capital got certain before returns did. Money flowed down the stack into infrastructure while the deployment layer stayed contested, and that contest never resolved. Application revenue was the most-worked hypothesis in the register — the sign of a layer where cash is real, pricing keeps moving, and staying power is untested.
The wider record adds the concession that keeps this honest. Real books of business already exist in pockets: Suncorp scaled AI into claims workflows, Rio Tinto into logistics, and Databricks reached a reported $188 billion valuation on enterprise data it already holds. Those outcomes are genuine. They are not yet widespread, and not what most of these valuations assume. Moving fast was never the question. Moving fast on a foundation no pricing cycle has tested is.