Back to insights
9 November 20267 min readMelverick Ng

Your Spreadsheet Is Doing Three Jobs. Split Them Before an AI Agent Touches It.

Before an AI agent takes over a shared spreadsheet, work out what the sheet is really doing. It is often a second system of record, a handoff queue and a log of decisions at once. Split those jobs first, then give each one the least autonomy that works.

Visual concept: Your Spreadsheet Is Doing Three Jobs. Split Them Before an AI Agent Touches It. within a human-controlled agentic operating model.

ANSWER-FIRST SUMMARY

Key takeaways

An invoice lands in the finance inbox. Someone opens the shared spreadsheet, adds a row, types in the supplier, the amount and the PO number, then checks the PO in the ERP. If the quantities match, the row turns green. If they don't, it turns amber, someone adds a comment for purchasing, and the work moves on. On Friday, someone goes through the amber rows, chases the approvals and keys the cleared invoices into the ERP.

Plenty of SMEs run a sheet like this, for invoices, orders, collections or customer follow-ups. When AI agents come up in a planning meeting, it is often the first thing someone points at. Surely an agent could fill this in.

It probably could. Before you let it, look at what the sheet is doing, because it is rarely doing only one thing.

The sheet is doing three jobs

Look closely and the invoice spreadsheet is carrying three separate jobs.

  1. It is a second system of record. The ERP says an invoice is unpaid. The sheet says it is on hold, waiting for purchasing. When the two disagree, people trust the sheet, because that is where the latest status lives.
  2. It is the handoff queue between teams. Purchasing knows to look at the amber rows. Finance knows the green rows are ready to key in. Nobody wrote this down; the colours carry it.
  3. It is the record of decisions. Why was this invoice paid at a different unit price? The answer sits in a cell comment, a note in column Q, or someone's memory of a phone call.

Each job is legitimate. The trouble is that all three live in one file, held together by habit and by the person who does the Friday clean-up.

What happens when an agent copies the sheet

Say you ask an agent to do exactly what the clerk does today: read the invoice, add the row, match the PO, set the colour and update the ERP on Friday. It will automate all three jobs, including the parts that only work because a person is quietly making up for the gaps.

The second system of record becomes permanent, and now it is maintained by software, so it drifts from the ERP faster. The handoff still depends on colours, set by something nobody in purchasing is watching. The decision record gets thinner too. An agent can write comments, but it cannot know why the purchasing lead accepted a price variance last month unless somebody recorded the reason.

You end up with a faster version of a process nobody would design on purpose. And when something goes wrong it is harder to spot, because the person who used to notice the odd row is no longer reading every row.

Run the subtraction test first

Before automating anything, go through the sheet one column and one step at a time. For each, ask whether it should be deleted, moved back into the ERP or CRM, or kept.

  • Delete it if nobody uses it. Spreadsheets collect columns for reports nobody reads any more and checks the ERP already does.
  • Move it if the information belongs in the system of record. Invoice status, the PO match result and approval status usually have a proper home in the ERP. If your ERP can't hold them, that is worth knowing before you build anything on top.
  • Keep it if it does a job no system covers yet, and write down which of the three jobs it is doing.

Deciding not to automate a step is a perfectly good result. Sometimes the best outcome of the exercise is a shorter sheet, one less step and no agent at all.

Give each job the least autonomy that works

Once the jobs are separated, they need different kinds of help. Use the least autonomous option that reliably gets each one done. It keeps cost, review effort and risk down, and it makes failures easier to find.

Records: a rule or an integration

If invoice status should live in the ERP, put it there. Where two systems genuinely need the same data, sync it with a fixed rule or a standard integration. A deterministic sync does the same thing every time and is easy to check. An agent here adds judgement where none is needed.

Handoffs: an agent that prepares and routes

This is where an agent earns its place. It can read an incoming invoice, match it against the PO and the goods receipt, prepare the exception with the documents attached, and route it to a named owner. The agent prepares the work and sends it to the right person. It does not decide the outcome.

Decisions: a named person

Approving a price variance, accepting a short delivery or putting a supplier on hold are decisions the business is accountable for. The finance lead or operations lead should see a short evidence summary and make the call. The agent's job is to make that decision quicker to take and to record the reason, so the next similar case is easier.

The Spreadsheet Job Audit

Take one spreadsheet and fill in one line for each step or column. The card has six fields:

  • Step or column: what it is, in the words your team already uses.
  • Job it does: record, handoff or decision.
  • Keep, move or delete.
  • Least-autonomy option: none, a rule or integration, agent-prepared, or a human decision.
  • Human owner: one named role accountable for it.
  • Evidence of done: what proves the step happened correctly, such as an ERP status, an approval record or a matched set of documents.

Here is how two lines from the invoice sheet might look.

The amber colour when quantities don't match is a handoff. Move it: the mismatch belongs in an exceptions queue or an ERP status, not a cell colour. The least-autonomy option is agent-prepared, with the agent flagging the mismatch, attaching the invoice, PO and goods receipt, and routing it to purchasing. The purchasing lead owns it. The evidence of done is a closed exception with a recorded decision and reason.

The cell comment explaining why a price variance was accepted is a decision. The decision stays with a person, but the record moves into the system, so the reason sits with the transaction instead of in a spreadsheet margin. The agent can draft the evidence summary. The finance lead owns the approval. The evidence of done is an approval recorded against the invoice, with the reason attached.

Once the card is filled in, the design tends to be clearer than people expect, and often only a few lines need an agent at all.

A one-workflow adoption plan

Pick one spreadsheet people already complain about. It doesn't have to be the most important one. Choose the one where the pain is easiest to see.

  1. Run the audit with the people who use the sheet every day, including whoever does the Friday clean-up.
  2. Move what belongs in the system of record. This may need a small ERP or CRM change, and it should happen before any agent work starts.
  3. Delete what nobody needs.
  4. Pilot one agent-prepared handoff, such as the PO mismatch exception, with the named owner reviewing every item at first.
  5. Measure accepted outcomes and rework: how many prepared exceptions the owner accepted unchanged, how many needed correcting, and how many the agent missed. Leave "hours saved" out of the report until you have real numbers to put there.

If the pilot holds up, take the next spreadsheet. If it doesn't, the audit will usually show you which job was still tangled up with another.

The agent should be the last thing you add. If the sheet is still doing three jobs when the agent arrives, the agent will do all three, faster and with less visibility. Split the jobs first. Then the agent gets a narrow task it can do well, and the person approving its work knows exactly what they are signing off.

RELATED NEXIUS FIELD GUIDES

Take the concept
into practice.

Continue with implementation-focused guidance from Nexius co-founder Darryl Wong.

AGENTIC SYSTEMS / 9 min read

How to Agentify ERP and CRM Systems Safely

A governed path from read access to approval-gated execution for businesses introducing AI agents into ERP, CRM, and operational systems.

Read field guide
OPERATING MODEL / 8 min read

How to Design Non-Technical Work Loops with AI Agents

A practical method for turning recurring business work into bounded, evidence-driven human-agent loops without giving away human authority.

Read field guide

CONTINUE THE JOURNEY

Related insights

TURN THE IDEA INTO AN OPERATING CAPABILITY

Ready to build your
agentic operating model?

Get the readiness checklist + your recommended next step