The pitch died in the first ninety seconds. The strategy lead opened the board deck with a slide that read "AI delivers 30% productivity gains," and the managing partner, who has sat through forty years of vendor demos and three failed software rollouts, leaned back and asked the only question that matters: "Thirty percent of what, costing us how much, paying back when, and what happens if it does not?" There was no slide for that. The deck had a productivity percentage where it needed a number ownership could underwrite, and a $1.2M ask collapsed into "come back when you have run the numbers." This lesson is about running the numbers the way ownership runs them. By the end you will be able to translate an AI initiative into the financial language a board funds: total cost of ownership, return on investment, payback period, risk-adjusted return, and scenario analysis with an honest downside, assembled into a $1.2M investment case with a 36-month projection that survives the partner's question instead of dying to it.

Why the Productivity Percentage Always Dies

Ownership does not buy productivity percentages because a percentage is not a commitment, it is a hope wearing a number. "30% faster takeoffs" tells the board nothing they can underwrite: faster than what baseline, on which of the firm's work, captured by whom, and converted into what dollars that show up in the financial statements. A productivity gain that does not convert into lower cost or higher throughput on constrained capacity is, to the people who read the P&L, a gain that does not exist. The board has watched software vendors promise percentages for three decades and learned that the percentage is the easy part and the conversion is where deployments die. So when you lead with the percentage, you signal that you have not done the hard part, and the partner's question is not hostility, it is the correct test.

The deeper reason the percentage dies is that it answers the wrong question. Ownership is not asking "is this technology impressive," they are asking "is this the best use of $1.2M of firm capital, compared to the other things we could do with it," which include hiring, acquiring a competitor, buying equipment, distributing to partners, or holding cash against a softening market. An AI investment competes for capital against every other use, and the only way to win is to express it in the same units as the alternatives: a cost, a return, a timeline, and a risk. The percentage is in different units, so it cannot be compared, so it is excluded from the decision. This is the controlling discipline of the lesson, the same as the ROI memo from the use-case prioritization work, scaled up to the level where ownership signs the check.

The translation is not dishonest dressing-up; it is the opposite. Converting a productivity claim into a financial case forces you to confront whether the gain is real, whether it converts to dollars, and what it costs to capture, the discipline that separates a substantiated case from hype. The firms that win board funding are not the ones with the most impressive demo; they are the ones who walked in having already asked themselves the partner's question and built the answer into the case. The percentage dies because it skips that work; the financial case survives because it does it.

Total Cost of Ownership: The Number Behind the Sticker

The first financial concept ownership expects you to have mastered is total cost of ownership (TCO), because the number a vendor quotes is almost never the number the firm spends. The sticker price is the per-seat license or platform subscription, but the real cost of owning an AI capability over a 36-month horizon includes a stack the sticker hides: implementation and integration with the firm's existing systems (the estimating database, the project management platform, the document control system), data preparation and migration, configuration to the firm's workflows, training for the people who will use it, the internal time of the champions and administrators who keep it running, ongoing support and version upgrades, and the verification overhead every AI deployment in this program carries, because a deployment that produces outputs nobody verifies is not a capability, it is a liability.

A useful way to present TCO to a board is to separate it into three buckets they already think in: acquisition cost (licenses, subscriptions, the contracted vendor spend), implementation cost (integration, data work, configuration, initial training, the one-time lift to get from purchase to productive use), and operating cost (ongoing support, upgrades, the internal labor to administer and verify, the recurring spend to keep the capability alive over the horizon). For a $1.2M case, ownership will expect the sticker to be a minority of the total. If your $1.2M is all license and no implementation or operating cost, the board will not believe it, because they have lived through the rollout that cost three times the license to deploy. Naming the full TCO, including the unglamorous internal labor, is what makes the number credible.

The analogy that lands with builders is the one they live every day: TCO is the loaded cost of a piece of equipment, not the purchase price. Nobody who has run a fleet confuses the price of a crane with the cost of owning one, because the cost is the purchase plus financing plus operator plus fuel plus maintenance plus insurance plus downtime, over the life of the asset. An AI capability is the same: the license is the purchase price, the TCO is the loaded cost of owning it over the horizon. Present the AI investment as a loaded cost and ownership recognizes the shape of the number immediately, because it is the shape of every capital decision they have ever made.

ROI, Payback, and the Return Language

Once TCO establishes the cost side, ownership wants the return side in two forms, the two questions a board asks of any investment: how much do we get back, and how soon. Return on investment (ROI) answers the first as the ratio of net benefit to cost over the horizon: if the 36-month investment costs $1.2M in TCO and produces $2.4M in benefit, the net benefit is $1.2M and the ROI is roughly 100% over the period. Payback period answers the second as the time until cumulative benefit equals cumulative cost: the month the firm has earned back what it spent and crosses into net positive. A board funds on both because a high ROI with a five-year payback is a different risk than a modest ROI that pays back in fourteen months, and ownership cares about the timeline because capital tied up for years cannot respond to a market that may turn.

