AI for small business: The first three jobs to hand over

AI for small business works best when it takes over recurring preparation work before it takes over decisions. Start with sorting incoming messages, preparing customer support replies, and organizing financial paperwork. Each job repeats often, has a result you can inspect, and leaves the business owner free to deal with exceptions.

You do not need to redesign the business around AI. Pick a job you already do every week, give an agent the instructions you would give a careful new employee, and check whether its work saves you a step. The first test is modest: did you get something useful back without having to reconstruct the work yourself?

Start with the inbox, where interruptions hide

An owner opens the inbox to find a supplier asking for confirmation, two routine customer questions, an invoice reminder, a meeting invitation, and a message that requires a decision. None is especially difficult. The problem is that each asks for a different kind of attention. Ten minutes disappear before the owner reaches the work they opened the laptop to do.

Give an agent the first pass. Ask it to group messages by what needs to happen next, identify deadlines, pull out missing information, and draft replies where the answer is already known. A useful output is a short queue, not a rewritten version of the entire inbox.

For example, a supplier's request for delivery confirmation might come back as: 'Confirm whether Thursday delivery is acceptable. Draft reply prepared. No response sent.' The owner can check the calendar or stock position and approve the answer. A message about a disputed charge should be marked for personal attention, with the relevant correspondence attached.

Judge the result by opening a few original messages beside the proposed queue. Did the agent miss a deadline? Did it label a complaint as a routine enquiry? Does each drafted reply actually answer the sender's question? A tidy list that buries the urgent supplier message has made the inbox more dangerous, not less.

Keep control of sending messages, making commitments, and deciding which relationships need personal attention. For the first week, have the agent prepare rather than send. If you find yourself correcting the same category repeatedly, change the instructions before giving it a larger batch.

Next, prepare support answers without promising the wrong thing

A customer asks why an order has not arrived. Another wants to know whether a particular service includes installation. A third says an item is defective. The questions may look similar in a support queue, but they carry different risks. One needs an order check, another needs the current service terms, and the third might lead to a refund.

Give the agent the current support policy, approved product information, and a clear rule about when to stop. Ask for proposed answers with the evidence behind them. If the information does not settle the question, the agent should say what is missing instead of writing a confident reply.

Suppose the customer asks for a replacement. The agent can gather the order details, identify the relevant policy, and prepare a response. The owner or support lead still decides whether to grant an exception, issue a refund, or offer a replacement outside the stated terms. Those decisions affect money and the customer's expectations.

Review the draft against the actual policy, then check the tone. A technically correct response can still sound dismissive to somebody who has waited a week for a parcel. Check especially for invented delivery dates, unsupported promises, and language that blames the customer.

This is a sensible job for an agent because the preparation can be separated from the commitment. The support triager template is one starting point for that division. The human still owns exceptions and the final response.

Then give the agent the paperwork before the payment

Small business bookkeeping often starts with scattered material: an invoice in email, a receipt saved in a folder, a supplier statement, and a note about a purchase that somebody forgot to explain. The repetitive work is finding the documents, extracting their details, and identifying what needs checking.

Ask an agent to prepare an invoice review sheet. It can record supplier names, invoice dates, amounts, due dates, and possible duplicates. It can flag missing attachments and separate items that do not match the available records. That gives the person responsible for the books a better place to start.

Do not start by asking it to pay suppliers, change accounting records, or decide how an unusual purchase should be classified. The consequences of those actions reach beyond a draft. An agent might extract the wrong number from a poorly scanned invoice or mistake a credit note for a bill. A polished spreadsheet does not make the underlying figures correct.

Take five entries from the prepared sheet and compare them with the original documents. Include a credit note, an invoice with tax, and a document with a similar supplier name if you have them. Then inspect every flagged exception. If the agent guessed at an unreadable amount instead of flagging it, that is a reason to tighten the brief.

Keep payment approval, unusual expense classification, and changes to established records with the owner or bookkeeper. The agent's job is to make the next review shorter without hiding uncertainty.

Use a small scorecard before expanding the work

A pleasant-looking deliverable is easy to mistake for a successful delegation. The owner needs a stricter test. Put the original request beside the result and ask whether the agent finished the assigned preparation, kept the facts straight, and stopped where instructed.

There is also a time test. Count the minutes you spend writing the instructions, inspecting the output, and correcting mistakes. Compare that with doing the job yourself. Include the interruptions caused by clarification requests. If reviewing a batch takes nearly as long as processing it, the job is not ready to expand.

Keep the first trial narrow enough to diagnose. Twenty similar messages tell you more about an inbox instruction than a random collection of errands. You can see whether one rule fails repeatedly or whether the source material itself is incomplete.

Make corrections specific. 'Be more accurate' gives an agent little to work with. 'If a supplier names a delivery deadline, put the date in the first line and mark it urgent' gives it a checkable instruction. The same applies to support policies and financial documents.

Keep decisions that change the business with a person

Preparation and action can look almost identical on a screen. A drafted customer reply and a sent reply may contain the same words. One can be edited quietly. The other can create an obligation.

We draw the boundary at actions with effects outside the workspace. In Delagents, an agent carries out a written brief and stops at checkpoints. Its approvals inbox holds actions such as sending, paying, publishing, or changing records until a person signs off. Each approval card shows the exact proposed action, the cost so far, and a deadline. A person can approve, change, or reject it.

Some actions always require a person, including first contact outside the workspace, moving money, deleting or overwriting records the agent did not create, changing access or policy, connecting integrations or widening permissions, signing agreements, publishing publicly, and acting in another workspace. Every delegation also has a hard budget cap and an append-only activity log of tool calls, approvals, and policy changes.

For an owner, that boundary should be practical rather than ceremonial. Approving every extracted invoice line would defeat the exercise. Approving a payment is different. The first is reviewable preparation; the second changes the bank balance. Operations and support teams can use Delagents for teams to structure that separation when several people share responsibility for the work.

A person must also decide what the agent should never attempt. A longstanding customer threatening to leave may need a phone call. A supplier asking to change bank details needs independent verification. The agent can bring the facts together, but those situations should not become routine approvals that somebody clicks between meetings.

Run one real delegation this week

Choose the job that interrupts you most often and already has written reference material. If your inbox is full of mixed requests, start there. If customer questions repeat, choose support. If invoices pile up before bookkeeping day, begin with document preparation. Do not launch all three at once.

Write a brief using one recent batch of real work. Name the inputs, the output you want, the information the agent may rely on, and the conditions that require a person. For inbox triage, the instruction might be: 'Review these 20 messages. Group them by next action. Put anything due within two business days first. Draft replies only where the answer is contained in the supplied correspondence. Do not send anything. Flag messages involving refunds, new commitments, or uncertain facts.'

Keep a copy of the batch and process it yourself once, or use your last completed batch as a reference. Compare the results. Note which errors are factual, which come from unclear instructions, and which need human judgement. Then change one instruction and run another batch of the same kind.

Before Friday, put 20 messages, five support enquiries, or one week's invoices into a single delegation. Give it a defined output and a clear stop rule. Review the result against the originals, record the minutes you spent checking it, and decide whether the next batch deserves the same assignment.