Why every agent reads the same policy book

Nine specialist agents could easily become nine separate opinions. Legal would have its own idea of what the business allows, Finance another, Customer Support a third. Every handoff between them would be a chance for something to get lost, contradicted or quietly dropped. So we built them around one rule: every agent reads the same policy book.

What the policy book is

The policy book is the written version of how your business works. It holds the rules you already follow, often without writing them down: who can approve what, which documents a new hire needs, how you talk to customers, what data you keep and for how long, and which requests go straight to a person.

It is not a prompt hidden inside one agent. It sits beside all of them. When the Finance agent checks an invoice and the Legal agent reviews the contract behind it, they are reading from the same page.

Specialists, not generalists

Each of our nine agents owns one discipline: Legal, Data Protection, Finance, HR, Sales, Business Assistant, Marketing, Website and Customer Support. Specialising keeps each agent's job narrow enough to do well. A generalist that tries to do everything tends to do each thing a little worse, and it is harder to tell where it went wrong.

Specialists create a new problem, though. Work rarely stays inside one discipline. A new customer touches Sales, then Legal, then Finance, then Customer Support. If each specialist has its own idea of the rules, the customer feels every seam.

The shared policy book is how we close those seams.

Why one book beats nine

Consistency at the handoff

When work changes hands, the receiving agent does not need to guess what the sending agent assumed. Both worked from the same rules. The HR agent does not promise a start date that the Finance agent cannot pay for, because both read the same approval limits.

One place to change a rule

Businesses change. A new supplier, a new law, a new price. With one policy book, you change the rule once and every agent follows it on the next piece of work. With nine separate configurations, you change it in eight places and forget the ninth.

A record you can read

The policy book is written in plain language. You can read it, question it and correct it. That matters, because the people who know how the business should run are the owners and operations leads, not us. We help write it down. You decide what it says.

Writing it down is the hard part

Most of the rules in a small business live in people's heads. Nobody ever needed to write down that refunds over a certain amount go to the owner, because everyone just knows. Agents cannot just know.

This is where forward-deployed engineering comes in. Before we switch anything on, our engineers learn how the business actually works: who does what, where information lives, and where work waits for someone's time. The first version of the policy book comes out of that work.

What it means for your team

For your team, the result is simple. Work that moves between agents arrives with its context intact. Answers are consistent whether they come from Sales or Customer Support. And when something needs a person, it arrives at the right person with the reason attached.

Your team gets its time back for the work only people can do: building relationships, solving problems and moving the business forward.