The same jobs still run, and they cost much less to run.
At a previous company, Zapier and n8n subscriptions were costing thousands of dollars a year. I moved the work off them, and the same jobs now cost much less to run. Here's how I approach a move like that, and how to decide whether you should.
Tools like Zapier, Make, n8n and Workato are a good way to start. You connect two systems in an afternoon and the job runs.
Most of them charge by use, so the bill grows as the business does. A few years in, a company is often paying thousands of dollars a year to move the same records between the same systems, and it's easy to lose track of what each one does.
What it does, how often it runs, what it costs and who would notice if it stopped.
Jobs that follow a rule every time, and jobs that need judgment.
A job that does the same thing every time doesn't need AI. A plain automation on a schedule is cheaper and does exactly the same thing on every run.
Only where a plain automation can't do the job, and with a limit on what it can do alone.
Every job is checked for failures, lateness and wrong output.
Anything that can't be undone waits for a person.
You give up the drag-and-drop editor. Someone has to own what replaces it, which is why I stay and run it after I build it.
If you have a handful of simple automations and people who like building their own, keep Zapier. The move pays off when the small bills have piled up, the jobs matter, or the automations break and nobody knows why.
No single one of these bills is the problem. They're papercuts: lots of little charges every month. I help you cut them one at a time, and you end up with a stack of your own.
I list every automation you pay for, what each one costs and which ones nobody would miss.
I move the expensive and important ones first, and keep each old one running until the new one has matched it.
I run them, fix them and add the next ones. You cancel the subscriptions when you're ready.
Often, yes. Andy Flowe moved a company off Zapier and n8n subscriptions that were costing thousands of dollars a year, and the same jobs now cost much less to run. Jobs that follow a rule became plain scheduled automations, and only the jobs that need judgment use AI agents.
Not while Andy runs it: he builds the replacements inside the company's own accounts and then runs, monitors and fixes them every month. When he hands over, the company's operations hire takes it on, with written notes on how each job runs.
Yes. The method is the same: list every job, turn the rule-following ones into plain scheduled automations, and use agents only where judgment is needed.
© 2026 Flowe State Ops. Product names are trademarks of their owners. Flowe State Ops isn't affiliated with or endorsed by any of them.
You tell me where your time goes, and I'll tell you what I'd take off your desk first.
Email Andy[email protected] or (347) 881-3681
About Andy and LinkedIn
A good fit: owner-led businesses, funded startups and investor-backed companies with more operations work than people to do it. Not a fit if you want a one-off workshop.