Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Operational ITAM Podcast

Operational ITAM Podcast artwork

The Meter Room: Read the Meter Before the Invoice Does

Sep 3, 202619 minAudio
ShareXLinkedInFacebookWhatsAppEmail

AI consumption pricing turned software cost into a meter. Here is how to read yours before the bill does. Software used to be priced at the signature. Now it accrues at the meter. Ramp's payments data shows AI token spend up twenty point seven times in thirteen months, and the FinOps Foundation reports ninety-eight percent of practitioners now manage AI spend, up from thirty-one percent two years ago. A seat is a price you approved once. A meter is a price you discover every month. Bill walks into the first room of the Grid, the meter room, and breaks down the four parts of every consumption agreement: the unit, the rate, the commitment, and the true-up. Along the way: why the median business pays two thousand dollars a month while the average pays one hundred forty thousand, how Coinbase cut its AI bill nearly in half while usage grew, the controller who found ten thousand dollars a month in a term he had never heard, and the arithmetic that turns any invoice into a meter reading. Plus, a listener question from Elena in Cincinnati: finance wants next year's AI budget as one fixed number, and consumption pricing makes that feel impossible. What do you actually give them? IN THIS EPISODE The anatomy of a meter: the unit, the rate, the commitment, and the true-up, and why you need all four named for every consumption agreement you own Ramp's April benchmarks: a sixty-times gap between median and average AI spend, and the twenty-times price difference decided by a model default How Coinbase halved AI spend while usage grew: better defaults, routing, and caching, not friction and spend alerts The AngelList controller who learned the phrase "prompt caching" from a spend briefing and recovered ten thousand dollars a month the same day The three numbers to hand finance instead of one fixed budget, and the one-hour homework that produces your first meter reading CHAPTERS (00:15) - Meter Room Opens (01:16) - Reading the New Bill (04:12) - What a Meter Is (07:32) - Real-World Savings (09:31) - How to Read Usage (12:55) - Budgeting the Unknown (14:21) - Utility Lessons (15:48) - Measurement Discipline (16:38) - Homework and Next Steps TRANSCRIPT Click here to view the episode transcript. SOURCES & FURTHER READING Ramp, AI token spend controls launch (July 2026): https://www.prnewswire.com/news-releases/ramp-launches-ai-token-spend-controls-302827389.html Ramp, AI token cost benchmarks (April 2026 data): https://ramp.com/blog/ai-token-cost-for-businesses State of FinOps 2026, Linux Foundation / FinOps Foundation: https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1 Coinbase CEO Brian Armstrong on cutting AI cost: https://finance.yahoo.com/markets/crypto/articles/coinbase-ceo-halved-ai-costs-130000536.html FOCUS 1.4, FinOps Foundation: https://www.finops.org/insights/introducing-focus-1-4/ ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology - hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com The Operational ITAM Podcast is an EpicB Media LLC production.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Hey everybody and welcome back to the Operational ITAM Podcast. I'm Bill Van Nort, and today, we are reading a meter. On July 16th, a New York fintech company called Ramp put out a press release with a number in it that I have been thinking about ever since. Ramp processes corporate card and bill payments for more than 70,000 American businesses, which means they are not surveying anybody. They are watching the money move. And what they reported it is this. Since June of 2025, AI token spend across their customers has increased 20.7

times, not 20%, 20.7 times in about 13 months. That is not a line item growing. That is a new category of spend arriving at full speed, and it does not behave like anything your procurement process was built to approve. Nobody signed a purchase order for that number. It accrued. One request at a time on a meter almost nobody in the organization has ever read.

Good morning, good afternoon, or good evening. This is the show where we take the unglamorous machinery of enterprise technology and make it make sense. Grab your coffee. Last episode, we did something we had never done before. We closed the library. 11 episodes in those rooms, and we walked out with full honors and stepped into the grid because the estate we managed stopped behaving like a collection and started behaving like a utility. Today is the first stop on the tour I promised you, the meter room.

In episode 11, we laid out the five forms AI takes in your estate, and one of those forms was metered, the form where spend scales with usage. Today, we walk all the way into that one. And honestly, the warning shot came even earlier. Back in episode 9, Zylo's SaaS Management Index told us 78% of IT leaders got hit with unexpected consumption or AI charges. At the time, that was a renewals problem. It is not a renewals problem anymore.

