Duration is set not by how much code is written but by how organized the data is and who needs to approve, and when. Even a simple task can stretch out as more approvers get involved.
When an automation project is proposed, the first question is usually "how many days will it take." There is no single right answer, because the real driver of duration is not how much code gets written. Two projects that look the same size can differ hugely — one done in a week, another in a month. The difference comes from data structure and the number of decision makers involved.
The three stages that set the duration
An automation project roughly has three stages: preparing data and rules, building the system, and testing plus approval. Quoted timelines usually cover only the build stage. Most of the time is actually lost in the first and last stages.
- Data and rule preparation. Building cannot start until it is clear where each piece of information lives and what counts as an exception.
- Build. The most predictable stage, where the flow is built to the defined rules.
- Testing and approval. The stage where real examples are tried and the relevant people sign off.
How data structure affects duration
If information sits in one place, consistently, the build moves fast. If the same information is scattered across files, in different formats, partly kept by hand, that mess has to be sorted first. We covered the preparation needed to bulk-import spreadsheets into a system in this article; the same logic applies to data preparation in automation projects.
In practice, most time is lost when a project assumes at the start that "the data is already clean," only to discover the mess halfway through. Reviewing sample data before the build starts is faster than backtracking later.
Number of decision makers matters more than lines of code
A flow that could technically be built in a few days can stretch for weeks as more people need to sign off. Each extra approver adds both decision time and the chance of a change request. That is why it matters, before starting, to clarify who decides what and in what order approvals happen.
A simple task with a single decision maker — say, an automatically generated report — can go live in a few days. A process touching several departments takes longer even with similar technical scope.
Building a realistic timeline
When asking for a duration estimate, ask about the three stages separately: how long will data preparation take, how long will the build take, how many days should be planned for testing and approval? A single number given without this breakdown usually reflects only the build stage and understates the real delivery date.
- Where does the data live today, and in what format?
- Are exceptions clear already, or will they surface during the project?
- Who approves, and in what order?
- Is real sample data ready for testing?
If these questions can be answered clearly, the quoted timeline will be close to reality. If the answers are unclear, so is the timeline — and the first step is not giving an estimate but resolving those unknowns.
Starting with a small scope shortens the timeline
Building a narrow version that covers one task first, rather than a broad automation in one go, both shortens the timeline and gives early feedback. We assessed which tasks suit this kind of staged rollout in which jobs are suited to automation. Starting small and seeing the result is more reliable than waiting for a large project to be delivered all at once.
Frequently asked questions
How fast can the quickest automation project go?
A simple project covering one repeating task, with organized data and a single decision maker, can go live in a few days. Scope and number of approvers stretch the timeline.
What stretches the timeline the most?
Usually not the code, but scattered data and a long approval process. Projects touching several people at different times can take weeks even when technically simple.
Why are duration estimates often unreliable?
Because the estimate usually covers only the build phase; data preparation, testing and approval are left out. A realistic estimate covers all three stages separately.
Is there a job that keeps repeating at your company? Tell us about it and we will build the tool that does it.
Tell us what you needOther articles
Does a small company need an AI budget?
The budget is not set by the size of the company but by how many hours a specific task wastes. A small company can also start with a single repeating task and a measurable budget.
23 September 2026Read →Who benefits from an appointment system?
An appointment system can help when customers need to reserve a time slot and arranging those slots by phone interrupts your work. First clarify service durations, shared resources and exceptions.
22 September 2026Read →What if AI makes things up?
A fluent answer is not verified information. A business tool needs more than well-written output: it needs a workflow that prevents actions based on incorrect or incomplete information.
22 September 2026Read →Can a spreadsheet with thousands of rows be entered into a system in bulk?
In most cases, yes. The hard part is not the entry itself but getting the data into the shape the system expects and verifying that every row was really saved. If the system offers no bulk route, the work goes through the screen, and that depends on the rules of that system.
21 September 2026Read →Why does preparing a quote take so long?
Writing the quote does not take long; the time goes into hunting for the price, copying and correcting an old quote, and rebuilding the layout every time. Once the price list sits in one place and the rules are written down, a quote comes out in minutes.
21 September 2026Read →Which jobs are suited to automation, and which are not?
The job best suited to automation is one that repeats often, whose rules can be written down and whose data is already digital. Work that needs judgement, is full of exceptions or has its data on paper needs another step first.
18 September 2026Read →What if the AI assistant on your site gives a wrong answer?
The risk is real, but manageable. An assistant's wrong answer usually comes from guessing about something it does not know. The solution is to draw a clear line from the start around what the assistant knows and does not know, and to have it hand over to a person when it does not know.
18 September 2026Read →Is ranking in Google the same as being mentioned by AI?
Partly. Both draw on the same foundation, but they do not reward the same thing: Google ranks a page, while AI reads several sources, writes an answer and decides for itself who to mention in it.
17 September 2026Read →Why doesn't ChatGPT mention my company?
The reason is rarely “the AI does not like us”. Usually it is a technical block, scattered company information, or the company not being mentioned anywhere else online. All three can be fixed.
17 September 2026Read →What should your site have so AI describes you correctly?
When AI describes a company, it uses the clearest sentences it finds on the site. The list below goes page by page through where those sentences should sit, how they should be written and the markup machines will read.
17 September 2026Read →What is GEO? Being visible in AI answers
GEO (Generative Engine Optimization) is the work of making sure that when ChatGPT, Gemini, Perplexity and Google's AI Overviews answer a question, they find your business, describe it correctly and cite it as a source. It does not replace SEO; it builds on top of it.
17 September 2026Read →Will an AI tool learn my company's data?
Short answer: not in a tool running through a commercial API. But that answer depends on how the setup was done, so it is worth knowing what goes where.
16 September 2026Read →When does a spreadsheet stop being enough?
Excel is not a bad tool; it handles most jobs and more. The problem is carrying on with it for months after the point where it stopped being the right fit.
16 September 2026Read →Off-the-shelf software or custom-built?
The right answer depends on how specific the work is to you. Work that everyone does the same way is cheaper off the shelf; work you do your own way is cheaper built for you.
16 September 2026Read →