How long does it take to automate a business process?

For most SME work the range is a few days to several weeks. Where a specific project lands has less to do with the technology than people expect.

The rough shape of a timeline

Days. One system, clear rules, no ambiguity. An email responder that drafts replies and flags urgent messages. A round-robin that distributes new leads across the team and posts to Slack. A follow-up that fires when a proposal goes quiet.

One to two weeks. Two or three systems, some data transformation, a review step. Extracting structured data from invoices and writing it to a database. Reading CVs and matching candidates against open roles.

Several weeks. A portal, a product, or a reporting pipeline that has to be right every day. We built an SDR reporting workflow pulling from Salesforce, Aircall and Google Sheets, with custom attribution logic and daily collection designed around API limits. That is not a two-day job, and pretending otherwise is how projects fail.

The two things that actually cause delays

Access. Nothing can be built against a system we cannot reach. Waiting on an admin to provision an API key or approve an OAuth app routinely costs more calendar time than the build itself. Sorting access before kickoff is the single biggest thing a client can do to compress a timeline.

Undefined process. “Automate our onboarding” is not a specification. When three people in the business each describe the process differently, the disagreement has to be resolved before anything can be built. This is genuinely useful work, and it is often the most valuable part of an engagement, but it is not free.

Why we scope before we quote

We start with your actual workflow rather than a generic AI roadmap, because the audit is what makes the estimate real. Looking at where time and money leak tells us what to build. It also occasionally tells us not to build anything, because the process should be removed rather than automated.

Getting to live faster

• Pick one process, not five. A narrow first build proves the integration path and de-risks everything after it.
• Name one decision-maker who can settle process questions without a committee.
• Have credentials and admin access ready on day one.
• Accept a version one that handles the common case and escalates the rest to a human. Chasing every edge case before launch is what turns a two-week project into a two-month one.