Claude Code and Cowork for non-technical UK teams: setup, connectors, governance and cost

A Claude workspace for a non-technical team is not a terminal on the founder's laptop. It is a Team or Enterprise tenancy with Claude Cowork as the everyday surface, Claude Code reserved for the one person who maintains the shared setup, connectors to the firm's systems on the least access each workflow needs, and a set of written files, the organisation instruction, the role prompts, the project seeds and the skills, that outlast whoever wrote them. Get the allocation right and a five-person firm has a working installation inside a week. Get it wrong and the pattern is familiar: licences bought, two people enthusiastic for a fortnight, a subscription nobody opens by month two.

This guide is for the managing director, founder or operations lead of a UK firm of roughly five to one hundred staff who has decided on Claude and now needs five questions answered in order: which surface non-technical staff should use, which plan to buy and what it costs in sterling, whether the accounting, CRM and email systems are safe to connect, what to do when IT says no, and who should set it up and what they should leave behind. Every vendor fact below was checked on 15 September 2026 against Anthropic's UK pricing page and Help Center, Xero's and HubSpot's own documentation, and Anthropic's Privacy Center; the sources are listed at the end. Our earlier guide to setting up Claude for a business as a stack describes the layers; this one is about the decisions around them.

Should non-technical staff use Claude Code or Claude Cowork?

Cowork, in almost every case. Both surfaces run the same agentic engine: Claude takes a multi-step task, works through files and connected systems, and produces finished output rather than a reply. The difference is the shell around it. Claude Code runs in a terminal or the desktop app and expects its user to manage a working directory, grant file and command permissions, and read what the agent did. That is the right fit for a developer, a technical operator or the person who maintains a repository of context files, and the wrong fit for an account handler, a finance manager or a recruiter. Cowork removes the terminal: the person describes an outcome, Claude works through the files, projects and connectors it has been given, and they approve before anything is sent, posted or changed. Anthropic's Help Center lists Cowork as available on every paid plan, on desktop for macOS and Windows and, in beta, on web and mobile.

The most-upvoted answer to "is Claude Code worth learning for a small business owner" on the largest Claude community forum is, in short, use Cowork, it was designed for you. The threads that go the other way describe firms that handed Claude Code to staff without a plan: no arrangement for review, ownership, access or support, and in one case a codebase broken twice by non-technical users. Neither is an argument against Claude Code. Both are arguments for giving it to the right person.

That person exists in every firm that runs Claude well: the founder, operator or technical lead who will maintain the organisation instruction, the role prompts, the project seeds and the skills library. That maintenance is code-shaped work, files in folders with versions, and Claude Code is the best tool for it. Everyone else gets chat with Projects for everyday drafting and analysis and Cowork for delegated, recurring work once the workflow and its boundaries are written down. On Team and Enterprise an Owner can switch Cowork on or off for the whole organisation, decide separately whether sessions may run in Anthropic's cloud (on by default on Team, off by default on Enterprise), and control whether members may skip per-task approval for write-capable connector tools, which is off by default. Our comparison of Claude Projects, Skills, Code and Cowork covers the allocation surface by surface.

Which plan should a five to twenty person UK firm buy, and what does it cost?

For a firm of that size the answer is Claude Team unless a specific obligation forces Enterprise, and the reasons are administrative rather than about the models. The individual plans, Free, Pro and Max, have no organisation-wide administration: no central billing, no organisation instruction, no admin control of connectors, no usage analytics, and a model-improvement setting on each personal account that is on unless someone turns it off. A firm running five staff on five Max accounts has five separate privacy settings to police and no way to see what any of them are doing. Team fixes all of that at a lower price per seat.

The figures below are Anthropic's own, taken from the UK render of claude.com/pricing on 15 September 2026. The page shows sterling prices to a UK visitor and states, in its own words, "Prices include 20% VAT". We quote that line rather than interpret it. Anthropic's Help Center says Team plans require a minimum of two members, support up to 150 seats, and allow standard and premium seats to be mixed. Enterprise is priced per seat plus usage at API rates, is billed annually, and carries seat minimums that differ by purchase route; our Team versus Enterprise guide sets those out.

Configuration	Published UK price per seat	Monthly	Annual
5 Team standard seats, annual billing	£18	£90	£1,080
5 Team standard seats, monthly billing	£22.50	£112.50	£1,350
10 Team standard seats, annual billing	£18	£180	£2,160
10 seats: 8 standard plus 2 premium, annual billing	£18 and £90	£324	£3,888
20 Team standard seats, annual billing	£18	£360	£4,320
5 Max seats at the published entry price	From £90	£450	£5,400
5 Pro seats, annual billing	£15 (£180 billed up front)	£75	£900
Enterprise	£18 plus usage at API rates	Annual billing; usage varies with models and tasks; seat minimums apply

Three things follow. Five Max seats cost five times as much as five Team standard seats and give up the whole admin layer, so Max is an individual power-user upgrade, not a team plan. Team's premium seat serves the two heavy users in a ten-person firm without moving everyone to usage-based billing: eight standard and two premium seats come to £324 a month against £180 for ten standard. And the context window on the plan page is 200k on Team and 500k on the default model on Enterprise; the 1M figures belong to the API model specifications, not to a subscription. Our sterling cost guide shows the working behind these figures.

