A8gent
Pricing guide - hiring a builder

What an automation build actually costs

Real price bands for hiring someone to build one automation, what pushes the number up, and the point where a $29 starter kit is the better buy than done-for-you.

A8gent
·

What you get from this page

  • Price bands for four levels of workflow complexity, with what each one includes
  • Published freelance hourly rates as of 2026, and why they tell you less than you think
  • The five things that actually move a quote, with data cleanup first
  • An honest line on when the $29 kit beats paying someone
  • How to scope the work so the quote you get is a real number rather than a guess

The question this page answers

There is a specific question people type into a search box when they have already decided to automate something: how much does it cost to hire someone to build this. Not what does automation cost as a category - what does this one workflow cost, from someone who will actually build it.

The results for that question are almost entirely marketplace listings and lead-generation pages that answer a different one. So here is the direct answer, with the caveat that matters most: every figure below is a market-typical range observed across the automation market as of August 2026. It is a planning aid, not a quote, and not our price list. Regional rates vary enormously and your own systems will move a number more than any published range can capture.

This page and the cost page are different questions

This page is about commissioning one build. AI automation cost answers the annual budgeting question for a small business - four common workflows priced across build effort, tool subscriptions, and monthly running cost, with the payback maths. If you are about to hire someone, stay here. If you are building a budget, read that one too.

Price bands by workflow complexity

Complexity is not about how impressive the automation sounds. It is about how many systems it touches, how much state it has to hold, and how many ways it can fail. Those three things predict a price better than any description of what the workflow does.

Market-typical build fees by complexity, August 2026. Illustrative planning ranges, not quotes.
BandWhat it looks likeTypical build feeWhat should be included
Single-triggerOne event in, one action out. Missed call text back, a form submission routed to email and a sheet, an alert on a status change.Roughly $500-$1,500Working workflow, error notification, and a page of documentation. No state, no conditional branching.
SequencedOne trigger, several timed touches, and a stop condition. Quote follow-up, appointment reminders, invoice chasing.Roughly $1,500-$4,000A state table rather than wait nodes, every stop signal wired, quiet-hours guards, and a scheduled sweep that survives restarts.
Multi-systemThree or more systems reading and writing to each other, with conditional routing and reconciliation between them.Roughly $3,000-$9,000Authentication per system, idempotency so a retry does not double-write, mapping between mismatched data models, and a reconciliation report.
Conversational or AI-judgedA model classifies, drafts, or decides. Two-way text back, inbox triage, quote drafting from a description.Roughly $4,000-$15,000A grounded fact set, explicit escalation rules, a human review step, logging of every decision, and a review cycle after launch.

Two observations about that table. First, the bands overlap because the boundaries are blurry - a single-trigger workflow against a system with no API can cost more than a sequenced one against systems that both have good ones. Second, the "what should be included" column is where cheap quotes and fair quotes actually differ. Two people can quote a sequenced follow-up automation at $800 and $3,000 and both be honest, because one is selling you the happy path and the other is selling you something that still works in March.

The conversational band is the widest for a reason. Getting a model to produce a plausible reply is a day. Getting it to reliably refuse to invent a price, escalate the right conversations to a human, and never claim to be a person is the rest of the budget - and it is the part that determines whether the automation is an asset or a liability.

What builders actually charge per hour

Hourly rates are worth knowing even if you should not pay hourly, because they let you sanity-check a fixed quote against a plausible number of days.

Published marketplace figures as of 2026 put freelance n8n specialists broadly in the $40 to $100 per hour band, with senior builders bringing infrastructure, container, and AI orchestration depth quoted well above that, and vetted networks pricing higher than open marketplaces in exchange for screening. Those figures come from marketplace and hiring-guide sources, are largely self-reported, and vary by region more than by skill.

Indicative freelance rates from published 2026 marketplace and hiring-guide sources
Source of builderIndicative hourly rangeWhat you are really buying
Open marketplace, low vettingRoughly $30-$100Cheapest and most variable. Screening is on you, and handover quality is the usual casualty.
Vetted freelance networkRoughly $80-$150Technical screening done for you at a premium. Better floor on competence, no guarantee of domain understanding.
Senior specialist$125 and upInfrastructure, self-hosting, orchestration, and AI depth. Worth it when the workflow is genuinely hard, wasted when it is not.
AgencyEffective rates higher againParallel delivery and continuity, paid for through account management overhead you do not directly consume.

Multiply and check. A sequenced follow-up automation is usually two to four days of work for someone competent. At the middle of the freelance band that is a low four-figure number, which is exactly where the table in the previous section puts it. When a quote does not survive that arithmetic - in either direction - ask what they are assuming that you are not.

