Guides

A 30-day AI rollout plan for a UK SME, from decision to first measured win.

By Zain M · 5 October 2026 · 12 min read

A UK SME can go from decision to a measured first win in 30 days. Days 1 to 5: choose the plan (Claude Team, ChatGPT Business or Copilot, by the work), buy it, connect single sign-on, adopt the one-page policy, cancel personal accounts, and start measuring the baseline of one process. Days 6 to 12: build the shared templates, run a session for the two teams with most to gain, and scope the first automation. Days 13 to 25: the automation goes live with a person deciding; the remaining teams get their sessions; the owner shares what they use it for. Days 26 to 30: compare the process against its baseline, survey who is using what, and decide the second process. The cost is a few pounds a seat plus a first implementation at £4,000 to £15,000 if the process needs a build.

Days 1 to 5Buy, set up, policy, baseline
Days 6 to 25Templates, sessions, first automation
Days 26 to 30Measure and decide

Before day one: the three decisions

Which tool. Claude Team for a firm that writes, advises and builds; ChatGPT Business for a general or creative workforce; Microsoft 365 Copilot for people whose day is email, meetings and SharePoint. Many firms buy two and split seats by role; the business plans cost about £15 to £19 a seat a month and are not exclusive. Which process. The one with the most volume and the most retyping, chasing or reading, because it is where the baseline is easiest to measure and the return most visible. Who owns it. A senior person who will use the tool in the open, not IT and not the supplier.

Days 1 to 5: set up and baseline

Buy the plan on the firm’s domain. Connect single sign-on to Microsoft 365 or Google Workspace so access follows the directory. Enter the VAT number so the invoice is reverse-charged. Adopt the one-page acceptable-use policy with examples and send it with the logins. Cancel the expensed personal accounts the same week, and record the provider as a processor with the DPA reference. Start counting the chosen process: units per week, hours per unit, time to first action, rework rate, cost per unit. The baseline runs for two weeks and nothing is built until it exists.

Days 6 to 12: templates, first sessions, scope

Build two or three shared projects or custom GPTs on the firm’s own documents: the proposal template, the client-letter tone, the standard replies. Run a ninety-minute session for each of the two teams with the most to gain, on their own work, ending with an artefact they keep. In parallel, scope the first automation: if the process can be handled inside the assistant with a template and a person, do that; if it needs to read documents, write to a system or run unattended, it is a build, and the discovery step produces the written scope, the acceptance threshold and the fixed price.

Days 13 to 25: live, with a person deciding

The automation runs on real inputs with a named person still deciding anything that affects a customer or an individual. The four metrics are measured weekly and the AI running cost per unit is read from the provider invoices. The remaining teams get their sessions. The owner shares, in the open, what they used the tool for that week and what went wrong, because the failures teach more than the successes. Anyone still on a personal account is moved. If the process needed a DPIA, it was written in the scoping step and the measures in it are now visible in the system.

Days 26 to 30: measure and decide

Compare the process against its baseline on all four metrics, with the running cost included. Read the active-seat report from the admin console and survey each team on which tasks they use the tool for. Then decide three things: extend, change or stop the first automation; which process is second; and which seats to upgrade or drop. Write the numbers down and share them with everyone. A firm that ends day 30 with a measured saving on one process, a policy staff have read and most seats in use has done more than most of the firms in the adoption surveys.

DayMilestoneOwner
1 to 2Plan bought, SSO connected, VAT number enteredOwner and IT provider
3Policy adopted and sent with logins; personal accounts cancelledOwner
3 to 16Baseline measured on the first processProcess owner
6 to 9Shared templates builtOwner with one person per team
8 to 12Sessions for the first two teams; first automation scoped and pricedTrainer, supplier
13First automation live, person decidingSupplier and process owner
13 to 25Weekly metrics; remaining sessions; owner shares in the openOwner
26 to 30Comparison, seat report, survey, decision, numbers sharedOwner and board

What it costs

Seats at about £15 to £19 a month each on Claude Team or ChatGPT Business, or £16.10 for Copilot Business on top of Microsoft 365. Training from £1,200 for a half-day session. A first automation at £4,000 to £15,000 fixed if the process needs a build, with the running cost stated per feature before go-live, or nothing beyond the seats if a template and a person cover it. The audit, at £2,500 to £6,000 and credited against a build, does the baseline, the scoping and the data position for firms that would rather it was done for them.

Common questions

How long does it take to roll out AI in a small business?

Thirty days from decision to a measured first win, if the sequence is followed: set up and baseline in the first week, templates and sessions in the second, the first automation live with a person deciding through the third and fourth, and a measured decision at the end.

Which AI plan should a UK SME buy?

Claude Team for firms that write, advise and build; ChatGPT Business for general or creative work; Copilot for Microsoft 365-centred desk work. Many firms buy two and split seats by role. Never personal accounts.

What should we automate first?

The process with the most volume and the most retyping, chasing or reading, because its baseline is easiest to measure and the return most visible within a month.

Do we need a supplier for the rollout?

Not for the seats, the policy and the templates, which a firm can do itself. For a build that reads documents, writes to systems or runs unattended, yes, at a fixed price with the running cost stated.

What does a 30-day rollout cost?

Seats at about £15 to £19 a month, training from £1,200, and a first build at £4,000 to £15,000 if the process needs one. Many firms spend only the seats and the training in month one.

How do we know it worked?

A measured saving on one process against a two-week baseline, most seats active in the admin console, and nobody left on a personal account.

Want the thirty days run for you?

We set up the plan, adopt the policy, build the templates, run the sessions and deliver the first automation with its baseline measured, at a fixed price.

Start a conversation →