Back to DAGDaily
Gate AIAugust 9, 20267 min read

The CFO Lens

AI Has Three Cost Centers. Only One of Them Sends an Invoice

In a new piece for the Gate AI blog, Kate Melvin makes the finance case for a control layer in front of every model a company touches. It is the clearest non-crypto argument for Constellation infrastructure we have read this year.

All quotes below are Kate Melvin's, from "AI Has Three Cost Centers" on constellationgate.ai. Credit and full context belong to her original article.

Metered
Infrastructure

Tokens, compute, storage. Variable by usage, not by seat.

Reshaped
Labor

Work is reduced, accelerated, or redeployed, not simply removed.

Unbudgeted
Governance

Someone has to prove what data went in and what came out.

The Line That Frames Everything

"One of those arrives as an invoice. The other two arrive as a surprise."
Kate Melvin, Gate AI

Melvin's starting point is the month-end question every finance team now dreads: what did we spend on AI, and what did we get for it. Some of the answer sits in a provider console billed by the token. Some is a subscription a team bought on its own and filed on an expense report. Some is a productivity claim nobody can reconstruct.

Her argument is that technology spending used to categorize itself. IT owned infrastructure, departments bought software, HR owned people costs. AI collapsed those lines, because a single AI workflow carries an infrastructure cost in tokens, a labor implication in the work it reshapes, and a governance cost because someone has to be able to explain the output later. Those three are one operating model now, and making it legible is a CFO problem.

The Metric She Refuses to Report

The piece is unusually disciplined about measurement. AI is metered and variable, so the classic software budget of licenses, renewals and seats stops describing reality once a workflow becomes daily operations. Melvin cites Flexera's 2026 State of ITAM finding that only 31 percent of organizations have accurate visibility into AI software spend, and 59 percent report wasted AI spend rising year over year.

"Cost per token is a vendor metric. It tells you what you paid, not whether it was worth paying. The number I want is cost per useful, verifiable outcome."
Kate Melvin

Note the word verifiable sitting inside a finance metric. That is the whole thesis in one adjective. An outcome you cannot evidence is an outcome you cannot book, and the reconstruction work required to prove it after the fact is where the productivity gain quietly leaks back out.

The Hidden Cost Is Not the Bill

Melvin's sharpest section is on unmanaged AI. When employees use different tools, models, prompts and data sources, any audit, customer question or security incident triggers a manual investigation. Who used the model? What information was included? Which model produced the output? Was sensitive data exposed? Can we demonstrate any of it?

Her answer, six months after the fact, is brutal and familiar: unclear, unclear, one of four, hopefully not, and no. So someone spends a week rebuilding history. The work was never eliminated. It moved downstream into review, remediation, compliance and investigation, where it is harder to see and nobody budgeted for it.

The Four Things She Asks For

None of these require buying a platform to start, which is what makes the list credible coming from someone who works at a vendor.

01
Usage by team and by model, not a total

A total only tells you the bill is growing. The split tells you which workflow, which team and which model is driving it.

02
Cost per workflow run, not cost per seat

Seats made sense when software was a license. They are the wrong unit once the meter runs on every call, retry and retrieval.

03
Every AI tool in the company, with a named owner

Melvin notes this exercise is always more interesting than anyone expects. Shadow subscriptions are the quiet part of the AI bill.

04
A retrievable record, without asking the person who ran the prompt

This is the line that lands hardest for anyone holding $DAG, because it is exactly what Digital Evidence was built to provide.

"If your evidence lives in someone's memory, you do not have evidence."
Kate Melvin

Owning the Rails, Not the Model

Melvin discloses her bias plainly: Constellation builds the gate that helps her meet her fiduciary requirements. What she does not do is claim the gate controls how a model thinks. Her scope statement is worth repeating, because the category oversells this constantly. It is control over what data is exposed to third-party models, not a claim to police how a model reasons.

"The real question is whether you own the rails around the models you use."
Kate Melvin

Within that scope, the value is concrete. Gate AI brings usage visibility, cost management, security controls and verifiable evidence together across the activity routed through it, so finance, operations and risk read the same picture instead of three partial ones. It protects sensitive information, credentials and personal data before that data leaves the organization, and its cache-aware prompt compression trims token use without changing the substance of a request. The financial result she names: fewer convenience purchases, less unauthorized tool use, fewer duplicate subscriptions, and less premium model usage disconnected from measurable value.

Evidence by Default Is Becoming Law

Melvin's conclusion on timing is the one holders should sit with: the teams that start keeping a verifiable record now are the ones ready when the rule lands, not the ones retrofitting it after an incident. Internally, Gate anchors AI activity to Constellation's Digital Evidence layer, which makes those records tamper-evident and independently verifiable.

DAGDaily's Take

This article never mentions a token price, a listing, or a chart, and that is precisely why it matters. It is a CFO explaining, in finance language, why an enterprise needs the exact thing Constellation spent years building: a metered control point with a tamper-evident record underneath it. Demand for $DAG does not come from people who want $DAG. It comes from people who want cost per verified outcome and discover that verification has to run on something.

Pair this with Part 7 of The Constellation Thesis and the independent gateway ranking. One is the product argument, one is the third-party validation, and this is the buyer's own reasoning written out loud.

Read the original

"AI Has Three Cost Centers" by Kate Melvin

Every quote on this page is hers. The full piece includes her complete citations, disclosures and the four asks in her own words.

DAGDaily

DAGDaily is an independent community publication. Quotes are excerpted from Kate Melvin's article on the Constellation Gate AI blog and remain her work. Nothing here is financial advice. Digital assets are volatile and you can lose money. Always do your own research.

Share this post
Your reaction
Stay Informed

Want more like this?

Get DAGDaily's weekly breakdowns of partnerships, enterprise adoption, and market shifts — straight to your inbox.