Pay someone to set up Zapier or n8n when the automation crosses three or more apps, needs webhooks or custom API calls, or touches money: leads, quotes, invoices. Do it yourself when it is two or three steps between apps that already have native connectors. And whoever builds it, the real cost is not the build. It is the Tuesday three weeks later when a connected app updates, the flow starts failing, and nobody notices.
That is the thread running through the busiest owner discussion on this topic. In an r/automation thread titled "90% of small businesses can't use Make or n8n" (157 comments), a 30-year small business owner put it bluntly: "The biz owner is stuck the first time this thing breaks." The top-voted comment agreed: "The best automation is the one people can actually keep using without calling someone every week."
If you have not picked what to automate yet, start with what to automate first. This post is about the next decision: DIY or hire, what it really costs, and how to scope a freelancer so you get something that keeps running.
The 3-question test: DIY or hire?
Answer three questions about the one flow you want built. Two or more "hire" answers means pay someone; otherwise, build it yourself this week.
| Question | DIY if | Hire if |
|---|---|---|
| 1. Do both apps have native connectors? | Yes, you can pick them from a list | You need webhooks, raw API calls, or an app with a thin integration |
| 2. Are the steps clean? | Three or so steps, same every time | Exceptions: two companies, shared customers, duplicates, missing fields |
| 3. What does a silent failure cost? | An internal note or a report is late | A lead is not followed up, a quote is not sent, an invoice is wrong |
Each question comes from what builders and owners actually said. A Zapier partner in r/zapier's learn it myself or hire thread: "If it's REALLY simple do it yourself." Another commenter, who had spent a couple of years learning Zapier: "for basic crap with prebuilt apps, sure, do it yourself all day. For custom work and webhooks, just hire out."
On question 2, the clearest line came from an r/TopAutomationTools thread on back-office automation: "A workflow that is three clean steps is a cheap no-code job you can probably do yourselves. One with a pile of exceptions in it is an automation project, and that's the one worth outsourcing to a specialist. You can't tell which you have until it's written down."
The owner story that fits question 2 best is a pool and construction owner on r/zapier running two companies with shared customers across Monday CRM, Jobber and QuickBooks. He tried Zapier himself: "once you start dealing with multiple systems, two companies, shared contacts, different job flows, and accounting… it gets messy fast." The most useful reply was not a sales pitch: "this is more a systems design issue than a Zapier skill issue." When it gets messy, the problem usually is not the tool. Nobody has decided which system owns which data. We cover that decision in why CRM duplicates keep coming back.
Question 3 matters most for service businesses, because the flows owners most want are lead flows: new form fill to CRM, text back, alert the owner. When that breaks, the lead waits, and how fast you respond to a lead is often the whole game.
What it costs: the builder bill and the tool bill
You pay a builder once (or on retainer) and a platform every month, and the platform bill depends on how each tool counts usage. Most cost pages quote only the first number.
The builder
Almost every published rate for this work comes from someone selling it, so treat these as ranges, not quotes:
| Source (seller) | Hourly | Project | Ongoing |
|---|---|---|---|
| GolmTech, a Zapier Platinum partner | Most consultants $40 to $150 | Simple automations $300 to $1,000; custom API $1,000 to $3,000; its own projects from $2,500 | Maintenance $300 to $600 a month for 1 to 5 Zaps, citing LowCode Agency |
| Hire Overseas, a staffing firm | $50 to $100 basic; $100 to $200 advanced | Not stated | Retainers from about $2,500 to $5,000+ a month |
The honest line in the GolmTech guide is worth repeating: for a simple two-app flow, "do it yourself; paying someone $500 for that is a waste."
The tool
This is where owners get surprised, because the three big tools count usage differently. Here is a typical lead flow: web form submitted, create the contact in your CRM, text the lead, post an alert to the owner, skip spam with a filter.
| Tool | How it bills | That lead flow, per lead | Watch out for |
|---|---|---|---|
| Zapier | Each successful action is a task. Triggers, failed actions, Filter, Formatter, Paths, Delay and Digest are free. | 3 tasks (CRM, text, alert) | Free plan is 100 tasks a month and two-step Zaps only. Paid starts from $19.99 a month. At the limit, Zaps pause or you pay a higher per-task rate. |
| n8n | One execution per run of the whole workflow, however many steps | 1 execution | Starter cloud is 20 EUR a month billed annually for 2.5K executions. A workflow scheduled every 5 minutes uses 8,600 to 8,900 a month on its own. |
| Make | Each module action uses a credit (most use 1) | About one credit per module in the run | Free is 1,000 credits a month. Scenarios stop when credits run out; Make warns at 75% and 90%. |
Run your own numbers. At 100 leads a month, the Zapier version uses about 300 tasks, past the 100-task free plan. The n8n version uses 100 executions, unless the builder set it to poll a spreadsheet every five minutes, in which case the schedule alone blows through Starter. Ask any builder how the flow is triggered and what it will use per month before they start. A good one answers in one sentence.
The real cost is keeping it running
Budget for maintenance from day one, because automations fail when the apps around them change, not when you touch them. The r/automation owner who had used Make described it this way: "if you build an automation powered by Make- it constantly breaks. Not because of make- but because word/excel/adobe/quickbooks/outlook/you name it continuously update and patch and what worked last week cracks this week."
Here is what actually happens in Zapier when that occurs, from Zapier's own troubleshooting guide:
- The run gets an Errored status and does not complete. An expired login (401) is one of the common causes: "you changed your password in the app."
- By default, Zapier emails the Zapier account's email address for each error.
- "Your Zap will automatically turn off if 95% of its runs result in errors in the last 7 days." On Team plans the owner gets an email and a 24-hour grace period first; on Enterprise, 72 hours.
- Autoreplay retries errored runs caused by temporary problems, and you can replay failed runs after fixing the cause so the data is not lost.
n8n works on the same principle but you have to set it up: an error workflow, starting with the Error Trigger node, that runs when an execution fails and can send you an email or Slack alert. If nobody built one, a failed run just sits in the execution log.
Now put those facts next to the most common freelancer setup: they build in their own account, with their own email. Your lead flow fails when your CRM forces a password reset. The alert goes to their inbox. Seven days of errors later, the Zap switches itself off. You find out when a customer says nobody called back. The same leak shows up in our list of where small businesses lose money: a lead that arrived and got no reply.
Watch out
The week-three question. In the r/automation thread, the original poster summed it up: "the real question is what happens on week three when an edge case shows up. If the answer is 'call the consultant', the automation is dead." Before you hire, decide who fixes it, how they hear about it, and how fast.
If the flow you want automated is lead capture or follow-up, the build is the easy part. We map where your enquiries arrive, build the capture and follow-up in accounts you own, and set alerts that reach a person on your team when something stops.
Who should own the account
You should, every time: the Zapier, Make or n8n account, and every app connection inside it. Owning the account is not just about control. It is how the alerts reach you.
Set it up this way before the builder starts:
- Create the account with a shared company email (ops@ or admin@), not your personal inbox and not the builder's.
- Connect apps with company logins. If the builder connects your CRM using their user, the flow breaks the day you remove them.
- Invite the builder to the account, or on n8n cloud, add them as a user. n8n says all its plans include unlimited users.
- Set error notifications to go somewhere a person looks daily. On Zapier the default is an email for each error, and there is an hourly summary option. Never set it to "Never."
- Keep a one-page map: each automation, what triggers it, what it touches, and who to call. That map is the "leave a way to fix it" one r/automation commenter said small businesses actually need.
The same rule applies to self-hosted n8n with more weight. Self-hosted n8n without a licence key runs as the free Community edition, which sounds like a saving until you ask who applies updates, backs up the database and notices the server is down. If you are weighing that, our self-hosted n8n checklist lists what production actually requires.
How to scope a freelancer on one page
A one-page scope turns an open-ended hourly job into a fixed quote you can hold someone to. Consultants bill for discovery, and in the r/automation thread one builder said the real gap is that "nobody sat with them to map the actual workflow before touching any software." You can do most of that mapping yourself, for free.
Fill this in for one flow:
| Field | Example: new web lead |
|---|---|
| Trigger | Someone submits the quote form on the website |
| Steps, in plain English | Create or update the contact in the CRM; text the lead within a minute; alert the owner by text; tag the source |
| Source of truth per field | CRM owns name, phone, address; form owns the job description |
| What counts as a duplicate | Same phone number, or same email |
| Missing or bad data | No phone: skip the text, alert the owner. Spam: filter out |
| Who gets alerted on failure | Office manager, by text, same day |
| Acceptance test | See below |
| Handover | Loom walkthrough, the one-page map, built in our account |
Two lines in that sheet do most of the work. "Source of truth" stops the duplicate-contact mess the pool owner hit. "What counts as a duplicate" is the question most DIY builds never answer. If your enquiries are coming from ad forms rather than your website, the trigger row changes; see Meta lead forms vs landing pages for why that matters.
Then send it to two or three builders. Anyone who quotes without asking a question about it is guessing.
The acceptance test: 5 leads is not a test
Pay the final invoice only after the flow survives real data and a forced failure. The demo always works, because demos use a handful of clean records.
In a widely watched video on learning n8n, Tom Crawshaw, who sells an n8n mentorship, described the pattern: tutorials use "test data in a perfect scenario. But nobody shows you what happens when you run 500 leads into your workflow instead of the five that you tested it with." The failures he lists are the ones owners see: duplicate leads, data landing in the wrong fields, errors. He also said his highest-earning automation is "about four or five different nodes," which is a useful check on anyone pitching a 30-step build.
A builder in the r/TopAutomationTools thread gave the best acceptance test we found: "a record changes once, the other systems match it, duplicates are blocked, and any exception is visible to a person." Turn that into four checks:
- Real data: replay last month's actual leads (or a big export) through it, not five samples.
- Duplicate: submit the same person twice with a different email. One record, not two.
- Missing field: submit without a phone number. It should take the fallback path and alert someone.
- Forced failure: disconnect one app. Confirm the alert reaches the person on your one-page scope, then reconnect and replay the failed run.
The middle option: player-coach
If you want to learn it but not from zero, pay someone to build one flow with you, then build the rest yourself. An r/zapier commenter called it "Middle ground: have someone build for you a specific automation, and answer questions about it, like a player-coach. Use that to build your own."
This works well for owners who will tweak things later, which is most of them. The r/automation thread's most repeated point was that the business needs someone who can change one step without breaking the rest. A paid first build plus a recorded walkthrough gets you there faster than tutorials, and you keep the judgment calls in-house.
It is also the right answer when the question is really about staffing. If the work is mostly judgment (quoting, scheduling, chasing), compare it against hiring office help before automating it. And if someone is pitching you an AI agent instead of a workflow, read the difference between an AI agent and a workflow first: agents cost more to run and are harder to test.
Checklist before you pay anyone
Run through this for the flow you have in mind. Every "no" is something to fix before the build, or something to put in the scope.
- I have written the flow as plain steps, including what happens with duplicates and missing fields.
- I know whether each app has a native connector in the tool we are using.
- I know roughly how many times a month it will run, and what that uses on the plan.
- The account is in a company email, and the apps connect with company logins.
- Error alerts go to a named person who checks daily.
- There is an acceptance test with real data and a forced failure.
- I get a one-page map and a walkthrough recording at handover.
- I know who fixes it in week three, and what that costs.
If the first box is the one you cannot tick, you are not ready to hire a builder. You need an hour with a notepad. A lot of what owners want automated turns out to be one missing step, like a missed call text back or a proper follow-up system, which many CRMs and field service tools already include.
Stuck on the first box, or the flow crosses more systems than you want to own? Send us how your enquiries come in today. We will map the lead flow, say what your existing tools already do, and build the rest with alerts and a handover your team can maintain.
When it is not worth anyone's money
Skip the automation, DIY or hired, when the process still changes every week or runs a few times a month. Automating a process you are still working out locks in today's version and makes every change a paid edit. If the task runs five times a month and takes ten minutes, that is under an hour a month. Against the $300 to $1,000 published for a simple build, that can take a year or more to pay back, before counting the tool bill.
One r/automation reply put the fix in a sentence: someone should "turn messy steps into a checklist, automate one piece, and leave a way to fix it when it breaks." Start with one flow, own the account, test it with real data, and only then decide whether you need the builder again.