It is the shape of the whole market. So let me give you the numbers and I'll name the sources because on this show, we do that. Ramp publishes benchmarks from their token spend product, real payments, not survey answers. And the April numbers tell you everything about how this category behaves. The median business paid about $2,246 a month for AI. The average paid about $140,842. Sit with that gap for a second. When the average is 60 times the median, that is not a typo.

That is a distribution with a long, expensive tail. And the distance between typical and tail is usually one team or one automated workflow running without a ceiling. Same dataset. The effective rate across everything averaged $0.72 per million tokens, but $1,000 buys you roughly 14.5 billion tokens on the cheapest mainstream model and about $704 million on a flagship. Same money, 20 times difference, decided by a default someone set in an afternoon.

And the FinOps Foundation, in their sixth annual State of FinOps survey, nearly 1,200 practitioners found that 98% now manage AI spend. Two years ago, that was 31%. The single most requested capability in the entire survey was granular AI spend monitoring. Tokens, requests, GPU utilization. The people whose whole job is reading bills are telling us the bill they cannot read yet. So here is the thesis. The price of software used to be set at the signature.

Now it accrues at the meter. A seat is a price you approved once. A meter is a price you discover every month. And the discipline this demands is simple to say and rare to find. Read the meter before the invoice does. So let's open the panel and look at what a meter actually is. Because every consumption agreement in your estate, AI or otherwise, is built from the same four parts, and you need to be able to name all four for every meter you own. Part one is the unit. What makes the meter click forward by one?

For a language model, it is the token, and here is the trap inside the trap. Tokens in and tokens out are different units at different prices, and output typically runs three to five times the cost of input. For infrastructure, it might be the GPU hour. For a platform agent, it might be the message, or the run, or a credit, which is a currency the vendor invented and controls. If you cannot say what the unit is, stop. Everything else about the meter is unknowable until you can. Part two is the rate, and this is where consumption pricing gets genuinely strange

because the same unit does not have one price. The same million tokens can bill at the full rate, at a cached rate, or at a batch rate on the same meter in the same month. RAMP's April data makes this concrete. Businesses running one popular mid-tier model paid an effective $0.62 per million tokens against a list price of $3. That entire gap is caching. Same model, same work. Fifth of the price because somebody engineered the request to reuse what was already paid for.

When your effective rate and the list price diverge that much, the list price stops being information. Your effective rate, your dollars divided by your units, is the only rate that is real. Part 3 is the commitment. Most enterprise consumption deals have a floor. You promise to burn a number, and the meter runs against that promise. Which means a meter can hurt you in both directions. Overage above the commitment, or a commitment you never consume, which is shelfware with a clock on it. Reading the meter mid-cycle means comparing the accrual against the commitment

while there is still time to steer. And I will hand you some humility on this one. Mine. Years ago, on a purchase order I signed, I sized a consumption commitment straight off the vendor's projection of our growth, because the discount at that tier was beautiful, and the projection came with a very confident chart. We never read the meter mid-cycle. Not once. The true-up arrived at the end of the year like a weather event, and I remember thinking we had been surprised. We had not been surprised. We had been unread. The meter knew the whole time.

So let me give you an opinion here, clearly labeled as an opinion. Size a consumption commitment to what your own history says you will actually burn. Your typical month. Not the vendor's growth curve for you. The counter-argument is real, and I'll give it to you fairly. Bigger commitments buy better rates. And if your usage genuinely is doubling, committing low means paying overage on growth you should have seen coming. Fine, then let your own meter readings make that case, three months of them, and commit on your evidence instead of their enthusiasm.

And part four is the true up. What happens when actual crosses committed? What rate applies above the line? When does the excess bill and can it carry over? Those four answers live in the contract and I will tell you from experience, almost nobody who watches the dashboard has read the contract and almost nobody who read the contract watches the dashboard. Now let me show you what this looks like when real organizations do it well, because two examples crossed the wire this summer and they teach opposite ends of the same lesson.

First one. In late June, Coinbase's chief executive, Brian Armstrong, posted their internal playbook, and the trade press picked it apart in detail. Coinbase cut its AI spend nearly in half while its token usage kept growing. Read that again. Half the spend. More usage. And the part I want you to hear is how. Not caps. Armstrong said 91% of employees never even hit the old usage caps, so the caps were friction pretending to be control.

His words on how you actually do it, quote, not with friction and spend alerts, with better defaults, routing, and caching, end quote. Their gateway defaults route routine work to inexpensive models. Harder work escalates when it earns it, and their caching went from hitting 5% of requests to 60%. Every one of those decisions happened before the meter turned. Second example, from the other side of the house. In Ramp's launch announcement, the controller at AngelList describes getting a weekly spend briefing that surfaced a term he had never heard.

