Renewal Radar

What it is

Renewal Radar is a commercial-lines renewal agent that runs against your live agency management system. It exists because the most expensive thing that happens in a commercial agency is a renewal that gets attention at day 30 instead of day 120: the remarket window is gone, the incumbent's rate is what it is, and the account either eats the increase or leaves.

Starting 120 days before each expiration the agent assembles, per account:

• policy, premium, carrier, and coverage lines from the AMS;
• the carrier's renewal status where a portal, download, or email notice exists;
• open items in the AMS activity log (loss-run requests, pending endorsements, unanswered questions);
• the most recent client and carrier email threads for that account;
• producer touch history (last call, last meeting, last email).

From that it produces a ranked list with a plain-English reason on every line, a daily digest to the account manager, and for accounts you flag it drafts the remarketing packet (updated ACORD applications, loss-run summary, narrative) and the client outreach email. Everything it writes goes into the AMS as an activity on the account, attributed to the agent, so your existing reports and E&O trail work unchanged.

What it is not

• It does not send anything. Every email, submission, and note is a draft until a person approves it.
• It does not rate or quote.
• It does not touch personal lines. That market has productized per-policy tools and we leave it to them.
• It is not a new dashboard. The digest is an email; the detail is in the AMS.

How we work with you

The work is billed hourly on a time-and-materials basis, and the engineer who scopes it is the engineer who builds it. A typical engagement runs about three weeks from first credential to rollout; the arc is the same even when the pace is not.

Connect and baseline. Read-only AMS access (Epic SDK or Applied's API program, HawkSoft Partner API, or EZLynx API), mailbox access for the renewal and account-manager inboxes, and portal credentials for your top five carriers by commercial premium. We run the agent silently against the next 120 days of expirations and compare its risk calls to what your account managers already know. That comparison is the tuning input.

Tune and write back. Adjust the risk rules to your book (a 12% indication may be routine for one carrier and a red flag for another), turn on activity-log write-back, and start the daily digest to one account manager.

Packets and rollout. Enable packet and outreach drafting, roll the digest to the whole commercial team, hand over the runbook and the accuracy report.

What you need to provide

• An AMS admin who can grant scoped API credentials (we specify exactly which).
• One account manager as the reviewer for the first two weeks, about 20 minutes a day.
• Carrier portal logins for the top five commercial carriers, or the notice emails they send.

Security and data

Credentials are stored in a secrets manager, never in prompts or logs. The agent runs in a single-tenant environment in a US AWS region under an account you can audit. Client data is not used to train any model. Details on the approach page.

After go-live

Most agencies add the COI Agent next, because certificate requests spike at exactly the renewals the radar surfaces, and the AMS integration is already in place. Ongoing operations work (monitoring, connector maintenance as carriers and the AMS change, accuracy review, tuning) is available on the same hourly basis.

Next step

Tell us which AMS you run and roughly how many commercial renewals you handle a month, and the engineer who would build it replies with how we would start. Contact us.