The proposal arrives pre-priced
Why every AI workflow recommendation should carry its own financial case before the human reads it.
An approval gate is only as good as what arrives at it. Enterprise AI governance has spent years on the gate itself: who approves, how many sign off, what the audit log looks like. Almost no attention has gone to the proposal the human is being asked to approve. A gate fed by a proposal without financial context is a speed bump. It slows decisions without improving them.
The thesis is simple. When a system proposes a workflow, it should already know what the workflow costs to take and what it costs to skip. Those numbers should arrive with the proposal. Not in a follow-up report, not in a dashboard the reviewer has to open separately. Attached. Before any human reads the draft. A proposal without a price is not a governed proposal.
What the system already knows
The intelligence layer that generated the proposal did not guess. It read the production data: output per producer, days in ramp, headcount in training, historical performance by cohort. That reasoning produced the recommendation. The cost of inaction is not a separate calculation the system needs to go fetch. It is a byproduct of the same reasoning that produced the proposal.
If the system read 62 days as the faster ramp trajectory in a given cohort, it already has what it needs to compute the daily gap between where a producer is and where they would be on that trajectory. That gap has a price. The system is already holding the data. The only question is whether it surfaces the number as part of the output or keeps it inside the reasoning and hands the human a recommendation with no denominator.
Most systems do the latter. They generate the action. They do not price the inaction. The result is a proposal that tells the human what to do without telling the human what it costs to wait.
The two numbers a human needs
A proposal that asks for approval needs to answer two questions the approver is already asking in their head. What does it cost to take the action? What does it cost not to?
The cost of action is the effort the workflow requires: time to implement, systems involved, ramp on the change itself. The system can estimate this from the workflow specification.
The cost of inaction is harder to feel but easier to compute. It is the output foregone for each day the decision sits unanswered. For a producer in ramp, that number is not abstract. Our anchor pilot at a Fortune 500 insurance carrier put the per-person-per-day ramp constant at $54.35. Every day a producer spends in ramp beyond the faster trajectory is $54.35 of output that does not appear. The cost of deferring a decision on a ramp intervention is that number times the deferral.
The system knows both sides. It can compute them in the same pass that generates the recommendation. A proposal carrying both numbers gives the reviewer a decision to make. A proposal carrying neither asks the reviewer to feel one.
Why this changes the approval dynamic
Insurance and financial services committees approve on evidence. The language they use is: "the evidence supports this," "the cost of waiting is documented," "the trace shows how we got here." That language is not incidental. It is what accountable governance sounds like in a regulated environment.
A pre-priced proposal fits that language. The reviewer receives the recommended action, the reasoning behind it, and the financial delta between acting now and waiting. That is an evidence review. The approval is still a human judgment, but it is a judgment with inputs.
What it replaces is a trust exercise. The reviewer is not being asked to trust that the system got it right. They are being asked to evaluate whether the evidence supports the action. Those are different things, and only one of them produces governance that an auditor can inspect.
The broader governance model that makes the trace inspectable is covered in the governance model that makes the trace inspectable. The agentic properties that make a system proactive rather than reactive are covered in what agentic should mean to a buyer. This piece is about one specific part of the proposal object: the financial context that makes the approval meaningful.
What this looked like in production
In the anchor pilot, every intervention on a producer in ramp carried an implicit price before the system was instrumented to surface it explicitly. The number of ramp days the intervention was expected to recover, multiplied by $54.35, gave the intervention its value. A 47-day reduction in time-to-hire means 47 days at $54.35 per person per day no longer lost to ramp. That is not a projection. It is the arithmetic of data the system had already read.
The early approval cycles were slow. Not because reviewers disagreed with the recommendations. They deferred because "approve" is a large word for something you cannot fully evaluate. The reviewer who cannot tell whether the recommended intervention is worth the disruption of implementing it will ask for more information, or simply delay. Two days of delay on a ramp intervention costs two days of the gap it was meant to close. The deferral compounds.
When the proposal carried the financial context, the dynamic shifted. The reviewer had a specific question to answer: does the evidence support this action, given that waiting costs this amount. That is a question with a bounded answer. Approval cycles compressed because the decision had inputs, and a decision with inputs is faster to make than a judgment call that requires the reviewer to supply the inputs themselves.
The $54.35 figure and the method for calculating inaction cost across your own cohort are covered in the status quo has a price.
What breaks when the price is missing
Two failure modes. They compound each other.
The first is deferral. A proposal without financial context is a proposal asking the reviewer to supply the cost calculation before they can evaluate the action. Some reviewers do that math. Many do not, because they have other decisions to make and this one does not arrive with a clear deadline. The proposal sits. Every day it sits is a day of the gap it was designed to close. The deferral is not a failure of the workflow. It is a failure of the proposal object.
The second failure is ceremonial governance. Approvals are logged, the audit trail exists, and the governance process appears to have worked. But ask the auditor's question: what did the reviewer see when they approved this? If the answer is "a recommendation without a financial case," the approval was a formality. It logged that a human touched the proposal. It did not log that the human had adequate information to make an accountable decision. Those are different things, and regulated enterprises are increasingly expected to know the difference.
An approval process designed around the gate while ignoring the proposal is governance built for the appearance of accountability rather than the substance of it.
The architecture the mechanism requires
The agents read the context graph continuously: output per producer, cohort trajectories, system of record events. When a proposal surfaces, the pricing step has already run. The proposal object that surfaces to the reviewer carries three fields: the recommended action, the evidence behind it, and the financial delta between acting now and waiting. That is what the mechanism requires: a system designed to surface the price as a first-class field in the proposal object, not as a follow-up report that the reviewer might or might not read.
The architecture that makes this possible is the same architecture described in the canonical loop: ingest from every system of record, process, brainstorm, propose the cross-system workflow with the cost of action and cost of inaction attached. The human approves, edits, or declines. Then the system acts, and every action ships with its trail. The pricing is not a bolt-on. It is a required output of the loop.
The governance question worth asking
Every enterprise AI program will eventually face one question: when humans approved AI-generated actions, did they actually know what they were approving?
The answer to that question is not in the audit log. It is in the proposal object those humans received. A log that says "approved" does not show whether the approval was informed. Only the proposal object can show that.
The governance frontier in regulated AI is not whether a human approved. Every program has human approval. The frontier is whether the human who approved had the financial context to make an accountable decision. The proposal that arrives pre-priced is the mechanism that makes the answer yes.
Saad Bin Shafiq is the founder of Nodes. Anchor pilot: Fortune 500 insurance carrier, four years of production data, 10,765 agents. Methodology: Decision Traces.