Whose Account Is It Running In?
The day you try to cancel is the day you find out who really owns your automation. Here's the question that tells you before you sign.
A restaurant owner I know went to fire his reservations vendor last spring. Nothing dramatic. He'd found something cheaper that did the same job, he gave notice, and he asked for his data. They sent him a CSV. Names, phone numbers, dates, the works. Clean export, no fuss. He figured he was done.
Then he sat down to rebuild the part that actually mattered. The text that went out two hours before a reservation. The flag that caught a no-show. The little sequence that asked for a review the next morning while the meal was still good in someone's memory. He opened the CSV looking for that and it wasn't there. It was never going to be there. He owned the phone numbers. He'd been renting the machine that did anything with them, and the machine stayed behind.
That is the cost nobody puts on the slide. Not the monthly. The exit. And you don't find out what it is until the exact moment you're trying to leave, which is precisely how it's designed.
You own the contacts. You're renting the thing that does anything with them.
Here's the sleight of hand. Every one of these tools has an export button, and the export button is a decoy. It gives you your data, and your data is the part you were never in danger of losing. What it does not give you is the thing you actually paid four figures to set up: the workflow. The rules. The connections between your calendar and your inbox and your point of sale. The prompts somebody tuned over three weeks so the reminder didn't sound like a robot. That logic lives in the vendor's account, in the vendor's format, and there is no export button for it because it is the entire reason you can't leave. Data portability is not logic portability. They let you believe those are the same word.
I sell AI automation for a living, and I'll tell you the single most important thing I do on a build, the thing I never charge extra for because it should be the floor: I run it in the client's own accounts. Their CRM, under their login. Their Google Workspace, their domain, their automation platform, their database, their keys. When I hand it over, I hand over the whole thing, and I say it out loud. You can fire me tomorrow and the machine keeps running, because it was never mine. It was always yours. I was just the guy who wired it up.
Compare that to the all-in-one platform the salesperson demos. Slick dashboard, everything in one place, "we handle the technical stuff so you don't have to." What that sentence means, translated, is: everything you build lives on our land. The prompts, the flows, the integrations, the months of tuning, all of it sits inside a system you rent by the seat and cannot take with you. The convenience is real. It is also the lock. Those are the same feature described by two different people, and only one of them tells you which it is.
Now stack the risks that platform is quietly carrying for you. They raise the price and you pay it, because rebuilding is worse. They get acquired and the new owners kill the plan you're on, because you were somebody else's customer they didn't want. They run out of money and turn the servers off with thirty days' notice, and thirty days is not enough time to reconstruct a year of operations you didn't know were trapped. None of that is paranoia. It is Tuesday in the software business. You are not buying a tool. You are taking on a dependency, and a dependency you can't move is just a landlord you didn't know you had.
So here's the question. Ask it before you sign, ask it out loud, and watch the room while they answer: if I cancel, what do I walk away with, and does this run in my accounts or in yours? Then make them show you. Not the marketing sheet. The actual thing. Log me into the accounts where this lives. Show me the export of the workflow, not just the contacts. Show me what Monday looks like the day after I stop paying you.
The honest ones have an answer ready, because they've already thought about it, and usually the answer is some version of "it runs in your stuff, here's your login." The rest get vague. They talk about your data being safe, which was never the question. They talk about how nobody ever leaves, which is not a comfort, it's a warning. The flinch is the answer. If leaving means starting over, you don't own an automation. You own a hostage situation with a monthly invoice.
I'm in the business of selling this stuff and I'm telling you to check whose name is on the account before you build anything on top of it. The best automation you'll ever buy is the one you could walk away with. If the vendor can't say, plainly, that you'd keep the machine and not just the spreadsheet, you already have your answer. You're not a customer. You're a tenant.