Claude for small business: put it to work inside the tools you already use

Claude for small business is no longer just a phrase for using a chatbot at work. On 13 May 2026 Anthropic launched a product called Claude for Small Business. Anthropic describes it as "a package of connectors and ready-to-run workflows that put Claude inside the tools small businesses depend on".

The important word in that description is inside. A small business rarely gets much from an AI model sitting in a separate window. It gets value when the model reads the ticket, the invoice or the customer record where it already lives. It also needs to hand its work back to the same system.

The argument here is practical. If you run or manage a small business, the question is not whether Claude is clever. The question is which of your daily tools it should sit inside, which job it should do first, and what you need in place before you let it act.

The sections below cover what the launch package includes and where it stops. They walk through a working service desk built on Claude inside a team chat tool and Zoho Desk. They then set out the UK data protection points you need to handle before you switch anything on.

Most teams start with a chat window. Someone pastes in an email, asks for a reply, copies the answer back and sends it. That can save a few minutes, but the gain is hard to repeat and harder to measure.

The weaknesses are structural rather than technical:

• Missing context. The model only knows what someone pasted in. It cannot see the customer's history, the open ticket or the agreed price.
• No record. The output lives in a private chat, not in your helpdesk or CRM. Nobody else can see what was suggested or why.
• Manual handling. Every step still needs a person to copy, paste, check and file. The slowest part of the job stays the same.
• Uneven use. One enthusiast uses it daily and the rest of the team never opens it. The business cannot plan around that.

Compare that with a model that runs inside the tool where the work already happens. It reads the record directly and writes its result back to the same place. The team keeps working in the same screens, so adoption does not depend on anyone changing habits.

That is the difference between a novelty and a working system. It is also why Anthropic built its small business package around connectors rather than around a better chat box.

According to Anthropic, the package ships with 15 ready-to-run agentic workflows and 15 skills. They cover finance, operations, sales, marketing, HR and customer service. The launch connectors reach accounting, payments, CRM, design and e-signature tools, as well as office suites.

The set-up is light. You toggle Claude for Small Business on inside Claude Cowork, connect the tools you already use and pick the job. One small business guide notes that it runs through the Claude Cowork desktop app and needs no IT support to set up.

What the workflows do

The same guide lists built-in skills such as an invoice chaser, a margin analyser, a month-end prep workflow, a contract reviewer and a lead triager. One payroll planning workflow checks your cash position in your accounting software against incoming payment settlements. It builds a 30-day forecast, ranks overdue invoices and queues payment reminders for you to review and send.

Who stays in control

Anthropic's own words are: "Claude does the work; you approve before anything sends, posts, or pays." By default, you approve each step. When you are ready, you can allow certain workflows to run end-to-end.

That default is sensible. Start with approval on every action, watch the results for a few weeks, and only then remove the checkpoint for jobs that have proved reliable.

The launch connectors cover a defined list of tools. If your team runs its support in Zoho Desk or its sales pipeline in Zoho CRM, those are not on the launch list. The same applies to any system you built in-house.

That does not rule Claude out. It means the connection has to be built rather than switched on. The UK government's Digital Marketplace listing for Claude states that Claude "integrates with and extends other software through APIs and partner integrations". Another listing on the same marketplace notes that customers can build custom Claude integrations via Model Context Protocol (MCP).

What a custom connection involves

• An API key. Use of the API requires a generated key, which you need to store and rotate like any other credential.
• Acceptable use. Users must follow the Anthropic Acceptable Use Policy, which restricts certain high-risk applications. Check your use case against it before you build.
• Admin stays separate. The API cannot manage billing, user accounts or core service configuration. Those stay in the Anthropic console or with support.

For most small businesses the choice is therefore simple. Use the ready-made workflows where your tools are on the list. Commission a custom integration for the one system where most of your repetitive work actually sits.

Routing is a good first job for Claude because the cost of getting it wrong is easy to see. A request that lands in the wrong queue waits, gets reassigned, and waits again. The person who raised it chases, and someone senior ends up sorting tickets by hand.

A service desk that sits inside the chat tool staff already use removes a step. People describe their problem in the team chat app where they already spend their day. Claude reads the request, works out what it is and who should handle it, and creates the ticket in the helpdesk. The support team keeps working in Zoho Desk as before.

Svennis built an IT service desk of this kind for Asset Services Group (Message Direct), running on Claude inside the client's team chat tool and fronting Zoho Desk. Their Head of Technology reports 99.7% first-time-right routing and a 40% efficiency gain in the published Asset Services Group case study.

The lesson for a smaller business is not the exact figures. It is the shape of the design. Claude sits inside two tools the team already uses and does one narrow job well. The helpdesk remains the single record of every request.

If you want the design detail, the post on running a chat-based service desk on Claude walks through how the pieces fit together.