The benefit side is where substantiation matters most and where most cases cheat. The benefit must be traceable to a mechanism ownership can audit: labor hours redeployed from low-value to billable or capacity-constrained work, cycle time reduced on a process that gates revenue, error or rework cost avoided, claims recovered that would have been under-recovered, or margin protected on work that would otherwise have leaked. Each is a dollar number with a chain of reasoning behind it, and the chain must be visible. "We will save 10,000 hours" is not a benefit; "we will redeploy 10,000 hours from manual takeoff to estimating capacity, which at our current win rate and average project margin converts to $X of additional captured margin" is, because the board can interrogate every link. If a benefit cannot be traced to a mechanism and a dollar, it does not belong in the ROI, no matter how real it feels.

The honest version of this discipline is to be conservative on the benefit and complete on the cost, the inverse of how vendors pitch and exactly why it earns trust. A board that has been burned learns to mentally halve any benefit a vendor claims and double any cost, so the case that has already done that halving and doubling and still shows a return is the one that survives scrutiny. Underclaim the benefit, overclaim the cost, and let the case win anyway: that is the posture of a strategist ownership funds, because it signals you are managing their capital the way they would, not selling them a percentage.

Ownership does not fund the most impressive technology; they fund the most credible number. A productivity percentage is a hope; a risk-adjusted return with an honest downside is a commitment, and only the second one survives the partner's question.

Risk-Adjusted Return: Because AI Deployments Fail

Here is the fact a credible case states out loud: AI deployments fail at a meaningful rate. They fail because the data was dirtier than expected, the integration with the legacy system stalled, adoption never reached the threshold where the benefit materializes, the verification overhead ate the time savings, or the vendor's roadmap diverged from the firm's needs. A board knows this, and a case that presents a single confident return as if failure were not possible tells ownership the strategist either does not understand the risk or is hiding it, both disqualifying. The mature move is to risk-adjust the return: discount the projected benefit by the probability that it does not fully materialize, and present the risk-adjusted number as the honest expected value.

Risk-adjustment is not pessimism, it is arithmetic that ownership respects. If the unadjusted case shows $2.4M of benefit but you assess a real probability that adoption underperforms or integration slips, you present an expected benefit that weights the upside by its likelihood, and you name the specific risks that drive the discount: data readiness, integration complexity, adoption dependency, vendor concentration, and verification load. Naming the risks is half the value, because it converts abstract fear into a managed list, and a board funds managed risk far more readily than unacknowledged risk. The risk-adjusted return is lower than the headline return, and that is the point: it is the number you can stand behind when the partner asks what happens if it does not go to plan.

This is the same discipline as the verification gates that run through the entire program, applied to capital instead of deliverables. Just as the firm does not stamp, schedule, or pay against an unverified AI output, ownership does not fund against an unverified return, and risk-adjustment is the verification gate for the dollars at the investment level. A case becomes verifiable when its return is adjusted for the probability of the failure modes it candidly names. The strategist who brings the risk-adjusted number, with the risks listed and a mitigation for each, is bringing ownership a decision they can make rather than a bet they must take on faith.

Scenario Analysis and the Mandatory Downside

Risk-adjustment compresses the uncertainty into a single expected number, but ownership also wants to see the range, which is what scenario analysis provides. The standard structure is three scenarios: a base case (the most likely outcome, the one the risk-adjusted return centers on), an upside case (adoption is strong, integration is clean, the benefit lands at or above plan), and a downside case (adoption lags, integration slips, the benefit underperforms and the cost overruns). Each scenario gets its own TCO, benefit, ROI, and payback, so the board sees not a point estimate but a distribution: here is what we expect, here is what good looks like, and here is what bad looks like and whether we survive it.

The downside case cannot be optional, because it is the scenario the board is actually testing for. A case with only a base and an upside is a sales pitch; a case with a credible downside is an investment proposal. The downside answers the partner's real fear: if this underperforms, how much do we lose, how soon do we know, and can we stop the bleeding. A strong downside names the kill switch: the decision point at which, if the leading indicators are not met, the firm stops, contains the loss, and redeploys the capital. A $1.2M investment with a defined downside of, say, a contained loss the firm can absorb and a kill switch at month nine if adoption metrics miss, is a far easier yes than a $1.2M bet with an unbounded downside, even if the base case returns are identical, because ownership is funding the bounded loss, not the headline gain.

Scenario analysis is the briefing discipline applied to capital: you are not asking the board to trust your optimism, you are giving them the full picture and letting them make the call with their eyes open. By presenting the downside yourself, before they ask, you demonstrate that you have already stress-tested the case and are not hiding the part that could hurt. The board that sees you name your own downside trusts your base case more, not less, because they know you are not selling them the percentage. The downside is not a weakness; it is the proof that the case is honest.

Assembling the $1.2M Investment Case

The pieces now assemble into a single document ownership can decide on. The case opens with the strategic frame (what capability, tied to which firm priority, why now), then the TCO over 36 months broken into acquisition, implementation, and operating buckets, the benefit traced to its mechanisms and dollars, the ROI and payback for the base case, the risk-adjusted return with the named risks and mitigations, the three scenarios with the downside and kill switch made explicit, and it closes with the ask and the decision the board is being asked to make. The whole thing is in the units ownership thinks in, so it can be compared against the firm's other uses of capital and decided rather than admired.

