How do you calculate the break-even point?
Add recurring fees, extra tools and the time your team needs to operate the workflow. Spread setup and integration over the period you expect to use it. For each additional job, subtract the direct cost of delivering it from the price paid. Divide total monthly cost by that contribution and round up.
Monthly operation costs $600. Setup costs $1,800 and you spread it over six months, adding $300 per month. At $450 contribution per additional paid job, break-even is two extra wins per month ($900 ÷ $450). One extra win leaves a $450 shortfall. Three leave $450 above monthly equivalent cost.
Those figures illustrate the method. Use your own costs, expected operating period and contribution. If the team cannot deliver another job, model that capacity limit before assigning value to another win.
How many sales could the workflow plausibly recover?
Start with qualified leads that were delayed, unassigned or missing a next action. Apply a conservative incremental win estimate to that group and round the resulting jobs down for a planning scenario. Some leads would have converted anyway. Compare the estimate with your break-even threshold and look at what happens if the result is half as high.
If you cannot estimate the affected volume yet, run the quote request audit. Use the capacity calculator to check the time assumption separately.
What should a pilot prove before you scale?
Scope one lead source, one failure point and one owner. Measure the rate of requests reaching that step before and after the change. Follow the matched cohorts until deals have comparable time to mature. Keep paid jobs, time saved and live handoff reliability visible as separate measures.
Define the decision up front: for example, continue if the workflow reliably assigns requests and observed additional contribution is enough to justify the scoped cost. The Arrow Revenue Engine describes the system a pilot can feed into.