You are sitting in the boardroom for the third quarter budget review. The vice president of agile transformation just spent the last forty-five minutes getting taken apart over the line item for agile coaches. Sixteen coaches, eighteen months, and the slide that was supposed to defend them has six metrics on it that the chief financial officer does not consider metrics. The room knows this is theater. The vice president knows this is theater. He pivots before he closes his laptop and offers to embed four of his coaches with the cloud migration team to help unblock the cross-functional collaboration model.
Your senior vice president of cloud operations does not let him finish. "We don't need more people who can't code or do!" The chief financial officer does not stop writing. The chief executive officer does not look up. The next twenty minutes belong to cloud ops anyway. The migration is six quarters late. The network redesign is on hold because the team has not figured out how to back out the last set of identity changes without breaking customer integrations, and the cloud bill is twelve percent over plan because the legacy footprint is still running in parallel. He is also paying overage to the old data center company on a contract he was supposed to have terminated last year. The chief financial officer is taking notes with the kind of precision that means somebody is being asked for a separate one-on-one before close of day.
The chief product officer goes after that, with the slide the product management group always brings to the third-quarter review. Another reorganization, and another offsite, dressed up as a quarterly cadence of cross-functional alignment workshops meant to keep the roadmap connected to the strategy. The chief financial officer does not look up. You have seen this slide three quarters in a row. Nothing in it is wrong, technically, but nothing in it has shipped a feature either.
You are up next, and for the first time in three years of these meetings you have real numbers. Not the get-off-the-stage kind. The teams that doubled their month-over-month spend on AI for building software shipped considerably more measurable value than the teams that did not. You have the AI spend matched against the delivery outcomes at the team level. You have the cost-of-delay math, which is the dollars the company misses for every day a feature is not in production, calculated against the revenue or savings the feature would unlock. You have the math on what the top-spending teams produced for what they cost. You have the winning numbers.
You should not be nervous.
You are nervous anyway. You are also leading a transformation. The difference is yours is the one that is actually working. The agile vice president just spent the last forty-five minutes making the room allergic to anyone asking for more money on a transformation. The cloud ops scene did not undo it. The product management slide did not undo it. You are about to walk into the version of the room those three made, asking for more money on a transformation, and the only thing that separates your line item from theirs is the spreadsheet on the second tab.
You are about to ask the room for more money. You are going to call it finding the ceiling.
If the version of you sitting in the chair has not yet pulled the winning numbers together, this is the wrong room to be sitting in this quarter. Read the audit-posture piece first. Come back when the spreadsheet is in your laptop bag.
Here is what is coming, in the order it will come, because every executive team grills in the same sequence.
The chief financial officer goes first. His question is the audit-posture question. "Walk me through the run-rate trajectory on this line. Same engineer cost us nothing in twenty twenty-two and one thousand four hundred dollars last month. Where does this sit in twelve months, and what is the floor under the one thousand four hundred dollars."
If you cannot match the AI spend to outcomes the board already recognizes, you are giving him the agile coach defense from forty-five minutes earlier, and he will treat your line the same way. The chief financial officer is not actually asking about run rate. He is testing whether you can defend the spend on output, because that is the only defense he is allowed to accept inside the audit framework his finance organization runs on.
Your answer is not a defense of the one thousand four hundred dollars. It is a redirect. "That team beat their delivery commitment for the entire quarter. They got out of the data center six weeks early, worth one hundred twelve thousand dollars against the legacy overage rate finance is paying right now. They shipped the pricing engine eleven days early, worth nine thousand six hundred thirty-six dollars in margin captured at the rate the pricing-strategy team has on file. And they shipped two retention features the customer-success team has modeled at three hundred twenty-one thousand dollars of first-year retention lift attributed to this quarter, against the cohort the customer-success team is measuring. Three contributors, three sources, three numbers a finance team can audit. Total benefit, four hundred forty-two thousand six hundred thirty-six dollars against thirty-four thousand dollars in AI spend on the team's quarter. The return is approximately thirteen dollars back for every dollar in. I have the spreadsheet. I want four more teams running this way by fourth quarter."
The chief financial officer will glance at the chief executive officer for a beat, then ask you for the spreadsheet. You hand it to him. The spreadsheet has two columns matched on team. Quarterly AI spend on one side. Delivery against commitment, infrastructure milestones, and the product team's customer-value scoring on the other. The winning numbers are the deliverable. He has been asking for two quarters whether the AI invoice is producing anything, and you are the first leader who walked in with them.
He follows up. "Walk me through the thirteen-to-one." You walk him through it.
That team is eight engineers. The team's total cost, including salaries, benefits, and overhead, for the quarter is roughly one point six million dollars. The AI spend across the same quarter was about thirty-four thousand dollars. Roughly two percent on top of what the team already costs us.
Now run that against what the team actually delivered. They got out of the data center six weeks before the migration team had scheduled them. At the legacy overage rate finance is paying right now, that is one hundred twelve thousand dollars of avoided overage in the quarter, attributed to this team's early exit. They came in eleven days early on the pricing engine, and the pricing engine lifts margin by zero point four percent on eighty million dollars of annual revenue. That feature is worth about eight hundred seventy-six dollars a day every day it sits in the backlog instead of in production. Eleven days at eight hundred seventy-six dollars is nine thousand six hundred thirty-six dollars of margin captured early. The two product features they shipped are tied to a three hundred twenty-one thousand dollars first-year retention lift on the customers who got them, attributed to this quarter, against the customer-success team's measured cohort. Total benefit, four hundred forty-two thousand six hundred thirty-six dollars. Total AI spend on the team's quarter, thirty-four thousand dollars. The return is approximately thirteen dollars back for every dollar in. The number is not theoretical. It is on the second tab of the spreadsheet, with assumptions and source citations on the third.
You hand the chief financial officer the slide. It looks like this. The first column is "Quarterly profit and loss for Team Number One, eight engineers". The second is "Source", and the third is "Value".
For "Pricing engine shipped eleven days early", the source is "eight hundred seventy-six dollars per day times eleven days, pricing-strategy team's rate", and the value is "nine thousand six hundred thirty-six dollars". For "Data center exit six weeks early", the source is "Legacy overage rate finance is paying", and the value is "one hundred twelve thousand dollars". For "Two retention features, Year One lift, attributed to quarter", the source is "Customer-success team's measured retention cohort", and the value is "three hundred twenty-one thousand dollars". The "Total quarterly benefit" has no source, and the value is "four hundred forty-two thousand six hundred thirty-six dollars". "AI for building software spend, quarter" has the source "Token invoice, eight engineers times quarter", and the value is "negative thirty-four thousand dollars". The "Net quarterly benefit" has no source, and the value is "four hundred eight thousand six hundred thirty-six dollars". The "Return on investment" has the source "four hundred forty-two thousand six hundred thirty-six dollars divided by thirty-four thousand dollars", and the value is "approximately thirteen to one".
The chief financial officer writes that down.
The chief operating officer goes second.
She watched the agile coach line item eat eighteen months of organization change without producing a number anybody could defend, and she is not interested in another transformation theater performance. Her question is operational. "How do you know this is reproducible?"
Your answer is the mechanism. "We remove the cap. The typical engineer in this organization has been running at one thousand four hundred dollars a month on AI because that is the cap they were observing, the social cap, not the budget cap. They did not know they were allowed to spend more, so they did not. On the cohort we are scaling, we tell them there is no per-engineer ceiling. We replace the individual cap with a program-level envelope, the maximum the company is willing to spend to find out where the ceiling actually sits. Inside the envelope, an engineer spends what they need to ship. We do not run a training program. We do not bring in a coach. We give them the permission and we watch what