Many Irish firms already have staff using Claude on their own accounts. Moving to a company rollout means a business plan, one IT approval, shared projects and training on real work.
A request we now hear most weeks goes like this: "We already use Claude individually. We want to set it up properly for the company and train people to use it well."
That is a good place to start from. People have found it useful on their own, so the question is no longer whether Claude helps. The question is how to move from a handful of personal accounts to something the business owns, controls and gets consistent value from.
Here is what changes, in the order it usually needs to happen.
1. The accounts move from personal to business
Personal Claude accounts belong to the person, not the firm. On the individual Free, Pro and Max plans, each person decides in their own settings whether their chats may be used to improve Claude, and the business has no view of what is in them. If staff have been pasting client material into personal accounts, that is the first thing to stop.
Claude Team and Claude Enterprise come under Anthropic's commercial terms. Anthropic may not train its models on your content, your firm is the data controller and Anthropic acts as processor under its Data Processing Addendum. Team runs from 2 to 150 seats, with monthly or annual billing, single sign-on and central control over connectors. Enterprise adds audit logs, SCIM user provisioning, a Compliance API and custom data retention, and has a 20-seat minimum.
For most Irish firms of 10 to 100 people, Team is the right starting point. Our Claude pricing guide works through what a 20-person team pays on each plan.
2. One approval from your IT provider
Most of the value people want from a company rollout comes from connecting Claude to Microsoft 365, so it can read their email, files and Teams conversations. That needs one approval in your Microsoft tenant, usually by your IT provider.
The approval is short. A Global Administrator grants consent for Claude's Microsoft 365 connector once, and can limit it to a pilot group. The connector acts as each signed-in person, so it reaches only what they could already open. Administrator rights stay with your IT provider.
The step people skip is a review of over-shared SharePoint sites before anyone connects. Claude will find anything a person can open, including folders shared more widely than anyone intended. Microsoft search and Copilot have the same exposure, and the fix is the same.
AI at Work, part of Acuity, has written the steps out for your IT provider in what your IT provider needs to do to connect Claude to Microsoft 365. You can forward it as it is.
3. Shared projects replace private prompts
When people use Claude on their own, the good instructions live in one person's head or one person's chat history. A company rollout is the chance to write them down.
A Claude project holds instructions and reference documents that a whole team uses. Pick two or three pieces of recurring work, such as a monthly report, a standard client letter or a tender response, and set up one project for each. Write the instructions in plain language: who the work is for, what a good result looks like, which documents to use and what to check before anything goes out.
This is where most of the gain in consistency comes from. A new starter gets the same quality of help as the person who figured it out.
4. Training on the work, not on the tool
Firms that roll Claude out with a login and a link to Anthropic's help pages usually find, three months later, that a few enthusiasts use it well and everyone else uses it like a search box.
Training works when it uses the firm's own kind of work. People bring a real document, a real email thread or a real report, and leave with something finished and checked. They also learn where Claude needs watching: figures that must be traced back to the source, drafts that read well but miss a condition, and anything that goes to a client.
A half-day workshop for up to 20 people covers this for most teams. Our Claude training courses set out the formats, from a team workshop to Claude Code for developers.
5. A short written policy
Keep it to a page. It should say which plan staff use and that personal accounts are not for work, which information may and may not go into Claude, who approves new connectors, and who checks consequential outputs before they leave the firm.
If you already have an AI policy, add a Claude section rather than writing a new one. Our AI governance advice covers the wider policy work.
What a sensible first month looks like
- Week 1: buy Claude Team in the firm's name for a named group, and close any personal accounts being used for work.
- Week 2: your IT provider reviews SharePoint sharing, approves the Microsoft 365 connector and limits it to the group.
- Week 3: set up two or three shared projects for recurring work, then run a half-day workshop on those tasks.
- Week 4: check what people are using it for, fix the project instructions that are not working and decide whether to widen the group.
For a firm that already has people using Claude, this usually takes a month rather than a quarter. The tool is already familiar. What the rollout adds is ownership, consistency and a clear line on what is checked before it goes out.
If the rollout is part of a wider change to how the firm works, our independent AI consultancy covers the workflow and governance side as well as training.
If you are at this point, tell us about your team and we will suggest a plan and a fixed fee.