What the work
actually produces.

Dispatch lives on a whiteboard and in the dispatcher’s head. It works, right up until she is out, and then the morning is spent reconstructing the day from call history. Nobody can say how many calls came in after hours, because nothing records them — they either reached someone or they did not.

Booking moves online with confirmation and a reminder before the window, so the customer stops being the reminder system. After-hours calls are captured and triaged instead of lost, and the day is visible to more than one person.

The point is not the automation. It is that the business stops depending on one person being available, and starts being able to count what it was previously only guessing at.

A four-person roofing company takes job enquiries through a website form, two personal mobiles and a shared Gmail. If the right person does not see the message first, nobody follows up. Underneath that sit three overlapping subscriptions — a CRM nobody adopted, a project tool from a vendor demo two years ago, and a scheduler from a promotion everyone has forgotten about.

The fix routes every channel into one intake with a same-day acknowledgement that does not wait for a human, and a pipeline — lead, estimate, job, complete — the whole team can see. The overlapping tools get itemised against what they actually do, and the duplicates are cut.

The change worth measuring is not response time. It is that duplicate spend becomes a line item instead of a direct debit nobody reads, and a lead going cold leaves a record — so what slow follow-up costs across a season can be counted rather than felt.

A regional insurance agency runs most systems on shared credentials, with passwords on notes near the monitors and no reliable way to end an account when someone leaves. At the same time a vendor is pitching an expensive AI document-processing product for policy applications.

Access comes first: individual logins, a password manager across the team, and an offboarding checklist so access ends the day someone leaves. Then the pitch gets tested rather than accepted — the job being sold can usually be done with the Microsoft 365 licences already on the invoice and a properly configured document route, with no new AI spend.

The point is not the automation. It is that the access exposure closes, and the buy-or-not decision gets made against what the stack already does rather than against a demo.