What automation really costs a small business in 2026, and how to scope yours

This post gives you the ranges other firms publish (with who said it and when), what the tools themselves charge today, a two-minute way to see what the manual version costs you now, and a one-page sheet to fill in before anyone quotes you.

One thing up front. We are Buzzy Automation, a two-person shop in Dallas, and we build this kind of thing. We do not list prices for it, because a number before the plan is a guess. Everything below is a vendor's own page, another firm's published number, or our opinion, marked as such.

The short answer

First, what is the manual version costing you?

Price the problem before you price the fix. Take one task you do by hand. Count the minutes it takes, how many times a week you do it, and what an hour of your time (or your staff's) costs you. Multiply by the weeks a year you work. That is what the task costs you now, and it is the number every quote should be measured against.

We built a small calculator that does that maths on your numbers and nothing else. It has no invented defaults, so it cannot flatter you. The result shows on the page, and there is no sign-up.

A made-up example, to show the maths only: 20 minutes, four times a week, at $40 an hour, for 49 weeks, is about $2,600 a year. Against that, a $1,500 build with $30 a month in tools is about $1,860 in year one and $360 a year after. Against a $6,000 build, the answer is different. That is the whole point of doing the sum first.

The 4 ways to automate, and what each costs

Do it yourself with Zapier or Make

Zapier and Make connect apps you already use: a form to a spreadsheet, a new order to a text message. You drag boxes. No code.

What their pages say, as of 2026-09-22:

• Zapier (zapier.com/pricing): Free, 100 tasks a month. Professional, $19.99 a month billed yearly or $29.99 billed monthly, from 750 tasks a month. Team, $69 a month billed yearly or $103.50 billed monthly, from 2,000 tasks a month.
• Make (make.com/en/pricing): Free, up to 1,000 credits a month. Core $12 a month, Pro $21, Teams $38, each shown for 10,000 credits a month. The page has a monthly-or-yearly switch and says yearly billing saves "15% or more".

A "task" or a "credit" is one small action, like adding one row. Count how many you would burn in a month before you pick a plan.

The real cost is your evenings, and the day it quietly stops because one app changed something. Nobody is on the hook but you.

Run n8n yourself

n8n does the same kind of job, and you can run it on your own server. The self-hosted Community Edition is free (n8n.io/pricing, as of 2026-09-22). On the same page, n8n hosts Starter for you at 20 EUR a month billed yearly, for 2,500 runs, and Pro at 50 EUR, for 10,000. Business (667 EUR, for 40,000 runs) is self-hosted.

Free software is not a free system. You pay for the server, the updates, the backups, and the morning you lose working out why it stopped. If you enjoy that kind of thing, this is the cheapest route by far. If you do not, it is the most expensive.

Hire a freelancer

For one clear job, a freelancer is often the best value. On rates, Ad Snipper (a firm that sells outsourced automation staff, so read its numbers with that in mind; article updated 2026-07-01) reports $40 to $100 an hour for mid-level n8n freelancers on Upwork, and $125 to $250 or more an hour for senior specialists. We have not checked those rates ourselves.

Three things to check: can they show you a build that is still running six months on? Will you hold every login? What happens after they move on? A good freelancer answers all three without flinching.

Hire an agency or consultant

An agency costs more and should bring more: someone who scopes it, builds it, tests it, and picks up the phone when it breaks.

The bands below are each firm's own published numbers, not ours.

• QBS Global (2026-06-27) reports $1,500 to $8,000 for a single automation, about $3,000 to $5,000 for a basic package, and $25,000 and up for a multi-system overhaul. By the hour, $75 to $150 for no-code work and $175 to $300 for custom AI work.
• Builts AI (published 2026-02-09, updated 2026-04-07) reports $3,000 to $5,000 for a single process, $5,000 to $10,000 for a multi-step build, and $10,000 to $15,000 and up for a full overhaul.
• Clutch (updated 2026-09-21) reports that US agencies most often list $50 to $99 an hour, and that custom software projects reviewed there most often cost $10,000 to $49,999. That last band is software in general, not small automations. Treat it as a ceiling, not a floor.

These numbers tell you the shape of the market, not what your job will cost. Ours works like this: one fixed price, in writing, before work starts, and you own everything we build. The steps are on how it works, and the reason there is no price list is on pricing.

What makes the price go up

Five things move a quote more than anything else.

1. How many systems it touches. Two apps is an afternoon. Five apps, one of them a spreadsheet only Dave understands, is a project.
2. Exceptions. "Every order goes to the sheet, except rush orders, except Joe's, except on Fridays." Each "except" is a branch that has to be built and tested.
3. Messy data. Names typed three ways, phone numbers with and without dashes, "the usual" in an email. Cleaning that up is most of the work.
4. Approvals. If a person has to say yes before something sends, that is a screen, a notification, and a record of who said yes.
5. Steps that use AI. Turning a voicemail into text, or sorting messages by what they want, works well but never perfectly. So it needs a check step and a way to fix mistakes. That adds cost, and it should.

If a quote looks high, ask which of the five it is. A good builder can point to the line.

The costs after launch

The sticker price is the start. QBS Global (2026-06-27) reports that the advertised price is often only "20 to 40 percent of the true first-year cost". Whether or not that figure fits you, three bills keep coming.

• Tool fees. The monthly plans above, plus per-message charges for texts and calls.
• Apps change. Every few months one of the apps you connected changes how it talks to the others. What worked on Monday fails on Tuesday, and someone has to notice.
• Who fixes it at 7 a.m. When it breaks on roast day, or the morning of the big job, who do you call? Get the answer in writing before you sign, whether it is "me", "the freelancer", or "the agency, and here is the number".

Cheap up front with nobody on the hook is not cheap.

Is there already an app for that?

Often, yes. Before anyone builds anything, run this five-question test.

1. Does an off-the-shelf app do 80% of it? If yes, buy it. The last 20% may not be worth a build. For a store, Shopify's own plans as of 2026-09-22 are Basic $39 a month ($29 billed yearly), Grow $105 ($79) and Advanced $399 ($299) (shopify.com/pricing). A lot of "automation" is already inside a plan like that.
2. Would you have to change how you work to fit the app? A little is fine. A lot means the app is running you.
3. Can you leave? Can you get your data out in a form another tool can read?
4. What does it cost at three times your size? Per-seat and per-contact prices climb fast.
5. Does the app know your exceptions? If your business runs on "except", a fixed app will fight you every day.

Three or more "no" answers and you are in build territory. Fewer, and you should buy the app and get on with your day. If a cheap app fixes it, you keep your money, and we would rather you remember us for saying so.

Scope it on one page before anyone quotes you

Most bad quotes come from a fuzzy ask. Fill this in first and every quote you get will be closer, cheaper, and easier to compare. Copy it.

ONE-PAGE SCOPE

Task name:
What starts it:            (a text arrives / a form is sent / 9 a.m. every Monday)
The steps, in order:
  1.
  2.
  3.
Systems it touches:        (email, the store, the spreadsheet, the books)
Every "except":
Who gets told, and how:    (owner by text / staff by email / customer by reply)
What "done" looks like:    (the order is on the list with the right size and day)
What happens if it fails:  (who is told, and what they do)
Who owns the logins:       (me, and here is where they are kept)
How often it runs:         (times a day / a week / a month)

Hand this to anyone quoting. If they never ask about the "except" line, ask why.

A real example: orders from everywhere into one list

Here is the sheet filled in for a job we get asked about most: a roaster whose wholesale orders arrive by text, voicemail and email, and get typed into a spreadsheet by hand.

• What starts it: a text, an email or a voicemail lands on the business number or inbox.
• The steps: the message lands in one place. Voicemails get written out as text. Each message becomes a draft order with the customer, the coffees, the sizes, the grinds and the day they want it. The owner glances, fixes anything wrong, and approves. The approved draft becomes a real order in the store.
• Systems: the phone number, the inbox, the online store.
• Every "except": "the usual" with no details. A rush order. A café that never confirms.
• Who gets told: the owner, by text, when a draft is waiting. The café gets a "got it" from the owner's own number.
• Done: the order is on the list with the right grind and the right day, and nothing was typed twice.
• If it fails: the owner is told the same morning, and the message is still in the inbox, so nothing is lost.
• Logins: the owner's, in a password manager the owner controls.

Where the money goes: the voicemail-to-text step, and "the usual". The rest is joining pipes.

The honest note: we have not built this one for a client yet. The full write-up is on orders come in from everywhere. What runs today is our own company: about twenty small automated jobs run Buzzy, from catching leads on this site to a daily check that the rest are still working (our own count, September 2026). The closest client work is the Barista Plus store, a Dallas roaster with a wholesale enquiry form. That store has not opened to the public yet, so there are no order numbers to show you.

Questions to ask anyone you hire

Six questions, and the answer you want.

1. Is the price fixed and in writing before work starts? Yes. Hourly with no cap means the risk is all yours.
2. Do I own the automations, the code and every login? Yes, in your accounts, not theirs.
3. What happens when it breaks at 7 a.m.? A name, a way to reach them, and what it costs.
4. What is not included? A clear answer is a good sign. "Everything" is not.
5. Can I see one you built that is still running? Even a small one.
6. If a cheap app fixes this, will you tell me? Watch their face.

Our answers are on how it works. Hold us to them.

Questions people ask

How much does it cost to automate a business process in 2026?

Other firms report about $1,500 to $8,000 for a single automation built for you (QBS Global, 2026-06-27) and $3,000 to $5,000 for a single process (Builts AI, updated 2026-04-07). Doing it yourself in Zapier or Make runs from free to about $30 a month in software (the vendors' pages, 2026-09-22), plus your time. Your real number depends on how many systems it touches and how many exceptions you have.

What is the cheapest way to automate a small business process?

Usually a setting in an app you already pay for that you have not turned on. After that, a free Zapier or Make plan for one simple hand-off. Cheapest in cash is not always cheapest in hours, so run the calculator first.

Is n8n really free?

The self-hosted Community Edition is free to use (n8n.io/pricing, 2026-09-22). You still pay for a server and for the time to keep it running. The hosted version starts at 20 EUR a month billed yearly.

Zapier or n8n: which costs less for a small business?

For one or two simple jobs at low volume, Zapier's Free plan or the $19.99 Professional plan (billed yearly, 2026-09-22) is hard to beat, and there is no server. Once you run many jobs, or many runs a month, n8n's flat plans or a self-hosted copy usually cost less per run but need more skill. That is our opinion. Price the hours, not just the plan.

Is it cheaper to buy an app or build a custom automation?

Buy, if an app does 80% of it and you can live with the rest. Build when your work runs on exceptions no app knows about. The five-question test above settles most cases.

What hidden costs come with automation?

Monthly tool fees, per-message charges for texts and calls, fixes when an app changes, and the hours someone spends checking it still runs. QBS Global (2026-06-27) reports the advertised price is often only 20 to 40 percent of the first-year cost. Budget for the rest.

How long does a small automation take to build?

It depends on the scope sheet more than the build. In our experience a simple two-app hand-off in Zapier is an afternoon for someone who has done one before. A build with approvals and exceptions takes weeks, and most of that is scoping and testing, not building. We do not publish timelines for work we have not scoped. You get a written plan before a price.

If I hire someone, do I own the automation?

You should. Ask before you sign. With us, yes: the code, the accounts and every login are yours, and you can leave with all of it.

Rather talk it through? Book thirty minutes.