Pick one job, not a programme. The best first candidate is high in volume, follows a pattern and already has a clear home in one of your systems. Routing, triage and drafting first replies usually fit. Anything that commits money or makes a final decision about a person does not.

Measure before you start. Count how many requests are reassigned, how long first replies take, or how many invoices go overdue. Without a baseline you will not know whether Claude helped.

Then keep a person in the loop. The approval default in Anthropic's package exists for a reason. Remove it only for the job you have measured and trust.

Security is the main objection in most small businesses, and it is a fair one. In a survey Anthropic ran with small business owners, half named data security as their single biggest hesitation about AI.

Three points from the published material address the common worries:

• Permissions carry over. Anthropic states: "If an employee can't see something in QuickBooks or Drive today, they can't see it through Claude." Claude cannot reach data in connected apps that the relevant user cannot already access.
• Training. Anthropic states it does not train on your data by default on its Team and Enterprise plans.
• Certification and transport. A marketplace listing states that Anthropic holds ISO 27001:2022, SOC 2 Type II attestation, ISO 42001 and Cyber Essentials. The Claude listing states that data between buyer and supplier is protected with TLS version 1.2 or above.

The permission point cuts both ways. Claude sees exactly what your users see, so any sloppy access in your existing tools becomes sloppy access through Claude. Before you connect anything, review who can see what in your helpdesk, file storage and finance system. Remove old accounts and shared logins, and tighten folders that have drifted open over time.

That review is cheap, and it improves your security whether or not you go ahead with Claude.

Putting Claude inside a service desk or CRM means it will process personal data. UK GDPR applies. The ICO notes that its guidance is under review following the Data (Use and Access) Act, so check the current version before you decide.

Data protection impact assessments

The ICO's guidance on when you need a DPIA names artificial intelligence as an example of innovative technology. A DPIA is required where that processing is combined with any of the European guidelines criteria. The ICO's list also covers decisions about a person's access to a product, service, opportunity or benefit based to any extent on automated decision-making.

An internal IT desk handles staff data. The ICO notes that employees could be considered vulnerable data subjects where a power imbalance means they cannot easily object. If in doubt, do the DPIA. It is a short document for a narrow use case.

Breaches and risk

If a breach is likely to pose a risk to people, you must notify the ICO as soon as possible and, where feasible, within 72 hours. Add your AI tools to your breach plan now. The ICO's AI and data protection risk toolkit, a downloadable spreadsheet, gives you a structured way to record risks. For a wider view, see this overview of AI law for UK businesses.

According to the small business guide cited above, Claude for Small Business is available on the Claude Pro or Max plan for individuals and on the Claude Team plan for whole-business access. The Digital Marketplace listing notes that the free version of Claude comes with limited usage per day. That is fine for trying things, but not for a workflow the whole team depends on.

The plan choice follows from the design choice. If one owner wants help with month-end and invoice chasing, an individual plan may be enough, but check that its terms cover business use of customer data before you connect your accounting or CRM data. If Claude sits inside a shared service desk or sales process, you need the team plan. That plan is also the one Anthropic names when it says it does not train on your data by default.

Plan the exit on day one

The Claude listing states that Anthropic does not retain prompts or outputs after account closure. Buyers must export any data they need before the service ends. On the Enterprise plan, the Primary Owner can request an organisation-level export through Admin Settings.

This is another reason to keep your helpdesk or CRM as the system of record. If every ticket, reply and decision is written back to Zoho Desk, closing a Claude account costs you the tool but not your history. Build that rule into any integration from the start.

You do not need a large project to test whether Claude pays off. You need one job, one system and a number to beat. A sensible order looks like this:

1. List your tools. Note which of your daily systems are on Anthropic's launch connector list and which are not. That tells you where you can switch on and where you would need to build.
2. Pick one job. Use the tests in the table above. Routing and triage are usually safer first choices than anything that sends money.
3. Take a baseline. Count the current volume, reassignment rate or response time for that job over two or three weeks.
4. Tidy permissions. Review access in the connected tools, because Claude will see exactly what each user sees.
5. Do the paperwork. Check that your Claude plan comes with a data processing agreement. Check how your data leaves the UK: the UK Extension to the EU-US Data Privacy Framework only covers suppliers listed as active participants in it, and if you rely on the IDTA or UK Addendum instead you also need a transfer risk assessment. Update your privacy notice so customers and staff know about the new supplier and any transfer outside the UK. Decide whether you need a DPIA, add the tool to your breach plan and record risks in the ICO toolkit.
6. Run with approval on. Keep a person approving each action until the results match or beat your baseline.
7. Train the team. Anthropic's free AI Fluency for Small Business course needs no Claude or Anthropic account and includes a completion certificate.

Review the results after a month. If the numbers moved, widen the scope to a second job. If they did not, change the job rather than adding more tools.