Most talk about the future of work is about big companies. Whole job titles disappear, or they don't, depending on who is writing. In a business of twelve people, it looks smaller and more practical.


People decide and approve. Agents do the repeatable steps. Jobs are redesigned one task at a time, not replaced in one go. That is the version of the future I find useful for a small business, because you can start on it this month.


A job is a bundle of tasks


Nobody's job is one thing. Take an inside sales rep at a distributor. In a normal week they answer inquiries by email and phone, check stock, build quotes, follow up on the quiet ones, update the CRM, chase a late delivery, and help a customer choose the model that fits their kitchen.


Some of those are steps. They follow a rule, they repeat, and the hard part is remembering to do them. Checking stock, drafting the follow-up, logging the call, sending the delivery update.


Some are judgment. Which model fits. Whether to hold a price for a good customer. How to answer someone who is upset.


An agent is good at the first kind and should not be left alone with the second. So the useful question is not "will AI replace this job?" It is "which tasks in this job are steps, and who checks them?"


The org chart gains agents, each with an owner


When you redesign work task by task, the org chart changes quietly. The boxes stay. Under some of them, agents appear.


Each agent needs an owner: a named person who writes or approves its instructions, approves what it produces when approval is required, reads its log and answers for it. Usually that is the person who used to do the task, because they know where it goes wrong.


We drew this out for a typical small business on the org chart with agents page: where agents fit in each team, who approves their work, and how much capacity it frees.


Twelve people, each with agents


Picture a hypothetical restaurant equipment distributor with twelve people: the owner, an office manager, a bookkeeper, two inside sales reps, an outside rep, a buyer, a warehouse lead, two warehouse staff and two service technicians.


Here is what their week could look like once each person has agents.


  • Inside sales reps. An agent drafts a quote from each inquiry, using the current price list and stock, and drafts follow-ups on quotes that went quiet. The reps fix and approve. They spend the time on calls with customers who need help choosing.
  • Outside rep. Before each visit, an agent prepares a one-page brief: what the account bought, what is open, what it asked about last time. After the visit, it turns the rep's voice note into a CRM entry for the rep to confirm.
  • Buyer. An agent watches stock against minimums and prepares purchase orders. Nothing is ordered until the buyer approves it, because it spends money.
  • Bookkeeper. An agent drafts polite payment reminders on overdue invoices, from the invoice and the account's history. The bookkeeper approves each batch and handles the accounts that need a phone call.
  • Service technicians. An agent turns job notes and photos into a service report and a draft invoice. The technician checks it before it goes to the customer.
  • Office manager. An agent sorts the shared inbox, answers routine questions about hours and delivery zones from approved answers, and routes the rest to the right person.
  • Owner. A Monday report arrives with sales, open quotes, money owed and stock issues, in plain sentences. Price changes and anything public wait in one approval queue.

Notice what is not in that list. Nobody's job disappeared, and nobody's judgment was handed to software. The warehouse lead still runs the warehouse. What changed is how much of each day goes to steps, and how much goes to customers, selling and fixing what matters. What to do with the time is the owner's call.


The skills that matter more


When agents take the steps, a few skills become the job.


  • Judgment. Knowing when a draft is wrong, when a customer needs a call instead of a message, when a rule should bend.
  • Writing good instructions. An agent follows what is written. A clear process, written step by step, is what turns a task into something an agent can do well. We show how a written process becomes an SOP, then a skill an agent follows.
  • Checking work. Reading a batch quickly, looking closely at the ones that matter, reading the log when something looks off. Approving is a skill, not a click.
  • Keeping the facts right. Prices, stock, policies and customer history in one place, current. Every agent depends on them.

None of these are new. Good employees have always had them. What changes is that they become most of the work, instead of what you get to once the busywork is done.


Managers own outcomes and approvals


A manager's job moves in the same direction. Less assigning and chasing, more deciding.


In practice that means three things. Decide what each agent may do on its own and what waits for a named person. A rule that holds up: anything that spends money, changes a price or goes public waits for approval. Approve, or hand the approval to the right owner. And check that the work got done: quotes followed up, invoices chased, reports delivered.


It also means reading AI cost the way you read payroll. We set out the measures for that on headcount to token burn: what agents cost per person, the hours they return and how often their work is approved as is.


What goes wrong


The failures are predictable. That is good news, because predictable failures can be prevented.


  • Bad data. An agent quoting from last year's price list does the wrong thing faster. Fix the facts before you add the agent.
  • No approvals. One message nobody saw, sent to the wrong customer, costs more trust than a month of good drafts earns.
  • Nobody owns the agent. Instructions drift, nobody reads the log, the same mistake repeats. An agent without an owner should be switched off.
  • Doing it to people instead of with them. If the person who does the task today does not help write the instructions, the agent misses what they know, and they have reason to distrust it.

Where to start


1. Pick one role and list every task in it for one week, in that person's own words.

2. Mark each task as a step, judgment, or both.

3. Choose two or three steps that repeat every week and follow a written rule, or could.

4. Write the process down with the person who does it now.

5. Name the agent's owner and set the approval rule before it runs.

6. Run it for a month, read the log together, then decide what comes next.


One role and one month at a time is slow enough to get right and fast enough to see the difference.


Where a Brain fits


This is the work a Humonix engagement is built around. The facts, the written processes and the approval rules go into a Brain the business owns. Agents work from it, each with a named owner, and every action is logged. How an engagement runs shows the steps, from the deep audit to the monthly report. People keep the decisions. That part of the work stays with them.