How long does AI automation take to implement?
Short answer
A first automated workflow should reach production in 2-4 weeks. Longer usually means discovery is being sold as a phase rather than done in days. Large transformation programmes genuinely take quarters, but you should not need one to automate your first process — and you should not fund one before seeing a single working result.
What the weeks are actually spent on
Week one is diagnostics: mapping how the process runs today, where the hours go, and which candidate has the best ratio of value to integration pain. This is analysis, and it takes days, not months.
Weeks two and three are the build — connecting the systems, writing the logic, wiring the human approval steps. Week four is pilot on real traffic, correction, and handover with documentation. That last week is the one vendors quietly skip; it is also the one that decides whether the automation survives a year.
What genuinely makes it take longer
Four things, and none of them are the AI. Legacy systems with no API, where integration means screen automation or an export-import bridge. Data that has to be cleaned before anything can run on it. A process nobody owns, so no one can approve how it should behave. And internal approval chains — security review, legal, procurement — which are often the single largest block of calendar time.
The honest version: a vendor cannot promise four weeks without knowing which of these apply. That is what diagnostics is for.
The question to ask before signing
Ask exactly this: what will be running in production four weeks after signature? A vendor building automation will answer with a process name. A vendor selling consulting will answer with a phase name.
If the answer is "a roadmap" or "the discovery output", you are buying a document.
Related questions
Can AI automation be done in a week?
A single-system task with clean data, sometimes. Anything crossing two or more systems will not be properly tested and handed over in a week, and skipping those steps is what produces automation nobody trusts three months later.
Why do large consultancies take months?
Because they are usually selling a different product: an organisation-wide programme with discovery, strategy, governance, and a change-management workstream. That is legitimate work at enterprise scale. It is the wrong shape for automating one process.
What slows projects down most often?
In our experience, internal approvals and unclear process ownership — not engineering. Naming one internal decision-maker before the project starts is the cheapest schedule insurance available.
Diagnostics is the part that decides whether four weeks is realistic for your process. It is free and takes fifteen minutes.
Start free diagnostics