Three ways to start with Claude
Most businesses start with one team. Some already have Claude and want a particular piece of work done better. Once Claude is in place, some want help keeping it current. Below is what each one includes, how long it usually takes and what we need from you.
We reply to arrange a short call. You don't need to know which plan or setup you want before you get in touch.
The three options
A one-team rollout gets Claude working for one group. Workflow implementation builds specific pieces of work on a setup you already have. Ongoing support keeps it working as people, tasks and Claude itself change.
- 1One-team rollout
Claude set up and connected for one team, with a small number of agreed workflows, training, and a review a few weeks later.
- 2Workflow implementation
Specific workflows built on a Claude setup you already have, such as a tender response, a monthly reporting pack or a document review.
- 3Ongoing support
Keeping Claude useful once it is in place: new staff, changes to Claude's models and features, new workflows and a periodic review.
Option 1
One-team rollout
Claude set up and connected for one team, with a small number of agreed workflows, training, and a review a few weeks later.
FeesFees agreed after a short scoping call
- Who it suits
- A business starting with Claude. Usually one team or a senior group, such as partners and directors, or a finance or bid team, with recurring work that involves a lot of reading, searching and drafting.
- What is included
- Advice on the Claude plan and number of seats for the first group.
- Setting up your Claude organisation: members, roles, and the settings that control data and connectors.
- Connecting Claude to Microsoft 365, or to the other systems you use where Claude has a connector, with your IT provider's approval.
- A small number of agreed workflows, built as shared projects with instructions and reference material, so the team starts from your conventions.
- Hands-on training on those workflows, with written steps each person keeps.
- A review with the team a few weeks after training, and a short written record of how everything was set up.
- Indicative timeline
- Typically four to six weeks from the first call to the review. Most of that time goes on agreeing the workflows, arranging your IT provider's approval and leaving the team time to use Claude before we come back.
- What you provide
- A sponsor who can make decisions about the team, the workflows and the budget.
- Your IT provider's approval of the Claude connector in your Microsoft 365 tenant. We write the instructions for them.
- Sample work for each workflow: past documents, templates or anonymised examples we can build and test against.
- Time from the team for training, and one or two people who will test the workflows before everyone else.
- At the end
- You own the Claude organisation and licences from day one. At the review we agree what to keep, what to change and whether to extend to more people. You receive the setup record and the written steps, and your IT provider gets a copy of the connector settings for their documentation.
Option 2
Workflow implementation
Specific workflows built on a Claude setup you already have, such as a tender response, a monthly reporting pack or a document review.
FeesFees agreed after a short scoping call
- Who it suits
- A business that already has Claude Team or Enterprise and knows which piece of work it wants Claude to handle better. Also suits a team that finished a rollout and wants to add a further workflow.
- What is included
- A working session with the people who do the task now, to map the steps, the sources they use and what they check.
- The workflow built in Claude: project instructions, reference documents, and skills or connectors where the task needs them.
- Testing on your sample material, with the team checking the output against what they would have produced.
- A short training session for the people who will run it, and written steps covering what to check before relying on the result.
- Indicative timeline
- Typically two to four weeks per workflow, depending on how much sample material exists and how quickly the team can test it.
- What you provide
- A named owner for the workflow who will use it and judge whether it works.
- Sample work: several past examples of the finished output and the material they were made from.
- Access to your Claude organisation, given by your Claude owner, so we can set up the project and any connectors.
- Your IT provider's approval if the workflow needs a connector that is not already in place.
- At the end
- The workflow sits in your Claude organisation and belongs to you. The owner has the written steps and knows how to update the instructions when the task changes. We hand over a short note describing how it is built.
Option 3
Ongoing support
Keeping Claude useful once it is in place: new staff, changes to Claude's models and features, new workflows and a periodic review.
FeesFees agreed after a short scoping call
- Who it suits
- A business using Claude across one or more teams that wants someone to keep the setup current, without building that knowledge in-house.
- What is included
- Setting up and training new starters on the workflows their team already uses.
- Checking your workflows when Anthropic changes Claude's models or features, and adjusting instructions where results change.
- Building new workflows as needs come up, within an agreed amount of time each month or quarter.
- A periodic review of what is used, what is not, and whether seats and plans still fit.
- A named contact for questions from your team and from your IT provider.
- Indicative timeline
- Agreed monthly or quarterly, usually after a rollout or workflow implementation.
- What you provide
- A contact in your business who tells us about new starters, leavers and new requests.
- Continued access to your Claude organisation for the work we agree.
- Your IT provider's involvement for any change to Microsoft 365 permissions, as before.
- At the end
- Each review ends with a short written summary of what changed and what we recommend next. If support stops, everything we built stays in your Claude organisation with its written steps.
Claude subscriptions are separate
Your business subscribes to Claude directly with Anthropic and pays Anthropic for it. Our fees cover our work only.
Keeping the two apart means the licences are in your name from the start, you can see exactly what the software costs, and our advice on plans and seats is not tied to anything we sell. We take no reseller margin or referral fee from Anthropic.
Anthropic publishes its current plans and prices on its Claude pricing page. Most businesses use Claude Team or Claude Enterprise, which come under Anthropic's commercial terms. How Anthropic handles data on commercial plans.
The two plans are priced differently: Team has a usage allowance for each seat, while Enterprise bills all usage at Anthropic's API rates on top of the seat fee. Claude Team or Claude Enterprise: which does a business need? compares them. If you already have either plan, see Claude training for teams, including sessions on building and sharing skills.
What happens when you get in touch
We reply to arrange a short call. On the call we talk about who would use Claude, the work they do and how your IT is looked after.
After the call we suggest which option fits, and send a short written proposal setting out the scope, timeline, what we need from you and the fee. Nothing starts until you agree it. If Claude is not the right fit for the work you describe, we say so.
You don't need to know which plan or option you want before you get in touch. To see how the setup itself works, read connecting Claude to Microsoft 365 or what your IT provider needs to do.
Questions we are often asked
Are Claude licences included in your fees?
No. Your business subscribes to Claude directly with Anthropic and pays Anthropic for it. Our fees cover the setup, workflows, training and support we provide. Anthropic publishes its current plans and prices at claude.com/pricing.
Which way should we start?
If you do not have Claude yet, a one-team rollout. If you already have Claude Team or Enterprise and a specific task in mind, a workflow implementation. Ongoing support usually follows one of the two. We suggest one after a short call.
Do we have to use Microsoft 365?
No. Microsoft 365 is the most common setup among the businesses we work with, but we also connect Claude to other systems where Anthropic or the system's provider offers a connector, such as Google Drive, Gmail and Google Calendar, or Slack.
What does our IT provider need to do?
Usually one approval: an administrator consents to Claude's Microsoft 365 connector in your tenant and can limit it to the people taking part. We send them written instructions, and they keep administrator rights throughout.
Talk to us about where to start
Tell us who would use Claude and what they work on. We'll suggest a time for a short call.