Sound familiar?
- Someone spends every morning copying orders or leads between systems
- Your Zapier or Make bill has grown faster than the business
- An automation broke weeks ago and nobody noticed
- Approvals are chased by email and nobody knows where a request is
- The person who built the Power Automate flows has left
- A no-code flow can't reach your in-house database or old system
Key facts
- Zapier bills per task, Make bills per credit (it moved from operations to credits in 2025) and Power Automate is licensed per user or per flow
- Power Automate premium connectors, including HTTP and most non-Microsoft systems, need a premium licence
- No-code tools suit low-volume, linear flows between popular SaaS apps
- Custom code suits high volume, complex logic, sensitive data or systems with no ready-made connector
- We often mix the two: a no-code front end calling a small custom API
- Every automation we build has error alerts and a named owner
- Custom automations are documented and owned by you, with no per-run fees
Start with the process, not the tool
Most automation projects go wrong because they start with a tool. Someone signs up for Zapier, connects two apps, and six months later there are forty zaps, three people who half-understand them, and no record of what happens when one fails. We start with the process: who does what, how often, what data moves, what can go wrong, and how much time it costs. Then we choose the cheapest reliable way to automate it.
Sometimes that's a no-code tool and an afternoon of setup. Sometimes it's custom code. Often it's both. We don't have a reason to push one or the other.
A fair comparison
| Zapier | Make | Power Automate | Custom code | |
|---|---|---|---|---|
| Best for | Quick links between popular SaaS apps | Multi-step visual scenarios with branching and data transformation | Businesses already standardised on Microsoft 365 | Volume, complex rules, in-house systems, sensitive data |
| Billing model | Per task (each successful action step) | Per credit (most modules use one per run) | Per user or per flow; premium connectors need premium licences | Build cost, then hosting; no per-run fees |
| Connectors | Very large catalogue | Large catalogue plus HTTP module | Strong for Microsoft, premium for many others | Anything with an API, database or file |
| Error handling | Basic retries and alerts | Error routes per module | Configurable run-after and scopes | Whatever you need: queues, idempotency, dashboards |
| Version control and testing | Limited | Limited | Via solutions and environments | Full Git history and automated tests |
| Main risk | Cost at volume, sprawl | Complex scenarios become hard to follow | Licensing surprises, flows tied to one user | Needs a developer to change |
Billing details change often. Make, for example, moved from operations to credits in 2025, according to Make's own help pages, so check each vendor's current pricing for your volumes before deciding.
When no-code is the right answer
If the workflow is linear, connects well-known SaaS apps, runs a few hundred times a month and a failure is an inconvenience rather than a disaster, a no-code tool is usually right. It's quick to set up and someone in the office can adjust it. Power Automate is a natural choice if you already pay for Microsoft 365 and the flow stays inside Outlook, SharePoint and Teams. We'll set these up properly: a shared service account rather than one person's login, naming conventions, error notifications and a written list of what each flow does.
When custom code pays for itself
- Volume: thousands of orders or records a day make per-task billing expensive, while a small service on a modest server costs the same at any volume.
- Logic: matching rules, calculations, lookups against your own data and multi-step approvals get messy in visual builders.
- Reach: your ERP, an on-premise database or an old system with no connector.
- Reliability: queues, retries, idempotent processing and a dashboard of failures. See webhook development.
- Data protection: keeping personal or financial data inside your own infrastructure rather than passing it through another processor.
We build these in PHP 8 with Laravel or Node.js with TypeScript, with queues, scheduled jobs and logging. You own the code. Where AI helps, for example classifying emails or reading documents, see AI automation.
A quick way to decide
These questions usually settle it in a few minutes:
- How many runs a month? Hundreds lean towards no-code; tens of thousands lean towards code.
- How many steps and branches? A straight line from A to B is easy anywhere. Lookups, loops and exceptions favour code.
- Is there a connector for every system? If one end is your own database or an old on-premise package, you'll need some code anyway.
- What does a failure cost? A missed Slack message is fine. A missed invoice or a double charge is not.
- Who will change it? If someone in the office will adjust it often, no-code has real value. If it rarely changes, code is cheaper over its life.
- What data passes through? Personal or financial data adds data protection questions for every extra processor in the chain.
Rescuing existing automations
A common job is untangling flows that grew organically: duplicated zaps, scenarios nobody understands, Power Automate flows owned by someone who left. We inventory what exists, document it, keep what works, and move the fragile or expensive parts into maintained code. That's quoted at a fixed price after a free chat. Get in touch.
What we deliver
- Process map of the current workflow and where time is lost
- Recommendation: no-code, custom code, or a mix, with running-cost comparison
- Built automations with logging, retries and error alerts
- Approval workflows with a clear audit trail
- Small custom APIs that let no-code tools reach your own systems
- Migration of fragile Zapier, Make or Power Automate flows into maintained code
- Runbook covering owners, credentials and how to change things
How it works and what it costs
Every project gets a fixed-price quote after a free initial chat and a short scoping stage. You own the code and the data.
Free chat
Tell us the problem in plain English: what you do now, what goes wrong and what "better" looks like. No charge, no obligation.
Scoping
We map the processes, systems and data involved, agree what is in and out, and write it down so there are no surprises.
Fixed-price quote
You get a fixed price for the agreed scope, or a phased plan for bigger builds, so you can start small and prove it works.
Build and test
We build in short stages you can see and try, test against real data, then go live carefully with a rollback plan.
Hand over and look after
You own the code and the data. We can host it, support it and keep improving it, or hand it to your own team.
Frequently asked questions
Should we use Zapier, Make or Power Automate?
Zapier is quickest for simple links between popular apps. Make handles more complex multi-step scenarios. Power Automate fits businesses already on Microsoft 365. dijitul will recommend one, or custom code, after looking at your volumes, systems and how critical the process is.
When is custom code better than no-code automation?
When volumes are high enough that per-task or per-credit billing gets expensive, when logic is complex, when you need to reach systems without connectors, or when failures must be caught and retried reliably. Custom code also keeps sensitive data inside your own infrastructure.
Can you fix our existing Zapier or Make automations?
Yes. dijitul inventories and documents what's running, fixes broken flows, removes duplicates, and moves the expensive or fragile parts into maintained code where that makes sense. Simple flows can stay where they are.
Do Power Automate flows need premium licences?
Flows using premium connectors, which include the HTTP connector and many non-Microsoft systems, need a premium licence. Standard connectors for Microsoft 365 apps don't. Check Microsoft's current licensing for your setup before committing to a design.
What happens when an automation fails?
Every automation dijitul builds has error alerts to a named person, logs showing what happened, and automatic retries for temporary problems such as timeouts. For custom code there's a dashboard listing failed items with a retry button.
How much does workflow automation cost?
It depends on the processes and systems involved. dijitul maps the workflow first, then gives a fixed-price quote, including an honest comparison of running costs for no-code versus custom options.
Related
Tell us what you need to build
Free chat, clear scope, fixed-price quote. You own everything we build.