Cursor built a CFO council this week, and quietly proved a thesis Olakai has been on for months.
The quick version of the week first: Microsoft cut another wave of jobs largely to fund its AI bet, continuing the pattern we broke down in why the accountability bar for AI spend just went up. The big labs kept softening their 2025 predictions about half of knowledge-worker jobs vanishing. xAI shipped Grok 4.5, OpenAI pushed a new ChatGPT release after a federal review, and — the one that drew a smile around here — Elon Musk publicly called Anthropic “obviously the leader in AI right now,” adding “I was clearly wrong,” a rival conceding the lead in writing days after launching his own model.
But none of that is the story worth unpacking today.
Cursor built a CFO council
This week Cursor, the AI coding tool, launched a CFO Council, a working group for chief financial officers, and published a stack of data alongside it. Sit with that for a second: a coding tool built a forum for finance leaders.
Here is why it matters. Cursor, more than almost any other AI coding vendor, turned coding into a metered cost. It was early and aggressive on usage-based pricing — its top consumer tier taps out around forty dollars a month, and past that, users are into custom, usage-based territory fast, even as individuals. Cursor made tokens a line item, and now it is walking straight into the CFO’s office to help make sense of the bill it helped create.
That is the point we have been making for months: the responsibility for winning at AI, the tokens, the consumption, the return, has moved into the CFO’s office. Coding used to be the CTO’s world, engineering’s world, and finance stayed out of it. Not anymore. Cursor just pulled the CFO directly into the coding room, in public, because somebody has to answer for the spend — a shift we mapped out in detail for what CFOs need from AI ROI reporting.
The data is fascinating, and a warning
Cursor’s headline number, published on its CFO Council blog: companies in the top quintile of token usage saw 16.5% year-over-year revenue growth, versus 5.1% for the bottom quintile. Use more tokens, grow faster — and AI genuinely does create real value. But that is a correlation, seen from thirty thousand feet. High token usage lining up with high revenue growth does not mean the tokens caused the growth. A thousand other things drive a company’s top line. What is missing in between is measurement: the step-by-step evidence that connects a token to an outcome.
Cursor’s own Developer Habits Report makes the case just as clearly from the other direction. The top 1% of users generate 46 times more AI-assisted code per day than the median developer. Value is wildly concentrated, so “we used a lot of tokens” tells a finance team almost nothing on its own. The real questions are who, what, and did it ship. Cursor’s data also shows cost per agent request swinging nearly nine times across model families — from roughly $1.57 on the most expensive model down to $0.18 on the cheapest — so the identical request is priced completely differently depending on where it gets routed, the exact dynamic we unpacked in why acceptance rate is the wrong metric for coding-tool ROI.
Put it together, and Cursor has accidentally proven the thesis it did not set out to prove. The correlation is interesting. It is not proof. Proof comes from measurement — who, what, and why, token by token, tied to what actually shipped. That is the game for 2026 and 2027.
What this means beyond coding tools
Cursor is a coding-specific example, but the same trap applies to every AI vendor a company runs, from customer-support copilots to autonomous agents handling multi-step workflows. A vendor’s dashboard will always show the metrics that make the vendor look good. A quintile chart on revenue growth is a marketing asset for Cursor, not an ROI audit for the buyer. The only way to get an honest answer is a measurement layer that sits above any single vendor, pulling cost-per-outcome data across every tool a company runs, which is precisely the gap custom KPI tracking is built to close — visibility a vendor’s own blog post will never hand over voluntarily.
The read
The headline this week is simple: the CFO just walked into the coding room, and Cursor held the door open. The number that should stick, though, is not the 16.5% versus 5.1%. It is the fact that Cursor felt it needed to build a CFO council at all. When the company selling the tokens starts speaking finance’s language unprompted, that is the clearest signal yet that unmeasured AI spend has become too large a line item to leave unmanaged, and vendor-neutral proof, not vendor-supplied correlation, is what the CFO’s office actually needs.
One question worth asking internally: is the CFO already in the AI tokens conversation at your company, or still on the outside looking in?