Agents at work

Telling your team about AI plans: say it early and plainly

How to tell your team about AI plans in a finance or bookkeeping firm: what to say, when to say it, and why the honest version is the one that works.

Beaks · · 5 min read
Hand writing with a blue pen on paper beside a white mug on a wooden table

Every firm that starts looking at AI agents reaches the same awkward moment. The partners have talked about it, someone has run a trial, and the team has noticed. Telling your team about AI plans is usually left until something is decided, on the theory that there is nothing to say yet. That is the wrong way round. By the time a plan is decided, the people doing the work have already filled the silence with their own version of it, and their version is rarely kind.

This post is about what to say, when to say it, and why the honest version is not just the decent one. It is the only one that works.

Why silence costs you the inventory

Any sensible route to agents starts with a list of what the team actually does, written down task by task. We argued in an earlier post that nobody has that list, and that building it is most of the AI strategy. The list comes from the people who do the work. They know which reconciliation always breaks, which client sends the bank statements late, which step in the VAT return depends on a judgement nobody wrote down.

Now picture asking for that detail while the team suspects it is being used to work out whose job goes first. People do not refuse. They do something worse. They write the tidy version. The exceptions disappear, the workarounds stay in their heads, and the time estimates drift. The list you get looks complete and is not.

So the first reason to be open is practical. Documentation written under suspicion is bad documentation, and an agent runs on the documentation.

When to start telling your team about AI plans

Earlier than feels comfortable. A reasonable rule: tell the team before you ask them to document anything for the purpose of handing it over, and before any trial touches their work.

That means you will be talking before you have all the answers. That is fine, as long as you say which parts are decided and which are not. "We have not decided" is an honest sentence. "Nothing is changing" usually is not, and people can tell.

Three moments are worth planning for:

  1. The start. Before the task list is built, say what it is for and what it is not for.
  2. The first handover. Before an agent drafts anything on a real task, tell the owner of that task first, then the team.
  3. Each step up. When a task moves from "agent drafts, person approves" to "agent acts, person reviews", say so, and say why the track record earned it.

What to say, in plain words

Leave the slide deck aside. The message fits on one page, and it should answer the questions people are actually asking in the kitchen.

What we are doing

Say it directly. Something like: "We are going to write down every recurring task we run, how often, who does it and how it is done. Then we will try AI agents on some of the rule bound steps, starting with drafts that a person checks."

Why we are doing it

Give the real reason. For most firms it is some mix of growth without matching growth in headcount, key person risk, and the hours lost to work nobody enjoys. If the reason is that fees are under pressure, say that. People respect a hard reason more than a soft one they do not believe.

What happens to the work

Be specific about the direction. The first steps to go are the dull, repetitive ones: pulling reports, matching, chasing, formatting. Judgement, client conversations and sign-off stay with people. That is how it should be designed anyway, as we set out in the ladder from drafts to trust.

What happens to them

This is the part most firms skip, and the part people actually want to hear. Say what the plan is for the time that comes back: more clients without a matching hiring plan, more review and advisory work, faster progression for people who were stuck doing preparation. Only say what you mean and can keep. If you do not know yet, say that, and say when you will know.

What we will not do

A short list helps. For example: we will not use the task list to rank individuals, we will not measure people by how much they document, and we will not move a task to an agent without telling the person who owns it.

What not to say

A few phrases undo everything else.

  • "It is just a tool." If it changes who does a task, it is more than a tool, and the team knows it.
  • "Nobody's job will change." Jobs will change. The honest promise is about how they change and who gets a say.
  • Silence about trials. If people find out an agent has been drafting their reconciliations from someone else, no later explanation recovers that.

The test is simple. Imagine the person whose task is being handed over reading every message you sent about it, in order. If they would feel deceived at any point, rewrite it.

Make it a two-way conversation

Telling is half the job. The other half is giving people a real part in it.

  • Ask the task owners to write the method. They are the experts. Asking them, and saying what it is for, is the difference between capture and extraction.
  • Let them name the boring parts first. Most people can point to the steps they would happily never do again. Start there.
  • Give them the review role. In the early months, the person who used to do a task is usually the best reviewer of the agent's draft. That is a step up in responsibility, not a demotion.
  • Show them the log. Corrections, exceptions and hours returned should be visible to the team, not kept in a partners' folder.

We are designing Beaks around the same principle: people are told plainly that documenting a task can lead to it being handed to an agent, and each handover is recorded where the team can see it. Whatever tools you use, the same rule applies.

One thing to do this week

Write the one page. Five short sections: what we are doing, why, what happens to the work, what happens to you, and what we will not do. Mark anything undecided as undecided, with a date. Then read it to one person who does recurring work on your team before you send it to anyone else, and change whatever made them frown.

← All posts

Know what your team actually does.

Beaks holds every recurring task, writes the manual as people work, and shows which work is ready for AI.

Request early access

Keep reading