Executive and board leadership · CEO AI agenda
The CFO Agenda: Value, Capital and Accountability
Fund uncertainty in forms that preserve choice, then demand finance-grade capture before commitments become hard to reverse.
TLDR
- Match funding form and evidence burden to irreversibility, consequence and capital at risk.
- Separate discovery, reusable capability, deployment, operation, risk and retirement cost accounts.
- Keep cash, capacity, loss reduction, service revenue and option value distinct to prevent double counting.
- Require a capture covenant with a counterfactual, owner, operational action and finance reconciliation before scale.
- Make continuation a forward-economic decision; historical spend cannot rescue a failing mechanism.
The pilot appears inexpensive because its model usage sits in one budget. Context preparation is in data, integration in technology, reviewer time in operations, training in the business, assurance in risk and supplier exit nowhere. The investment paper compares the visible invoice with projected labour savings. It is precise about the smallest cost and vague about the production system.
The CFO’s AI agenda is not to demand a definitive return before learning begins, or to let experimentation claim a permanent exemption from financial discipline. It is to match funding form, evidence burden and accountability to each commitment’s reversibility. Discovery buys information. Capability formation creates reusable assets. Deployment changes work. Operation consumes variable resources. Controls and incidents carry cost. Retirement releases or strands dependencies.
Value becomes finance-grade when a defined route changes an observable operational or financial account relative to a credible counterfactual, has a capture owner, survives full-cost and downside adjustment, and can be reconciled without double counting. The CFO stages uncertainty while making continuation, scale, redirection and stop decisions explicit.
Capital under uncertaintyBetween false precision and unbounded learning
Requiring near-term cash return from every experiment can kill valuable information before it is available. Giving pilots an indefinite learning label can hide weak economics. Real-options theory helps frame commitment versus flexibility, but this article does not require complex option pricing. The practical question is what decision the spend keeps open, what information it buys, when the option expires and which irreversible commitment it delays.
Discovery-driven planning similarly makes assumptions and milestones visible. Reverse the claim: what customer behaviour, operational change, full cost and risk outcome must be true for the commitment to work? A bounded pilot tests the assumptions with the highest decision value. It should not merely demonstrate technical feasibility or repeat favourable cases.
The strongest rival is decentralised operating expense. Give units modest budgets, let them move quickly and hold them to normal P&L results. This avoids a slow central process and can fit low-consequence local use. It fails when reusable capability is duplicated, shared controls are unallocated, variable consumption is opaque, dependencies concentrate or one unit’s benefit shifts cost and loss elsewhere.
The capital-to-capture system can also fail. Finance invents precision, gates become procurement queues, sponsors relabel run cost as investment, options never expire or central allocations hide marginal economics. The ledger must preserve ranges, local speed and substantive judgement rather than reward a complete-looking spreadsheet.
A finance-grade decision therefore has three clocks. The evidence clock asks when the next material uncertainty can be resolved. The commitment clock asks when spend, dependency, workforce design or market promises become difficult to reverse. The capture clock asks when an operational change should reach a financial or service account. Treating those clocks as one produces predictable errors: a short pilot is expected to prove mature cash economics, or a long supplier commitment is approved on evidence that expires before the commitment does.
The governing unit is the capability and its decision path, not the model invoice. Context preparation, controls, integration, workflow change and recovery may dominate vendor consumption. Conversely, a reusable capability can support several later decisions even when the first consumer is small. Finance should trace which assets, obligations and observations survive each gate. That makes the record useful when leadership stops, narrows, transfers or expands the work, rather than only when the original forecast succeeds.
Six cost accountsFollow the capability through its lifecycle
1Discovery option
Include problem evidence, prototypes, evaluation design, customer research and information gained. State the learning question, disconfirming test, expiry and residual artefacts. Discovery is justified by a better decision, not by the volume of experiments.
The option earns another period only when the observation is capable of changing a named decision. Record the current belief, the range of plausible outcomes and the action associated with each result before testing. This limits hindsight and makes a negative result valuable when it prevents a larger irreversible commitment. A prototype that proves only that an interface can be built has little decision value if customer need, workflow fit or loss exposure remains the binding uncertainty.
Spend range, question, evidence date, information value, expiry, owner and decision released.
2Reusable capability formation
Include context, data, platform, evaluation, controls and integration designed for several consumers. Name intended consumers and marginal onboarding cost. Shared capability cannot be charged fully to every business case or left costless in all of them.
Formation is not automatically justified because an asset might be reused. Finance should distinguish committed consumers from speculative ones, identify the services they genuinely share and preserve alternatives where requirements diverge. The record should show how much formation cost remains if only the first consumer arrives, what another consumer adds at the margin and which components retain value after a stop. This exposes both premature platform building and local duplication.
Formation range, reusable assets, consumers, allocation rule, residual value and retirement exposure.
3Deployment and change
Include workflow redesign, adoption, training, migration, dual running and role transition. A technically working service can fail economics when verification queues, incentives or customer behaviour do not change.
Separate installation from operating transition. Installation makes the capability available; transition changes who decides, who checks, how exceptions move and what old work ends. Measure the duration and cost of parallel processes, because benefits often assume immediate removal while risk plans require lengthy overlap. The accountable process owner should name the adoption boundary and the exit criterion for old steps. Without that action, forecast productivity is merely unused technical capacity.
Change range, process owner, adoption boundary, transition period, dual-run exit and capability impact.
4Recurring operation
Include inference, tools, licences, people, review, support, monitoring and exception handling. Track marginal cost of the next consumer or outcome alongside average allocation. FinOps practices can support consumption allocation and forecasting; they do not establish business value.
Unit economics must follow operational shape. A request is a weak denominator when one request resolves a case and another triggers several tools, escalations and human reviews. Segment standard and exception paths, then connect consumption to a useful outcome such as an assessed claim, served customer or completed control. Forecast step changes as volumes approach quotas, staffing thresholds or service-level constraints. A low average price can coexist with an unaffordable exception tail.
Volume driver, unit range, fixed and variable components, review burden, service level and finance owner.
5Risk and recovery
Include assurance, expected loss, incidents, remediation, contingency and insurance effects. Control and resilience are production inputs, not overhead to remove from the case. Prevented loss belongs in a risk account, not booked again as revenue or cash.
Expected-loss ranges should expose frequency, severity, changing exposure and confidence rather than compress them into one favourable amount. Add the cost of detecting failure, serving affected customers, restoring records and proving recovery. Where controls reduce throughput or require review, include that effect in the production design. The economically relevant comparison is controlled capability against the credible alternative, not controlled production against an imaginary service with no assurance burden.
Exposure, counterfactual loss, control cost, contingency, incident range, recovery evidence and risk owner.
6Dependency and retirement
Include supplier minimums, switching, data and state migration, contract termination, decommissioning and stranded commitments. A discounted current unit price may increase total option cost by hardening concentration.
Price the right to change direction. Identify which prompts, evaluations, context, workflow state and audit records can move, how long migration takes and what service interruption is tolerable. Minimum commitments should be compared with conservative consumption, not the sponsor’s scale forecast. Retirement also includes notifying users, preserving required records, revoking access and closing parallel infrastructure. These obligations turn an apparently variable service into a partly irreversible capital decision.
Minimum, concentration, trigger, exit range, portable assets, termination terms and residual value.
Five value accountsDo not add unlike routes
Cash
Observable receipts or payments that change because of the capability and capture action. A modelled saving is not cash until a budget, contract or spend path changes.
Specify the ledger account, timing and responsible action. If automation reduces forecast contractor demand, the capture event is a contract, hiring or budget decision, not the estimated hours. If improved service accelerates collection, distinguish timing benefit from permanent margin. Reconcile realised changes against demand and price movements that would have occurred without the capability.
Redeployed capacity
Time or throughput released and assigned to demand, service, control or another constrained task. Capacity without a redeployment action is an operational observation, not captured value.
Measure at the constrained workflow, not by summing task minutes across people. Released time may fragment, arrive in the wrong role or be consumed by review. Name the receiving work, the queue or service measure that changes and the manager who alters assignments. Capacity can be valuable without reducing headcount, but only when it supports a visible outcome.
Loss and risk
Credible reduction in expected or realised loss relative to a counterfactual. Keep avoided loss separate from revenue and account for control cost, selection and changing exposure.
Record exposure units and detection changes so apparent improvement is not created by serving fewer or safer cases. Use ranges when rare events make point estimates unstable. A control can be worth funding even when prevented loss never appears as income, but the decision still needs a credible mechanism, downside tolerance and periodic challenge of the baseline.
Service and revenue
New or improved customer value that changes demand, price, retention or margin. Require willingness-to-pay, adoption, capacity and cost evidence, not technical possibility alone.
Trace the route from customer behaviour to contribution after delivery, support and acquisition costs. A new advisory offer may expand access but cannibalise an existing service or require scarce expert review. Test price and adoption in context, then separate gross demand from profitable demand. Scale evidence should survive a full-cost and capacity constraint, not only a favourable demonstration.
Option and learning
Information or reusable capability that improves a later decision. State the decision, expiry and residual asset. Learning that never changes commitment is not continuing value.
Value can lie in rejecting an expensive path, negotiating better terms, narrowing a risk range or identifying reusable context. Record what became knowable, which commitment changed and when the information loses relevance. The amount at risk in the next decision bounds practical information value. Repeated discovery with no released or avoided decision is operating activity wearing an option label.
Why non-additive?
The same outcome can appear in several descriptions. Faster service may release capacity and support revenue, but the case must specify the causal route and prevent counting one change twice.
Build a bridge from operational observation to one primary finance account, then disclose secondary effects without summing them. If shorter handling time permits extra volume that generates margin, the primary route may be service revenue; the released minutes are the mechanism. If the organisation instead removes external spend, cash may be primary. One change can support several decisions, but not several copies of value.
Value captureThe capture covenant
A capture covenant states the value route, counterfactual, observation period, causal confidence, range, operational action, finance account, owner and review date. It also states the disconfirming test and stop threshold. The covenant is not a guarantee; it is the condition under which production scale remains funded.
For capacity, the action may be absorbing demand, reallocating work, reducing external spend or improving service. For risk, it may be lowering fraud loss while holding exposure and detection changes visible. For revenue, it may be launching a priced service with margin and adoption thresholds. For cash, it should reconcile to receipts, payments or budget. For learning, it should release a later decision before expiry.
Counterfactuals need care. Before-and-after comparisons can confuse the capability with process standardisation, management attention, demand or selection. Use a credible comparison, staged rollout, operational model or sensitivity range proportionate to the commitment. Causal confidence can remain a range, but finance should know which rival explanation threatens the case.
Complementary investment can delay measured productivity. The productivity J-curve research provides a reason to expect an initial period of intangible formation and organisational adjustment. It is not an excuse to roll forward weak evidence indefinitely. The ledger should show which capability asset is being formed, which consumers use it and when capture should become observable.
Set the review cadence from the evidence and exposure, not the annual budgeting calendar. Early discovery may need a short expiry because customer or technology conditions move quickly. Production value may require a longer observation window but tighter operating monitoring. A covenant can distinguish an early warning, a corrective threshold and a stop threshold. Crossing the first should trigger investigation; crossing the last should change funding unless an authorised decision records new evidence and the cost of delay.
Ownership must be joint but not blurred. The operational sponsor owns the workflow action and customer or service result. Product and technology owners carry capability performance, consumption and dependency evidence. Risk owners challenge exposure and recovery. Finance owns reconciliation, allocation integrity and the connection to capital decisions. A committee is not an owner. Each covenant field needs one accountable role and an escalation path for unresolved evidence.
Ranges should narrow for a reason. Replace an assumption with a measured distribution, contract term, observed adoption rate or tested recovery time. Do not narrow a forecast merely because a gate requires a precise number. When evidence remains weak, show sensitivity across demand, cost, loss and delay. The decision can still proceed if downside is bounded and reversible, but scale should not inherit discovery-level confidence without stating the risk.
Portfolio economicsShared cost, variable consumption and supplier commitment
Shared-platform double counting occurs when several cases claim the full enabling benefit and none carries the common cost. Maintain the capability as its own account with intended consumers, allocation rule and residual value. Consumer cases carry marginal onboarding and run cost, plus a transparent share for decision support. Allocation should aid accountability, not disguise the economics of the next use.
Variable AI consumption needs unit drivers: requests, tokens, tool calls, reviewed cases, resolved outcomes or customer journeys. Average cost can hide a costly exception tail. Marginal cost can change when capacity, rate limits or review thresholds step. Finance, product and platform teams should agree which unit follows value and which follows spend.
Supplier discounts can exchange current price for minimum spend, concentration and exit exposure. Compare the present saving with unused commitment risk, switching assets, termination terms and reduced bargaining flexibility. A vendor commitment may still be rational. The ledger should show the dependency rather than call the discount unconditional value.
Controls and resilience are part of economic design. NIST lifecycle governance and the Basel operational-resilience principles identify roles, monitoring, dependencies, response and recovery that create real cost and loss limits. Apply them within scope and proportion. Removing their cost from the investment case would compare an uncontrolled aspiration with a production capability.
Portfolio reporting should distinguish formation health from consumer value. A shared context or evaluation service can be delivered on time while consumers fail to capture value; a valuable consumer can also survive despite a weak shared platform. Show adoption, reliability, variable consumption, allocation and exit exposure at the capability level, then show the causal value route for each consumer. This prevents a successful local case from certifying every platform claim.
Allocation has two purposes that should not be confused. Stewardship allocation shows where common cost and capacity are consumed. Decision allocation helps compare the next consumer, supplier tier or feature. The first may use stable policy for planning; the second must expose avoidable and incremental cost. A business case should not reject a beneficial new use because of an arbitrary share of sunk formation cost, nor approve it by pretending shared services are free.
Commitment is a portfolio property as well as a contract field. Several small renewals can create concentration through common models, scarce skills, context formats or review processes. Aggregate minimums, correlated failure, migration demand and negotiating leverage across capabilities. Finance should ask whether the portfolio can change direction within its stated time and loss tolerance, not merely whether each purchase met its own approval threshold.
Negative controlsCases that expose accounting fiction
Capacity fiction
Task time falls but no demand, redeployment or cash action follows. Restructure the capture plan rather than count released minutes as value. Test whether the saved time is usable at the constrained step, then name the queue, assignment or budget that changes. Until that action exists, report operational potential rather than realised value.
Shared-platform double count
Five cases claim the same enabling benefit and omit common cost. Reallocate formation once and reconcile each consumer’s marginal economics. Keep the platform account independent, with named consumers and residual value, so a consumer cannot claim the whole asset while another case treats it as free infrastructure.
Exploration laundering
A pilot renews under a learning label without a disconfirming test or expiry. Stop or redesign the option before another period is funded. The next release requires a question whose answer changes commitment, a dated observation and an owner. Activity, prototypes and favourable examples do not substitute for decision value.
Vendor commitment
A lower unit price increases minimum spend, concentration and exit cost. Restructure supplier terms or scope before committing scale. Compare conservative consumption with the minimum, test portability of context and evaluations, and price termination assistance. The discount is value only after the additional obligation and lost flexibility are visible.
Risk route
Fraud loss falls relative to a credible comparison. Record prevented loss in the risk account after control cost; do not add it as cash or revenue. Hold exposure, detection and case mix visible, and preserve a range for rare-event uncertainty. Continue while the controlled service remains better than the credible alternative within appetite.
New service
AI makes an advisory service viable. Scale only with demand, margin, capacity and capture evidence under a covenant. Include expert review, customer acquisition, support and exception cost. A technically reachable customer segment becomes a finance route only when willingness-to-pay and contribution survive operational constraints.
Sunk-cost stop
A heavily funded programme fails forward economics. Historical spend does not change the continuation counterfactual; stop and recover residual value. Compare future cost and risk with future value, sale, narrowing and redeployment alternatives. Record what was learned and which assets remain usable without turning prior commitment into a claim on new capital.
Accounting boundary
Management’s preferred capitalisation is separated from investment value and routed to qualified policy and audit review. The economic route may still fund, restructure or stop the capability. It does not determine recognition, useful life, impairment, tax or disclosure, and those conclusions must not be inferred from the Console result.
Interactive instrumentCFO AI Capital and Accountability Console
The Console separates stage, costs, value evidence, capture, supplier commitment and stop logic. It returns a funding route and conditions, not one ROI or accounting conclusion.
Lifecycle cost ranges
Fund a reversible discovery option
The commitment is bounded, the learning question is priced and the evidence can change a later capital decision.
Funding condition: expiry, disconfirming test, information owner and residual artefacts are recorded before release.
The CFO operating agendaBuy learning early, demand capture before scale
Create one capital-to-capture record for each material capability, not one ROI for the portfolio. Link consumer cases to shared capability accounts. Preserve cost and value ranges, evidence dates, causal rivals and owners. Use the commitment ladder to decide what proof the next release of capital requires.
Give discovery a priced question and expiry. Give reusable capability named consumers and an allocation rule. Give production a capture covenant and finance reconciliation. Give hard supplier, workforce or market commitments a tested downside and exit case. Keep accounting policy review visible but outside the economic route.
Review forward economics. Historical spend can reveal what was learned and what residual asset remains. It cannot make a weak next period attractive. Stop, sell, narrow or redeploy when the future mechanism fails, and account for recovery rather than hiding it.
Finance discipline should improve speed by matching evidence to the decision. Small reversible learning does not need scale-grade precision. Irreversible production should not rely on pilot optimism. The CFO adds value by making the transition explicit, so capital buys information when uncertainty is high and earns capture when the organisation chooses to commit.
Run the agenda through existing planning and performance rhythms, but preserve stage-specific decisions. Monthly operating reviews can reconcile consumption and covenant signals. Quarterly portfolio reviews can challenge shared allocation, correlated dependency and capability reuse. Capital releases should cite the evidence gained since the last gate and the commitment created by the next one. This creates continuity without forcing every decision into one annual forecast.
Publish internal decision receipts that state route, range, conditions, owner, review date and accounting-review status. Receipts make exceptions legible and allow later comparison between expected and realised mechanisms. They also expose repeated optimism, unclosed pilots and benefits claimed by several sponsors. Accountability improves when the record shows why a reasonable decision was made under uncertainty, not only whether the eventual outcome was favourable.
The management view should make five questions easy to answer. What uncertainty is the next pound buying down? Which costs and dependencies become unavoidable after the next gate? Through which account will value be captured? What observation would reduce or end funding? Which reporting questions remain with qualified policy and audit specialists? If those answers cannot be reconciled from the ledger, apparent portfolio precision is not decision control.
Use post-decision review to improve the system, not to reward confident forecasts. Compare the expected mechanism, range and timing with what occurred, then identify whether the variance came from evidence, execution, demand, cost, dependency or capture. Feed those observations into later ranges and gate design. A well-governed option can end with no scaled service and still be a sound investment if it avoided a larger mistake. A favourable outcome does not excuse an uncontrolled decision path.
Capital, innovation and governance spineReferences
- McGrath, R. G. and MacMillan, I. C. (1995), “Discovery-Driven Planning”, Harvard Business Review. hbr.org/1995/07/discovery-driven-planning.
- Dixit, A. K. and Pindyck, R. S. (1994), Investment Under Uncertainty. Princeton University Press record.
- Trigeorgis, L. and Reuer, J. J. (2017), “Real Options Theory in Strategic Management”. doi.org/10.1002/smj.2593.
- Cooper, R. G. (2008), “The Stage-Gate Idea-to-Launch Process”. doi.org/10.1111/j.1540-5885.2008.00296.x.
- Hall, B. H. and Lerner, J. (2010), “The Financing of R&D and Innovation”. verified DOI record.
- Brynjolfsson, E., Rock, D. and Syverson, C. (2021), “The Productivity J-Curve”. doi.org/10.1257/mac.20180386.
- Kaplan, R. S. and Norton, D. P. (2004), Strategy Maps. HBR Press record.
- Jensen, M. C. and Meckling, W. H. (1976), “Theory of the Firm”. doi.org/10.1016/0304-405X(76)90026-X.
- NIST (2023), AI RMF Core. airc.nist.gov AI RMF Core.
- NIST (2024), Generative Artificial Intelligence Profile. doi.org/10.6028/NIST.AI.600-1.
- FinOps Foundation, FinOps Framework. finops.org/framework.
- COSO, Enterprise Risk Management: Integrating with Strategy and Performance. coso.org enterprise risk management.
- OECD (2023), G20/OECD Principles of Corporate Governance. doi.org/10.1787/ed750b30-en.
- IASB, IAS 38 Intangible Assets. ifrs.org IAS 38.
- FASB, Accounting Standards Codification. asc.fasb.org.
- Basel Committee on Banking Supervision (2021), Principles for Operational Resilience. bis.org/bcbs/publ/d516.htm.
- Power, M. (2007), Organized Uncertainty. Oxford Academic record.