Claude implementation

Claude, set up properly for your whole team.

Most businesses buy a few AI seats and hope for the best. We pick the right Claude plan, put the guardrails and data controls in place, connect it to the tools you already use, and train every person on it. Two weeks, start to finish.

A typical rollout

Most engagements look like this. The variables are your team size, whether your IT policy calls for Enterprise, and which systems Claude needs to see.

Three things a good rollout gets right.

Buying the seats is the easy part. The value comes from what sits around them.

01

The right plan and settings

Team is right for most businesses. Enterprise earns its price when you need single sign-on across a directory, audit logs, or custom data retention. We choose with you, then set up the workspace, roles and permissions so people can only see what they should.

02

Guardrails and data controls

A short usage policy your team will actually read: what can go into Claude, what can't, and how to handle customer data. Configured in the workspace, not just written down, and checked against GDPR and any sector rules you work under.

03

Connected to your work

Claude is far more useful when it can see your calendar, files and email. We connect the tools you already run on, set up shared Projects for the jobs your team does most, and write the instructions that make Claude answer like your business.

Two weeks, start to finish.

Days 1 to 2

Discover

We sit with each team for an hour and list the jobs that eat time: drafting, summarising, chasing, reporting. That list becomes the training plan.

Days 3 to 5

Configure

Plan chosen, workspace built, SSO and permissions set, usage policy written and applied, connectors switched on and tested with your data.

Days 6 to 8

Build Projects

A shared Project for each recurring job, loaded with your templates, tone and rules, so anyone gets a good answer first time.

Days 9 to 10

Train and hand over

Two half-day sessions by role, a one-page guide per team, and a 30-day check-in to see what stuck and what to add.

What each part of the business gets.

Everyone uses the same tool. The Projects and training are different for each role.

Owners and managers

A weekly brief drafted from your numbers, meeting notes turned into actions, and first drafts of the letters, proposals and policies you keep putting off.

Front of house

Replies to enquiries in your tone, appointment and quote follow-ups, and answers to the same twenty customer questions without hunting through files.

Finance and admin

Invoice chasers, supplier emails, summaries of contracts and terms, and spreadsheets explained in plain English before you send them on.

Sales and marketing

Proposals, case studies and social posts built from your own material, and research on prospects before a call.

Team or Enterprise? Usually Team.

QuestionClaude TeamClaude Enterprise
How many people?From five seats; suits most businesses up to around 150Larger seat commitments, custom-priced
How do people sign in?Google or Microsoft single sign-onAny SAML identity provider, with SCIM to add and remove users automatically
Do you need an audit trail?Standard admin controlsAudit logs, role-based access and a compliance API
Data retentionDefault retentionCustom retention, including shorter windows
Is your data used for training?NoNo
When we recommend itNearly every business we work withRegulated sectors, or when your IT policy requires directory-based access and audit logs

Plan details and prices are set by Anthropic and change; we confirm the current terms at claude.com/pricing during discovery. Seat costs are paid to Anthropic directly and are not included in our fee.

Questions people ask

We already have a few Claude seats. Can you start from there?

Yes. Most rollouts begin with an existing workspace. We audit what's there, tidy the permissions, add the policy and Projects, and train the people who haven't yet picked it up.

Will our customers' information be used to train Claude?

Anthropic states that content on its business plans is not used to train its models. We still write a policy on what customer data should go in, and configure retention to match, so you're covered by practice as well as terms.

Why not just let people use the free version?

Free and personal plans sit outside your control: no shared workspace, no admin, no way to remove access when someone leaves, and different data terms. A business plan brings it under one roof with one invoice.

Do we need IT to be involved?

For Team on Google or Microsoft, usually not; an owner or office manager can approve the sign-on. Enterprise with SAML and SCIM needs whoever manages your identity provider for about an hour.

What happens after the two weeks?

You own the workspace and everything in it. The 30-day check-in is included. After that, most clients either move on to agents, where Claude becomes part of a wider setup, or keep us on hand for questions and new Projects.

Give your team Claude, done properly.

Forty-five minutes to see whether a rollout would pay for itself in your business.

Book a call