The 36-month horizon is chosen deliberately: long enough to capture the implementation lift in the early months and the steady-state benefit in the later ones, short enough that the board is not asked to believe a five-year prophecy. A 36-month projection shows the J-curve every real deployment follows: cost-heavy and benefit-light in the first quarters as the firm implements and adopts, crossing into net positive at the payback month, accumulating return through the back half. Showing the J-curve rather than a flat average tells ownership you understand that the return is not instant and the early months are an investment, not a failure, which preempts the panic when the month-four numbers look bad on plan.

One discipline ties the whole case together: every number must be defensible to the partner's question, which means every number carries its source and reasoning. The TCO carries the vendor quote, the integration estimate, and the internal labor assumption; the benefit carries the mechanism and the conversion math; the risk-adjustment carries the probability assessment and rationale; the scenarios carry the assumptions that distinguish them. A case where the strategist can answer "where does that number come from" for every line is a case the board funds, because it is one they can verify. The investment case is not a persuasion document, it is a verifiable financial argument, which is precisely why it survives the room the productivity percentage died in.

The Applied Problem: Present a $1.2M AI Investment Case with a 36-Month Projection

Here is the exercise. Build the investment case for a $1.2M AI deployment at your firm and present it to ownership in the financial language they fund in, structured around a 36-month projection. Pick a real candidate capability from the firm's priorities, then construct the full case: the total cost of ownership over 36 months, broken into acquisition, implementation, and operating buckets, with the internal labor and verification overhead named rather than hidden; the benefit, traced to specific mechanisms (redeployed labor, reduced cycle time, recovered claims, protected margin) and converted to dollars with the conversion math visible; and the base-case ROI and payback period derived from the two.

Then do the part that makes it credible rather than a pitch. Compute the risk-adjusted return by discounting the benefit for the probability it does not fully materialize, and name the specific risks that drive the discount (data readiness, integration complexity, adoption dependency, vendor concentration, verification load) with a mitigation for each. Build the three scenarios, each with its own TCO, benefit, ROI, and payback: a base case, an upside case, and a downside case that names how much the firm loses if it underperforms, how soon the leading indicators reveal it, and the kill switch, the decision point at which the firm stops and contains the loss. Plot the 36-month J-curve so ownership sees the cost-heavy early months, the payback month, and the accumulating return.

The deliverable is the assembled investment case: a strategic frame, the TCO, the traced benefit, the base-case ROI and payback, the risk-adjusted return with named risks and mitigations, the three scenarios with an explicit downside and kill switch, and the 36-month projection, closing with the ask. The lasting product is a case that survives the partner's question, because every number carries its source and reasoning, the benefit is conservative and the cost complete, the downside is named before the board asks, and the whole thing is expressed in the units ownership uses to allocate capital. The strategist who masters this does not lead with a productivity percentage that dies in ninety seconds; they lead with a risk-adjusted return and an honest downside the board can underwrite, the only form in which a $1.2M AI ask becomes a $1.2M AI investment.

Key Takeaways

• A productivity percentage dies in the boardroom because it is not in the units ownership funds in: it cannot be compared against the firm's other uses of $1.2M, so it is excluded from the decision. The translation into a financial case is not dressing-up, it is the discipline that confronts whether the gain is real, converts to dollars, and is worth its cost.
• Total cost of ownership is the loaded cost of owning the capability over the horizon, not the vendor sticker: acquisition plus implementation (integration, data work, configuration, training) plus operating (support, upgrades, internal admin and verification labor). If the $1.2M is all license, the board will not believe it, because they have lived the rollout that cost triple the sticker to deploy.
• ROI answers how much the firm gets back and payback period answers how soon, and ownership funds on both because a long payback ties up capital a turning market may need. The benefit must be traced to an auditable mechanism and a dollar, with every link visible, or it does not belong in the ROI.
• The honest posture is to underclaim the benefit and overclaim the cost and let the case win anyway, which is the inverse of a vendor pitch and exactly why it earns trust from a board that mentally halves benefits and doubles costs by reflex.
• Risk-adjusted return discounts the projected benefit by the probability it does not fully materialize, because AI deployments fail at a meaningful rate (data, integration, adoption, vendor, verification load). Naming the risks converts abstract fear into managed risk, which a board funds far more readily than unacknowledged risk; this is the verification gate applied to capital.
• Scenario analysis shows the range with a base, an upside, and a mandatory downside case, each with its own TCO, ROI, and payback. The downside is what the board is actually testing for, and a strong one names the loss, the leading indicators, and the kill switch: the point at which the firm stops and contains the loss.
• Presenting your own downside before the board asks earns credibility for the base case, because it proves the case is stress-tested and honest rather than a sale; the board that sees you name your downside trusts your upside more.
• The assembled case is a verifiable financial argument, not a persuasion document: a strategic frame, TCO, traced benefit, ROI and payback, risk-adjusted return with mitigations, three scenarios with a kill switch, and a 36-month J-curve, every number carrying its source. That is the form in which a $1.2M AI ask becomes a $1.2M AI investment.