What forces Enterprise at this size is a short list, and it is worth naming so nobody promises it on Team. Both Anthropic's pricing page and its Help Center place audit logs, SCIM provisioning, the Compliance API and custom data retention controls on Enterprise only. If your IT lead, your regulator or a client contract requires any of those, buy Enterprise and configure it as part of the install. If not, Team is the plan, and the Team-to-Enterprise migration path exists for later.

Is it safe to connect Claude to Xero, HubSpot and Google Workspace?

Safe enough for most UK SMEs, provided you treat the scope of each connection as the decision rather than the connection itself. Three facts from Anthropic's Help Center apply to every connector on Team and Enterprise. An Owner enables a connector for the organisation, and until then nobody can use it. Enabling it grants nobody access: each person authenticates individually, and Claude inherits that person's permissions, so someone who cannot see a record in the source cannot reach it through Claude. And Owners can restrict what a connected service may do organisation-wide, allowing Claude to read email but not send it, or to read Drive files but not edit them, by setting each category of tool to always allow, needs approval or blocked. Connected services process the data on their own infrastructure under their own terms, a point for your data protection record rather than a reason not to connect.

Xero. Xero's own connector for Claude is read-only at launch. It connects one Xero organisation at a time, answers questions about revenue and profit, receivables and payables, cash position and invoices from live Xero data, and links back to the report, invoice or contact it drew on. Xero states that the data is not used to train AI models and that Claude cannot edit invoices, post transactions or change anything in the books. It is available on any Xero business plan and needs a Claude account on a free or paid plan. Xero also publishes a separate open-source MCP server for developers building custom workflows; that is a different thing with a different risk profile, and it is not what a non-technical team should be given. The complaints that circulate on the Xero user forum attach to the developer server and to questions the read-only connector was not built to answer; if your need is "what is overdue and how is cash", the connector does that.

HubSpot. HubSpot's connector for Claude is more capable and therefore needs more governance. According to HubSpot's Knowledge Base, it can read, create and update contacts, companies, deals, tickets and custom objects, log calls, meetings, notes and tasks, and read invoices, orders, payments and users, but it cannot delete anything. A HubSpot Super Admin must approve the connector before anyone can use it and chooses, at approval, which data permissions it may have and who may install it. Every user then sees only what their own HubSpot permissions allow. Sensitive Data properties are excluded, and if a HubSpot account has Sensitive Data turned on the connector gets no engagement data at all. Every create and update is written to HubSpot's audit log against both the user and the connector. A paid Claude plan is required, and HubSpot itself recommends setting the connector's write tools to needs approval so nothing changes without a person confirming it.

Google Workspace. Anthropic's Google Drive, Gmail and Google Calendar connectors are listed on the Team plan and follow the same model: enabled by an Owner, authenticated per person, permissions inherited from the person's own Google account, and sending mail restrictable to needs approval or blocked. For a first pilot, read access to Drive and Calendar with Gmail set to read and draft but not send is the usual starting point.

The training and retention position is the other half of the answer. Anthropic's pricing page lists model training as none by default on Team and Enterprise, and its Privacy Center states that data from its commercial products is not used to train its models. On Free, Pro and Max a model-improvement setting decides, with de-identified retention of up to five years when it is on, although raw connector content is excluded from training data unless copied into the chat. Deleted chats leave back-end storage within 30 days. Our guide to whether Claude is GDPR compliant for UK business works through the controller and lawful-basis questions, and our supporting piece on connecting Claude to Xero and HubSpot under UK GDPR goes into both connectors in detail.

What does a governance-first pilot look like when IT says no?

The objection is almost always to the version of AI use that is already happening: staff on personal accounts, client data pasted into chats, no record of any of it. An IT lead who says no to that is right. The firm that wants to proceed is also right that the work will happen regardless. The pilot that satisfies both has six parts, and none of them is exotic.

1. A company-owned tenancy. Team or Enterprise, with a named admin on your side, single sign-on where your identity provider supports it, and the plan-level training setting confirmed. Personal accounts are retired for work use.
2. A defined pilot group. Five to twelve people across two or three roles, chosen because their work is document-heavy and repeatable, not because they are the keenest.
3. Approved use cases and banned data. Three workflows per role, written down with an example of each, and a one-page list of what must never go in: special-category personal data, anything under a client confidentiality clause, credentials, payroll. This is the document IT usually wants and rarely gets.
4. Read-only connectors first. Each connector enabled by the Owner, scoped to the least access the workflow needs, with write actions set to needs approval. In Cowork, the organisation setting that lets members skip per-task approval for write tools stays off. A connector inventory records what is connected, at what scope, and who signed it off.
5. A data protection screen. Where personal data is involved, a short DPIA screening exercise on the pilot use cases, recorded; our DPIA screening test is built for exactly this decision.
6. A review date with evidence. Thirty days, with the usage analytics the plan provides: on Team the admin dashboard (weekly active members, adoption by product, connector read and write counts, skills usage, spend export) plus OpenTelemetry export of Cowork events; on Enterprise that plus audit logs and the Compliance API. If the IT lead needs the Enterprise items before signing, buy Enterprise; do not promise Team can produce an audit log.

