5 Questions Economic Governance Answers (and Compliance Doesn't)

The next board meeting that asks for a granular account of what AI really costs your company will want two separate answers, and most people only bring one. The first is regulatory, and that one you have on the tip of your tongue: formal policy, audit trail, team training, committee minutes. The second is economic, and on that one almost everyone goes quiet: how much AI is costing in coordination, and whether that bill is growing faster than the gain it promised.

The typical mid-sized company in 2026 answers the first question well, because compliance matured over the past two years, and shows up empty-handed for the second. The regulatory front earned a committee, a cadence, and an owner. The economic front does not even have a seat at the table yet.

Five questions separate the two. Economic governance answers each one in cash. Regulatory compliance reaches none of them, and not for lack of effort: the question simply is not in its nature.

Why These 5 Questions Have No Owner in Mid-Market Today

The AI governance map inside a mid-sized company in 2026 has four fronts with a clear owner and one orphan. Compliance goes to Legal or a dedicated committee. Model risk goes to the CTO. AI safety goes to engineering and security. Infrastructure cost, the tokens and the compute, goes to engineering and finance. The fifth front, what it costs to coordinate human and machine in cash, has no named seat anywhere.

The CFO is the closest to taking it on, but the category still gets treated as technical and pushed onto the CTO or Operations. The CTO looks at inference. Operations looks at process. Neither one has the financial vocabulary to carry the thing to the board in money. The result is an organizational gap, and the five questions below expose it one by one.

Question 1: What Does a Decision Crossed by Human and Agent Cost, in R$?

The unit is not the hour, not the API call, not the slice of the salary of whoever walked into the room. It is the fully loaded sum of all of that, per decision that crossed departments and passed through AI along the way. You do not need anyone to hand you the number: take the fully loaded hourly cost of your senior team, add the hours each major decision burns in meetings, calibration, and ratification, and build the arithmetic. In a 500-person SaaS, a typical crossed decision tends to land between R$ 8,000 and R$ 15,000, and that is your account, not a promise from me. If yours comes to R$ 30,000, your ratification chain carries structural fat. If it comes to R$ 3,000, you are probably cutting context, and you will pay the difference later, in an avoidable error.

The defensible answer does not need a platform installed. The 30-day starter inventory maps three to five real decisions and gives back the order of magnitude of your own house, not the market average. A CFO who walks into the next board conversation without that number walks in with a story. Regulatory compliance has no tool for this question, and it should not: its unit of measure is legal risk, not operational cost.

Question 2: Which Edge Eats the Most Senior Payroll in Your Company?

The question forces you to split by type. Lumped together, senior payroll is a single line that says nothing. Split apart, it shows which front is growing fastest and where an economic intervention pays off most. Each of the four edges has its own cost signature and its own growth trigger. The pattern that repeats in a mid-sized company in 2026 has a recognizable shape: human to human still leads the aggregate while adoption is early; human to machine gains weight as more people touch AI; machine to human grows alongside it, as agent output starts feeding senior decisions; and machine to machine stays a minority, but grows under the radar and tends to be the biggest source of silent incidents through 2028.

The practical reading almost draws the intervention for you. If human to human still dominates the aggregate and the company is already in advanced adoption, there is a calibration gap: everyone uses the agent alone, at their own desk, but the decisions that matter keep crossing human meetings without ever entering a real agentic loop. If human to machine grows beyond reason, there is a tooling gap: the senior is burning hours re-explaining the same context that could already be encoded. Each pattern calls for a different economic remedy, which is exactly why lumping it all into one line erases the very thing you need to see. The four coordination edges (human with human, machine with machine, human with machine, and machine with human), each in cash give you the full vocabulary.

Question 3: Where Do AI Gains Leak Before Reaching the Margin?

The leak usually runs through four channels, and they repeat because the arithmetic that creates them is the same in every company. The team mix got more expensive: the base was cut and the senior was kept, so their hour in coordination weighs more. The meeting to align AI usage climbed to a fixed weekly slot on the C-level agenda. Ratification grew because agent output arrives in volume but still needs an expensive human to stamp it. And prompt calibration became a recurring senior hour, because a good prompt remains a human craft that nobody encoded.

Each of these channels eats a slice of the individual gain that AI delivered. None of them show up in the inference report. None of them show up in the compliance policy. All of them show up in consolidated payroll, only diluted, with no label of their own, too small for anyone to add up. That is the drain that the AI Multiplier paradox opens, one by one. The defensible answer is to put a number on each channel, in cash, and take it to the board in the next window. Regulatory compliance does not see this leak, because its front answers an entirely different question.

Question 4: Who Is the Named Role Responsible for Cutting Coordination Cost Each Quarter?

The question has three plausible candidates in 2026 and no settled owner in a mid-sized company. The CFO is the most natural name for the financial vocabulary, but still looks at cloud spend and payroll in separate drawers. The CTO knows the agentic edge from the inside, but does not answer for operating margin in front of the board. The COO holds the crossed operation in hand, and lacks the financial muscle to put a price on it. Three roles, one problem, and each one sees only half of it.

The most useful historical parallel is cloud spend around 2015 to 2017. Back then, engineering provisioned the resource, finance received the bill, and nobody answered for the crossing of the two. It was the discipline of FinOps that settled a shared owner and put the CFO in charge of reporting the aggregate bill to the board. The CFO took on cloud spend at the turn of the last decade; this one, takes on human-agent coordination on the same trigger: the category becomes material on the P&L and no better role is left to answer for it in cash.

Naming no one has a concrete cost. With no owner, the category gets stuck in a ping-pong between three areas, the decision of where to put capital waits, and when the board asks for the aggregate bill, there is no one to present it. The informal committee with no named role is the classic anti-pattern of 2026: it covers the regulatory front and leaves the economic one exposed.

Question 5: How Does the CFO Defend AI ROI to the Board When the Gain Vanishes in Coordination?

This is the most political of the five, because it lays bare the mismatch between who promised (the CTO, the technical leadership, selling adoption) and who gets asked for the result (the CFO, answering for margin to the board). It is the conversation that repeats most in the QBR of a mid-sized SaaS today. High adoption, individual gains everyone confirms, and an operating margin that stubbornly refused to rise in the proportion the pitch swore it would.

The defense that holds has three parts. First, name the category in full, the cost of coordinating human and machine in cash, separate from inference and from consolidated payroll. Second, bring the order of magnitude with an inventory of your own house, three to five decisions measured in 30 days. Third, put that number side by side with cloud spend and payroll, on the same sheet, to show where coordination fits and how long until it earns fine instrumentation.

The economic defense does not deny the gain from AI. It puts a number on how much of that gain leaks into coordination that nobody governs, and proposes a horizon to recover it. A CFO who arrives this way earns room to lead the conversation. One who denies the hole, or promises a magic turnaround in three quarters, loses the board in the same meeting.

Why Regulatory Compliance Answers 0 of the 5 Questions

AI regulatory compliance in 2026 aims at legal risk, and it aims well: which systems the company runs, what risk level each one falls into, the legal basis to process the data, the audit trail of the automated decision, the mandatory human review ritual. PL 2338 and the EU AI Act translate those obligations into the currency of a fine, up to €35M or 7% of global revenue in the European case. It is real law, with teeth and a deadline, and ignoring it would be irresponsible.

And none of that says how much the company spends coordinating human and machine. The two fronts have a different object, a different metric, a different owner, a different cadence. Compliance is a necessary and insufficient condition: it closes one flank and never touches the other. PL 2338 and the EU AI Act resolve the regulatory piece, and stop there. A board that asks about an operating margin hole does not accept an audit trail as the answer, because its question is about money, not conformity.

Frequently Asked Questions

The Close

The five questions are not a theory exercise. They are what the board will ask between the third and sixth quarter after AI enters at scale. Regulatory compliance answers a parallel agenda, and none of the five sit in its scope. Economic governance answers all of them, but it asks for a named role, a vocabulary of its own, and a starter inventory that holds up at the table.

Whoever prepares over the next six months reaches the following cycle with a number in currency. Whoever waits arrives with a story. The difference between the two positions is who takes on the invisible vector of AI governance over the next three years, and who outsources the explanation to whatever vendor shows up with the ready-made narrative. The dashboard that answers all five in cash is in five economic governance metrics and five anti-metrics that only make noise. The category exists, the questions are already on the agenda, and the window to answer on your own time is open now. Later, it closes from the outside.