What makes an AI workflow worth building?
A useful ROI estimate connects a specific process improvement to a business result, then compares that benefit with the full cost of achieving it. Start with the work your people do today. The technology comes after the economics.
When someone tells me Claude can save a team hundreds of hours, my next question is simple: what will those hours make possible? Less overtime? More work delivered by the same team? A hire you no longer need? Those are different outcomes, and they belong in different parts of the calculation.
You do not need a complicated financial model to get started. You need a clear baseline, honest assumptions and someone responsible for checking the result.
1. Describe the current process
Choose one repeatable piece of work, such as preparing a proposal, checking an invoice or assembling a weekly report. Write down what starts it, who handles it, where the information comes from and what a finished result looks like.
Include the work people tend to leave out: finding missing information, fixing errors, reviewing drafts and moving the result into another system. Ask the people doing the work to walk through a recent example. A process diagram is helpful only if it matches their day.
2. Measure volume and cost today
Count how often the process happens and time a representative sample. Separate routine cases from exceptions. Use a realistic number of working weeks, and check whether volume changes through the year.
For a capacity estimate, multiply time by an agreed fully loaded hourly employee cost. That gives you a way to value time, not evidence that payroll will fall. Track actual outside spending, overtime and rework separately so you can see which costs might really change.
3. Estimate the improvement, including review
Compare the current process with a small pilot. The new time should include preparing inputs, checking Claude’s output, correcting mistakes and handling exceptions. A draft produced in seconds may still need meaningful human review.
A fictional proposal workflow
Suppose a team prepares 12 proposals each week. Each takes two hours today. A tested workflow could bring the total to one hour, including review.
12 proposals × 1 hour freed × 48 weeks = 576 hours of annual capacity.
At an agreed fully loaded cost of $60 per hour, that is $34,560 in potential annual capacity value. It is not $34,560 in automatic cash savings, and it is not a build-price quote.
If only half of the proposals can use the workflow during rollout, reduce the estimate accordingly. If adoption starts in month four, count the months it is actually in use. Model a conservative case as well as the expected case.
4. Connect capacity to a 12-month economic outcome
Decide what happens to the time. If it allows the team to deliver additional paid work, estimate the incremental contribution after the costs of delivering that work. If it avoids a planned hire, document the role, timing and cost that will actually be avoided. If the same people simply finish earlier, describe the result as capacity.
Do not add the wage value of freed hours to all the revenue those same hours produce. That can count the same benefit twice. Likewise, collecting an existing invoice sooner improves cash timing; the invoice amount is not new revenue.
Use a simple benefit register: outcome, calculation, evidence, owner and overlap with other outcomes. Our guide to time savings and real ROI explains these distinctions in more detail.
5. Include every cost required to get the result
Your first-year cost includes the fixed build fee, monthly management, Claude subscriptions, other software, API usage and required internal time for setup, training, review and ownership. Use incremental costs for an investment decision and show any shared-cost allocation clearly.
Managed Claude starts at $1,500/month. That is at least $18,000 over a full year before implementation, software, API charges and internal costs. If management supports several workflows, allocate it reasonably across them and also assess the total portfolio. Do not make each project look profitable by leaving shared costs out of all of them.
12-month ROI = (12-month economic benefit − total 12-month cost) ÷ total 12-month cost × 100. Keep a cash-based view separate from a capacity-based view. A positive capacity estimate alone does not establish positive cash ROI.
6. Agree on value, then decide what to build
Build hours describe the supplier’s effort. They do not tell you how valuable the result is to your business. A small workflow used every day can matter more than a complicated tool used twice a year.
Together, we estimate the solution’s expected 12-month economic value and agree on a percentage that makes sense for your business. That sets a fixed build price before work begins.
Set the measurement plan before launch: baseline, target, owner and review date. Then compare actual usage, time, quality and cost with the estimate. If the expected benefit is too uncertain or too small, narrow the scope or choose another process.
A free AI Value Assessment starts with one team, such as sales or finance. We help turn the work your people describe into opportunities you can evaluate.
Frequently asked questions
What is the formula for AI workflow ROI?
Subtract total 12-month cost from the economic benefit expected over the same period, then divide by total cost and multiply by 100. Identify whether the benefit is cash savings, avoided cost, incremental contribution or capacity, and do not count overlapping benefits twice.
Does time saved count as cash savings?
Only if a cash expense actually falls. Otherwise, time freed is capacity. Explain how that capacity will be used and measure the resulting outcome separately.
Which costs belong in the calculation?
Include implementation, monthly management, software subscriptions, API usage and required internal setup, training, review and ownership costs. Account for rollout timing and shared costs consistently.