The week-by-week shape
A productised setup follows a fairly consistent shape. It starts with a short setup session, usually on the fit call and just after, to capture how you work, your tone, and the two or three jobs you want handled first. The foundation goes in quickly after that: the private record of how your business runs, the self-updating memory, and drafts learned from your own writing. In practice the first automations are drafting real work within the first week, on real examples from your business rather than toy demos.
The weeks that follow are not more building. They are fine-tuning: teaching it your edge cases, sharpening the tone, and personalising each job until the drafts are ones you would send yourself. That is what turns something that works into something you trust, and it is why handover lands at two to three weeks rather than one.
If you begin with a Bottleneck Audit, add about a week for that up front. It is time well spent: you arrive at the build with the scope already decided and the right problem in the crosshairs, which usually makes the setup itself quicker than starting cold.
Why most AI projects take months
Most AI projects run long for reasons that have little to do with the technology. The scope gets invented as they go, people weigh in at every stage, and generic tools have to be bent to fit a workflow they were never built for. Industry-wide, IDC found in a 2025 study for Microsoft (The Business Opportunity of AI) that most generative AI deployments go live in under eight months - and that figure is weighted by large enterprises with sign-off at every step. A small business working from a defined menu does not carry that weight, which is why the timeline is measured in weeks, not months. The lesson is not that faster is always better. It is that most of the delay in AI projects comes from indecision and scope creep, both of which a fixed menu removes before the work begins.
What speeds it up, and what slows it down
A few things move the timeline within that window. It goes faster when you can give access to the accounts it needs without a fortnight of back-and-forth, when decisions get made quickly, and when your business is already reasonably documented. It slows down when access is tangled, when every choice waits on a busy week, or when the process lives only in your head and has to be drawn out first. None of these are dealbreakers. They just decide whether you land at the fast or the slow end of the two to three weeks.
What "done" actually means
Done is not a switch-on date. It means the foundation is in place - the business brain, the self-updating memory, and drafts in your voice - and the automations you chose are built, tested, and running with your approval. You have been trained to use it, and it is handed over as something you own outright. From there it is yours to run, not a project you are still waiting on. See the full menu of automations.
After it is live
Once it is live, the system keeps itself current. A short daily wrap-up updates its memory of your business, so it sharpens with use rather than going stale, and a weekly health check quietly flags anything that has stopped or drifted. If you take the optional care plan, that covers maintenance and improvements - upkeep, not rent. Either way the system keeps working, because you own it. Most owners add an automation or two over the following months, once they have seen the first ones earn their place, but that is your call on your timeline, not a queue you are stuck in.