What does automation cost for a small business?
By Aaron Melton,
Automation cost is set by scope, and scope should be set by payback. A first project is scoped to one defined process with a defined return, so you know the cost and the expected payback period before work starts. Fully custom systems are affordable for a small business today because AI-assisted engineering has cut the cost of building them.
Why we do not publish a price list
Two businesses can ask for "an email automation" and need completely different things: one needs a rule that files attachments, the other needs an agent that reads technical inquiries and drafts replies from a parts list. Publishing one number would mislead one of them. What we publish instead is how the number is arrived at, so you can check our reasoning.
What drives the cost of a build
- Scope. One process, or several? The single biggest driver.
- Integration effort. Platforms with good APIs are quick to connect. A system with no API needs a custom bridge, which is real engineering time.
- Data condition. Clean, consistent source data is cheap to build on. Data that needs cleaning first adds a phase.
- Review requirements. A step that needs a human approval screen costs more than a step that runs unattended, and is sometimes the right call anyway.
- Ongoing support. Systems need an owner. We offer ongoing support, and it is a line item, not a surprise.
How payback sets the scope
Before we quote, we want to know what the process costs you today: how often it runs, how long it takes, and what an hour of the person doing it is worth. That gives a monthly cost of doing nothing. We size the build so the payback period is short, usually under a year, and we tell you the expected payback along with the price. If a process cannot clear that bar, we recommend against automating it. Our free ROI calculator runs the same arithmetic, with a sensitivity table, so you can check a project before you ever talk to us.
Why custom is affordable now
A few years ago, custom software was out of reach for most small businesses, so the only option was a subscription bent around your process. AI-assisted engineering has changed that. We still do the work properly, with version control, tests, and documentation, but the hours required to build a well-scoped tool have fallen enough that a system built for your process is often cheaper over two years than a subscription that almost fits.
Starting small is normal
The typical path is one workflow, proven in production, then expanded. For a medical products distributor, the first work was CRM intake: deduplication, assignment, and pipeline hygiene at roughly 4,500 new leads a month. Sales-agreement vetting and daily retry sweeps came as the relationship grew. Each phase had its own scope and its own payback.
The entry point
If you are not sure which process to start with, the readiness assessment is a fixed-fee engagement that produces a ranked backlog with the payback reasoning written down. The fee is scoped on the discovery call. If we then build together, you start from a plan instead of a guess.