Agents for accountants/Client onboarding agent

Accountancy agent

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.

Ready, scoped per firm

How it runs

The client onboarding agent starts on its own and stops for your team to approve.

What starts it, what it does and where your team approves are set out on this page.

Book a Copilot Readiness Check

How it's sold

Sold with the adverse media and conflict checks as Client Acceptance. It's scoped per firm because it touches your templates, practice system and e-signature tool.

About Client Acceptance

What starts it

It starts on its own.

Standard trigger

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

It could also start when

  • An opportunity is marked won in your CRM
  • A signed proposal comes back from e-signature
  • An email with the client's details arrives at a new client mailbox

Manual fallback

Your admin team starts the case from Teams and completes the form for the client.

  1. Trigger

    The intake form is submitted.

  2. AI

    The form is checked for gaps, and the client is chased for anything missing.

  3. System

    Companies House details are pulled and the adverse media and conflict checks run.

  4. Action

    A client workspace is created with your folder structure. Engagement letters and letters of authority are generated, with the schedules for the services chosen.

  5. Your team approves

    The partner approves.

  6. Action

    The letters are sent for e-signature and the signed copies filed.

  7. Action

    The client is created in your CRM and practice system where they allow it; otherwise an admin task is raised. The team is told the client is live.

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.

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.

Standard in every firm

  • Form
  • Completeness check
  • Workspace creation
  • Letter generation
  • Approval
  • E-signature
  • Filing

Set up for your firm

  • Form fields
  • Service schedules
  • Letter templates
  • Folder structure
  • Practice system mapping

Today

Data is collected by PDF or email, then keyed into the AML tool, the letter, practice management and the CRM. Letters are edited by hand. It takes days, and the same address is typed four times.

With the agent

Details are captured once and reused everywhere, the letters are right first time and the partner approves in one place.

Worked example

What it could give back to your firm.

Worked example

Hours back a year
480
Value of that time a year
£33,600
Days sooner to a signed letter This brings first fees forward. It doesn't add to them.
7

Illustrative defaults. Put in your own numbers.

How it's worked out

  • Hours = new clients a month × 12 × (hours of admin now − hours with the agent).
  • Value = hours × value of an hour.
  • Days sooner = days now − days with the agent. That brings first fees forward; it doesn't add to them.

What you need in place

Before it can run in your firm.

  • An intake form
  • Controlled Word templates
  • An e-signature service (DocuSign, Adobe Sign or similar)
  • Your CRM, plus either a direct connection to your practice system or an admin task instead

How it's bought

Built as part of a Firmwide install, or added to a Run plan from £2,500.

Firmwide install, first department
£6,950
Each extra department
£2,500
Extra agent on Run
From £2,500
Run
£750 or £1,950 a month

Most firms get it as their department's agent in a Firmwide 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, built on the templates and procedures the foundation step put in SharePoint and connected to the systems it needs. Once live, Run keeps it working, from £750 a month with the first month included and Run optional after that. A bespoke agent built onto a Run plan is priced lower than one handed over with no support. Both prices are fixed before anything is built.

Microsoft's own usage charges (Copilot Credits) are billed by Microsoft to your firm. We estimate them during mapping and keep them low by design: routine steps run as standard automations and AI is only used where judgement is needed.

All prices exclude VAT.

What if our practice system can't be updated automatically?
Then the agent raises an admin task instead. It creates the client in your CRM and practice system where they allow it, and where they don't, a person does that step with everything they need in front of them.
Who sees the letters before the client does?
A partner. The engagement letters and letters of authority are generated with the schedules for the services chosen, and nothing goes for e-signature until the partner approves.
Why is it scoped per firm?
Because it touches your templates, your practice system and your e-signature tool, and every firm's are different. The Readiness Check gives you a rough price, the Plan on a Page fixes it before any build starts and mapping confirms the detail.
Where does our data go?
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.
  1. User documentation

    Written for a normal member of staff, in plain English: how to use it day to day.

  2. Technical documentation

    For your IT team or another technical person: how it is built, where it lives, permissions, how to change it and how to switch it off.

  3. A hands-on handover session per department

    The people who will use it use it on their own data, with us in the room or on the call.

Next step

Find out where Copilot can and can't see your 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.