Who owns your automations when the consultant leaves?

Picture a Winter Park pool service whose consultant stopped answering in May. In June the texting number, on his account and his card, was suspended, and quote follow-ups went quiet for three weeks.

So who owns your automations? You do, if the handover was done right: every account in your name, every key rotated and handed over, a runbook per workflow, and the price of the next fix in writing. Here is the standard we hand over to, and you can hold us to it.

The handover checklist

This is the literal content of “yours to keep.” Give it to any vendor before the work starts, including us, then tick through it on the last day.

Checking it takes an afternoon:

• Log in to each account yourself. If the login goes to the vendor’s email, it isn’t yours yet.
• Have the person who’ll live with each workflow explain its runbook back to you. If they can, it’s done.
• Trace one customer through the diagram, and match the list of bills to your card statement.
• Run the test on handover day, then on the first of every month.

Entrepreneur’s advice on renewals applies to consultants too: “price the exit” (Entrepreneur). With the eight items in hand, the exit costs close to nothing, because leaving means removing one user.

Five questions before you sign

The question runs both ways. Lilach Bullock screens prospects for an internal owner before taking them on (Lilach Bullock), and so do we: someone in the office reads the runbook.

Why owners are asking now

On June 26 The Useful Daily summarized small-business Reddit threads under “The Generic AI Automation Pitch Is Dead.” The pitch that still landed promised “narrow relief rather than transformation” (The Useful Daily). Nobody there was against automation, only against owning something they couldn’t see into.

Lilach Bullock, a UK consultant, says the businesses that get burned “automate something and then stop watching it” (Lilach Bullock). Holding the keys is what lets you watch.

Plenty is written about vendor lock-in for software and little about this. One outsourcing guide flags “over-reliance on a single consulting firm” without saying who holds the keys when that firm leaves (SoftwareSeni). The useful question is bookkeeping: if this person vanished tomorrow, what would I hold?

SBE Council’s March survey put data security and privacy at 42 percent of small employers (SBE Council). Accounts in your own name answer much of that worry.

What upkeep costs

Anything that touches customers needs a few minutes a week from somebody reading the exceptions. Studies of staff using AI at a desk put it higher: a Workday study found nearly 40 percent of AI time savings lost to checking (The Lonely Entrepreneur), and Forrester about 4.3 hours a week (Tendem). Those describe people using chat tools, not a narrow automation with a fallback, but they’re the reason to count supervision before you count savings.

Retainers elsewhere run $500 to $5,000 a month (Codewave), and one Los Angeles consultancy monitors for 30 days without saying what follows (Bushe.co). Ours: 60 days of free fixes, then a fixed price per fix or a support plan, month to month, with no hours counted and no markup on the services you pay directly.

• Pay per fix for internal systems, where downtime is an annoyance: a morning report, a form that fills itself, a weekly cleanup.
• Monitor, $150 a month, for one small system customers can wait on, such as review requests or quote follow-up texts.
• Care, $350 a month, when a phone line, an AI employee with phone answering or up to three systems depend on it. A phone that stops answering matters by lunchtime.
• Care plus, $750 a month, for several systems or locations, or software staff use all day.

If a customer would notice a failure before you do, a plan earns its keep. If you’d notice first, pay per fix.

Send this page to whoever built what runs in your office now; if they can tick all eight lines, you’re in good hands. Still deciding whether to build at all? Build it, buy it, or fix the spreadsheet? comes first.