Prompt caching. Not a controller's phrase. He routed it to engineering. They found they had been losing about $10,000 a month, and the fix went in the same day. Think about what actually happened there. The control lived in engineering. The visibility lived in finance. The money got saved on the day those two met in the middle. That meeting place is the meter room, and in most organizations, that room is empty. Let's take a quick break. If you're getting value from this show, subscribe wherever you're listening.

And if you know somebody who just opened an AI invoice they could not explain, send them this episode because the explanation is in part 2. Every episode with full transcripts is at operationalitam.com. Ok, Part 2 – How you actually read a meter before the invoice does. Step 1 – Find every meter. A meter you have not located is a meter the vendor reads alone, and your meters are hiding in all five forms from episode 11. If you did that episode's homework, the Shadow AI Census, you already hold the

beginning of your meter list – expense data, single sign-on, asset records. Every AI vendor on that census either bills a seat or bills a meter, and your first pass is just sorting them into those two piles. Add the cloud AI services riding inside your existing cloud bill, because those meters do not even arrive as separate invoices. They arrive as line items inside a bill you already pay, under your cloud provider's name, which is exactly why the census keeps missing them. Step 2. Reconcile every invoice line to a meter you found. And I mean arithmetic, not vibes.

Take the dollars on the line, divide by the units consumed, and write down the effective rate, then do last month. A line you cannot tie to a meter is not a cost you approved, it is a cost you absorbed, and an effective rate that moved is telling you one of exactly three stories. The mix changed, meaning somebody moved work to a pricier model. The caching changed, meaning the engineering got better or worse. Or the price changed, meaning the vendor moved the rate. Three stories, three different owners, and the invoice total tells you none

of them. The effective rate tells you all of them. Step 3. Watch the drivers, not the total. Ramp's data says the single biggest driver of surprise cost is model tier migration, teams upgrading to premium models for quality, usually invisibly. Premium models went from 5.7% of business token cost in June of 2025 to 55.9% by April, 10 months. And the difference per workflow can run 10 to 100 times.

The other driver is agents, and I want to say this one carefully, because it is the future of this problem. An agent takes as many steps as it decides the task needs, which means you approved the task, and the agent is deciding the bill. Any automated workflow without a per-run ceiling is a meter with no shutoff valve. Step 4. Set the defaults, because this is the actual governance layer. The Coinbase lesson is not that they saved money, it is where the saving lived. In the gateway default, in the routing rule, in the cache policy.

Decisions made once, upstream, that shape every request afterward. A spend alert fires after the money is gone. A default decides whether it ever leaves. And one thing I am deliberately not giving you today, there is a token price decline statistic making the rounds, a big satisfying percentage. I chased it to its source, the way we did with refresh numbers back in episode 7, and it traces to a platform vendor measuring its own customer base. So you will not hear it here. What I can give you is Ramp's paired numbers across the same window.

Token usage among businesses up 1,001% January 2025 to April 2026. Spend up 497%. Falling unit prices are real, and they are not saving anybody money because usage is growing faster than prices falling and it is not close. Which brings us to a listener question, and this one landed in my inbox from Elena in Cincinnati. Elena writes, Our finance team wants next year's AI budget as one fixed number.

With consumption pricing, that feels impossible. What do I even give them? Elena, your instinct is right, and here is the move. Do not give them one number, because one number is a guess dressed up as a commitment, and finance people can smell that. Give them three numbers, reported separately, never blended. Number one, the committed floor. That is contractual. It is the most honest number you own. Number two, the expected run rate. Built from this year's effective rates and named drivers and put a real buffer on it because ramps data shows month-over-month

swings above 40% are common even with stable headcount. When finance asks why the buffer is that big, do not defend it. Show them the swing data and let the data do the arguing. Number three, the uncapped exposure. And next to every meter that creates it, the specific control that caps it. The per run ceiling, the gateway default, the alert threshold. Here's the reframe, Elena. You cannot promise finance what a meter will read, and you should stop pretending you can.

What you can promise is which drivers are governed and who owns each one. Budget the drivers. Report the meter. That conversation is the whole job. All right, the grid room. We are standing in the meter room this week, and if you have ever actually looked at the utility meters in a commercial building, you know three things about them that map onto everything we just covered. First, the meter spins whether anyone reads it. It does not care about your budget cycle, your approval workflow, or your fiscal year.

