How do I stop staff signing up for AI tools on company cards without approval?

23 October 2026

Why are staff buying tools without asking?

Usually because the purchase route is slower than the work. Someone needs to summarise calls, prepare proposals or search a pile of documents. A free trial asks for a card after a week, the company card is nearby and the employee thinks a £20 monthly charge is too small to bother anyone. Sometimes the employer has told people to be more productive with AI without naming an approved tool. That is an invitation to improvise.

Do not begin with a ban and a lecture. Ask which task the person was trying to complete, which information they uploaded, who owns the account and whether a paid subscription has started. Those four answers distinguish an innocent procurement gap from a data incident. If the tool has only seen invented examples, the immediate issue may be cost and account ownership. If it has seen customer records or confidential files, involve the person responsible for data protection before deciding what to do next.

The NCSC small organisations guidance recommends basic controls such as managing access and keeping software up to date. The lesson for AI subscriptions is practical: a card payment alone cannot establish who has access, what data enters the tool or how to remove access when someone leaves. Finance and operations need one shared view of the tools in use.

Set a buying rule people can follow

Write a one-page rule: nobody starts a paid AI subscription, adds a company card to an AI account or connects an AI tool to company email, files or CRM without an approval record. A named manager approves the business need, a finance owner approves spend and a data owner checks information access. In a business of ten people, those may be two people rather than three departments. Name them anyway. An approval sent in a chat is fine if it is copied into a register.

Make the fast route genuinely fast. Offer a short form with six fields: proposed tool, intended task, staff owner, monthly and annual cost in pounds, information it will handle and integrations requested. Promise an initial decision within two working days for a low-risk trial. If the answer is no, offer an approved alternative or a way to test with dummy data. If approval routinely takes three weeks, staff will work around it.

Separate a trial from production use. A seven-day trial with fictional data and no integrations is not the same risk as allowing a browser extension to read customer messages. Even free tools need review when staff upload business information. The rule should cover personal cards reimbursed through expenses as well as company cards, because otherwise the same problem simply moves to the expense claim.

Use financial controls as a backstop, not the whole policy

Ask your card provider whether you can issue virtual cards with individual owners, merchant restrictions and spending limits. Put software subscriptions on a designated card controlled by finance, not on every employee card. Where practical, set a transaction alert for new software merchants and require approval before a recurring payment is accepted. Your provider's merchant categories will not identify every AI product, so treat alerts as a prompt to review, not a perfect block.

Review card and expense statements monthly. Look for small recurring charges, unfamiliar company names and multiple staff paying for the same product. A £20 monthly subscription is £240 a year before VAT, exchange-rate charges or extra seats. Five duplicate subscriptions at that illustrative price cost £1,200 a year. The bigger exposure may still be the client data in five unmanaged accounts, not the £1,200.

Never punish someone solely because a merchant name looks unfamiliar. The payment might be for an approved feature inside existing software. Check the receipt, account owner, purpose and renewal date. Cancel unused trials before renewal, but export business data and confirm ownership first. A hasty cancellation can strand important work in an employee's personal account.

Give people an approved route to useful AI

Publish a short approved-tools list with the exact account type, login method and permitted uses. For example, a company-managed assistant might be approved to draft internal summaries from non-sensitive information, while customer files require a separate approved workspace. State what staff should do when a needed feature is missing. An accessible request route is more effective than a vague instruction to “use AI responsibly”.

Check what you already pay for. Microsoft 365, Google Workspace and your CRM may include AI features with central administration. These are not automatically safe, but using a managed account can make ownership, offboarding and permissions easier than buying a separate tool for each employee. Compare the actual licence price and data settings before expanding. A specialist product may still be better if it solves a defined job that the bundled assistant cannot do.

Use single sign-on where available, company email addresses rather than personal logins, multi-factor authentication and a named administrator. Record the tool's renewal date and who can change billing. Do not grant broad access to email or files simply because an integration wizard suggests it. The {link2} emphasises appropriate technical and organisational security measures. For a small firm, that translates into knowing who can get into each system and removing access when roles change.

What to do with subscriptions that already exist

Run a two-week discovery exercise. Finance exports the last three to six months of card and expense transactions. Staff are invited to disclose tools they use without automatic blame. Managers ask which workflows depend on each tool. Add approved business use, account owner, payment method, data categories, connected systems, renewal date and cancellation process to a simple register. A spreadsheet is enough for a small business.

Then triage. Keep a useful tool in a company-managed account if the supplier's terms, access controls and information handling pass review. Migrate work out of personal accounts where possible. Stop or replace tools with unclear data practices or unnecessary permissions. If sensitive information may have been exposed, preserve facts about what was shared, when and with whom, then assess the incident under your data protection process. Do not promise that deletion from an account instantly deletes every supplier copy. Check the supplier's retention and deletion terms.

Set one owner for each approved subscription and revisit it at renewal. Ask whether people use it, whether it saves measurable time and whether permissions have expanded. A 30-minute monthly review of new charges and access changes can prevent months of invisible spend. It is a better control than trying to recognise every new AI brand name at the point of payment.

When a strict purchasing block is not right for you

A blanket ban is usually counterproductive if your team genuinely needs to test new tools to deliver work. A product team, development agency or research business may need controlled experiments every week. Give them a capped experimentation budget, test accounts, synthetic data and a fast approval lane. Make clear that a low-value trial does not authorise a live customer-data connection.

Likewise, an elaborate procurement committee is disproportionate for a three-person company buying one assistant. One owner can approve a £25 test after checking the supplier and writing down the purpose. The process should become more formal when the tool handles personal data, makes customer-facing decisions, connects to core systems or locks the business into an annual contract.

If you discover staff have already adopted a tool that works well, assess it fairly. The goal is not to prove they were wrong. It is to preserve the value while bringing spend, access and data handling under company control. If you need a second pair of eyes on the register and approval rules, ask for a focused review rather than buying a large AI strategy project.

Is This Right For You?

This approach is right for a UK business where staff can buy software or connect tools to work systems. Keep approval proportionate: a small test with dummy data needs less scrutiny than a CRM integration. If you have only one account managed by the owner, use a one-page register rather than a committee.

Frequently Asked Questions

Can I simply block all AI subscription payments?

You can restrict cards and require a central purchasing card, but merchant blocks are imperfect. Pair payment controls with an approved-tools list and a fast request route.

Should employees be disciplined for an unapproved £20 subscription?

Investigate the purpose and any data shared first. Apply your policy consistently, but fix unclear rules and slow approvals rather than treating every first breach as misconduct.

Do free AI tools need approval?

Yes if they handle business information or connect to company systems. A free price does not remove data, access or account-ownership risk.

Who should approve an AI tool in a small business?

A named operational owner should approve the use case, finance should approve cost and whoever leads data protection should review information access. One person may hold more than one role.

What if a tool is already connected to our CRM?

Record its permissions, account owner and data flows. Limit access to what the workflow needs, review supplier terms and revoke the connection if it cannot be justified.

How often should we review AI subscriptions?

Check new card and expense charges monthly and review each approved tool at renewal or after a material change in use, permissions or supplier terms.