Enterprise automation roundups aren't written for your 8-person shop

If you have eight people and no IT department, the "best enterprise automation platforms" roundups are the wrong shopping list — here's the list that fits, plus what a first build actually costs.

Those lists answer a question you didn't ask

The genre is easy to spot. n8n's guide to enterprise workflow automation and its roundup of DevOps automation tools are both well-made pieces of writing — and the titles tell you who they're for. Enterprise. DevOps. Those are job functions, and if you had them on payroll you wouldn't be reading a blog post about whether to automate your quote follow-ups.

Our read, stated plainly as opinion: these roundups are written for a buyer who has colleagues. Someone to run a security review. Someone who owns the platform after launch. A budget process that treats a recurring software subscription as a line item rather than a decision you make at 10pm. Score a tool against that reader's needs and you get a shortlist that is genuinely good — and, in our view, genuinely irrelevant to a shop where the person evaluating the software is also the person who'll be fixing it on a Saturday.

The mismatch isn't about company size for its own sake. It's that the enterprise checklist optimizes for coordination problems you don't have, and ignores the single constraint that we think dominates everything you do.

The constraint nobody models: one person owns every workflow

In most businesses this size — this is our experience, not a survey — the automation has a bus factor of one. The owner or the office manager built it, understands it, and is the only person who will notice when it quietly stops firing. Nobody is paged. Nothing is on-call. If it breaks in March, you might find out in May when a customer asks why they never heard back.

That single fact rewrites the evaluation criteria. Raw scale doesn't matter the way the roundups assume — the throughput ceilings they compare sit far above the volume an 8-person shop will ever push through. Role-based permissions don't matter much when there are three logins. What matters is whether a busy non-engineer can understand, trust, and switch off the thing they built six months ago.

Four questions that replace the enterprise checklist

1. What breaks, and who hears about it? Every workflow needs a failure path that ends at a human phone. Not a dashboard you'll never open — a text or an email that says "the Tuesday follow-ups didn't send." If a tool can't do that in one step, it's a worse fit than a clunkier tool that can.

2. Can someone who didn't build it read it in ten minutes? Name every step in plain English. Write a one-page runbook: what this does, what it touches, how to turn it off. Ten minutes of documentation is the difference between an asset and a haunted house.

3. Does it survive the vendor? Your data should land somewhere you own — a spreadsheet, a database, your CRM — not only inside the automation tool. The honest test: if the platform raises its price next year, how many hours does it take you to leave?

4. Does it pay back inside a year at your real volume? Not at the volume in the case study. At your fourteen-jobs-a-week volume. This is where we'd kill most small automation projects, and where we think most owners don't.

A worked example (hypothetical — swap in your own numbers)

Every number below is invented to show the structure. It is not from a client, a benchmark, or a survey. Use the method, not the digits.

Say you're an 8-person specialty contractor. Your office admin re-types job details from the website form into the scheduling tool and then again into invoicing. Fourteen jobs a week, six minutes of re-typing each: 84 minutes a week, call it 1.4 hours. At a $28/hour loaded cost, that's about $39 a week — roughly $170 a month, or $2,040 a year.

Now price the fix. A build like that costs real money, and tooling isn't free. If the build is $2,400 one-time and the tooling is $60/month, you're at $3,120 in year one against $2,040 of recovered time. It doesn't pay back in year one. With $60/month of tooling continuing, it crosses break-even somewhere around month 22 — assuming nothing changes.

That's the automation most owners start with, because it's the one that annoys them daily. We'd argue it's the wrong one.

Now the second lever, same hypothetical business. You send out nine quotes a week and follow up on them when you remember. Average ticket $1,900, gross margin 40% — about $760 of gross profit per won job. Same build cost: $2,400 plus $60/month, so $3,120 in year one.

You don't need to guess the conversion lift. Just compute the break-even: $3,120 ÷ $760 = 4.1 extra jobs a year, out of roughly 470 quotes sent. You know your business well enough to judge whether consistent two-day and seven-day follow-ups would win you four more jobs out of 470. If the answer is obviously yes, build it. If you're unsure, it's a no — and you've saved yourself $3,120 and a weekend.

That break-even calculation is the whole method. Enterprise roundups can't do it for you because it depends entirely on your ticket size, margin, and volume.

What we'd build, and what it costs

For the quote-follow-up version, here's the actual scope we'd propose:

• A single intake point — web form or email parser — that writes every lead to one place you own.
• A follow-up sequence: day 2 and day 7, email or SMS, pausing the moment the customer replies or the job is marked won.
• A daily digest at 7am: new leads, quotes with no reply, anything that errored overnight.
• A kill switch: one toggle that stops all outbound messages, because the day you need it you won't want to debug.
• A one-page runbook and a 20-minute walkthrough recording for whoever inherits it.

As of late 2026, our typical build price for a scope like that is $1,800–$3,500 depending on how messy the existing systems are, plus roughly $40–$120/month in tooling (automation platform, form, SMS credits — the SMS line is what moves). Those are our own numbers for our own work, quoted at that date; other shops will price differently, and tooling costs change.

What we would not build first: the re-typing automation. It's the loudest pain and, on the math above, the worse return. Five workflows that save typing lose to one workflow that touches revenue.

Read the enterprise roundups anyway — just steal selectively

There's real value in those guides. Take the operational discipline: logging, error handling, a plan for what happens when an API changes, keeping credentials out of individual people's personal accounts. Those concerns are correct at eight people and at eight thousand.

Skip the governance chapters, the approval hierarchies, and anything that compares throughput ceilings. You are not going to hit a throughput ceiling. You are going to hit the ceiling of one tired person's attention, which is a different problem entirely — and we'd solve it with fewer workflows, clearer names, and a text message when something fails.

Do this in the next 30 minutes

List every repetitive task that costs you time or money. For each one, write two numbers: the annual value at your real volume, and your honest guess at build plus tooling cost for year one. Rank by ratio, not by irritation. Then build exactly one — the top one — and leave the rest alone until it's working and documented.

If the top item's ratio is below 1, that's a legitimate result. Not automating is a decision, and it's free.

---

Before you commit a dollar: our AI Readiness & ROI Calculator is a free five-minute assessment that projects your return over 24 months, so you can see where a first build lands before you buy anything.