--- title: "An agent factory for a firm with no IT department" url: "https://biznesiq.com/blog/an-agent-factory-for-a-firm-with-no-it-department" description: "Software teams are moving from one assistant to a loop of agents. The same model will reach small service firms, provided their work is written down." --- # An agent factory for a firm with no IT department November 2, 2026·5 min read·BiznesIQ The agent factory will reach a five-person service firm sooner than it reaches many large companies, because the firm’s work is short, repetitive and has a clear end. There is one condition: the work has to be written down somewhere, not just remembered. “Factory” sounds like a stretch here. Nobody at a heat pump installer is going to build one. But software teams are walking a road that small firms will walk shortly, and it is worth seeing where it leads. ## From a chat window to a loop Over a few years developers went through four stages. First they asked a chat window and pasted the answer. Then the tool suggested code while they typed. Then they steered an agent step by step on their own laptop. Now, more and more often, a ticket enters a loop, agents carry it through the stages, and a person signs off at a handful of decision points. In a small service firm the same stages look like this: Stage What it looks like in a service firm A chat beside the work the owner asks a chatbot at night for a politer version of an email to a customer Suggestions in the tool the invoicing program proposes a line description An agent steered by hand the owner pastes in an enquiry thread, asks for a draft quote, then retypes it into a document A loop the enquiry lands in one queue, the draft quote, the booking and the invoice are prepared along the way, and a person approves every step that leaves the firm Most small firms are at stage one or two. The gap between three and four is bigger than the table suggests. At stage three the agent is an extension of one person and disappears when that person closes the laptop. At stage four the work stops being private and becomes the way the firm runs. ## Why developers got there first Not because they are cleverer than the owner of a plumbing firm. Their work has long met three conditions that small-firm work usually does not. **The input is recorded.** A ticket has a text, an author and a date. In a small firm an enquiry arrives as a phone call to the technician who is up a ladder, and its content lives in his head until the evening. **The output can be checked.** Code passes the tests or it does not. A quote in a small firm is right or wrong depending on whether the owner remembers what he charged for a similar job last year. **Every change leaves a trace.** A developer can tell who changed what and why. In a small firm a new date is a text message and a change of scope is a conversation on a doorstep. So an agent factory in a service firm will not start with buying an agent. It starts with the job having a record from the customer’s first message to the paid invoice. Then the agent has something to read and a person has something to approve. How a firm that lives in one head loses all of that the first time the owner takes a week off is the subject of [A firm that lives in one head](https://biznesiq.com/blog/a-firm-that-lives-in-one-head). ## Two jobs instead of one In teams that already work in a loop, everyone has two jobs. The first is the work for the customer. The second is improving the loop that prepares that work. In a small firm this looks ordinary. The owner still decides what a job costs, because he knows the customer, the street and what the bathroom wall looked like once the tiles came off. But when a draft quote is wrong, he fixes more than that quote. He fixes the rule it came from: add an hour for surprises behind the plaster in the old blocks, give a referred customer an earlier slot. After a quarter the drafts need fewer corrections, because the loop has learned what only one person used to know. That is the whole difference between a tool and a system of action. A tool does the same thing every week. A loop with recorded corrections does it a little better each time. ## Where the factory does harm Two traps are already visible in software teams, and both are worse in a small firm. **A loop with nobody in it.** Part of the market promises agents that send quotes on their own, chase payment on their own and answer complaints on their own. A five-person firm has one reputation and a town that talks. An agent that chases an overdue invoice from a customer with an open complaint does not save time. It costs a customer. The agent reads, prepares and proposes. A person decides, sends and answers for it. **Work that suddenly becomes visible.** Once jobs have records, you can see who went back for callbacks most often and whose quotes the owner rewrites most. In a firm where everybody knows everybody, a league table built from those numbers will break the team faster than in a corporation. The numbers are there to improve the loop: the quote, the price list, the plan. Not to rank people. ## How to tell it is working Vanity metric Outcome metric how many drafts the agent produced how many times a person touched one job from enquiry to payment how many AI features your software has how many drafts went to the customer with no change to the content how many messages the system read how many days pass between a finished job and a sent invoice Be honest with yourself. A customer may turn a quote down on price, and an invoice may sit unpaid because the customer is having a bad month. The loop gets you to that truth faster. It does not change it. ## Where to start Pick one thing that comes round every week and has a clear start and end. Usually that is a quote from an enquiry or an invoice after a finished job. Write it down as if you were handing it to a new hire: what comes in, what must come out, how you know it is right, and who signs it off. If it does not fit on one page, an agent will not manage it. Neither will a new person in the office. BiznesIQ is being built as that kind of loop around the job: it reads the enquiry and prepares the quote, the booking, the invoice and the reminder, and nothing leaves without a person’s approval. For now we run our own work on it. The [home page](https://biznesiq.com/) describes the whole of it. That leaves a choice. You can wait until agent loops mature in large companies and only then start writing your work down. Or you can start now, so that on the day the tools are ready your firm does not first have to get everything out of one person’s head. - agent factory - AI agents - jobs - small business ## Keep reading - [An agent factory in a small firm: the loop around the job](https://biznesiq.com/blog/an-agent-factory-loop-around-the-job) - [What is operational intelligence software? A guide for small businesses](https://biznesiq.com/blog/what-is-operational-intelligence-software)