Free book The Agentic OS: how to run your business with a team of AI agents. Get it free

AI AutomationNo. 01

Choosing an automation platform: a practical decision framework

The best automation platform is the one your team can maintain at the volume you'll actually run. Here's how to choose without a month of trials.

The short answer

  • There are four families of options: hosted no-code tools, open-source or self-hostable platforms, the automations built into your CRM, and custom code.
  • Decide on who will maintain it, how it's priced at your real volume, how it handles data and errors, and how easy it is to leave.
  • Model the cost at ten times today's volume. Pricing models differ (per step, per operation, per run) and the differences compound.
  • Whatever you choose, document every workflow as a plain-English procedure so it can move platforms later.

“Which automation tool should we use?” is usually the first question teams ask, and it’s the wrong place to start. Start with the work you’re automating and the people who will look after it. The tool choice mostly falls out of those answers.

If you haven’t chosen what to automate yet, do the AI time audit first.

The four families of options

1. Hosted no-code platforms. Tools like Zapier and Make let you connect apps visually with hundreds of ready-made integrations. They’re the fastest way for a non-technical team to get something working.

2. Open-source or self-hostable platforms. Tools like n8n can run on your own infrastructure or as a hosted service. They offer more control over data and costs at high volume, in exchange for more technical responsibility.

3. Built-in automations. Most CRMs, help desks and marketing platforms include their own workflow builders. If a process lives mainly inside one of these tools, its native automations are often the simplest option.

4. Custom code and agent frameworks. Writing the automation as software gives total flexibility and proper testing. It also needs developers to build and maintain it.

The questions that decide it

Question Why it matters
Who will build and maintain this? A tool your team can’t maintain becomes a liability the day the builder leaves.
What volume will it run at? Pricing is usually per step, per operation or per run. The model you’re charged on decides your bill at scale.
Where must the data live? Regulated or sensitive data may rule out some hosted options, or require specific business terms.
Are the integrations you need available? Check the exact actions you need, not just the app logo on a list.
How does it handle errors? Retries, alerts and clear logs matter more than features once workflows run daily.
Can it run AI steps well? Look for model choice, structured outputs, human approval steps and cost controls.
How hard is it to leave? Export formats, versioning and documentation decide your future options.

Common patterns

  • Small team, no developer, moderate volume: a hosted no-code platform, plus your CRM’s native automations for anything that lives inside the CRM.
  • Technical team, high volume or sensitive data: a self-hosted platform or custom code, with proper monitoring.
  • Everything happens in one system: that system’s built-in automations first, and an external platform only for the gaps.
  • Automation is part of your product: custom code, owned by your engineering team.

Model the cost properly

Before committing, write down your five most important workflows, count the steps in each and estimate how often they run each month. Then price them on each shortlisted platform using its current pricing page, at today’s volume and at ten times today’s volume. The ranking often flips at the higher number.

Remember to add the cost of AI model usage for any AI steps, and the time someone spends maintaining the workflows.

Protect yourself from lock-in

Whatever you choose, keep a plain-English procedure for every workflow: trigger, steps, decisions, exceptions and owner. It’s useful for training, it’s essential for debugging, and it’s what lets you rebuild on another platform if you need to.

The bottom line

Choose the platform your team can maintain, priced on your real volume, with the data handling your business requires and an exit you understand. Document everything. The best tool is the one that’s still running reliably a year from now.

Questions people ask

Which is best: Zapier, Make or n8n?
It depends on your team and your volume. Hosted tools are fastest for non-technical teams. Self-hostable platforms suit technical teams with high volumes or strict data requirements. Compare current pricing pages against your own workflow volume, because pricing models differ and change.
Can I just use the automations in my CRM?
Often, yes, and it's a good first choice if most of your workflows start and end in that CRM. The limits show up when you need to connect many other tools or add complex logic.
When should we write custom code instead?
When workflows are core to your product, need to run at very high volume, or require logic and testing that visual tools make awkward. You'll need developers to own and maintain it.

Written by

Devian Chard

AI automation and SEO consultant. I help founders and lean teams get found on Google, get cited in AI answers and hand their busywork to agents that ask before they act.

Popular

↑↓ to move Enter to open Esc to close