Should I build the automation myself or hire someone?
Build it yourself when the workflow lives inside one system, the steps are short, and you can afford for it to break for a day while you work out why. Hire when the workflow crosses three or more systems, when money or a customer-facing reply depends on it running, or when the person who would build it is the person whose time the automation is meant to free up. The deciding factor is almost never whether it can be built, because the tools are easy to use now. What decides it is who maintains it in month seven, when the person who built it has forgotten how and the business has changed around it.
When is building it yourself the right answer?
One system, short chain. A form that writes to a sheet, a tag that sends an email. Four or five steps, one place for them to go wrong. Nothing customer-facing depends on it. An internal notification failing for a day is an inconvenience. An enquiry going unanswered for a day is lost work. Somebody enjoys it. This matters more than it sounds. The automations that survive in-house are the ones somebody is interested in maintaining. You want to learn where the bottleneck is. Building one by hand teaches you more about your own process than any discovery call will.
What are the three signs you have crossed the line?
The third integration
It stops failing loudly
The builder is the bottleneck
What about hiring someone in-house to do it?
What should I ask whoever I hire?
Whose accounts does it run in? It should be yours, under your logins. That is what makes the work transferable, and it is what decides whether leaving means starting again. How will I know when it breaks? A credible answer names where the alert goes and what happens to the work that was missed in the meantime. What happens when my prices change? This is the maintenance question in disguise, and it separates a build from an arrangement that keeps working.
Can I start myself and hand it over later?
Questions people actually ask
- Are no-code tools good enough to do this properly?
- For the shape of work on this page, yes. The limits that bite are visibility when something fails, version control when somebody changes a step, and cost once you are paying per run at volume. The tool’s capability is not the problem. Those are the same limits whoever builds it, which is why the question is about maintenance rather than tooling.
- How long does it take someone else to build what I would build?
- Less time than it takes you. The comparison that matters is who answers the message at 11pm on a Thursday when a step has failed and four enquiries are sitting unprocessed. Build time is a one-off; that question recurs.
- What if I build it and it works?
- Then it works, and you should not pay anybody for it. Plenty of businesses never need to hire for this. The ones that do are the ones where the automation is on the path that brings work in, because that is where a quiet failure costs more than the fee.
- Do you take over automations somebody else built?
- Yes, and that is what the Care tier is for: looking after a system that already exists rather than building a new one. What it takes depends on whether the existing work is documented and whose accounts it is in. That is the same pair of questions as everything else on this page.