Who we work with/Accountancy

Agents for accountants

AI agents for accountancy firms, built in Copilot Studio inside your Microsoft 365

The six agents a Firmwide install is built from, for the admin every practice shares. Each one starts on its own when something happens, does the checking, drafting and filing, then waits for one of your team to approve. For smaller and mid-sized firms.

Make Copilot safe and useful first, and an agent with one named job, inside the tools your staff already use, can change how a practice runs.

These agents take on the admin that comes up in every practice: WIP nobody reviews until it has aged, new clients keyed into four systems, records chased by hand every January, meeting notes written up days later and VAT returns scrolled line by line.

Each one starts on its own when something happens: a report is exported, a form is submitted, a meeting ends. It does the checking, drafting and filing in your own Microsoft 365, then stops for one of your team to approve.

They are the agents your Firmwide install is built from. Each department gets one, chosen in the mapping sessions, built in Copilot Studio and Power Automate on the templates and procedures the foundation step put in SharePoint, connected to the systems it needs and handed over with user documentation, technical documentation and a hands-on session by the people who built it. Then Run keeps it working. You deal with James Wilkinson throughout, and every engagement follows the five steps on How we work.

The agents

Six agents, each with one job.

Each agent has a standard trigger, a set job and one place where your team approves. The details below are the same in every firm; your thresholds, templates and folders are set up for yours. One comes with each department in your install, or add one to a Run plan from £2,500.

Ready

WIP and billing agent

Every manager gets their own WIP exceptions in Teams on Monday morning, then chooses bill now, defer or write off for each client and submits.

How it runs

What starts it

Your practice management system emails its scheduled WIP report to a shared mailbox, and the agent files it when it arrives. Managers get their card on Monday morning.

What it does

When the week's WIP report arrives, the agent files it and flags every client over your threshold that hasn't been billed in the period you set, grouped by manager. On Monday morning each manager gets one card in Teams to choose bill now, defer or write off for each client and submit. A fee request is emailed to your billing team for every client they bill, and partners can see who hasn't acted.

Where your team approves

When the manager chooses bill now, defer or write off for each client and submits. The agent never raises a bill.

See every step
Ready

Adverse media and conflict checks

Every new client and every annual refresh is checked, evidenced and filed, without anyone having to remember.

How it runs

What starts it

A new client record is created in your CRM or practice system. The agent reads the company number and starts.

What it does

The agent pulls the company's officers, persons with significant control and filing history from Companies House, runs your approved searches on every name and checks for conflicts across your own clients and engagements. It files a scored report with an evidence line on the client, sets the next refresh date and only asks your MLRO, or a partner where the firm has no MLRO, to look when something scores.

Where your team approves

The MLRO reviews the hits only.

See every step
Ready

Client meeting agent

Briefs the adviser the day before, then turns the meeting into the file note, the tasks and the record updates when it ends.

How it runs

What starts it

The calendar event has your firm's “Client meeting” category.

What it does

The day before a client meeting, the agent reads the client folder, recent emails and open actions and sends the adviser a one-page brief in Teams. When the meeting ends it drafts the file note in your template with the actions and a follow-up email, and files the note, creates the tasks and updates the record only once the adviser approves.

Where your team approves

Before anything is filed or sent.

See every step
Pilot places open

PBC and records chaser

Knows what each job is still waiting for, matches what the client sends and chases what they haven't.

Matching what clients send to what you asked for has to be right before it's left to run, so this agent starts with a pilot period.

How it runs

What starts it

A job is created in your practice system. The agent loads the standard list for that job type and sends it to the client.

What it does

When a job is created, the agent sends the client the right request list and then watches the shared mailbox and upload folder, matching everything that arrives to a line on the list. It keeps the tracker current, drafts chasers at day 7 and day 14 for the manager to approve and tells the partner about anything still missing after day 21.

Where your team approves

The chasers (unless you choose automatic sending) and escalations.

See every step
Ready, scoped per firm

Client onboarding agent

One form in; a signed engagement letter, a client workspace and a live client record out, with one partner approval in between.

How it runs

What starts it

The intake form is submitted (a Microsoft Form or your website form).

What it does

From one intake form, the agent chases any gaps, pulls the Companies House details, runs the adverse media and conflict checks, creates the client workspace and generates the engagement letters and letters of authority. Once a partner approves, it sends them for e-signature, files the signed copies and sets the client up in your CRM and practice system, or raises an admin task where it can't.

Where your team approves

A partner approves before anything goes to the client.

See every step
Ready, scoped per firm

VAT return review agent

Checks the coding on every VAT return before it's filed, and gives the accountant a red, amber and green list with the source line for every flag.

Scoped per firm because the check set is built around your coding conventions, your materiality and each client's known exceptions.

How it runs

What starts it

The VAT return detail export lands in the client's quarter folder. Xero, QuickBooks and Sage all produce one in Excel or CSV.

What it does

The agent checks the return against the client's last four quarters and known exceptions, ranking every flag red, amber or green with the source line. It files the review working paper to the quarter folder and drafts a client query for anything ambiguous, and the accountant clears each flag and signs off.

