Activate when: an insurance agent wants to keep clients renewing and buying more lines; 'how do I stop losing clients at renewal', cross-sell/round-out accounts, book retention; 'my retention is dropping'. Do NOT activate when: the agent has no existing book to retain. More: deciqai.com/s/insurance-renewal-retention-ladder
Scanned 9/3/2026
Install to Claude Code
npx -y skills add deciqAI/knowledge-skills --skill insurance-renewal-retention-ladder --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Insurance Renewal Retention Ladder?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/deciqai-insurance-renewal-retention-ladder)More formats (shields.io, HTML) on the badges page.
---
name: insurance-renewal-retention-ladder
description: "Activate when: an insurance agent wants to keep clients renewing and buying more lines; 'how do I stop losing clients at renewal', cross-sell/round-out accounts, book retention; 'my retention is dropping'. Do NOT activate when: the agent has no existing book to retain. More: deciqai.com/s/insurance-renewal-retention-ladder"
---
# Insurance Agent — Renewal & Retention Ladder
> **Industry front door for [customer-relationship-ladder](../customer-relationship-ladder/SKILL.md).** Adds domain triggers, example, packs. Parent Process unchanged.
> **Guidance, not professional advice.** No legal, tax, financial or regulatory advice; verify anything jurisdiction- or rate-dependent against current authority. The professional who acts owns the decision.
**Activate when:** building a renewal/retention cadence; deciding cross-sell timing; a book with single-line clients; retention slipping at renewal.
**Do NOT activate when:** no book yet.
## Why this variant
The parent [customer-relationship-ladder](../customer-relationship-ladder/SKILL.md) moves contacts up rungs. Insurance is a recurring-revenue business where retention and account rounding (multiple lines per household) drive profit far more than new logos. The ladder turns a one-policy buyer into a multi-line, long-retained, referring client.
## Domain inputs → the ladder
Rungs and lift triggers:
- One policy → **rounded account** (auto+home+umbrella; business owner: add lines) via annual review.
- Rounded → **retained** (proactive pre-renewal contact, coverage-gap review before the carrier's rate letter causes shopping).
- Retained → **advocate** (referral ask after a good claim experience or a savings win).
Each rung = a scheduled touch (feed a CRM/renewal agent), not a hope.
## Worked example
Client has only auto; agent contacts them only when the renewal price jumps → client shops and leaves.
→ Ladder fix: annual review rounds the account (multi-line clients retain far better), proactive pre-renewal outreach reframes value before the rate letter, referral ask after a smooth claim. Retention and premium per household both rise.
## Packs
- **Solo agent**: annual-review + pre-renewal outreach cadence; round-out checklist.
- **Agency**: monoline-account report → cross-sell campaign; at-risk renewal alerts.
## Red flags
- Only contacting clients when price rises.
- Monoline households left un-rounded (low retention).
- No proactive pre-renewal touch (carrier rate letter drives shopping).
## Verification
- [ ] Annual review / account-rounding process in place
- [ ] Proactive pre-renewal outreach scheduled
- [ ] Multi-line penetration tracked
- [ ] Referral ask timed to a positive moment (claim/savings)
---
*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/insurance-renewal-retention-ladder** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*
*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/insurance-renewal-retention-ladder.json*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!