# Cursor's CFO Council: Leading AI's Financial Revolution > Discover how Cursor's CFO Council is transforming AI strategy by putting finance leaders at the forefront of AI's financial impact. > By Dave · 2026-07-23 > Source: https://otf-kit.dev/blog/cursor-cfo-council-ai ## The CFO has a new seat at the AI table Cursor — the AI coding company heading into a $60B SpaceX acquisition — stood up a CFO Council this month, and the framing Jordan Topoleski put on it is the part worth pausing on: "Everyone's spending on AI...but it's really hard to actually understand how we can measure the tactical ROI." That sentence is doing a lot of work. It names the thing every finance leader has been muttering in QBRs for two years: the spend chart goes up, the productivity chart is fuzzy, and nobody can hand the board a defensible multiple. Putting CFOs in a working room with vendors and peers is a structurally different answer than another whitepaper. ## Why ROI, and why now The whole pretext of the council is that the CFO's job on AI is no longer "sign the PO." CIOs and CTOs are still the ones running implementation; the CFO is the one who has to answer the harder question — the one Topoleski names directly: where does a dollar of AI spending reliably generate ten dollars in business value rather than fifty cents? That's a dollar-in, ten-out-or-fifty-cents framing. Most vendors, Cursor included, would rather avoid pinning a number on their own productivity claims. A council whose primary deliverable is a shared framework for that measurement is, mildly, the adult in the room. It also lands at a moment when AI budgets have outrun AI accounting. The CFO used to be downstream of engineering; on AI that ordering inverts, because the spend is large, recurring, and spread across enough cost centers that no single engineering manager owns the line item. ![a single AI deployment — $1 of spend flowing in, branching at measurement time into either](https://cdn.otf-kit.dev/blog/cursor-cfo-council-ai/inline-1.png) ## What's in the council, and how it's shaped Cursor launched the council with a quiet LinkedIn post from Topoleski. The response surprised him: enough inbound interest from finance teams that the council filled mostly without a formal application. Members span tech-forward and legacy operators — a deliberate cross-section, not a curated brand list. The announced roster, as of the July 23 update: | Company | CFO | | --- | --- | | SentinelOne | Sonalee Parekh | | Paytm | Madhur Deora | | Asana | Aziz Megji | | Natera | Michael Brophy | | Payoneer | Bea Ordonez | | Firstsource | Dinesh Jain | | First American Bank | Matthew Wajner | | JFrog | Ed Grabscheid | | Amplitude | Andrew Casey | Format: quarterly meetings in rotating cities, first meeting Aug. 18 in San Francisco. Open-ended membership on a rolling basis. Public-company, private-company, vertical-mixed by design. The shape matters — it isn't a customer advisory board where Cursor runs the agenda, and it isn't a research consortium where the output is a paper. It's a working forum whose stated outputs are practical tools. ## The deliverables the council is aiming at The brief lists three concrete artifacts the council is set up to produce: 1. Shared benchmarks for AI productivity. Not vendor benchmarks — numbers a CFO can pull from a peer and trust, because both sides measured the same way. 2. A framework for "return on intelligence." Naming it that way is on-brand for an AI coding vendor, but the underlying object is a unit-economics model: spend, substitution, lift. 3. Guidance on model allocation and cost controls. The least glamorous deliverable, and the one with the most direct effect on the next quarter's P&L. Worth flagging what isn't in the brief yet. No published ROI lift number from members. No external benchmark the council has blessed. No co-authored report. The promised outputs are forward-looking; the group just stood up. Anything you read online claiming a precise ROI improvement figure from this council is, today, unattributed — not because the work isn't being done, but because the work hasn't shipped. Honesty about that gap is the part worth keeping in your own board deck when you reference the council. ## How to actually use this today You don't need a seat at the table to start adopting the framing the council is converging on. Three concrete moves: ```md 1. Pick a single AI line item. Spend, seats, tokens, model mix. 2. Define one substitution metric per deployment. - coding agent: PRs merged per week per engineer, or review cycles cut - doc search: tickets resolved without escalation - customer support: deflection rate, AHT delta 3. Define one lift metric per deployment. - revenue per FTE on a function the agent supports - cycle-time delta on a workflow that wasn't AI before ``` The dollar-in-ten-dollars-or-fifty-cents framing collapses to a single question per deployment: at current run rate, does this deployment substitute cost or add revenue, and by what multiple? If you can't answer that for a deployment in two sentences, you don't have ROI measurement, you have an attestation. For tracking inputs, the cheapest starting point is a shared spreadsheet by team with three columns: vendor, monthly spend, owner. The council's eventual benchmark is useless to you if your own internal numbers don't exist at the row level. For engagement: the first meeting is closed, but published outputs — when they appear — will be the read. If your company is in the size band Cursor is courting, the rolling-admission window is the lever to pull. ## What this changes for AI-spend accounting more broadly The interesting move isn't the council itself — it's what it implies about where AI ROI is being measured for the next several years. If a vendor with Cursor's reach can't get CFOs to converge on a framework alone, the answer is a peer forum with skin in the game. Expect adjacent vendors — the other AI coding platforms, the model API providers, the productivity-suite makers — to either build parallel councils or compete for membership. The CFO seat at the AI table is becoming a fixture, not a guest appearance. There's a smaller lesson under that: when a category's spend outruns its accounting, the vendors who help the buyer's finance team catch up become the trusted partners. The vendors who only keep raising the seat count on the engineering side become the line item that gets cut in the next budget cycle. ## The part underneath the AI churn — where this lands for builders A finance-side framework for AI ROI is the part above the model layer. The part below it is the component layer that has to keep shipping correctly when the model changes underneath it. Cursor's value is the agent loop; the durable asset is the codebase the loop writes into. When the agent ships a button, a form, or a screen on three platforms, the button has to look and behave the same on all three — that's the part that doesn't rotate when a $60B acquisition closes or when Cursor ships the next model swap. It's the same cross-platform component API across web, iOS, and Android, written once, with the same visual contract the agent can describe in plain English. That's the layer OTF operates at. Not the model. Not the council. The piece that survives the council's deliverable shipping, the next coding agent replacing this one, and the next acquisition rumor after that. When the dollar-in-ten-dollars-out question gets asked, you want a UI layer you can hand the auditor with one source of truth. Measure the AI. Pick the model that wins. Build on the part that doesn't change when they do.