In an independent insurance agency AI arrives in three places before anyone decides anything: the producer's desk that summarises a prospect's policies and drafts the proposal, the service team's inbox that answers the client's coverage question and sends the certificate, and the renewal desk that remarkets the account and writes the comparison. The owner's job is not to pick the tool. It is to decide three things before a tool touches a quote, a client's policy or a claim: who in the agency owns the question, what may never go into an outside tool, and what the agency will never let a machine do alone. This article is for the owner or principal of an independent property-casualty or benefits agency, or a brokerage built by acquisition, with a few dozen to a few hundred people.

I was COO and then President of a public company that closed more than forty acquisitions, and I ran the integration on most of them. I am a lawyer by training. Now I write fixed-fee AI plans for CEOs of private-equity-backed and owner-led mid-market companies through 013 Labs, and agencies are the group where a tool's mistake becomes coverage advice, given in the agency's name, that a client relies on.

Where AI already is in your agency

Ask a producer what the free tools on the desk's phones are doing this week and the honest answer is: reading the prospect's current policies into a summary, drafting the proposal, writing the follow-up. Ask the service team and it is the first draft of the answer to "am I covered for this", the certificate request, the answer to the carrier's underwriter. Ask the renewal desk and it is the comparison of the incumbent against the remarketed quotes and the letter that explains the increase. Ask the agency-management vendor and it is the drafting feature that switched itself on with the last release. None of it was approved. Some of it has already told a client what a policy covers with nobody's name on it, and some of it has carried a client's policy, loss runs, driver list or medical information onto a vendor's server.

The three decisions, in the order an agency makes them

Who owns the question. Not the IT provider, not the agency-management vendor and not a new hire. In most agencies it is the operations lead, the commercial lines manager or the compliance lead, because they are the people the producers and the service team already ask when something new shows up. Give that person a written scope of half a page: what they may approve alone, what comes to the owner, when the page is reviewed. The article on AI for a small business with no IT department draws the line between their column and yours.

The data rule. One sentence. For an agency it usually reads: no client's policy, application, loss runs, driver or employee list, claim file or medical information, no carrier's rates or appointment terms, and nothing about an employee go into a tool the agency has not approved. The owner writes it, because the client's file is protected by the privacy rules the carriers hold the agency to, and the carrier's terms are under contract.

The never-build list. The three things the agency will never let a machine do alone. For an agency the list writes itself: no coverage advice, answer to "am I covered" or recommendation leaves the agency without a licensed person reading it and putting a name to it; no quote is bound, no certificate issued and no application submitted to a carrier by a tool; no claim is reported, described or advised on by a tool alone. Everything else is a question of fit. These three are not.

What fits at fifty people, and what does not yet

The first project is the work your people already do by hand, the same way, every week: the prospect's policies read into a summary for the producer to check against the declarations, the first draft of the proposal, the renewal comparison for the account manager to finish, the certificate request logged, the follow-up written. The article on picking your first AI project has the five tests. What does not fit yet, in most agencies this size, is anything that decides for a client or a carrier: the coverage answer, the recommendation, the binding, the application, the claim. A tool can prepare any of those for a licensed person. It should not finish them. The earlier page on how AI can help an insurance agency lists the tasks; this one is about the decisions.

The carrier, the errors-and-omissions insurer, the regulator and the buyer will ask

The AI question reaches an agency from four directions that have nothing to do with technology. The carrier's agency audit and its appointment agreement now ask which systems touch the carrier's rates and the client's information, and whether a licensed person stands behind every submission. The errors-and-omissions insurer's renewal form asks whether automated tools give advice or produce documents in the agency's name, because an answer a tool gave is an answer the agency gave. The state regulator asks it in its own words about licensed activity. And a buyer, strategic or private equity, asks it in diligence, because agencies are the most acquired businesses in the country; the article on whether AI makes a business worth more when you sell has that version, and the one on what to tell your bank about AI covers the bank. One dated page answers all of them.

Picture a commercial-lines agency of ninety people with three offices, built from four acquisitions in six years. One office's service team has been answering clients' coverage questions from a free tool on their own logins for a season, and the inbox has been clear by noon for it. The owner finds out when the errors-and-omissions renewal form asks whether automated tools produce advice in the agency's name, and then finds that a client was told a loss was covered when the policy excluded it, that the answer went out under the account manager's signature without her reading it, and that the client's policies and loss runs went into the same tool. The fix takes a week and one call to the agency's own errors-and-omissions carrier. The operations lead is named as the person who owns the question, with a half-page scope. The owner writes the data rule: no client file, no carrier rate, no employee file into an outside tool. The never-build list goes on the page, starting with no coverage answer sent unread by a licensed person. The free tool is replaced by the agency plan the same week, the client gets a corrected answer in writing from a licensed person, the files are deleted from the vendor's account with the deletion confirmed in writing, and the renewal form gets the page. This is a hypothesis, a composite and not a client.

The one page

What is in use, by desk and task, including the free tools and the features the agency-management vendor switched on. Who owns the question, with the written scope. The data rule in one sentence. The never-build list, the three items above. The review date and who signs. The owner signs it, the compliance lead keeps it with the licensing records, and the operations lead attaches it to the next carrier audit and the errors-and-omissions renewal. The board-briefing template has the same page in a form an agency can fill in. Not sure which of the three is missing? The AI readiness scorecard asks the questions an agency principal can answer from memory.

Mistakes that repeat

Letting the agency-management vendor switch it on. A drafting feature arrives in a release, defaults to on, and the next client letter carries advice nobody read. The owner decides, feature by feature.

The client's file in a free tool. The one mistake that puts the agency in front of the carrier's auditor and the client's lawyer. The data rule exists for this.

A coverage answer nobody licensed read. A tool drafts the answer to "am I covered"; the account manager sends it at the end of the day. The client relies on it. A licensed person reads every answer about coverage.

A comparison that flatters the tool. The renewal comparison a tool wrote from the quotes it could read misses the exclusion in the one it could not. A person reads the forms.

No review date. Carriers change their audits, regulators change their rules, people change offices. A page without a date is a page nobody opens.

Frequently asked questions

Should an insurance agency use AI?

It already does, through the producers' desks, the service team and the renewal work. The decision worth making is who owns the question, what may never go into an outside tool, and the three things the agency never lets a machine do alone: coverage advice without a licensed person's name, a quote bound or an application submitted by a tool, and a claim handled by a tool.

Who should own AI in an agency?

The person the producers and the service team already ask when a new tool shows up, usually the operations lead, the commercial lines manager or the compliance lead, with a written scope of half a page and a review date. Not the IT provider and not the agency-management vendor.

Can AI answer our clients' coverage questions?

It can draft, from the policy forms a person has given it, for a licensed person to check against the forms and sign. It should not answer, because the answer is advice given in the agency's name and the errors-and-omissions carrier will ask who gave it.

What about client information in these tools?

It is first in the data rule. No client's policy, application, loss runs, driver or employee list, claim file or medical information goes into a tool the agency has not approved, and the approved tools are on business plans whose terms keep the data out of the vendor's training. If client files have already gone into a free tool, delete them from the vendor's account, get the deletion confirmed in writing, and tell the agency's errors-and-omissions carrier the same week.

Why does my carrier or my errors-and-omissions insurer ask about AI?

Because each carries the risk when advice, a submission or a document that a tool touched turns out to be wrong, and each wants to know whether a licensed person stands behind it. One dated page with names on it is the answer, and the same page answers the regulator, a buyer and the bank.

Not sure where you stand? Take the 3-minute AI readiness scorecard.