How to calculate the real ROI of a sales AI tool before you buy it

The formula for calculating ROI on a sales AI tool is not complicated. It equals (time saved multiplied by loaded cost per hour, plus pipeline or revenue lift if genuinely attributable) minus total cost of ownership, all divided by total cost of ownership. Total cost of ownership includes the license fee, implementation time, and ongoing maintenance, not just the pricing page number.

Most vendor ROI calculators often omit significant parts of this formula. They typically highlight hours saved multiplied by a generic hourly rate, while downplaying the denominator by excluding implementation costs, maintenance, or the risk of non-adoption. This approach presents a sales aid rather than a true financial calculation.

Here is how to build a real ROI calculation.

The formula, in plain terms

Start by identifying the actual time savings provided by the tool. For example, if an AI tool reduces manual research time from four hours to one hour per rep per week, that is three hours saved weekly per rep. Multiply these saved hours by your loaded cost per hour, which includes payroll tax, benefits, and overhead, not just base salary.

A common method for calculating loaded hourly rate is OTE multiplied by 1.25, then divided by 2,000 working hours per year. For a rep with an illustrative OTE of $120,000, the loaded rate would be $75 an hour ($120,000 x 1.25 / 2,000). Saving three hours a week over 46 working weeks (accounting for PTO, holidays, and training) amounts to 138 hours annually. This is worth $10,350 per rep at the $75 rate. For a team of 10 reps, this represents $103,500 in annual time value.

This represents the easier part of the calculation.

A full worked example, step by step

To illustrate the complete formula, let us consider a hypothetical scenario for a 10-rep team. All numbers used are placeholders and not reflective of actual client data.

Assume an AI research assistant reduces pre-call preparation from four hours to one hour per rep per week, using the $75 loaded hourly rate previously calculated. As established, this translates to $103,500 in annual time value across 10 reps.

Now, let us calculate the denominator, total cost of ownership:

• License cost: A placeholder of $12,000 per year for 10 seats.
• Implementation: Two weeks of a RevOps lead’s time, approximately 60 hours at a loaded rate of $90 per hour, totaling $5,400. This covers connecting the tool to the CRM and configuration.
• Ongoing maintenance: An estimated two hours per month to maintain data currency and address integration issues, costing $2,160 annually at the same RevOps rate.

The total cost of ownership is $12,000 + $5,400 + $2,160 = $19,560.

The net benefit is $103,500 minus $19,560, which is $83,940. The ROI, calculated as net benefit divided by total cost of ownership, is approximately 4.3x, or 430 percent, in year one, before considering any adoption risks.

A conservative ROI number that survives scrutiny is worth more than an inflated one that falls apart the first time someone in finance asks how you calculated it.

Next, apply an adoption-risk discount. If historical data suggests only 70 percent of reps will consistently use the tool by month six, multiply the time-saved benefit by 0.7. This adjustment reduces the benefit to roughly $72,450, the net benefit to $52,890, and the ROI to about 2.7x. This provides a more realistic figure than an uncapped estimate and is an adjustment vendor calculators typically do not include.

Why revenue attribution is the hard, honest half

The second component of the formula, pipeline or revenue lift, is often where ROI claims become problematic. It is tempting to claim the tool will increase close rates by a certain percentage to inflate the ROI. Avoid this unless you can directly link the lift to the tool, isolating it from other pipeline changes like new reps, seasonality, pricing adjustments, or competitor issues.

If direct isolation is not possible, either exclude revenue lift from your calculation or clearly label it as directional and unverified.

What vendor calculators leave out

The denominator, total cost of ownership, is where a truly honest assessment takes place. Vendor calculators almost always omit three key elements:

• Implementation time: Setting up the tool, connecting it to your CRM, and configuring it for your workflow requires real hours from your team or a paid consultant. These hours have a loaded cost.
• Ongoing maintenance: Prompts can drift, integrations may break with CRM updates, and someone must be responsible for keeping the tool accurate. Budget for this as an ongoing expense, not a one-time cost.
• Adoption failure risk: Not all pilot programs succeed. If there is a 40 percent chance the tool will not achieve full usage in your organization (based on your team’s history with new tools), your expected ROI should reflect this risk, rather than assuming 100 percent adoption from day one.

By combining license cost, implementation cost, and an estimate for ongoing maintenance, you arrive at a realistic total cost of ownership. Dividing the net benefit by this number yields a genuine ROI, not a marketing figure.

Build a 3-month and a 12-month view

Year-one ROI can obscure the ramp-up period. A tool that appears break-even at 12 months might actually be unprofitable for the first quarter while your team learns it and integrations are finalized. It could then become strongly positive from months four through twelve.

Calculate both a 3-month and a 12-month view. The 3-month view helps manage early expectations with leadership, especially if quick progress is required. The 12-month view assesses the tool’s long-term value after the initial ramp-up. A tool that does not become profitable by month six presents a different decision than one that breaks even by month three and continues to improve.

When good ROI still isn’t a reason to buy

Even if a tool shows a positive ROI on paper, it might still be the wrong choice in certain situations:

• Opportunity cost: If your team is already engaged in a CRM migration or stack consolidation, adding a new tool competes for limited attention and change-management resources. A positive ROI does not account for alternative uses of your team’s time.
• Organizational readiness: If the workflow the tool addresses is not documented, or the data it relies on is inconsistent, the ROI calculation is based on unfulfilled assumptions (clean inputs, defined processes). Address these foundational issues first, or the real-world ROI will fall short of expectations.

This highlights why a stack audit should precede an ROI calculation. It clarifies what you are replacing or consolidating, influencing both sides of the ROI formula.

The mistakes that make a good ROI number worthless

Several common errors can invalidate an ROI calculation. Check your own math against these pitfalls:

• Using list price instead of your actual negotiated price. Vendor calculators often use sticker prices, assuming you will negotiate a lower rate. Use the price you realistically expect to pay.
• Counting the same hours saved twice. If a tool is credited with both saving research time and increasing close rates, verify these are distinct effects and not the same underlying benefit described differently.
• Ignoring the cost of the adoption champion. Someone on your team will spend time encouraging reps to use the tool in the initial months. This time has a cost, even if it is not an invoiced item.
• Assuming a uniform loaded rate for all roles. Different roles, such as a rep, a manager, or a RevOps lead, have varying loaded rates. Use the specific rate for the individual whose time is being saved or spent.

You can run this formula with your own numbers using the Leak Ledger at /roi. This free, ungated tool guides you through calculating loaded rates, identifying common time leaks, and determining the total cost of maintaining the status quo. It is a useful step before a discovery call, allowing you to approach vendors with concrete data.

Before calculating ROI, consider conducting a sales tech stack audit to understand your current technological environment.