What actually breaks when you ship AI agents for real service businesses (a year in)

I've spent the last year building and running AI automation for service businesses — HVAC, contractors, notaries, a few law firms — and I wanted to share the stuff nobody warns you about, because the demos make it look way cleaner than it is. A few things that bit me: \- The AI layer is the easy 20%. The hard 80% is the boring plumbing around it — auth, per-client data isolation, billing edge cases, retries, what happens when a webhook fires twice. An agent that books an appointment is a demo. An agent that books an appointment, doesn't double-charge, and recovers when the calendar API times out is a product. \- Owners don't want "AI." They want their Tuesday back. The wins that land are embarrassingly specific: "stop missing after-hours calls," "stop chasing people for the same form." Scope to the painful workflow, not the buzzword. \- Most custom builds for this market are a 1–2 week scope, not a quarter. If you're quoting months, you're either gold-plating or you don't understand the workflow yet. \- Multi-tenant from day one or you'll rewrite everything. Adding real per-client isolation after the fact is brutal. \- Voice is finally good enough to put in front of customers, but only if you get the transfer/escalation path right. The AI knowing when to hand off to a human matters more than how smart it sounds. Happy to get into specifics on any of these in the comments — stack, how I scope with non-technical owners, where agents quietly fail in production, whatever's useful. (For context, I build and run this stuff myself, so most of what's above is scar tissue, not theory.)