The no-code stack — Zapier, Make, Power Automate
No-code automation tools democratised workflow automation for small businesses. Before them, connecting two SaaS apps required a developer. Now it requires an afternoon and a credit card. That's a genuine improvement, and it's worth acknowledging before the criticism.
Zapier is the easiest entry point. Its trigger-action model is intuitive, its integration library is large, and it works well for simple, high-level workflows. Make (formerly Integromat) is more powerful for multi-step scenarios with conditional logic. Microsoft Power Automate integrates tightly with the Microsoft 365 ecosystem and is the natural choice for businesses already invested in that stack.
These tools are the right answer when your workflow involves two or three standard SaaS platforms, runs at low volume, doesn't require custom data handling, and doesn't need to be bulletproof. Use them. They work for those use cases.
Where no-code breaks down at scale
The limitations appear predictably as businesses grow. They are not edge cases — they are structural properties of how these platforms are designed.
- Pricing at volume. Zapier's pricing is task-based. At low volume it's affordable. At enterprise volume, the monthly bill can exceed the cost of a custom build within the first year of operation. We've seen clients spending four to five figures monthly on Zapier for workflows that a custom integration would serve for a fraction of that.
- Rate limits and reliability. No-code platforms sit between your systems, not within them. When a third-party integration breaks — and they do — your automation breaks. Debugging a failed Zap in a chain of fifteen steps is significantly more painful than debugging a well-written codebase.
- Data handling limitations. Complex data transformations, custom validation logic, proprietary data formats, and large payloads all push against the boundaries of what no-code tools handle gracefully. The workarounds become increasingly fragile.
- Vendor dependency. Your automation logic lives in a third-party platform. If that platform changes its pricing, deprecates an integration, or goes offline, your operations are affected. You don't own what you've built.
RPA tools — promise vs reality for SMEs
RPA (Robotic Process Automation) tools like UiPath and Automation Anywhere are frequently pitched to SMEs as the next step beyond no-code. The pitch is compelling: automate any application, even ones with no API, by mimicking how a human uses the interface.
The reality for most SMEs is that RPA is expensive, technically demanding to maintain, and fragile in ways that become apparent quickly. When the application being automated updates its interface — and SaaS applications update frequently — the RPA bot breaks. Maintaining a library of RPA scripts requires specialised skills that most SME teams don't have in-house.
RPA is a legitimate tool when you're working with legacy enterprise systems that have no API and no roadmap for providing one. For most SMEs using modern cloud software, it is a solution to a problem they don't have.
When custom automation pays for itself in under 12 months
Custom business process automation software built specifically for your workflow is the right answer when any of the following apply. The process runs at high volume — meaning thousands of transactions per month, not hundreds. The workflow involves proprietary data structures or internal systems that no-code platforms can't reach cleanly. The business logic is complex enough that no-code workarounds are becoming a maintenance burden. Or the data being processed is sensitive enough that running it through a third-party platform creates security or compliance exposure.
In these situations, a custom build amortises quickly. Fixed build cost, no per-task pricing, runs on your infrastructure, maintained under your control. The twelve-month breakeven calculation is simple arithmetic when you're currently spending significant money on business process automation services through no-code platforms and still hitting limitations.
The contrarian point worth making: most companies reach for custom too late, after they've already spent a year and a significant budget patching together no-code workflows that barely work. The right time to evaluate custom is before you've over-invested in the workaround.
Our framework — start no-code, graduate to custom
We don't tell clients to skip no-code entirely. That would be bad advice. What we recommend is a staged approach that makes honest use of each tool's strengths.
Start with no-code to validate that the workflow is right. Run it for three to six months. Measure whether it produces the output you expected. If it does, and if you're hitting the ceiling — volume, cost, reliability, or complexity — that's the signal to build a proper custom solution around the validated workflow design.
This approach does two things. It reduces the risk of building custom automation around a process that turns out to be wrong. And it means when you do build custom, you're building something you already understand from having run it in practice, not from a whiteboard exercise.
The AEKIOS take
We build custom automation for SMEs that have outgrown the no-code stack, not for companies that should still be on it. If you're happy with Zapier and it's working, stay there. If you're fighting it every month, spending more than you expected, or hitting a ceiling you can't grow past — that's when a conversation with us is worth your time. We'll tell you honestly whether the problem warrants a custom build or whether there's a no-code fix you haven't tried yet.
Frequently asked questions
Is Zapier good enough for a growing SME
For simple workflows at low to medium volume, yes. Once you're running thousands of tasks per month, building multi-step workflows with complex logic, or hitting the pricing ceiling, it starts to cost more than it saves. The question isn't whether Zapier is good — it is — it's whether it's the right tool for where your business is going, not just where it is now.
What does custom business process automation actually cost to build
It depends heavily on scope. A well-defined single-process automation — invoice intake, onboarding sequence, reporting pipeline — typically runs from a few thousand euros to twenty or thirty thousand, depending on complexity and integration requirements. The right comparison isn't against zero cost, it's against the ongoing cost and limitations of the alternative.
Can I use both no-code tools and custom automation in the same business
Yes, and most businesses we work with do. No-code tools handle simple, peripheral workflows where the cost and speed of setup outweigh the limitations. Custom automation handles the core operational processes where reliability, data control, and scalability matter. The two approaches coexist without conflict.
How do I avoid being locked in to a vendor when automating business processes
With no-code tools, vendor lock-in is structural — your logic lives on their platform. Mitigate it by documenting your workflow logic separately so you can rebuild it. With custom automation, you own the code and it runs on your infrastructure. That's the deeper form of the anti-lock-in argument: owning what you build versus renting what you run.