Consumption is recorded the moment it happens, and the only question is who reads it first, you or the biller. Second, utilities have a thing called an estimated read. When nobody physically reads the meter, the utility guesses your usage from history and bills the guess, and they reconcile it later. And I want you to notice whose model produces the guess. When you do not read your own meter, you are living inside the vendor's estimate of you. Third, and this is my favorite, commercial power bills carry something called a demand charge.

You do not just pay for the energy you used. You pay a premium pegged to your single worst 15 minute window of the month. Your peak sets the price. Now think about an agent workflow with no ceiling, spiking on a Friday night. Consumption billing is demand charge economics, and your estate is full of peaks nobody is watching. The utilities figured all this out a century ago. They read on a schedule. They audit the estimates. They engineer the peaks down. None of it is new. It is just new to us.

Which brings us to today's principle. And let's take the whole run from the top. Hardware asset management is a custody discipline. Software asset management is an evidence discipline. Audit defense is a process discipline. Settlement is a commercial discipline. Shadow IT is a service discipline. Refresh is an economics discipline. Disposal is a liability discipline. Renewal is a leverage discipline. Tooling is a judgment discipline. The AI estate is a governance discipline.

And consumption? Consumption is a measurement discipline. The seat asks you to count people. The meter asks you to measure flow. And a flow you do not measure is a price you do not know, on a bill you have already agreed to pay. Class dismissed. Here is your homework and it needs about an hour. Pull your largest AI or consumption invoice, last full month. Go line by line and do two things for every line. First, name the meter behind it, the unit and the rate.

Second, divide the dollars by the units and write down the effective rate, then do the same for the month before. When you are done, you will hold a one-page list of two kinds of findings, lines with no meter you can name, and rate movements with no story you can tell. Date the page, sign it. That page is your first meter reading, and whoever you show it to will understand this episode without hearing a word of it. Next episode, we walk from the meter room to the standards body,

because here is what happened while nobody in ITAM was watching. The FinOps Foundation built a common language for exactly the bills we struggled with today. It is called FOCUS, the FinOps Open Cost and Usage Specification. And this June, their steering committee ratified version 1.4, which adds invoice reconciliation, the exact discipline we just did by hand, straight into the standard, with native AI support already on the roadmap for the next version. These are the people who renamed their own flagship conference around the token.

The meter readers built themselves a language. Next week, we learn to speak it, and I will show you what it means for how ITAM and FinOps stop working the same estate in different rooms. And listen, the case files are open. One situation, one page. The constraint you were under, what you did, what happened. No company names, I will sanitize everything. Send me one worth working at the website and I will build an episode around it. I'm Bill Van Nort. This is the Operational ITAM Podcast. Find every meter. Compute your own effective rate. Set the default before the invoice sets it for you. I'll talk to you next week. Take care.

Open the transcript file

Hosts and Guests

Hosts

  • Bill Van Nort Host Feed-stated

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. The Decision Table: Keep the Result

    Oct 8, 202622 minAudio

    The project is finished. The invoice is lower. Six weeks later, someone asks for more licenses. What changed? Bill Van Nort follows a fictional software service after its initial improvement has been verified. This...

    Credit the people on this episode

  2. The Decision Table: Where Did the Saving Go?

    Oct 5, 202621 minAudio

    An approved reduction is only the beginning. Bill Van Nort follows a fictional software subscription change from forecast through the signed agreement, implementation, invoices and a delayed credit. See why a $48,000...

    Credit the people on this episode

  3. The Decision Table: Who Owns the Renewal Decision?

    Sep 28, 202620 minAudio

    A renewal can pass through every department and still arrive at its deadline without a decision owner. Bill Van Nort works through a fictional customer-support renewal to show how ITAM, FinOps, procurement, finance,...

    Credit the people on this episode

  4. Challenge the Bill Before You Negotiate the Discount

    Sep 25, 202620 minAudio

    Twenty percent off sounds like progress. Until the new bill is still twenty percent higher than last year - and nobody has checked whether you need everything on it. In Episode 014 of the Operational ITAM Podcast, Bill...

    Credit the people on this episode

  5. The Standards Body: FOCUS Put Our Name on the Door

    Sep 18, 202621 minAudio

    The FinOps people wrote the bill down as a standard and invited ITAM in. Here is how to speak FOCUS before your CFO asks. On June fourth the FOCUS Steering Committee ratified version 1.4 of the FinOps Open Cost and...

    Credit the people on this episode