Whether a freelancer, a solo consultant, or an agency is right for you is a separate question from price, and consultant versus agency lays out the trade-offs properly. If you are at the stage of choosing a person rather than a price, how to hire an AI automation consultant has the questions worth asking.

What drives the number up

Five things, roughly in order of how much they move a quote.

1

The state of your data

This is the biggest one and the one most quotes omit entirely. If your contact records are duplicated, your job statuses are free text that four people spell differently, or half your invoices live in a second system, the automation will act on bad inputs. Cleanup is real work, it is frequently a meaningful share of first-project cost, and discovering it mid-build is how a fixed price becomes a renegotiation. Ask for it to be priced explicitly, even if the answer is that your data is fine.

2

Whether the systems have usable APIs

A system with a documented API and a ready-made node is close to free to integrate. A system with a real API but no node - Jobber's GraphQL API is the example we write about most - costs the extra hours of authentication and error handling that the Jobber and n8n guide walks through. A system with no API at all means screen scraping or a manual step, and it is the one answer that can make a project not worth doing.

3

How many ways it can fail

The happy path is a fraction of the work. What happens when the API is down, when a customer replies twice in ten seconds, when the workflow restarts mid-sequence, when a phone number is malformed, when the same event arrives twice. Each answer is code, and collectively they are the difference between an automation you trust unattended and one you have to check.

4

Compliance steps in the path

Some workflows carry a regulatory prerequisite that has nothing to do with the build. Any US SMS automation needs A2P 10DLC registration before a single message reaches a handset. The registration fees themselves are trivial, tens of dollars; the cost is the calendar time, the opt-in page and privacy policy work, and the resubmission if the campaign is rejected. Any builder who has not mentioned it has not done this before.

5

Who has to agree it is finished

One owner who can make a decision is the cheapest possible client. Three stakeholders with different ideas of done, a security review before anything touches live data, and a procurement process add real cost - not to the build, but to everything around it. The build effort for a single workflow barely changes with company size; the coordination around it changes a lot.

Where the $29 kit beats done-for-you

An honest section, because the pages that rank for this query all conclude that you should hire the person who wrote them.

For one narrow workflow, on tools you already pay for, when you have a few free evenings and you find this sort of thing satisfying, building it yourself is genuinely the right call. Our $29 starter kit exists for exactly that person, and the build guides on this site are free and complete - the Jobber, Housecall Pro, and follow-up guides give away the actual builds, not a teaser. Nothing about that is a loss leader we regret.

An honest split
Build it yourself whenPay someone when
The workflow touches one or two systems that both have good APIs.It touches three or more systems, or one with no node and an OAuth flow.
A failure is an inconvenience you notice the same day.A failure means a lost job, a double-charged customer, or a compliance problem.
Someone in the business genuinely enjoys this and will still be here in six months.Nobody will own it, and the person who built it is the person who is always on a job.
You want to learn how it works before you buy anything bigger.The time cost of learning exceeds the build fee at your own hourly value.
The data it reads is already clean.The first honest step is a data cleanup nobody in-house has time to do.

The middle row is the one that decides most cases. An automation is not a purchase, it is a small piece of software that needs an owner. If there is nobody to own it, a cheap build is expensive - and if there is someone who will, an expensive build is often unnecessary.

How to scope it so the quote is real

The difference between a quote that holds and one that gets renegotiated is almost entirely the brief. Twenty minutes of writing before you ask anyone for a number is the highest-return work in this whole process.

  1. Name the trigger precisely. Not 'when we get a lead' but 'when a quote's status changes to awaiting response in Jobber'. Vague triggers are where estimates go wrong.
  2. List every system it touches, and for each one write down whether it has a documented API and whether you have admin access. Missing admin access is a surprisingly common blocker.
  3. Write the definition of done as something observable. 'The customer receives a text within two minutes and the conversation appears on their record in the CRM.' If you cannot observe it, you cannot accept it.
  4. Describe the failure cases you care about. What must never happen? Duplicate messages, a wrong price, a message at 11pm. These are requirements, not edge cases.
  5. Say what you already pay for. A workflow built on tools you have is cheaper than one that introduces a new subscription, and any builder should tell you that rather than adding to your stack.
  6. Ask for the price to be fixed per scoped workflow, with the software costs itemised separately and billed to your own accounts.
  7. Agree handover in writing before work starts: you own it, it runs in your accounts, and documentation is part of delivery.

Then do the payback arithmetic yourself before you commit. Multiply the minutes the task takes by how often it runs, times the loaded hourly cost of whoever currently does it, to get monthly time saved in money. Add any revenue lost to delay - leads that go cold overnight are the big one for service businesses. Divide the build fee by that monthly figure. If the answer is more than about twelve months, you have picked the wrong workflow to start with, not the wrong builder.

