How long does a business automation project take?

Question

VX-N · Accepted Answer

The first deliverable — a written plan, a mock, or a working demo — lands within 24 hours of the first call. Full builds are scoped from there; a well-defined SMB system is typically weeks, not months, and payback on a properly scoped project usually lands inside two to six months. Timelines stretch for one reason more than any other: the scope was never written down, so it kept moving. A plan that says what is being built and what is explicitly not being built is worth more than an extra developer. The 'not being built' half is the load-bearing half — every project that ran twice as long as quoted got there through additions that each seemed small at the time. The parts that take the time are rarely the parts anyone expects. Building the happy path — the workflow when everything goes right — is fast now. What consumes the calendar is the edges: what happens when the API is down, when the record is a duplicate, when the customer replies to the automated email with a question, when two systems disagree about a field. A builder who quotes only the happy path will deliver on time and then spend the next two months delivering the actual project as 'fixes'. Waiting is the other hidden schedule item, and it is usually on the client side: access to accounts, API credentials, a decision about which of two conflicting processes is the real one, sample data that reflects reality rather than the ideal. A useful discipline at kickoff is to list every input the builder needs from you with a date beside it — projects where that list exists run close to plan, and projects where it does not stall in week two for reasons that look like the builder's fault and are not. AI has genuinely compressed the build itself — work that was quoted in months now ships in weeks, because the code, the tests, and the documentation are produced with AI in the loop. What it has not compressed is deciding what to build, which is why the fast firms front-load that decision into something concrete immediately. If a proposal quotes you months before anyone has seen how you work, that is a scheduling estimate, not an engineering one — and if its first milestone is a document rather than something running, the timeline is already wrong.