The 90-day window before a policyholder shops the renewal.
By the time a policyholder calls to shop the renewal, you have a couple of weeks to save them. Per industry research on B2B retention precursors, the carrier-side, DocuSign-side, and AMS-side signals that precede shopping typically fire 6–12 weeks earlier — but nobody pipes them to your Applied Epic or your HawkSoft. So most of those calls feel like ambushes. They aren't. The book has been telling you for weeks. Aurora's predictions get sharper over time as your outcomes feed back into the model.
If you run a 5- to 50-producer independent agency — somewhere between $2M and $20M of commission revenue, 500 to 5,000 policyholders — the math on retention is the only math that matters. A new commercial-lines account costs you 3 to 5x more in producer time than retaining one. And in the standard book, anywhere from 8 to 15 percent of policyholders shop their renewal in any given year. Most of them shop quietly — through a digital aggregator, through a friend at another agency, through their accountant who knows a guy. You only find out when the BOR letter arrives or when the renewal application stops getting returned.
The frustrating part: the signal that they're shopping starts firing months before they call. It just fires in places your AMS doesn't see.
Why your AMS doesn't tell you
The agency management systems were built to do three things well: store the policy, track the commission, and produce the renewal application on schedule. They were not built to be retention systems. The retention signal lives in three places outside the AMS, and your AMS doesn't pull from any of them by default.
The first place is the carrier portal. When a policyholder logs into Progressive Commercial or Liberty Mutual or The Hartford and starts pulling their declarations page, that's a signal. When they're requesting Loss Runs — especially if your agency didn't put in the request — that's a stronger one. When their broker-of-record letter is being prepared on the carrier side (which has a status flag visible to the agency), that's the last warning before it lands in your inbox.
The second place is e-signature activity. DocuSign and similar tools log envelope opens, signer drop-offs, and re-routes. A policyholder who used to sign a renewal in 30 minutes and now leaves it open for 11 days is telling you something.
The third place is the inbox cadence between the producer and the policyholder. Same pattern as every other vertical: response time elongates, replies get shorter, the holiday-card warmth fades from "great hearing from you" to "thanks." Your producers feel it but rarely log it. Even if they did, no central view aggregates twenty producers' email tone.
The five insurance-specific signals
Here is the inventory we are building the ClientPulse insurance vertical around. Every one of them comes from a tool the agency already runs — we don't introduce a new system, we read the systems you already have.
What changes when you see it in week six
The conversation in week six is a relationship call, not a sales call. It sounds like:
Hey — we're seeing this renewal come up in October. Wanted to get on the calendar for fifteen minutes before the markets get tight. Anything new on your end I should know about — new locations, new equipment, anything that would change the program?
About half the time, the policyholder volunteers what's actually going on: a price hike they're worried about; a friend at another agency who quoted them; a coverage gap their accountant pointed out. You get the chance to address it before they've signed anything. The other half, the conversation simply renews the relationship and the file goes through normally.
The same conversation in week sixteen — once the BOR letter is on the way — is a different call. It's recoverable, but the math gets ugly. You're now competing on price against the broker who already has the quote.
Where ClientPulse is in the insurance vertical
ClientPulse is a client-health platform built on 25 source categories — portable-core sources every retainer business has (Gmail, Calendar, Slack, HubSpot, and more), plus vertical-specific integrations for insurance: Applied Epic, HawkSoft, DocuSign, AMS360, and carrier-portal data.
The platform scores each account across communication, financial, and operational signals — then surfaces the renewals you need to call this week, with a plain-English reason for each. Premium analytics (NRR, GRR, Per-AM Scorecard, Forward Renewal Pipeline, and more) give you the book-level view that no AMS provides.
If you've watched accounts BOR-out in the last year and want the system that catches the next five before the loss-run gets pulled, ClientPulse is built for exactly that job.
What to do this week, with or without us
Three things to do tomorrow morning that don't cost anything:
- List your top fifty commission-revenue accounts with renewals coming in the next 120 days. For each one, log into the carrier portal and check loss-run request history. Anything pulled by a party that isn't your agency in the last 30 days is a five-alarm signal. Make those calls this week.
- Pull the DocuSign envelope log for the same fifty accounts. Sort by time-from-send-to-signed. Anything sitting open longer than ten days is worth a producer follow-up call.
- Decide which AMS report shows you producer-email-response time across the book, and if the answer is "none of them," put a thirty-minute weekly review on someone's calendar to do it manually for the top fifty accounts. It's tedious work that pays back the first time it surfaces an account before the BOR.
See your book, color-coded by renewal risk.
ClientPulse watches the signals that precede policyholder shopping — loss-run pulls, envelope delays, producer response gaps — and surfaces the accounts you need to call this week. Try the live demo or join the waitlist for early-access pricing.
$99 / $299 / $799 per month · Cancel anytime · Stuttgart, Germany.