Most business owners think setting up automation will take months. The reality is closer to 10 days from first conversation to fully working system. But those 10 days aren't all waiting — some of it's us building, some of it's you providing information, and some of it's testing together.
Here's exactly what happens at each stage, what you'll need to do, and what could make it take longer.
The Full Timeline: Day by Day
Day 1: Discovery Call (1 hour)
We talk through your current process. What's taking time? What's falling through the cracks? What's costing you money? We look at a week's worth of your inbox or client communication to understand the patterns. By the end of the call, we know exactly what needs automating and whether it's feasible.
Days 2-3: Voice and Tone Work (2-3 hours from you)
We pull examples from your sent emails to identify your communication style. Then we write AI prompts that replicate your voice. We send you test outputs and refine until you say "yep, that sounds like me." This step matters because if the automation doesn't sound like you, you won't use it.
Days 4-6: Build (mostly us, minimal input from you)
We build the workflows, connect them to your tools (Gmail, CRM, calendar), configure the AI classification logic, write the reply templates, and set up alerts. You'll need to provide API access to your systems, but otherwise this is hands-off for you.
Days 7-8: Testing (1-2 hours from you)
We run test emails through the system. New leads, client queries, supplier messages, junk. We check that classification is accurate, replies sound right, and alerts go to the right places. You review the outputs and flag anything that needs adjusting. We refine based on feedback.
Days 9-10: Handoff and Training (2 hours)
We walk you through how everything works. How to check logs, how to adjust reply templates, how to add new categories if your business changes. Then we hand over full admin access to all systems. From this point, it's yours. We're available for support but you control it completely.
What You'll Need to Provide
Access to your systems. We'll need read/write access to your Gmail or Outlook, your CRM (if you have one), and any other tools the automation connects to. This is temporary during the build. Once we hand over, you can revoke our access if you want.
Examples of your communication style. We'll ask for 10-15 real emails you've sent to clients. Sent folder screenshots work fine. This helps us write the voice prompts accurately.
Decision-making on edge cases. What should happen when an email doesn't fit a clear category? What priority level for different types of messages? These decisions are yours — we just implement them.
Time for testing and feedback. You'll need 2-3 hours spread across days 7-10 to review test outputs and confirm everything works as expected.
What Could Make It Take Longer
Unclear requirements. If you're not sure what you want automated, or requirements keep changing during the build, we'll need extra discovery time upfront. The clearer you are about the problem you're solving, the faster we can build the solution.
Access delays. If it takes a week to get API credentials or admin access to your systems, the clock stops until we have them. This is why we ask for everything upfront.
Complex integrations. If you're using niche software with limited API support, or you need the automation to connect to five different systems instead of two, build time extends. We'll flag this in the discovery call.
Excessive perfectionism on voice. Getting the tone right is important, but if we're iterating 10 times on reply templates instead of 3-4, it eats into the timeline. There's a balance between "sounds like me" and "good enough to start."
Can It Be Faster?
For very simple automations — say, just a quote follow-up system with no AI classification — yes, we can do it in 5-6 days. But most business automations worth building involve multiple workflows, AI logic, and voice customisation. Rushing those steps produces poor results.
The 10-day timeline exists because that's how long it takes to do it properly. Build, test, refine, verify. If someone promises you a custom automation in 48 hours, they're either cutting corners or using templates that won't fit your business.
What Happens After Day 10?
The automation runs independently. You own it, control it, and can modify it if needed. We provide 30 days of included support for bugs or adjustments. After that, support is available on-demand if something breaks or you want to add new features.
Most clients don't need ongoing support. The systems are stable, the tools are reliable, and the logic is straightforward enough that small tweaks can be made without technical help.
But if something does go wrong — an API changes, a tool updates and breaks the integration, or you want to add a new workflow — we're available to fix it. That's billed hourly, not as a monthly retainer.
The Bottom Line
10 days from kickoff to handoff. About 5-6 hours of your time spread across that period. The rest is us building and testing.
That's fast enough to see results quickly but slow enough to do it properly. Which is exactly what business automation should be: effective, owned by you, and running smoothly from day one.