Open any shared drive and you will find them. Quote v3 FINAL. Induction pack (copy). Monthly report, March, updated for April.

Every business has documents it builds the same way each time. Someone opens last month's version, saves it under a new name, and spends an hour changing the parts that are different.

That copy and edit routine is the best place I know to start with AI agents.

Copied paperwork

When people ask me where to start with agents, they usually expect an answer about chatbots or customer service. My answer is far more boring. Start with the document your team keeps rebuilding.

It suits an agent for three reasons.

  • There are plenty of examples. Every past version shows the agent what good looks like.
  • There is a template. The structure already exists, so the agent only fills in what changes.
  • A person already checks it. Someone reviews the document before it goes out, so a mistake gets caught where it always has been.

That last point matters most. Your first agent should sit inside a process that already has a check at the end.

The right document

Not every document is a good first candidate. I look for three things.

  1. It is built often. Weekly or monthly beats once a year. More repetitions means more time back.
  2. It follows a pattern. If each version is mostly the same sections with new details, an agent will do well. If every version starts from a blank page, leave it for later.
  3. Being wrong is cheap. Start with something reviewed internally before it reaches a client or a regulator.

Quotes, job sheets, weekly reports, proposals and onboarding packs often tick all three.

The tools you already have

You probably do not need a new tool. Microsoft Copilot, ChatGPT and Claude all let you set up an agent with its own instructions and a library of files to work from. Use whichever one your business already has and trusts with its documents.

The setup is simpler than it sounds.

  1. Gather the examples. Collect a good handful of past versions and the blank template. Choose the ones you would be happy to send again.
  2. Write the instructions. Explain in plain English what the document is for, who reads it, and which parts change each time.
  3. Point it at the library. Load the examples and the template so the agent works from your real documents rather than its general knowledge.
  4. Test it on real jobs. Have one or two people use it on live work for a couple of weeks, alongside their usual way of doing it.
  5. Fix what it gets wrong. Each mistake usually points to a missing line in the instructions or a poor example in the library.

Expect some steps to need a second go. Every business has its own quirks, and so does every tool. A bit of patience early saves a lot of frustration later.

Here is a starting set of instructions you can copy.

Copy and adapt

Starter instructions for a paperwork agent

Paste this into your agent's instructions and replace everything in square brackets.

You help our team prepare [document name].

Purpose: [what the document is for and what it helps the reader decide or do].
Readers: [who reads it and what they care about most].

Always work from the template and examples in your files. Match their structure, headings, tone and level of detail.

Each time, I will give you: [the details that change, for example customer, dates, quantities, site].
Change only those parts. Keep everything else as it appears in the template.

If any information is missing or unclear, list it as a question instead of guessing.

Finish with a short list of every detail you filled in, so the person checking can confirm each one.

Use Australian English.

An owner and a signature

Two rules keep a paperwork agent safe and useful.

The first is a named owner. One person looks after the agent, updates its examples and decides when it is good enough for the rest of the team. Without an owner, an agent drifts the same way an unloved spreadsheet does.

The second is a human signature. A person reviews and signs every document the agent produces. The agent does the copying and filling in. Your people keep the judgement and the accountability.

The baseline

Here is the step most people skip.

At a recent talk I asked the audience how much of their team's week goes on assembling paperwork. More than a third had no idea.

If you do not know how long the job takes today, you cannot show what the agent saved. So time it first. One week of honest tallying is enough to set a baseline and make the case for building the next one.

Run your own numbers here.

Try the numbers

Time back calculator

Pick one document your team copies and edits. Use your own honest numbers.

Hours spent today48a year

Hours back with an agent36a year

That is about0.9working weeks

Working weeks use a 38 hour week. Hours back assume a person still checks and signs every draft.

The second agent

Once the first agent is working, the second one comes quickly. You will have a feel for writing instructions, a sense of what makes a good example library, and a team that has seen it work.

Most businesses have more than one document that fits the pattern. Start with the one that wastes the most hours.

Try this. List the three documents your team most often builds by copying last month's version. Pick the one with the most past examples and gather ten of them this week.