Ask "what does automation cost?" and most of the internet answers with a sales call. Here's the actual number: at Harbor Tree, workflow automation projects land between $750 and $3,500, quoted as one fixed figure before any work starts. This piece unpacks what sits inside that range, what pushes a project toward either end, and the back-of-envelope math for deciding whether it's worth it at all.
- where single-workflow projects typically start
- $750
- the top of the typical range — a full multi-workflow build
- $3500
- when the first working workflow usually ships
- 1 week
What the money actually buys#
An automation project isn't "install software." The work splits into three parts: mapping (a working session to find where your hours actually go — often the most valuable hour of the project), building (wiring the workflows across your existing tools and testing them against real cases), and handover (plain-language documentation plus a walkthrough, so nothing is a black box and your team runs it without us). If a quote you're comparing skips the mapping or the documentation, that's the gap the cheap price is hiding in.
| Project size | Typical range | What it looks like |
|---|---|---|
| One workflow, done right | $750 – $1,200 | A single high-leverage chain — say, form inquiry → instant reply → lead filed → you notified — built, tested and documented |
| A connected handful | $1,500 – $2,500 | Three or four workflows sharing plumbing: intake, booking, reminders, invoice nudges, wired across your email, calendar and invoicing tools |
| The full starter kit | $2,500 – $3,500 | The whole seven-workflow kit across multiple tools, with a weekly summary, review asks and handover training |
What moves the number#
Two things, mostly. How many workflows, obviously. Less obviously, how many tools they touch — connecting a form to your email is an afternoon; threading data through a form, a CRM, a calendar, an invoicing system and a text-message provider is real plumbing. Tool quality matters too: modern software with good connections automates cheaply, while that one legacy system everyone hates usually costs more to wire around than everything else combined. We'll tell you which one yours is on the discovery call.
How a quote gets built
Map where the hours go
A working session walking through your week: every repeated motion, who does it, how long it takes, what it costs when it gets dropped. Most owners are surprised by the list.
Rank by leverage
Each candidate workflow gets a blunt score: time saved × frequency × cost-of-dropping-it, against effort to build. The top of that list is your project scope; the rest is a roadmap for later.
One fixed number
You get a one-page plan and a single quote covering everything in it, approved before work starts. The quote is the contract — if you want more later, that's a new conversation, never a surprise line item.
The ROI arithmetic#
Skip the consultant math; use a napkin. Count the hours you (or staff) spend weekly on motions a machine could do — intake, follow-ups, reminders, chasing invoices. Five hours a week at even $40/hour is over $10,000 a year in time, before counting the inquiries that go cold because a reply went out late — usually the bigger number, as the speed-to-lead data shows. Against that, a $2,000 build that permanently deletes most of those hours pays for itself in months, then keeps paying. Automation is one of the few purchases where the boring math is the persuasive part.
Automation is one of the few purchases where the boring math is the persuasive part.
If you're not sure what's worth automating in your business yet, start with our seven-workflow starter kit — it's the menu most projects get scoped from. And if your website itself is the bottleneck feeding the machine, that's a different fix: see why your website isn't getting you leads.