Written and maintained by Ersan Jahed Tabrizi · Updated October 30, 2026
Start with the workflow, not the software
Before estimating a return, describe the current process in plain language. Who performs it, how often, how long does it take, and where do delays or errors occur? A CRM does not create value because it has many features. It creates value only when a team adopts a better workflow: fewer missed follow-ups, faster handoffs, cleaner reporting, or less manual entry.
Measure one normal month if possible. Record hours spent, people involved, error or rework frequency, and the financial consequence of delays. This becomes the baseline. Without it, an ROI calculation is only a story about a future that cannot be compared with the present.
1. Calculate recurring monthly value
For a time-saving tool, begin with a transparent labor-value estimate:
Monthly time value = hourly value × people affected × hours saved per week × 4.33
Example: three people valued at $40 per hour each save two hours per week. The modeled monthly value is $1,039. This is not automatically cash in the bank. It may appear as extra delivery capacity, shorter response time, or reduced overtime. State which form of value you expect so it can be measured.
For a revenue tool, do not count an entire sale as software-created revenue. Use the incremental improvement that can reasonably be attributed to the new workflow, then apply gross margin rather than top-line revenue when appropriate.
2. Include the full cost
Subscription price is only one part of cost. Add implementation labor, migration, training, integrations, paid add-ons, and the expected cost of ongoing administration. If five people each spend four hours learning a tool, that effort belongs in the first-year model even when the vendor calls onboarding free.
First-year net value = (monthly recurring value − monthly recurring cost) × 12 − one-time setup cost
Also check whether annual billing, seat minimums, usage limits, support tiers, or currency conversion change the real commitment.
3. Calculate payback and test uncertainty
Payback answers a practical question: how long does it take for monthly net value to recover the setup cost?
Setup payback in months = one-time setup cost ÷ monthly net value
Run at least three cases. In a conservative case, reduce adoption and hours saved while increasing setup time. The base case should use the most defensible assumptions. The optimistic case can show upside, but it should never be the only number presented to a buyer.
- Conservative: partial adoption, slower implementation, lower time savings.
- Base: expected adoption based on the planned rollout.
- Optimistic: strong adoption after the process is stable.
4. Run a small pilot
Choose one team, one workflow, and a fixed test window. Record the baseline before the pilot and measure the same indicators during it. Useful measures include cycle time, manual touches, error rate, response time, completion rate, and active usage. Ask users what changed and where the new tool added work instead of removing it.
A pilot should be able to disprove the model. If the result can only be called successful, the measurement plan is not useful.
5. Replace estimates before renewal
Before increasing seats or renewing annually, repeat the calculation with actual usage, measured time saved, real support costs, and the current contract price. Remove inactive seats and unused add-ons. A tool can have a positive first-year result and still become poor value if adoption falls or pricing expands faster than the benefit.
A compact buyer checklist
- Is the current workflow measured?
- Is the claimed value recurring, measurable, and attributable?
- Are implementation, migration, training, and administration included?
- Does the conservative case still make sense?
- Can the product be tested with a small pilot?
- Are security, data export, cancellation, and renewal terms acceptable?
