AI for insurance
Live systemMedicare brokers, independent agencies, and the licensed agents who live and die by enrollment windows.
In a Medicare brokerage, timing is the product. A lead has an enrollment window, a scope of appointment has to be signed 48 hours ahead, and a disclaimer has to land in the first minute of a call. We build intake and follow-up systems that hold the timing, and we put a licensed human in front of every decision that matters.
4,742
Contacts flagged do-not-contact for compliance
61 / 116
Workflows and tags audited and rebuilt
Human signs
Every enrollment decision, every time
Where the time goes
A Medicare brokerage does not lose money because the agents are bad at selling. It loses money in the places where the clock runs out while somebody was busy.
The call comes in, the agent writes it on a lead sheet, and that works fine for the conversation. Everything after it depends on somebody re-entering the lead, classifying it, and starting the right follow-up. The CRM shows a quiet week that was not quiet, and the paper is the only record that a person exists.
The record starts on a page nobody types up
Every Medicare lead has a date attached: turning 65, a Part B effective date, the annual enrollment period. Miss the window and you did not lose a sale, you left a beneficiary on the wrong plan for another year. Timing this by memory works right up until volume arrives, which in this business happens on a calendar you can see coming.
AEP runs Oct 15 to Dec 7, every year
A scope of appointment has to be agreed 48 hours before a sales appointment, with a few narrow exceptions. When it is a signed PDF in an inbox, proving you had it is an archaeology project. The rule is not hard. Producing the evidence a year later is.
SOA required 48 hours ahead
The fear that stops brokers from automating is specific and correct: that a status change on a test record fires a real "thanks for enrolling" email to a live client. One broker we worked with entered fake email addresses on test records because he did not trust the system not to do exactly that. He was right to be careful.
One wrong send is a real problem
The same person exists three times: once from a purchased list, once from a referral, once from a web form. Merge them carelessly and you drop the tag that says do-not-contact, or the one that says they are already enrolled. Now your compliance posture depends on a database cleanup nobody wants to run.
A careless merge drops a compliance tag
The renewals, the annual reviews, the people whose plans changed in the notice they got on September 30. The whole book needs a touch before enrollment season, and it does not get one, because touching it means somebody remembering every name.
ANOC lands Sept 30. Then the phone should ring
The machine
Here is the machine. In this industry the calendar is a structural part of it, which is why generic sales automation does not fit.
01
02
03
04
The split
Anything regulated passes through a human. The system organizes the pipeline, holds the timing, and surfaces who needs what today. It does not decide, it does not recommend a plan, and it does not enroll. One broker we worked with named the compliance gap himself before we did: pushing a Social Security number or a Medicare number through a generic automation is not compliant, so we did not build it that way. That instinct is the right one, and a system that cannot survive it is the wrong system.
What we build
01
Every inbound call becomes a structured record the day it happens, with the effective dates captured and the enrollment timeline classified automatically. Paper stops being the system of record. The lead sheet can still exist. It just stops being the only place the lead lives.
02
Leads are placed on their real timeline: turning 65, or the annual enrollment period, or an open enrollment window. The pipeline moves them as dates arrive, so the follow-up that matters in October gets queued in October without anybody building a list.
03
Who signed, when, and whether the 48 hour window is satisfied, visible before the appointment gets booked rather than discovered after. The evidence trail is a byproduct of the workflow instead of a folder somebody maintains.
04
Sequences that know what a person has consented to, what they already have, and where they are in the calendar. Kill switches pause everything the moment an appointment books. Nothing fires from a status change on its own, because that is the exact failure that keeps brokers from automating at all.
05
Find the contact before writing, never blind-write over a record. On the audit we ran, 4,742 purchased contacts were flagged do-not-contact, and the merge logic had to protect that tag above everything else. A duplicate is annoying. A dropped compliance tag is a different category of problem.
06
The annual notice of change lands September 30 and tells members what is changing on their plan. That is a reason to call the entire book, and it is the same date every year. The system queues it, aware of what each person is on, so the agent's day is a call list rather than a research project.
In production
Capstone Health · Medicare insurance
Ran live for months / engagement ended when the agency changed CRMsCapstone Health is an independent Medicare agency in Tampa. Every inbound call started life on a paper lead sheet, and everything after it depended on somebody remembering. We rebuilt intake, timing, consent, and follow-up into one operating system, and audited 61 workflows and 116 tags on the way through.
4,742
Contacts flagged do-not-contact
61 / 116
Workflows and tags audited and rebuilt
Same day
Paper leads entered and routed
Under the hood
Agency CRM
Phones and messaging
Carrier registration
A2P 10DLC is the carrier registration a business needs before it can mass-text, and without it the messages are simply blocked. It is not exciting and it is not optional. Half of what makes outreach work in this industry is plumbing like this, done before anybody writes a sequence.
Principles
Most sales automation is built around a funnel. Medicare is built around dates: turning 65, Part B effective dates, October 15, December 7, March 31, September 30. A system that treats these as fields on a contact record instead of the spine of the pipeline will be wrong every season.
The scope of appointment window, the TPMO disclaimer timing, the do-not-contact flags. These are not things you add at the end. They decide what the system is allowed to do, which means they get written down before anything is built, and they show up as tests.
Search for the contact first, then update. Writing without looking is how a purchased-list import silently overwrites a do-not-contact flag on a real client. We learned this rule on a real book of business, and it is now the default on every CRM system we build.
One broker told us that once the appointment is booked, the CRM's job is finished. He trusted his own close rate and wanted the record pushed to his enrollment system the instant it booked. He was right. The bottleneck was never the selling. It was everything that had to happen to get a qualified person on his calendar on the correct day.
Same approach, different language
Home services
Roofing, siding, gutters, windows, and the exterior trades that sell from an inspection instead of a price list.
Live system →Financial services
Advisory firms, lenders, and finance teams where senior people spend their day gathering what they need to think about.
Patterns, no client yet →Healthcare
Practices and clinics where the front desk, the phone, and the documentation load are eating the day.
Patterns, no client yet →Questions
Yes, if the automation stops where the regulation starts. The system captures intake, classifies leads against their enrollment windows, tracks consent and scope of appointment, times follow-up, and keeps the book visible. It does not recommend plans, it does not enroll, and it does not send anything a licensed agent has not approved. Compliance rules get written into the build as constraints and tests, before anything gets built, rather than reviewed at the end.
T65 means turning 65, the age at which a person first becomes Medicare-eligible. It is the single most important date in the business, because it defines a person's first enrollment window and it is knowable years in advance. In the systems we build, the T65 tag is permanent and never removed, because it is a fact about the person rather than a stage in a funnel.
A scope of appointment has to be agreed 48 hours before a sales appointment, with narrow exceptions for walk-ins and the last four days of an election period. We make the status visible before booking rather than after: whether it is signed, when, and whether the window is satisfied. The evidence trail comes out of the workflow itself, so proving it a year later is a lookup instead of an archaeology project.
Not if it is built correctly, and this is the fear worth taking seriously. The specific failure is a status change firing a real message to a live client, and one broker we worked with entered fake email addresses on his test records because he did not trust software not to do it. So the guarantee gets built as a constraint: dispositioning a lead never fires an automated message, kill switches pause sequences the instant an appointment books, and every outbound path has a human in front of it.
Yes, and carefully. The rule is search-first, never blind-write: find the contact before touching it, and protect the compliance tags above all else. On the book we audited, 4,742 contacts carried a do-not-contact flag, and a careless merge that dropped one of those would be a bigger problem than the duplicates ever were. Merges get proposed by the system and approved by a person.
They do not go through generic automation. A broker we worked with flagged that gap himself before we did, and he was right. Sensitive identifiers stay in the systems built to hold them, and the automation works with the pointer rather than the person. If a design requires pushing a Medicare number through a marketing tool, the design is wrong.
Not currently. We ran a live Medicare brokerage system for months with Capstone Health, an independent agency in Tampa: intake, T65 and AEP pipelines, tag architecture, deduplication, and a quality-monitoring loop. That agency has since moved to a different CRM. The system was real, the numbers on this page came out of it, and the domain knowledge did not leave when the engagement ended.
It is the carrier registration a business needs before it can send bulk text messages. Without it, the messages are blocked, and an outreach sequence that nobody registered simply does not arrive. It is boring, it is plumbing, and it decides whether the rest of the work matters. Most of what makes automation succeed in this industry looks like this.
Read next
Explainer
What an AI-legible business actually looks like, the five-point readiness checklist to score your own operation, why one person is usually compensating for every broken handoff, and the 90-day path from messy to legible.
Operations
How to automate workflows without hiring by identifying the repeatable operating loop, clarifying ownership, and embedding the right automation in the right place.
Proof
How a Medicare insurance workflow goes from paper to searchable, trackable, and automatable using cleaner intake, routing, and system-of-record design.
Where to start
Find the bottleneck, price the fix, build the system, then keep compounding it. The four engagements are how you buy it, and you can start on any rung.
See the four engagements →Get started
Book a 30 minute call. We find the one place your work waits on you, and you get a straight answer about whether AI is the fix. No pitch, no deck.