The most common reason AI projects stall after a successful pilot is not technical failure — it’s an inability to answer one CFO question: “What’s the return?” If your answer involves phrases like “productivity gains” or “long-term strategic value,” you’re not ready for that conversation. The executives who get AI budgets approved have a specific three-number model, and it takes less than five minutes to build.
Why Most AI Business Cases Fail
There are two ways AI projects get killed in budget reviews. The first is the “vibes business case” — a deck full of McKinsey AI adoption statistics and bullet points about competitive advantage but no financial model. The second is the overengineered business case — a 40-row spreadsheet with 20 assumptions that nobody trusts and that takes three weeks to build.
What works is a focused, defensible model with three inputs, a clear output, and honest uncertainty ranges. The CFO doesn’t need a perfect forecast — they need to understand the magnitude of the opportunity and the key assumptions driving it.
A working AI ROI model has three inputs: time saved per task, number of people affected, and fully loaded cost per hour for those people. Everything else is derived.
The 3-Input ROI Model
Here is the core formula:
Annual time savings = Hours saved per person per week × People affected × 50 working weeks
Annual cost savings = Annual time savings × Fully loaded hourly cost
ROI = (Annual cost savings − Annual AI cost) ÷ Annual AI cost × 100%
Payback period = Annual AI cost ÷ Monthly cost savingsLet’s work through a concrete example. A 50-person sales team spends 4 hours per week on manual prospect research. AI automates 75% of that task, saving 3 hours per person per week. Fully loaded cost (salary plus benefits, plus employer taxes) is $80/hour.
Annual time savings: 3 hours × 50 people × 50 weeks = 7,500 hours
Annual cost savings: 7,500 × $80 = $600,000
Annual AI cost (Perplexity Pro plus a custom pipeline on GPT-4o-mini): $48,000/year
ROI: ($600,000 − $48,000) ÷ $48,000 = 1,150%
Payback period: $48,000 ÷ $46,000/month savings = 1.04 months
You don’t need to build that calculation from scratch. Plug your team size and hourly cost into our free AI ROI Calculator — it outputs annual savings, ROI percentage, and payback period in under 30 seconds.
What the Research Actually Shows
Your CFO will ask how you arrived at your time-saved estimate. “I think” is not enough. Here are defensible benchmarks from published research:
GitHub Copilot study (2023): Developers using Copilot completed coding tasks 55% faster than the control group in a controlled experiment. GitHub published this as a peer-reviewed study in collaboration with researchers. For development-heavy teams, 55% task time reduction is a legitimate benchmark.
McKinsey Global Institute (2023): Estimated that generative AI could automate 60-70% of time spent on tasks classified as “data collection and processing” and “generating reports and analyses.” For knowledge workers, the institute estimated 1.5-2.5 hours per day that could be augmented by AI tools.
Harvard Business School / BCG study (2023): Found consultants using Claude completed tasks 25% faster and produced outputs judged 40% higher quality by blind evaluators. Applied to consulting-adjacent knowledge work, a 20-30% time reduction estimate is conservative and defensible.
Rough benchmarks from NMM student cohorts: For email drafting and communication tasks, 30-45 minutes saved per person per day is typical. For research and summarization tasks, 45-90 minutes saved per person per day is consistent across cohorts.
Use these numbers to build your estimate. Pick the most conservative applicable figure, cite the source, and present a range (e.g., “We estimate 1-2 hours saved per day per affected employee, consistent with McKinsey’s estimates for data processing tasks”).
The Three Objections You’ll Face and How to Answer Them
Every AI ROI presentation faces the same three pushbacks. Prepare for them explicitly.
Objection 1: “People won’t actually use the time savings productively.”
This is the “hours saved don’t equal dollars saved” challenge. The correct answer is to reframe: time savings translate to capacity, not necessarily headcount reduction. With 7,500 hours of freed capacity, your sales team can pursue 40% more leads without adding headcount. That’s revenue upside, not just cost savings. Quantify the capacity upside in revenue terms: if each rep closes $200K/year and can now work 25% more leads, the revenue impact exceeds the direct cost savings.
Objection 2: “The model assumes 75% automation. That seems high.”
Run a sensitivity analysis in your presentation. Show the ROI at 25%, 50%, and 75% automation rates. Even at 25% automation, the annual savings in the example above are $150,000 against $48,000 in AI costs — a 212% ROI. The business case holds across a wide range of assumptions.
Objection 3: “What about implementation and change management costs?”
This is a valid point. Add implementation costs to your model: engineering time to build the pipeline (cost per hour × hours), training and onboarding time (cost per employee × hours), and ongoing maintenance (hours per month × 12 months × hourly cost). For the example above, assume 80 hours of engineering at $150/hour ($12,000), plus 2 hours of training for 50 people at $80/hour ($8,000). Total implementation: $20,000. Revised first-year ROI: ($600,000 − $48,000 − $20,000) ÷ $68,000 = 782%. Still strong.
Revenue Upside: The Second Column of Your ROI Model
Cost savings get you in the door. Revenue upside closes the deal.
Three revenue-side ROI categories that are frequently quantifiable:
Faster sales cycles: If AI-assisted research shortens your average sales cycle from 45 days to 35 days, you close 22% more deals in a year with the same team. Model this as: (deals per year × 22% × average deal value) = incremental annual revenue.
Higher conversion rates: AI-personalized outreach consistently outperforms templated sequences in A/B tests across industries. A 5-point improvement in email open rates and a 2-point improvement in reply rates at scale translates to measurable pipeline. Use your current conversion funnel metrics to calculate the value of each percentage point improvement.
Reduced churn through faster support: If AI reduces support ticket resolution time from 24 hours to 4 hours, customers have a measurably better experience. Use your NPS data and churn correlation to estimate the retention value.
Not every business case includes revenue upside — and that’s fine. A pure cost-savings model at 500%+ ROI is already a strong business case. Revenue upside is the “and here’s why it’s actually conservative” argument.
See Your AI ROI in 30 Seconds
Stop estimating in isolation. Plug your team size, hourly cost, and estimated hours saved per week into the free AI ROI Calculator. It outputs annual savings, ROI percentage, payback period, and a breakdown you can paste directly into a budget slide — all without any signup required.
Frequently asked questions
Should I use fully loaded cost or base salary in my ROI model? Always use fully loaded cost. Base salary understates the true employer cost by 25-40% once you add payroll taxes, benefits, equity, and overhead (office space, equipment, management time). A $100K base salary employee typically costs $130-145K fully loaded. Using base salary makes your ROI look worse than it is in early stages of modeling, but using it in a final presentation will get challenged immediately by any experienced CFO. Use fully loaded cost throughout.
What if the AI is augmenting work, not replacing it — can I still build an ROI model? Yes. Augmentation ROI models use quality improvement as the lever rather than time savings. If AI helps your team produce better outputs — more accurate reports, higher-converting copy, fewer customer escalations — you quantify the value of that quality improvement. For example: if AI-assisted contract review reduces legal error rates by 30% and the average legal error costs $15,000 to remediate, and you process 200 contracts per year, the risk reduction value is $900,000. Model it as risk-adjusted savings.
How do I handle cases where AI is replacing a vendor, not employee time? This is the simplest ROI case: current vendor cost minus AI tool cost. If you’re spending $80,000/year on a translation agency and can replace 80% of that volume with AI at $4,000/year, the net savings is $60,800/year. Subtract implementation costs and you have your first-year ROI. No need for complicated time-savings modeling.
What ROI threshold should I target to get budget approved? In most finance organizations, a 3-year IRR above 30% or a first-year ROI above 100% (payback under 12 months) is enough to clear the hurdle for discretionary technology investments. AI projects with well-documented ROI models routinely show 300-1,000% first-year ROI once implementation costs are included. If your model shows less than 100% first-year ROI, check whether you’re using conservative enough benefit estimates or whether the specific use case is a good fit.
How often should I update my AI ROI model after deployment? Track actual time savings versus projected savings every quarter for the first year. Run a brief survey of affected team members asking how many hours per week they’re saving with the AI tool. Compare to your projection. If you’re at 60% of projected savings, understand why (adoption issues? prompt quality? task fit?) and update the model. A model that predicted $600K and delivered $360K is still a strong result — and honest tracking builds credibility for your next budget request.
Related reading
- AI ROI Calculator — calculate your annual savings and payback period in 30 seconds
- AI Automation Saves How Many Hours? Benchmark Data by Role
- AI Cost Projection and Budgeting Framework
