Where it produces real leverage
- Drafting the repeated document: estimate, message, summary, invoice.
- Keeping follow-up timing without a human holding the calendar.
- Turning an unstructured conversation into a structured record.
- Surfacing what needs attention instead of requiring someone to look.
- Handling the first response so a lead is never left waiting.
Where it produces none
- Physical capacity — crews, trucks and installation hours.
- Processes that are undefined; the AI inherits the ambiguity.
- Decisions somebody must be accountable for having made.
- Data that is wrong, where faster action makes the problem worse.
Delegate to it the way you would to a new hire
Define the action, define the boundary, require confirmation on anything destructive, financial or customer-facing, and review the output for a while before you widen the scope. The difference from a new hire is that the boundary is enforced by the system rather than by trust.
Verify before you count the saving
A capability that appears in a feature list is a declaration. A capability that produced a record you can open, with an audit entry behind it, is current. Only the second kind belongs in a leverage calculation — and the same rule applies to any vendor's claims, including ours.