How Long Does a Custom Automation Take to Build for a Small Business?
A typical custom automation for a small business takes two to four weeks to build, once the job is clearly scoped. If the problem still needs finding, add about a week for an audit first. You should be able to use something real from the first week, not wait a month for a big reveal.
Here is how that time breaks down, and what makes it longer.
Week zero: finding the right job
If you already know what you want, this is short. A call, a written scope and a fixed price.
If you do not, it is worth paying for the problem to be found properly. My AI Audit takes about a week and costs £297. You get one bottleneck costed in hours, three ideas in priority order with rough prices, and a written roadmap. Then you decide whether to build.
Skipping this step is the most common reason automations take longer than they should. Building the wrong thing quickly is still slow.
Week one: something you can use
The first week should end with a working piece, even if it is small. A draft reply appearing in your inbox. A quote landing in a folder for you to check. Something real you can try on real work.
This matters. It shows whether the idea works before more money goes in, and your feedback shapes the rest of the build.
Weeks two and three: the full flow
This is where the remaining parts get connected. The edge cases get handled. The tool learns your wording and your rules. You use it on daily work and point out where it gets things wrong.
Week four: handover
For bigger builds, the last week is testing, tidying and handing over. You get the accounts in your name, a short written guide, and an alert set up so you know if anything stops working.
Smaller builds finish earlier. Some take two weeks from start to handover.
What makes it take longer
Waiting for access. If logins, plan upgrades or a supplier's permission take a week to arrive, the build waits a week.
A scope that keeps growing. Adding "one more thing" each week is the quickest way to turn three weeks into eight. Write the extras down and do them as a second job.
Messy data. If prices live in someone's head and customer records are in four spreadsheets, some tidying has to happen first.
Software without proper connections. Older systems can need workarounds, which take longer to build and test. See will a custom AI tool work with my existing software.
After it is built
Expect it to settle in over the first month as real work throws up cases nobody thought of. I check in at six weeks to see what is working and what needs adjusting. How long until AI actually saves you time covers that settling in period.
Quick answers
How long does a custom AI automation take to build?
For most small business jobs, two to four weeks once the job is scoped. Add about a week if the problem needs finding first through an audit.
Can I use it before it is finished?
You should be able to. A good build gives you something working in the first week, so you can test it on real work and shape the rest.
What slows a build down?
Waiting for logins or plan upgrades, a scope that keeps growing, messy data and older software without proper connections.
How long does an AI audit take?
Mine takes about a week and costs £297 fixed. You get the main bottleneck costed in hours and three ideas in priority order with rough prices.
Get a timeline for your job
Tell me the job on a free 20 minute call and I will give you a realistic timeline. Prices are on work with me, and more on the AI consultant page.
The 5 Step AI Roadmap for Small Businesses
The order I actually work in when somebody asks me to help, written so you can do it yourself if you would rather. Five steps, no jargon, including the step where the honest answer is that you do not need me.
I read every answer myself, and it only goes to me. Unsubscribe whenever.