Where your team approves

The accountant reviews the flags and signs the return. The agent never files.

See every step

Client Acceptance

Two agents, built together.

A new client fills in one form. The checks run, the evidence is filed, the letters are generated and a partner approves once, before anything goes to the client.

The onboarding agent calls the adverse media and conflict checks as it goes, so every new client arrives checked and evidenced. Onboarding is scoped per firm because it touches your templates, practice system and e-signature tool.

How the agents get built

They're built as part of a Firmwide install.

Mapping first, then the foundation, then each department's agent and skills pack, then the handover. Nothing goes live until it has been run on your own cases with the people who will use it.

  1. Weeks 1 to 2

    Map

    Two hours with each department, recorded, with their templates and letters collected beforehand. Some departments need a follow-up hour. You check what we captured before anything is built.

  2. Weeks 3 to 4

    Foundation

    Permissions are checked and any oversharing fixed before Copilot or an agent can surface it. A named owner and simple rules are agreed, your templates and procedures go into SharePoint and the standard automations are set up. Client files and systems stay where they are.

  3. Weeks 5 to 6

    Agents and skills

    Each department's agent is chosen from the six accountancy agents or built bespoke, its skills pack is built on its own templates and everything is tested on real cases with the people who will use it.

  4. Final week

    Handover

    Each department gets user documentation, technical documentation and a hands-on session on its own data, agents and skills, and the named owner at your firm takes over.

Firmwide is a fixed-price install, typically six to eight weeks including mapping, with the price fixed on your Plan on a Page and the timetable by the end of mapping. We check permissions and fix any oversharing, agree a named owner and simple rules, put your templates and procedures in SharePoint, build an agent and a skills pack for every department in scope and hand it over with training. Then Run keeps it working, with the first month included and Run optional after that. See Firmwide.

Nothing is handed over without two sets of documentation, one for your team and one for your IT people, and a session where your team uses it on real work. You will not end up with tools nobody knows how to use.

What you need in place

What your firm needs before an agent can run.

  • Microsoft 365 with Teams and SharePoint. The foundation step of the install checks permissions, puts your templates and procedures in SharePoint and connects each agent to the system it needs. We don't move your data or replace your systems. Client files and systems stay where they are, and Copilot and the agents work from what is in Microsoft 365 and what people send them.
  • Copilot Chat, which Business Premium already includes. Copilot licences help, and the install is usually the reason to buy them, but the install works without them.
  • For some agents, a scheduled export from your practice software or a shared mailbox.
  • Someone who can approve the agent's access to your Microsoft 365. The install includes a tenant check, and we tell your IT provider exactly what to set up.

Works with your practice software

Which practice software do you work with?

Each agent is connected to the system it needs, confirmed in mapping, and Copilot itself is not connected to your practice software. Most agents start from something every system can produce: a scheduled report emailed to a shared mailbox, or a file saved to a folder. Where your software allows a direct connection (Xero Practice Manager and Karbon do, for example), the agent can pull what it needs straight from it. For practice software that runs on your own server, a read-only connection to the database is possible with your IT provider's agreement. Where we can't write back to your system, the agent creates a task for a person instead. Your practice system stays.

Your data and who approves

Built in your Microsoft 365. Approved by your team.

You decide what each agent may do on its own and where a person has to approve. By default, anything that goes to a client or raises a bill waits for one of your team.

Built in your Microsoft 365

Everything is built in your own Microsoft 365, and your own Azure subscription where a job needs it, not on our servers. We don't host your data.

Agents you talk to see what you can see

An agent your team talks to only sees what the person using it can already see. The install sets permissions so people only see what they should.

Agents that run use a service account

Agents that run on their own use a dedicated service account. Its access is limited to the mailboxes, folders and systems the job needs, agreed with you in advance.

Not used to train Microsoft's models

Microsoft doesn't use your Microsoft 365 content to train its foundation models.

UK regions where Microsoft offers them

We build in UK regions wherever Microsoft offers them. Where a service isn't available in the UK, or a build uses a model from another provider, we set out where processing happens so your compliance lead can approve it before anything goes live.

Every run is logged

Every run is logged: what came in, what the agent did and who approved it. Every agent has a kill switch and a named owner.

What it costs

The agents come with the install. One install, priced by department.

Typically six to eight weeks including mapping, with the price fixed on your Plan on a Page and the timetable by the end of mapping. Every install includes the first month of Run, and Run is optional after that. All prices exclude VAT.

First department

£6,950

fixed, typically six to eight weeks

The foundation, done once, plus the first department. In a small firm where everyone does a bit of everything, this is the whole firm.

  • The foundation: a permissions check with any oversharing fixed, a named owner and simple rules, your templates and procedures in SharePoint and the standard automations, with other systems connected for the agent that needs them
  • The first department: a two-hour mapping session, one agent, a skills pack of around 20 skills built from your own templates and procedures, user and technical documentation and a hands-on handover session
  • First month of Run

Each extra department

£2,500

