Most AI rollouts fail at the trades because the implementer talks down. Here is the change-management playbook we use with HVAC, roofing, and plumbing teams.
Most AI implementers come from a software background and they talk to trades teams like they are software teams. The HVAC dispatcher who has been dispatching for 22 years is not going to take prompt-engineering advice from a 26-year-old with a Vapi account. Here is the change-management playbook that does work. The numbers we hit, with the baselines Below is a representative 90-day delta from a recent client deployment in this category. The baseline is from the trailing 90 days before deploy, the post numbers are from the 90 days after first traffic.
The baseline is from the trailing 90 days before deploy, the post numbers are from the 90 days after first traffic. Metric Baseline After 90 days Delta --- --- --- --- Inbound handle rate 47% 94% +47pts Median time to first response 4h 32m 38s -99% Conversion to booked outcome 18% 31% +13pts Cost per resolved interaction $7.10 $1.20 -83% 5-star reviews per month 6 14 +133% Net CSAT (sample of 200) 71 79 +8pts Numbers vary by vertical. Once you get the data pipeline right and the eval gate in place, handle rate jumps 40-60 percentage points within the first month, conversion follows two to four weeks later as the prompts get tuned, and cost-per-interaction drops as caching and model routing kick in. The CSAT delta is the one that surprises new operators. The conventional wisdom that customers hate AI is mostly wrong when the AI works.
Most AI rollouts fail at the trades because the implementer talks down. Here is the change-management playbook we use with HVAC, roofing, and plumbing teams. It is filed under AI Strategy because that is where operators looking for this problem actually start, and it is written from production work rather than from a content calendar.