If you would rather have someone else do the scoping, that is exactly what the free automation audit is - a ranked list of what is worth automating in your business, with no obligation to have us build any of it.

Quotes that should worry you

  • A price given before anyone asked what systems you run. That is a menu, not a quote.
  • No mention of what happens when something fails. The failure paths are most of the real work.
  • Software billed through the builder with a markup rather than to your own accounts. You should hold the credentials and the invoice.
  • No documentation in the deliverables. An automation nobody can read is a dependency on one person.
  • An automation you cannot export or edit, running on infrastructure you have no access to. That is a subscription described as a build.
  • A US SMS build with no mention of A2P 10DLC registration.
  • An AI step with no stated escalation rule, no grounded fact set, and no human review.
  • Refusal to name a fixed price after a scoping conversation. If it has genuinely been scoped, it can be priced.
  • A five-figure quote for a single-trigger workflow, which usually means agency overhead you are paying for but not consuming.

Read against that list, the ten-times spread in quotes stops being mysterious. The cheap quote is usually the happy path with your credentials in it. The fair quote includes the failure handling, the write-back, and the documentation. Both are honest descriptions of "an automation", and only one of them is still working in six months.

For sector-specific context on which workflow to commission first, the HVAC and plumbing and cleaning company pages rank the usual candidates by return, and automation services sets out how we scope and hand over work.

FAQ

How much does it cost to hire someone to build an n8n automation?
For a single well-scoped workflow with a clean trigger and two or three systems that all have APIs, market-typical build fees sit in the high hundreds to low thousands of dollars. A multi-step workflow with conditional logic, an AI step, and write-back into a CRM commonly runs into the mid four figures. Anything quoted below a few hundred dollars is either a template with your credentials pasted in or an underestimate that will be renegotiated. These are planning ranges observed across the market as of August 2026, not our price list.
What is the hourly rate for an n8n or Make developer?
Published marketplace figures as of 2026 put freelance n8n specialists broadly in the $40 to $100 per hour range, with senior builders who bring infrastructure, orchestration, and AI depth quoted considerably higher, and vetted-network rates sitting above general marketplace rates. Treat all of these as indicative: marketplace rates are self-reported, vary enormously by region, and say nothing about whether the person can scope your particular problem.
Should I pay hourly or a fixed price?
Fixed price per scoped workflow, almost always. Hourly billing puts all the estimation risk on you, and the discovery work that determines the estimate is precisely the part you cannot supervise. The honest exception is genuinely open-ended exploratory work, where nobody can scope it because nobody knows what it is yet - and in that case, buy a small paid discovery block first and get a fixed quote out of it.
Why do quotes for the same automation vary by ten times?
Because they are not quoting the same thing. One quote is a template wired to your credentials with no error handling, no state management, and no documentation. Another includes scoping your actual data, handling the failure paths, writing back into the system you already use, and handing over something you can maintain. Both are described as an automation. Ask what happens when the API returns an error and the two quotes will separate themselves immediately.
What is the difference between this and your AI automation cost page?
This page answers what it costs to hire someone to build one specific automation - the price of the build itself, hourly rates, and how to scope it so a quote means something. Our AI automation cost page answers the broader budgeting question for a small business: what four common workflows cost across build effort, tool subscriptions, and monthly running cost, plus the payback maths. Read this one if you are about to commission a build, and that one if you are working out an annual budget.
What ongoing costs come after the build?
Three separate things, none of which is the build fee. Platform subscriptions for the automation tool, usage-based AI model costs which for small-business volumes are usually modest, and optional maintenance. Insist these are billed to your own accounts rather than marked up through the builder, and get them itemised in the quote so a low headline build price is not concealing an expensive stack you are locked into.
Is a $29 starter kit really an alternative to paying someone?
For one narrow workflow, on tools you already pay for, when you have a few evenings and enjoy the work - yes, genuinely. The kit is the cheapest way to find out whether you are the sort of person who will maintain an automation. Where it stops being an alternative is when the workflow touches live customer data, when a failure costs you a job, or when nobody in the business will own it when it breaks in four months.
What does A8gent charge to build one automation?
We quote a fixed price in writing per scoped workflow after a free consult, and we do not publish package prices, because any number we published would be a guess at your systems and your data. Third-party software you pay for directly in your own accounts, so nothing is marked up. You own what we build, and documentation plus a recurring summary report is part of handover rather than an extra.

Done for you

Want a real number for your specific workflow rather than a range?

The free audit scopes what is worth automating in your business and ranks it by return. If you want us to build something after that, you get a fixed price in writing per workflow, and you own what we build.

The consult is free, and you keep whatever we build.

Related reading

Before you commission anything