Most businesses need a tool, not an agency.
We build automation for a living, so treat this with appropriate suspicion — but the honest position is that a large share of what people hire agencies for can be done with a subscription and an afternoon. Here is what each category of tool is actually good at, and the specific point where it stops being enough.
Connector platforms
Zapier, Make, n8n
Move data between apps that already have integrations. Excellent for straight-line processes, and the correct first choice for most businesses. Cost scales with task volume, which is what eventually pushes high-throughput workflows toward self-hosting or a custom build.
Model APIs
OpenAI, Anthropic
The reasoning layer: classify an email, extract fields from a messy document, draft a reply, decide what something is about. Rarely used alone — they supply judgement to a process that something else orchestrates.
Voice and conversation
Retell, Vapi
Answer and hold a phone conversation, qualify, book, escalate. The category that has moved fastest recently, and the one where the gap between a demo and something you would put in front of real customers is still widest.
Built systems
Custom
Code that does exactly your process, hosted and monitored. Justified when logic branches heavily, several systems disagree, or a silent failure costs real money — not because it is more advanced, but because the alternatives stop being reliable.
The line between a tool and a system
A tool is a good fit while the process is a straight line: this happens, then that happens, and both systems already speak to each other. Under those conditions a connector platform is cheaper, faster to change, and does not depend on anyone being available to maintain it. If that describes your process, stop reading and go build it — you will be finished this afternoon.
The line is crossed when the process needs judgement about something unstructured, when several systems hold conflicting versions of the same record, or when a failure is silent. That last one is the expensive case: an automation that stops working and tells nobody accumulates cost quietly until a customer complains, and by then the damage is reputational rather than operational.
The useful question is not "tool or agency" but "what happens when this breaks at 2am on a Saturday". If the answer is that nothing happens and nobody notices, that is when a maintained system starts costing less than the tool.