// Resources
Written for a principal or operations lead at an independent agency who has been pitched four AI products this quarter. Which parts of the work are safe to put a system in front of, what the handling costs today, and where the errors and omissions exposure moves.
An independent agency can automate most of the handling and none of the advice. Intake from ACORD forms and emails, certificate and endorsement requests, renewal preparation, direct bill reconciliation, document filing and the chasing that goes with all of it are doing real work in agencies now. Choosing coverage, recommending limits, and telling a client they are covered stay with a licensed person, because that is exactly where errors and omissions claims come from: Utica National's loss control library names failure to obtain or maintain proper coverage as the most common source of claims against property and casualty agents, with failure to communicate a coverage change at renewal a recurring way a gap reaches a client. Adoption has moved fast. The Big "I" and Future One 2026 Agency Universe Study found 46% of independent agencies using AI, against 15% in 2024, while 60% named not knowing what the technology can do as their main barrier. The build worth doing reads your agency management system, drafts, and routes anything it is unsure about to a person whose name is on the file.
An insurance agency can automate the handling, the chasing and the paperwork. What it cannot automate is the advice, or the sign-off that tells a client they are covered.
Sort the work by what it costs to be wrong and the answer gets precise.
| Work | Can AI run it today | What a licensed person still does |
|---|---|---|
| Reading submissions, ACORD forms, dec pages and loss runs into structured data | Yes, with low-confidence items flagged | Checks the flagged reads, handles the unreadable documents |
| Certificate of insurance requests, standard and repeat | Yes | Reviews anything where the holder's wording asks for coverage the policy may not grant |
| Endorsement requests: pre-filling, checking for missing information, submitting | Yes, with review | Approves anything that changes coverage |
| Renewal preparation: pulling the expiring file, flagging exposure changes, assembling the comparison | Drafts it | Decides what to recommend and makes the call |
| Direct bill and commission reconciliation | Yes, first pass | Clears the unmatched items |
| Chasing missing documents, signatures and payments | Yes | Nothing, until somebody does not respond |
| Filing correspondence to the right account and policy | Yes | Spot checks |
| First notice of loss intake and triage | Yes, with review | Owns the claim conversation |
| Recommending coverage, limits, endorsements | No | Everything |
| Telling a client what is covered | No | Everything |
Two patterns in that table decide what a build is worth. The gain comes from volume rather than from complexity: an agency that handles two hundred certificate requests a month gets more out of automating that than out of anything clever. And "with review" is a design decision rather than a disclaimer. A system that drafts two hundred certificates and surfaces the eight it is unsure about is doing the job. A system that drafts two hundred and asks somebody to check all of them has moved the work rather than done it.
Nearly half of independent agencies are already using AI, and the uses are narrower than the pitch decks suggest.
The Big "I" and Future One 2026 Agency Universe Study, released on 23 September 2026 and fielded by Zeldis Research across 1,376 agency responses, found 46% of independent agencies reporting AI use, against 15% in 2024. The leading applications were marketing content generation at 49%, coverage form analysis at 43% and contract review at 35%. The barriers were a lack of knowledge about what the technology can do, named by 60%, and security and privacy, named by 48%. Both barriers were about ten points higher than in 2024, so more agencies are buying than understanding. Insurance Journal covered the same release. One housekeeping note if you go looking: the Big "I" technology landing page currently shows a higher adoption figure than the study release does, and the release is the number used here.
Read those three use cases carefully, because they describe where agencies are comfortable rather than where the hours are. Marketing content is a low-risk place to start and it saves nobody a day. Coverage form analysis and contract review are reading tasks with a person at the end, which is the right shape. What is missing from the list is the servicing and back office work that actually fills a service week.
The same study puts the number of independent agencies at about 37,000 in 2026, down from 39,000 in 2024, while average agency headcount rose from 8.2 to 9.9 staff, and three in four agencies reported revenue growth from 2024 to 2025, with the share reporting declines falling from 12% to 8%. Fewer agencies, each carrying more revenue and more people: that is a market consolidating, and the agencies on the right side of it are the ones getting more out of each person they employ.
"Keeping up with the latest in AI" entered the study's top challenges list this year at 43%, just behind finding and screening good candidates at 45%, with growing personal lines business third at 41%. The first two are one problem. An agency that cannot hire its way out of a service backlog has to run the backlog differently.
The manual work in an agency costs more than most principals have ever put a number on, and the arithmetic takes ten minutes.
There is no credible published benchmark for how long a certificate or an endorsement takes in an independent agency. We looked. The figures in circulation come from vendors and outsourcing firms, they range from eight minutes to nearly an hour for the same task, and not one of them publishes a method. Any page quoting you a single number is quoting a sales deck. So count your own, which is more useful anyway.
Take the volume and the loaded rate. The US Bureau of Labor Statistics puts total compensation for private industry workers at $46.89 per hour worked as of June 2026, in a release dated 9 September 2026, with wages and salaries at $32.82 and benefits at $14.07, so benefits run about 30% on top of pay. Apply that ratio to what you actually pay an account manager rather than to the national average, because your number is the one that matters.
Then the arithmetic. A task that takes twelve minutes, done two hundred times a month, is 40 hours a month. At a loaded rate of $35 an hour, taken from your own payroll rather than from a national average, that is $1,400 a month and $16,800 a year inside one task. Four tasks of that size are $67,200 a year, which is a full-time salary nobody budgeted for, because it is spread across everybody's week instead of sitting on one line. How to count the before and the after properly is in how to measure whether AI automation is saving money.
What follows from that figure is not a saving, it is capacity. Ask what the agency would write if four people had a day a week back, because that is the version of this that shows up in revenue rather than in a cost line.
An insurance agency should never automate anything that constitutes advice, or anything that tells a client they have coverage they may not have.
That is not caution for its own sake. It is where the claims are. Utica National's errors and omissions loss control library names failure to obtain or maintain proper coverage as the most common source of claims against property and casualty agents, and it names renewal handling as a recurring contributor: failing to recognise and communicate a coverage change at renewal is how a gap reaches a client. Certificates appear in the same library, where incorrect information on a certificate is a documented claim source and the errors are usually administrative rather than technical. Worth knowing what you are reading: that is a carrier's own loss control material written for agencies it insures, not independent industry data, and it is still the most specific public account of where these claims come from.
Put those two facts together and the design rule follows. The tasks with the highest E&O exposure are precisely the high-volume administrative ones, which means automation does not avoid the exposure, it changes who touched the record. That cuts both ways. A system that reads a dec page the same way every time removes a class of transcription error a tired person makes at four o'clock on a renewal Friday. The same system, left unsupervised on a certificate that asks for additional insured status the policy does not grant, produces a confident, consistent, documented error.
Four rules keep the exposure where it belongs. A named reviewer for each class of output, because "the team checks it" means nobody checks it. A confidence threshold you set deliberately rather than inheriting from a vendor's default. An audit trail recording what the system proposed, who approved it and when, which is also what makes a claim defensible two years later. And a written scope: the transactions the system may touch and the ones that always go to a licensed person.
Your E&O carrier is a party to this conversation whether or not you invite them. Ask before you deploy, not after, and tell them what stays with a person. What to do when a system does get something wrong is covered in what happens when AI gets it wrong.
Usually, and the agency management system is the first thing to look at rather than the last.
The common systems in independent agencies, among them Applied Epic, AMS360, EZLynx, HawkSoft and QQCatalyst, differ in what they will let another system read and write, and in whether your particular deployment is hosted or on premises. We are not going to tell you what your vendor's interface does, because vendor documentation is not public and the answer depends on your contract. Ask them, in writing, four questions: what can be read programmatically, what can be written back, what is read-only, and whether your agreement permits a third party to connect at all.
Where a documented interface exists, a system reads and writes through it and nothing changes about how your staff work. Where one does not, the work moves to the edges: the documents arriving, the exports going out, the queue a person works from. Both shapes work. The second takes longer and is worth saying out loud at the start rather than discovering it halfway through a build.
Two other things decide feasibility more than the software does. Whether your data is consistent enough to act on, since a system coding into an inconsistent file produces confident nonsense, and is our data good enough for AI covers how to tell. And whether carrier downloads already populate the fields a system would otherwise have to read off a document, because the cheapest automation is the one you do not have to build.
The general version of this question, across every kind of business software, is in does AI automation work with my software.
No, and the industry's own hiring data says agencies are adding account managers rather than replacing them.
The 2026 Agency Universe Study found average agency headcount rising from 8.2 to 9.9 staff, with about one in three agencies reporting more employees than two years earlier and the larger agencies most likely to have added people. Agencies are not shedding service staff while adopting AI. They are adding staff and still falling behind, which is why finding and screening candidates is their top-named challenge at 45%.
What changes is the shape of the role. A service week dominated by keying, chasing, filing and reconciling becomes a week dominated by exceptions, judgment and client contact. That is a harder job and a better one, and it is also the one your licence pays for. The agencies that get this wrong are the ones that automate the handling and leave the freed hours unassigned, because unassigned capacity gets absorbed by whatever is loudest rather than by the renewal book nobody has reviewed in two years.
Decide in advance what the capacity is for. More accounts per account manager, a round of proactive renewal reviews, a cross-sell motion that currently never happens, or a service standard you cannot hit today. That decision is management work rather than technical work, and it is worth making before anything is built. The broader argument about roles is in will AI automation replace my employees.
Start in the order of least risk per hour saved, which is not the order a software demo suggests.
Reading and filing first. Documents arriving, data extracted, correspondence filed to the right account and policy, nothing issued and nothing decided. It removes the single largest block of handling time and the worst outcome of a mistake is a misfiled email. Measure the share of documents read correctly with no touch.
Then chasing. Missing signatures, outstanding documents, unpaid premiums, unreturned renewal questionnaires. The system contacts and tracks, a person handles anybody who replies with a question. Measure how much of the chase list clears without a human touching it.
Then certificates and endorsements with review. The system drafts, a person approves, and anything with unusual wording surfaces individually with the reason. Measure the approval rate, then sample the approvals, because an approval rate on its own tells you how trusting your team is rather than how accurate the system is.
Then renewal preparation. Expiring file pulled, exposure changes flagged, comparison assembled, the recommendation left blank for a licensed person to make.
Keep coverage advice, limits and anything a client could reasonably read as a promise outside the automated path indefinitely. The capability by capability picture for firms that sell and service client relationships like this is on our professional and advisory firms board, with maturity marked honestly on each one.
What moves the number is how many systems the work touches, whether your agency management system exposes a documented interface, how consistent your data is, how many carriers and forms are involved, and how much review you want before anything is issued. A six-person personal lines agency on one system is a different job from a commercial agency running four carriers' portals and a legacy server. BLACKSIG does not publish a rate card; scope is set on the call after the strategy work has said which parts are worth doing. The drivers are broken down in how much AI automation costs.
Documents and requests arrive by email, portal or form. A model reads them, extracts the data, and either acts on it or drafts an action, with a confidence score attached. Anything above your threshold goes into a batch a person approves. Anything below it surfaces individually with the reason. Every proposal and approval is recorded against the account, so the file shows what the system suggested and who accepted it. Coverage decisions never enter that path.
Different trades, and plenty of agencies end up with both. An outsourced service centre gives you judgment and flexibility at a lower hourly cost, and it still has to be managed, trained and kept current on your carriers. A system gives you consistency and instant turnaround on the repeatable share of the work, and it does nothing outside its scope. The useful question is which of your tasks are genuinely repeatable, because those are the ones a system does better and cheaper than any person, and the rest is where a human service team earns its place.
Yes, and email is the normal case. The system reads the request, identifies the account and policy, checks the requested wording against what the policy supports, drafts the certificate and routes anything unusual to a person. The part worth scoping carefully is the unusual wording, since a request for additional insured status or a waiver of subrogation the policy does not grant is a coverage question wearing an administrative costume.
Tell them before you build, and tell them specifically. What the system reads, what it drafts, what it is allowed to issue without a person, who the named reviewer is for each output class, and what the audit trail records. Carriers are increasingly used to this question and the conversation is easier than the one after an incident. Keeping a record of what the system proposed and who approved it is as much for your defence as for your workflow.
We map how your business actually runs, decide where AI is worth using, then our engineering team builds what the plan calls for and we run it from there. We own the outcome, not the deliverable.