This is the page we wish existed when agency principals started calling us. Not a case for AI, which you have heard, and not a tool review, which will be out of date by the time you read it. Just the sequence that works, the questions that stall agencies, and honest answers to each one. Every section links to a deeper guide if you want it.
How does an insurance agency actually adopt AI?
In five steps, in this order: discovery to find the workflows worth building, governance written and signed before anything is built, building the working projects in the agency's own templates, hands-on training on live client files, and a way to sustain the library afterward. Agencies that skip discovery build the wrong thing. Agencies that skip governance stall at the first compliance question.
The order is the whole trick. Nearly every stalled AI rollout we have seen at an agency went build-first: somebody bought licenses, a few enthusiastic people made something, and then the compliance question arrived and nobody had an answer, so it stopped. Governance written up front is not bureaucracy. It is what lets the building continue.
- Discovery. Walk the actual week with the people doing the work. Not a survey, not a leadership offsite. At one brokerage this surfaced 20 candidate workflows, of which the ten highest-value were built and ten were roadmapped for later.
- Governance. Write and sign the AI Governance Policy before anything gets built. Where the work touches protected health information, the policy has to be HIPAA-aware.
- Build. One project per use case, each carrying the agency's own templates, worked examples, voice rules, and data guardrails.
- Train. Hands-on, on live client files, not sample data. This is the step most programs skip, and it is the step that decides whether any of it survives contact with a busy week.
- Sustain. Put the library somewhere it keeps growing and new hires can find it.
Which workflows should move first?
Template-driven, high-volume work where the inputs already exist and the output follows a fixed format: carrier quote comparisons and renewal analysis, benefit booklets, census-to-bill reconciliation, open enrollment communications, and compliance notices.
The test we use is simple. If the information already sits in a carrier PDF, a census file, or last year's document, and the finished product follows a format your agency has used for years, then a person is currently doing assembly work that does not need their judgment. That is the candidate. We wrote up all five with real before-and-after times from client engagements in the five use cases every agency builds in week one, and if your work does not match that list, the method for picking your own first workflows is the page you want.
The one thing not to start with is anything where the output is a judgment call. Coverage recommendations, claims decisions, and anything a regulator would want a name attached to belong to your people. AI does the assembly, your team does the judgment, and a person reviews every output before it reaches a client.
What does governance have to cover?
Which data can go into an AI tool and which cannot, hard stops on sensitive fields, who reviews output before it reaches a client, and what your vendor does with what you send. Written down, signed, and built into the projects themselves rather than left to memory.
Two pages go deeper here, because agencies ask two different questions. If you are asking what the document needs to say, read what belongs in an insurance agency's AI governance policy. If you are asking whether it is safe to put client information into these tools at all, read client data, HIPAA and PII. The short answer to the second one is that the risk is real and it is manageable, and the agencies in trouble are the ones where staff are already pasting client data into consumer tools without a policy, which is more common than most principals think.
What does it cost, and can grants help?
Our training engagement is $25K and the recurring partnership starts at $2,500 a month. State incumbent-worker training grants can often reimburse employers 50 to 90 percent of training costs, but they generally must be applied for before training starts.
The full breakdown, including what is not in the number, is in what AI training for an insurance agency costs. The grant question deserves its own page because the sequencing is unforgiving: how state training grants work covers what to check and when. Get that order wrong and the money is simply gone, which is a bad way to learn the rule.
Worth separating from cost: whether to train your team or buy a tool that promises to do this for you. Those are different purchases with different failure modes, and we laid the comparison out in AI training or an AI tool.
What changes for the team?
The assembly work shrinks and the review work grows. In our engagements teams recovered 7 to 13 hours per week, and that time went into client conversations, work that used to get squeezed, and service that used to depend on who had bandwidth.
This is where the honest conversation about staffing belongs, and it is the question your team is asking privately whether or not they ask you. We answered it directly in will AI replace account managers and producers. The short version: in the engagements we have run, nobody's job disappeared, and the work that changed most was the work people liked least.
There is also a credential question, since insurance is a continuing-education industry. Where that actually stands, including what does and does not qualify for CE today, is in AI training and insurance CE credit.
What does the proof look like?
Two documented engagements. A five-person group benefits team left a two-day onsite with 11 production Claude Projects and recovers 7 to 13 hours per week, with Phase 1 payback in under 9 weeks. A benefits brokerage put 10 renewal-season workflows on Claude in about six weeks, timed ahead of open enrollment.
AFC-AIS: an AI-powered back office in 30 days
- 11 production Claude Projects, one per use case
- 7 to 13 hours per week recovered across the team
- Roughly $32.5K in annualized capacity, conservatively
- Phase 1 payback in under 9 weeks
LaSalle Benefits: 10 workflows in six weeks
- 10 production Claude Projects in LaSalle's own templates
- Discovery to trained team in about six weeks
- Timed to land ahead of open enrollment
- Signed HIPAA-aware AI Governance Policy
Both are benefits engagements, which is why the benefits brokerage page goes into more segment detail. We would rather point you at two documented engagements than at a longer list of logos.
Where should we start?
With a discovery pass over your real week, whether you run it yourself or with us. The workflows worth building are usually already obvious to the people doing them, and nobody has asked.
If you want to do it with us, that is the Insurance AI Training engagement, and it starts with a free 30-minute call where we walk your week and tell you honestly what would move first. If it is not a fit, we will say so on the call.