Mapped, built, documented and handed over the same way, on the foundation the first department put in place.

  • A two-hour mapping session, one agent, a skills pack of around 20 skills built from your own templates and procedures, documentation and a handover session

Whole firm

Priced on the Readiness Check

Every department in scope. The number of departments and systems decides it, so it is priced on the call and fixed on your Plan on a Page.

See Firmwide in full

Then Run keeps them working, from £750 a month with the first month included. See pricing.

Our practice runs on IRIS, CCH, Xero and Dext. Does an agent have to plug into them?
Not directly. Most of these agents start from something those systems can already produce: a scheduled report or an export, saved to a folder or emailed to a shared mailbox. Where a system allows a direct connection (Xero Practice Manager and Karbon do, for example), the agent can pull data straight from it, and where we can't write back, the agent raises a task for a person instead. Your practice system stays. The install sorts everything around it. On the Readiness Check we ask which practice software you use and confirm how it connects during mapping.
Which agents should we start with?
Usually the ones where the time goes. For most practices that's WIP, client onboarding and AML checks, records chasing, the post or meeting notes. The Readiness Check names the two jobs to automate first, and the mapping sessions at the start of the install confirm them.
What if our client data is in four places?
It can stay in four places. We don't build a client database or move anything. Copilot already sees what is in SharePoint, Outlook and Teams, and each agent is connected to the system it needs, confirmed in mapping. What the foundation adds is a permissions check, a named owner with simple rules and your templates and procedures in SharePoint, so Copilot and the agents work the firm's way. If bringing a scattered list together turns out to be part of your foundation, we say so on the Readiness Check and it goes on the Plan on a Page.
Do we need Copilot licences first?
No. The install works on Microsoft 365 Business Premium with Copilot Chat, which everyone already has and which already sees what is in SharePoint, Outlook and Teams. The install is usually the reason a firm buys Copilot licences, because for the first time Copilot is safe to use and works the firm's way. We ask about your licences on the Readiness Check. If you already have licences and want your team getting more from them first, Copilot in your workflows is the one open session we run. Copilot in your workflows
Will Microsoft's own Copilot make these agents pointless?
Some of what people call agents, yes, and we'll tell you when Copilot already does the job. Meeting recaps, drafting and “prepare me for my meeting” are now built in. What isn't built in is your firm: your clients, your thresholds, your templates and your naming conventions. Nor is filing to your document system, updating your records or the approval and evidence trail your regulator expects. That's what the install and the agents do.
Couldn't someone in our own team build this?
They could build a first version of some of it. The time goes on everything after the first version: connecting it to the systems it works from, the exceptions, the approval steps, the audit trail and keeping it working when Microsoft changes things. That's what the fixed price and Run cover, and the documentation and handover mean your team knows exactly how to use what was built.
Where does our client data go when an agent reads a client's tax return?
We build everything in your own Microsoft 365, not on our servers, and we don't host your data. An agent your team talks to only sees what the person using it can already see, and the install sets permissions on least privilege. Agents that run on their own use a dedicated service account, limited to the mailboxes, folders and systems the job needs, agreed with you in advance. We build in UK regions wherever Microsoft offers them, and anything that has to run elsewhere is set out for your compliance lead to approve before go-live. Microsoft doesn't use your Microsoft 365 content to train its foundation models, every run is logged and every agent has a kill switch. That matters where client records, payroll data and personal information sit under professional confidentiality duties.
How much does an AI agent cost for an accountancy firm?
Built as part of a Firmwide install, or added to a Run plan from £2,500. The install is first department £6,950, each extra department £2,500, whole firm priced on the Readiness Check, with one agent and a skills pack per department. Microsoft's own usage charges (Copilot Credits) are billed by Microsoft to your firm, separately from our fees. We estimate them during mapping and keep them low by design.
How long does it take?
Typically six to eight weeks including mapping: two to map, two for the foundation, two for the agents and skills and the rest to hand over. The price is fixed on your Plan on a Page before anything starts, and the exact timetable is fixed no later than the end of mapping. The number of departments sets the pace.
What if it breaks?
That is what Run is for. The first month is included with every install and Run is optional after that: Run Starter £750 a month or Run Growth £1,950 a month keeps your agents and skills working through Microsoft's changes and yours, with fixes started within two working days on Starter and one on Growth. See Run
Do agents replace our accounts staff?
No. They take the admin off your team (the sorting, chasing, retyping and checking) so your team can do the client work. Judgement, advice and sign-off stay with people, and anything that goes to a client or raises a bill waits for one of your team.
Do we need an IT team?
No. The install includes a tenant and licence check, and where your IT provider needs to approve an agent's access to your Microsoft 365 or set up a shared mailbox, we tell them exactly what to set up. They also get the technical documentation for every agent and skills pack.
Do you do training on its own?
Training is part of every install: a handover per department, with user documentation and technical documentation. For firms already on Copilot licences there is one open session, Copilot in your workflows, from £1,150. For Run clients, a handover session for new starters is £850. Copilot in your workflows

Next step

Find out where Copilot can and can't see your client data.

Free, 30 minutes, online, with James. You leave knowing where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.