Local AI vs cloud AI for service businesses: what actually belongs on each

Local versus cloud is a bad argument if you treat it like a religion. Some work should never leave the building. Some work needs a frontier model. Most service businesses need both, routed on purpose.

Local wins when the job is repetitive, high-volume, and sits next to records you do not want to ship off-site. Owner reports. Ticket watches. Drafting a follow-up from a job file you already store. Dedicated hardware you control also makes the cost of a run more predictable than renting tokens every time a bay opens.

Cloud wins when the job is messy, rare, or needs a model that is still moving fast. A weird customer email. A long estimate that does not match a template. A one-off summary of a messy file. Paying for that occasionally is cheaper than pretending a small local model can do everything.

Rules still beat models for a surprising amount of operations work. If a repair order has no approval and no customer update after X hours, you do not need a language model to notice. You need a watcher, a permission, and a person who still owns the customer.

The practical answer for most shops and trades is hybrid. Local for the overnight watch and the daily briefing. Cloud when the agent has to write something that would embarrass you if it were dumb. The audit is where we decide which jobs belong where, not a slide about GPUs.