Framework · free to use

How to measure AI ROI honestly.

Most AI ROI calculations are theater. They count hours saved per task without netting against the costs (license, training, internal time, output review) — and then compound speculative annual savings into a number that looks great on a slide and means nothing. This is a more honest methodology.

By Bill Colbert · Founder, Treetop Growth Strategy
Published May 2026 · More from the library
The framework

Net benefit, not gross savings

ROI = (Net benefit / Total cost) over a defined period. "Net benefit" means realized value after accounting for the cost of using the tool — not the gross time "saved."

Period matters. For AI tooling, the right frame is usually 12-month rolling, with a separate first-90-days view that often shows negative ROI (which is fine — you are buying the foundation).

Cost categories

What to include — all of it

CategoryOften missed?Example
Direct license / platformNoClaude Team \$30/seat/month
ImplementationSometimesTreetop engagement, internal build hours, vendor onboarding
TrainingOftenOnboarding sessions, training material, time spent learning
Internal adminAlmost alwaysAI lead time, weekly office hours, prompt library maintenance
Review & QAAlmost alwaysHuman-review time for AI outputs, error-correction time
Tool sprawlOftenWhen AI tool # 4 duplicates something tool # 2 already did
Opportunity costSometimesWhat the AI lead could have been doing instead

The two most-missed cost categories are internal admin time and human review time. Both are real costs that should be in the denominator. Excluding them produces fake ROI numbers that fall apart on second review.

Benefit categories

What counts as realized value

1. Time recovered, validated

Hours saved per task × tasks per period × load-cost-per-hour. Only count hours that visibly translate into either more output or actual time off. Saving the CEO 2 hrs/week that just gets absorbed back into more email does not count as ROI.

2. Cycle time compression that closes more deals

If shorter quote turnaround = higher win rate, the additional deals are real ROI. Track it as: incremental deals attributable to faster cycle × average deal contribution margin.

3. Throughput gains

More content shipped, more proposals sent, more tickets resolved per FTE. Count the additional output only if it produced incremental revenue or eliminated a hiring need.

4. Avoided hires

If the AI rollout means you do not hire the next coordinator/analyst/SDR, that is real value. Use loaded cost of the avoided hire, time-weighted to when the hire would have happened.

5. Quality improvements that reduce rework

Real, but rare in measurable form at <$50M scale. Skip unless you have hard data.

Common ROI mistakes

Where the math goes wrong

A worked example

Realistic numbers from a real-shaped engagement

Setup

20-person B2B services firm. 6-month period. Three workflows rolled out: proposal drafting, content production, and meeting summarization.

Costs (6 months)

Benefits (6 months)

Net ROI

Net benefit: \$84,960 / Costs: \$49,800 = ~170% return over 6 months. Annualized (cautiously, since the first 90 days are atypical) closer to 250-300%.

Related

Related frameworks & reading

Want a roadmap built for your business?
The $1,500 AI Audit produces a written, prioritized roadmap in 5 business days.
Book the AI Audit → Take the Gap Assessment