How long does an automation build take?
A small build of two or three automations takes days. A GoHighLevel setup takes 5 to 7 business days for a small account, 2 to 3 weeks for a medium one and 3 to 4 weeks for a large build with AI agents. Custom software takes longer: our nine published builds took between 5 and 10 weeks each.
The GoHighLevel timelines are the ones on our GoHighLevel setup page. The custom software figures come from our own case studies, where each client-approved page states how long the build took. The biggest factor in every range is not the build itself; it is how quickly access, decisions and content arrive from your side.
How long do different kinds of builds take?
The build type sets the range. Fixing one process is quick, because it touches one workflow and one or two tools. A whole CRM system takes weeks, because pipelines, calendars, forms, texting registration and training all have to fit together. Custom software is measured in weeks to a few months, because it is designed, built and tested from scratch.
Our published custom software builds
Typical build times in working days
| Build | Typical time | What decides it |
|---|---|---|
| Small build (2 to 3 automations) | Days | Access to the tools and one agreed process |
| GoHighLevel setup, small | 5 to 7 business days | One pipeline and core automations |
| GoHighLevel setup, medium | 2 to 3 weeks | Several pipelines, calendars and integrations |
| GoHighLevel setup, large with AI agents | 3 to 4 weeks | AI scripts, testing and consent handling |
| Custom software | 5 to 10 weeks in our published builds | Scope, number of user types, integrations |
For custom work, the build plan is set after discovery; our custom software page explains the stages. For AI agents specifically, see AI agents.
What slows a build down?
Most delays come from waiting, not building: waiting for logins to existing tools, for the texting registration to be approved, for a phone number to port, for someone to decide how a process should work, or for content such as prices and service descriptions. Each wait adds days that no amount of build speed can recover.
- Texting approval: A2P 10DLC campaigns take up to about three business days with fast-track; see our A2P registration guide.
- Number porting: two to four weeks for under 50 numbers, running in parallel with the build; see keeping your business number.
- Data migration: cleaning and importing years of contacts; see CRM migration.
- Decisions: who gets which leads, what counts as qualified, what the reminders should say.
- Integrations: an outside system with a slow or limited API.
What happens week by week in a typical setup?
A medium GoHighLevel setup usually runs in three stages over two to three weeks: agree the plan and get access in the first days, build and connect everything in the middle, then test with real scenarios, train the team and go live at the end. Registration and porting run in the background from day one.
A medium setup, stage by stage
- Start: written plan approved, logins shared, A2P registration and any port submitted.
- Build: pipelines, calendars, forms, workflows and integrations built and connected.
- Test: every path run with a test contact: new lead, booking, reschedule, no-show, opt-out.
- Launch: team walkthrough, go-live, and the six months of included maintenance begin.
Can a build be done faster?
Yes, by shrinking the first release, not by skipping testing. Launch the part that loses you the most money first, such as missed-call text-back or reminders, in days, then add the rest in a second phase. Skipping tests saves a day and usually costs a week of fixing live mistakes.
That is the approach behind a small build at about $1,000; prices are in how much an automation project costs. For larger custom builds, the Spirit Airlines group travel platform took 10 weeks and the Coo marketplace took 6.
What can you do to speed up your build?
Most of the time you can save is on your side of the project. Share logins on day one, start texting registration and any number port immediately, decide who handles which leads before the build starts, and give feedback on messages within a day. Each of these removes a wait that the build cannot work around.
- Access: admin logins to the CRM, phone system, domain registrar and any tool the build connects to.
- Registration: legal business name, EIN and a live website with a privacy policy, so A2P can be submitted on day one.
- Port documents: a recent phone bill and the account PIN if you are keeping your number.
- Routing rules: who gets which leads, and what happens after hours.
- Content: services, prices, hours and the questions an AI agent should answer.
- One decision-maker who can approve messages and test results quickly.
Questions about build timelines
When does the timeline start?
When the written plan is approved and access to your tools is shared. Before that, nothing is scheduled.
Does texting work on day one?
Only once the A2P campaign is approved. That is why we submit registration at the very start, so it is ready by launch.
How long does custom software take to reach a first version?
Our nine published custom builds took 5 to 10 weeks each. Larger products are delivered in releases after the first version.
Will my business be disrupted during the build?
No. We build alongside what you run now and switch over at launch. Phone numbers keep working during a port.
Sources and further reading
- Autoesta case studies, build durations as published on each case study page (Coo, DEMP, Farmers Market Haul 6 weeks; Our Fusion, GoHangars 7; Drop My Drip, HirePrep 8; ITS 5; Spirit Airlines 10).
- HighLevel, A2P 10DLC fees and fast-track review, updated September 24, 2026.
- HighLevel, porting timeline, updated September 3, 2026.
