Most AI vendors will tell you their platform delivers significant ROI. Very few can tell you how much, when, and why. This is the framework we use to put a number on a workflow before anyone builds it. The number is a capital-budgeting figure: a baseline, a cost, and a cash flow.
This framework has three phases: baseline quantification, impact modeling, and net present value calculation. Each phase builds on the last. Skip any one of them and your ROI number is a guess.
Why Most AI ROI Calculations Are Wrong
Before we get to the framework, let us diagnose why so many AI business cases fail to materialize. McKinsey's annual State of AI survey keeps finding that only a minority of organizations can attribute a meaningful share of EBIT to AI. The root causes are predictable:
- Costs are underestimated. Integration, data preparation, change management, and ongoing maintenance rarely appear in vendor ROI projections.
- Benefits are overstated. Automation rarely eliminates 100% of a role's cost — it changes the mix of work and requires human oversight.
- Time to value is unrealistic. A platform that delivers ROI "in 90 days" typically assumes clean data, fast approvals, and cooperative stakeholders — conditions that rarely exist.
- Soft benefits are substituted for hard ones. "Improved employee satisfaction" and "better decision-making" are real, but they are not cash flows.
Our framework addresses all four failure modes by anchoring every assumption in observable, verifiable data from your current operations.
Phase 1: Baseline Quantification
You cannot measure improvement without a baseline. The goal of Phase 1 is to produce a fully-loaded cost figure for every process you are considering automating.
Step 1: Map the Process
Create a process map that captures every step, every handoff, and every decision point. For each step, record: who performs it (role, not name), how long it takes on average, how often it occurs (daily, weekly, per transaction), and the error rate.
This sounds basic, but most organizations have never done it rigorously. Asked to estimate, process owners anchor on the best case, so the estimate runs low. Use time-tracking data, system logs, or structured observation instead.
Step 2: Calculate Fully-Loaded Labor Cost
For each role involved in the process, calculate the fully-loaded hourly cost: salary + benefits + overhead + management allocation. As a rule of thumb, fully-loaded cost is 1.25–1.4× base salary for most white-collar roles.
Multiply hourly cost × hours per occurrence × annual volume. This gives you the annual labor cost for that process step.
Step 3: Add Non-Labor Costs
Labor is rarely the only cost. Add: error and rework costs (hours spent correcting mistakes × frequency × fully-loaded rate), delay costs (late payments, missed SLAs, customer churn attributable to slow processes), compliance costs (audit preparation, regulatory reporting, remediation of violations), and technology costs (current systems that would be displaced).
Step 4: Document the Baseline
Produce a one-page baseline document per process: total annual cost, unit cost per transaction, error rate, cycle time, and headcount directly attributed. This document becomes your measurement benchmark.
Phase 2: Impact Modeling
Phase 2 translates your baseline into a projection of post-automation costs and benefits. The key discipline here is conservative realism — not pessimism, not optimism.
Step 5: Define the Automation Scope
Not every step in a process is automatable. Classify each step as: fully automatable (AI handles end-to-end with minimal exception), partially automatable (AI handles routine cases, humans handle exceptions), human-required (judgment, relationship, or regulatory requirements preclude automation).
In back-office work, a large share of steps often falls in the first two categories, though your own map is the only count that matters. The steps that need a person often still get faster and less error-prone when AI prepares the context around them.
Step 6: Apply Conservative Reduction Rates
For each automatable step, apply a cost-reduction percentage. Start with a conservative figure, and replace it with a measured one as soon as a pilot runs on your data. A vendor case study is not a source. The methodology target AIPIVT plans against is 60–80% lower cost on a high-volume workflow, measured against the Phase 1 baseline. That is a target, not an AIPIVT client result. Within one workflow, the step types differ:
- Data entry and document processing: usually the top of that range, when the inputs are consistent.
- Workflow routing and approval: the middle of the range.
- Analysis and exception handling: well below it, because a person stays in the loop.
- Report generation: near the top, when the source data is already structured.
Apply the figure for each step to its Phase 1 cost to get a post-automation estimate.
Step 7: Model Revenue Impact Separately
If automation frees capacity that can be redeployed to revenue-generating work, model this as a separate line item — not a cost saving. Use your actual sales productivity data: revenue per sales hour, conversion rates, customer lifetime value. Revenue impact is the hardest component to quantify in advance, so keep it out of the payback calculation until the freed capacity has a named use.
Step 8: Build the Cost Side
Now model the full cost of the AI implementation: software licensing or API costs, implementation services (internal and external), data preparation and integration, change management and training, ongoing maintenance and model retraining, and a contingency buffer (we recommend 20% of total estimated cost for first-time implementations).
Map these costs across a monthly timeline from kickoff to full production. The ramp profile matters. AIPIVT structures first measurable impact for 4–8 weeks after kickoff, calibrated to the baseline in assessment, with full benefit some months after that. That is a methodology target, not a promise. Model the ramp from your own plan.
Phase 3: Net Present Value Calculation
Step 9: Build the Cash Flow Model
Assemble a monthly cash flow model for a 36-month horizon. On the cost side: implementation costs in months 1–6 (typically front-loaded), ongoing licensing and maintenance from month 1. On the benefit side: ramp from 0% in month 1 to 100% by month 6–9, then sustained benefit through month 36.
Your net cash flow each month is benefit minus cost. Cumulative net cash flow shows you the payback period — the month when total benefits exceed total costs. A workflow worth starting pays back well inside the horizon. Step 11 tests that at 24 months.
Step 10: Apply a Discount Rate
Discount your cash flows at your company's weighted average cost of capital (WACC). For most mid-market companies, this is 8–12%. Calculate NPV over 36 months. A positive NPV confirms the investment creates value even accounting for the time value of money.
Step 11: Sensitivity Analysis
Run three scenarios: base case (your central estimates), conservative case (20% lower benefits, 20% higher costs, 3-month delay), and optimistic case (20% higher benefits, costs on plan). If the conservative case still shows a positive NPV within 24 months, the investment is robust. If only the optimistic case produces positive NPV, proceed with caution.
Putting It Together: A Worked Example
Consider a hypothetical 300-person financial services firm with a manual accounts payable process. Phase 1 baseline: 2.5 FTEs dedicated to AP, fully-loaded cost $180,000/year, a 4% error rate costing $12,000 a year in rework, $12,000 in late payment penalties annually. Total baseline cost: $204,000/year.
Phase 2 impact model: AP automation reduces the 2.5 FTEs to 0.5 (exception handling only), saving $144,000/year in labor. Error rate drops to 0.3%, eliminating $9,000 in rework and $10,000 in penalties. Total annual benefit: $163,000.
Phase 2 costs: $45,000 implementation, $24,000/year licensing and support. Phase 3 NPV at 10% WACC, 36 months: $287,000 positive. Payback: 11 months. This is a straightforward, fundable business case. The figures are illustrative. They are not from a client engagement.
Common Traps to Avoid
Do not count the same benefit twice. If you project headcount reduction, do not also count freed capacity as revenue upside — choose one. Do not assume immediate ramp. Model the first months well below steady state. Do not ignore change management costs. If the people who run the workflow do not use the system, the benefit line never arrives.
And finally: do not accept a vendor's ROI model at face value. Ask them to walk you through every assumption with your data, in your system, with your headcount costs. Any vendor unwilling to do this is selling you a story, not a business case.
Getting Started
The hardest part of this framework is Phase 1 — the baseline. Most organizations have the data somewhere (time-tracking systems, ERP transaction logs, email volumes, headcount reports) but have never assembled it into a process-level cost view. That gap is exactly where we start every engagement.
Phase 1 fits on one page. The process cost worksheet is that page: twelve lines, free, PDF.
If you want to run this framework against one specific process, book a 30-minute scoping call. We use it to name the workflow and to decide whether you can grant access to the process and the data to set a baseline. Without that access there is no engagement.
Source: McKinsey, "The State of AI," annual global survey.