Two boundaries make the pilot credible. Nothing in it lets Claude send client email, submit a filing, make a payment, sign a document, give regulated advice or update a production record without a person approving, and those rules are written into the organisation instruction and the connector settings. And where a regulator or client contract rules out cloud processing altogether, the honest answer is not a Claude pilot; our Private AI Concierge service exists for that case.

Who should set it up, and what should the handover contain?

Three people could do it, and the choice is about what they leave behind. A founder can set a workspace up in a weekend, and the result then depends on that founder's attention and leaves with them, which is the training burden and hand-off anxiety the public failure stories describe. An IT lead will get the tenancy, identity and connector governance right and rarely has the mandate to write role prompts for the finance team, because that requires knowing the work. A consultant with a method sits between the two: the governance from IT's list, the workflows from the people who do them, and a written handover so the firm owns the result.

Whoever does it, the test is the same. If the setup is only in someone's head, it is not a setup. The handover should contain, as files the firm can read and change:

• The organisation instruction: company identity, house tone, formatting standards, standing data-handling reminders, with an owner and a review date.
• One role prompt per role, not per person, so a new starter is assigned a role rather than given a blank page.
• A project instruction and a seeded memory for each recurring workflow, so each project is useful from the first prompt.
• A skills register: each skill's owner, purpose, risk tier, version and test case, and which seats it is provisioned to.
• A connector inventory: every connected system, the scope granted, whether writes are allowed and under what approval, and who on the client side signed it off.
• The data exclusions list and the human-sign-off rules.
• The plan-level data and training settings as configured, with the date checked.
• An install-day acceptance checklist and a 30-day adoption tracker with a keep, fix or retire decision on every workflow at the end.

That list is what our Claude Enablement service delivers as a fixed-price install: two or three days on site, Cowork as the default surface, Claude Code for the operator, and a 30-day adoption window inside the price because, in our own delivery records, installs that stalled did so after the on-site days when nobody owned the follow-up.

What does it cost beyond the licences?

Three costs sit alongside the seats: setup, whether that is a founder's weekend, an IT lead's week or a fixed fee; your own people's time in the first month, roughly an hour a week per seat if the adoption plan is followed; and the cost of doing it badly, which is the subscription nobody opens. Our Claude Enablement packages are GBP 4,500 ex VAT for a founder plus up to five seats over two on-site days with a remote follow-up day, and GBP 7,500 ex VAT for up to twelve seats over three days with two follow-up sessions, both with the 30-day window included and additional seats at GBP 250 to 350 each; our pricing page sets out the terms.

Anthropic gives the shallow end away. Claude for Small Business, launched on 13 May 2026, is a toggle inside Cowork with fifteen ready-to-run workflows, fifteen skills and connectors for QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace and Microsoft 365, with a free AI Fluency for Small Business course alongside it. Use both where they fit. What they do not hold is your context files, your role prompts, your governance decisions, your connector scopes or training on your own work, and neither is there in week four. That gap is where the setup cost goes, whoever bears it.

Sources

• claude.com/pricing, UK render, checked 15 September 2026 from a GB connection with no cache (metadata timezone Europe/London): plan prices, "Prices include 20% VAT", plan feature matrix, context windows, model training defaults.
• Claude Help Center, "What is the Team plan?": minimum two members, up to 150 seats, mixed seat types, connectors on Team, 200k context window. Accessed 15 September 2026.
• Claude Help Center, "View usage analytics for Team and Enterprise plans". Accessed 15 September 2026.
• Claude Help Center, "Use Claude Cowork on Team and Enterprise plans" and "Get started with Claude Cowork": availability, cloud sessions, connector tool approvals, OpenTelemetry, Compliance API coverage. Accessed 15 September 2026.
• Claude Help Center, "Use connectors to extend Claude's capabilities": organisation enablement, per-user authentication, inherited permissions, action restrictions, third-party processing. Accessed 15 September 2026.
• Anthropic Privacy Center, "Is my data used for model training?" (consumer and commercial articles), "How long do you store my data?" and "How long do you store my organization's data?". Accessed 15 September 2026.
• Xero, "Get clear answers on your Xero finances from Claude" (xero.com/uk) and Xero Central, "Connect Xero using the Xero connector in Claude". Accessed 15 September 2026.
• HubSpot Knowledge Base, "Set up and use the HubSpot connector for Claude", last updated 11 September 2026. Accessed 15 September 2026.
• Anthropic, "Introducing Claude for Small Business", 13 May 2026.
• Community discussion on r/ClaudeAI, r/smallbusiness, r/sysadmin, r/cscareerquestions, r/xero and r/hubspot, read in September 2026 and paraphrased above; no thread is quoted.

This guide is general information for UK businesses, not legal, tax or data protection advice. Prices and plan features are Anthropic's, Xero's and HubSpot's as published on the dates stated and change without notice.