Every business owner asks the same question before committing to an AI rollout: how long is this actually going to take? The honest answer depends less on the technology and more on how many people need to agree on how it gets used. A sole trader in Sydney can be running Claude inside a week. A 200-person financial services firm in Melbourne with APRA obligations might need three months before the first workflow goes live. Neither timeline is wrong. They are solving different problems.
Solo operators and small teams: days, not months
For a business under ten people, a Claude rollout is mostly a decision, not a project. There is one person who owns the budget, one person who uses the tool, and usually no procurement process to navigate. Most solo operators and small teams we work with in Sydney and Brisbane go from first conversation to daily use inside five to ten business days. The bulk of that time goes into picking the right entry point, a Claude Team plan, a Cowork setup, or a narrow automation like invoice chasing, and connecting the two or three tools that actually matter: email, a calendar, and whatever accounting software the business runs on.
A fixed-fee Cowork setup for a business this size runs around $3,500 and typically produces a working automation by the end of the first week. The constraint here is rarely technical. It is whether the owner can carve out ninety minutes across two sessions to walk through their actual workflows instead of sitting through a generic demo.
Mid-size businesses: four to eight weeks
Once a business crosses roughly ten to fifty staff, a rollout stops being a single decision and becomes a small project with real dependencies. There is usually more than one stakeholder, an operations lead, a finance person, sometimes an external IT contractor, more systems to connect, and a genuine need to define who is allowed to use Claude for what. We typically see a working pilot in two to three weeks, followed by another four to six weeks of refinement before the tool is trusted enough to touch client-facing work without a human checking every output.
Waiting on IT or an external managed service provider to approve new connectors, particularly for email and CRM access.
No single owner, so decisions about scope bounce between two or three people for weeks.
Underestimating how much existing process documentation is missing, so the first two weeks become discovery rather than build.
Treating the pilot as the finished product instead of budgeting time to fix what breaks in week three.
None of this is a Claude problem specifically. It is the standard shape of any operational change inside a growing business. The rollouts that move fastest have one person with the authority to say yes to a workflow without escalating it, and a realistic budget, often in the $8,000 to $15,000 range for a mid-size engagement covering setup, training, and the first round of fixes.
Regulated and enterprise businesses: two to six months
Financial services firms, healthcare providers, and anyone with APRA, AUSTRAC, or Privacy Act obligations should plan for a longer runway, and that is appropriate. A rollout at this scale usually needs a security review, a data handling assessment, and sign-off from a risk or compliance function before the first real workflow goes live. We have run enterprise engagements that reached a working pilot in six weeks and others that took closer to five months, with the difference almost entirely explained by how mature the client's existing governance process was going in. A business that already has a vendor risk assessment template moves fast. A business building that process from scratch as part of the AI rollout does not.
The good news is that most of this work only has to happen once. After the first workflow clears security review, the second and third move considerably faster because the governance groundwork is already in place. On one Sydney engagement, the gap between workflow one and workflow two shrank from twelve weeks to under three.
What actually determines your timeline
Strip away the size bracket and three factors do most of the work in predicting how long a rollout takes: how many people need to sign off, how messy the existing systems are, and whether there is a single accountable owner for the project. A twenty-person business with a clean tech stack and one decision maker can move faster than a five-person business split across three founders who disagree on scope. Timeline estimates are a proxy for organisational clarity, not a measure of how complicated the AI itself is.
If you want a realistic timeline for your own business rather than a generic bracket, the fastest way to get one is a short scoping conversation. Book a slot and we will tell you, honestly, whether you are looking at a week or a quarter.
