Insurance · Manager Coaching Call
Two Quarters Down: A Sales Coaching Roleplay for Insurance Teams
Your rep sells claims technology into carriers. Their territory is a mix of regional mutuals and mid-size stock companies, their buyers are Chief Claims Officers, VPs of Claims Operations and the occasional SIU Director, and every single deal has to survive a conversation with a chief actuary who wants the savings expressed in ALAE per claim, not in "efficiency." They've missed two quarters. Not spectacularly — 81% and then 76% — which is the hardest kind to coach, because there's always a Guidewire migration or a hail event you can point at and be partly right.
And they will point at them. This rep walks in with the excuses pre-loaded and half of them are legitimate: three of their best claims contacts really did go to storm duty in April, two of their target accounts really are 18 months into a core replacement with zero IT bandwidth, and mutuals really do treat surplus as policyholder money. Underneath all of that, their discovery calls end at minute nine with a demo of the SIU scoring module, and they stopped building pipeline sometime around the week they got excited about two deals that were never going to clear actuarial review.
This playbook is the manager's side of that 1:1. It follows the sequence that actually works — pull the tape first, drain every excuse before you touch any of them, concede the one that's true so you earn the right to press the ones that aren't, and leave with one changed behaviour the rep wrote themselves. In the sample dialogue below, "Rep" is you, the manager running the call, and "Buyer" is the rep you're coaching — because in this conversation, they're the one you have to sell.
The manager coaching call script
Say it in your own words. The structure is the part that matters.
- 1
Before you open your mouth: pull the tape
Do not walk into this with a feeling. Walk in with six things printed: 1. **New opportunities created per week, last 90 days.** If they created 7 in month one and 2 in month three, that chart is the entire conversation and you barely have to talk. 2. **Coverage against next quarter, split by carrier type.** Mutual, regional stock, national. A pipeline that's 3x on paper but 80% mutuals in a closed planning cycle is not 3x. 3. **Stage conversion vs. team median.** Specifically: first call to second call. In claims tech, that's where the floor drops out, because the first call is where you either got the Chief Claims Officer to say their days-from-FNOL-to-final-payment number out loud or you didn't. 4. **Closed-lost reasons.** Count how many say "price" or "no budget." Then count how many of those had a documented loss ratio impact or a quantified leakage number in the CRM. It'll be close to zero. 5. **Who they actually met with.** Meetings with a Director of Claims Transformation are not meetings with an SVP Claims. Innovation-team meetings should be logged separately, because that's where claims vendors go to die. 6. **Two recordings, timestamped.** One won, one lost. If "my territory is all mutuals" is real, you'll see it in their meeting-to-second-call rate matching a peer's on the same segment. If it isn't, you'll see their meeting rate is fine and everything after the first call is where it collapses. Know which is true before you sit down.
- 2
Open: name the stakes in two sentences
"Two quarters is a pattern, not bad luck, and I'm not going to sit here and pretend it's variance. But I didn't book this to read you your attainment — you know your attainment. I want to work out what's actually going wrong, because I think it's one thing and not five, and I genuinely don't know yet which one it is. Fair?" That's it. No "how was your weekend." They know why they're here. The false warmth reads as a setup and they lock down before you've asked a real question. Do not say the words "performance plan" in the first ten minutes — the second a rep hears it, they stop diagnosing and start building a defence, and you've lost the only honest thirty minutes you were going to get.
- 3
Drain the tank — every excuse, before you touch any of them
"Before I say anything at all, give me the full picture. What's making this hard? Everything — I don't want the diplomatic version." Then after each one, only two words: **"What else?"** Ask it three times minimum. Write them down where they can see the pen moving. In this territory the list usually runs: my accounts are all mid-migration and IT has nothing until 2027; cat season wiped out April and May because half my claims contacts were on storm duty; every mutual in my patch says surplus is policyholder money; the challenger is 20% under us; every SIU Director I talk to got burned by a fraud analytics vendor two years ago and turned it off. Then read it back flat, no editorial: *"So — core migrations, cat season, mutual budgets, price against the challenger, and the SIU fraud-vendor hangover. That's the list? Nothing else?"* Getting explicit agreement that the list is complete is what closes the escape hatches later. If a sixth thing appears in minute twenty-five, you get to name it.
- 4
Sort the list: real, partly real, story
Work each one *with* them, and take it completely seriously before you test it. Start with the one you can settle with data: "Let's take mid-migration first, because if every account in your patch is frozen until 2027 I need to go argue about territory design and I'd rather know now. You had 38 target accounts. Priya had 34 in the same segment mix. She booked 16 first calls, you booked 15 — so at the top you're identical. Where it splits is after: she moved 9 of 16 to a second call, you moved 3 of 15. Help me understand that gap." Then stop talking. Ten seconds of silence here is worth more than anything you could add. On price: "Five of your eight losses say price. Of those five, how many had a number attached — like, this carrier is running 4% leakage on $180 million of paid losses and here's what one point back is worth? Walk me through Keystone Mutual. What did the VP of Claims Operations say their average cycle time was, and what did they say a day was worth?" When they can't answer, do not say "exactly, that's the problem." Say: **"Okay. What do you make of that?"** And concede the true one out loud, by name: *"Cat season is real. The April hail event pulled three of your live accounts into storm response and you lost six weeks of calendar. I'm not going to pretend that didn't happen."* Conceding the real grievance is what buys you the right to press on the invented ones. A rep who feels heard on one thing stops defending all of them.
- 5
Make it safe to say the real thing
"Let me say the thing that's probably sitting between us. I am not building a file right now. If the answer is 'I got spooked after the Cardinal Casualty loss and I stopped picking up the phone in week three' — that is a fixable thing, I've fixed it with reps before, and it stays in this room. What I can't fix is a version where nothing is in your control, because then neither of us has anything to do on Monday." Then the two questions that usually crack it: "If I handed you fifteen warm Chief Claims Officer intros tomorrow, do you hit the number?" The hesitation is the admission. Let it sit. Then: "What's the part of this you'd fix if nobody was watching and there were no consequences?" Or the direct route into activity: *"Walk me through the last three weeks of the quarter. What did Tuesday morning look like?"* A rep who's stopped prospecting cannot describe a Tuesday morning. They'll describe deals instead of activity, and they'll do it fast. One warning: if you get a flat "yeah, you're right, I need to prospect more" at minute six, before a single number has been on the table — that's not an admission, that's a rep managing you out of the room. Slow it down and go to the tape.
- 6
Go to the tape — a moment, not a theme
"Your discovery needs to be deeper" is a horoscope. Play ninety seconds. "This is minute nine of the Keystone Mutual first call. Their VP of Claims Operations says — and I'm quoting — 'we're supposed to close auto at twelve days and we're sitting at twenty-six, and the board asked about it in November.' Listen to what you do next." [play it] "You went straight into the fraud scoring screen. Give me three questions you didn't ask." Let *them* name the misses. The good ones are sitting right there: what does a day cost you in DOI complaints; what's your ALAE per claim on those files; is the twenty-six days an adjuster capacity problem or a queue problem; what did the board actually ask for; who else in the building owns that number — is it you or is it the COO. If they can name the misses, this is execution. They know the move and aren't making it, usually because they're rushing to prove value before the buyer has admitted a cost. If they genuinely cannot name them, it's a skill gap and your plan is training, not accountability. That distinction decides everything you do next — don't skip it.
- 7
Land on one root cause and say it plainly
"Here's where I've landed. Cat season cost you six weeks and that's real. But the thing actually killing you is that you're demoing at minute nine instead of getting them to say what the cycle time is costing them — so every deal turns into a feature comparison against the challenger and you lose on price. And because you only created eleven new opps in ninety days, you can't afford to disqualify the Meridian deal that was never going to clear actuarial, so you spent October on it. The thin discovery and the thin pipeline are the same problem feeding itself. Does that match what you see?" Ask for agreement. If they push back with a real argument, listen properly — you might be wrong. If they push back with a new excuse, name it: *"That's a sixth thing. We agreed the list was five. I think you're hunting for a reason this isn't about the calls."*
- 8
Let them write the plan, then make it checkable
"Given all that — what do you want to change first?" Manager-authored plans get complied with for eleven days. Rep-authored plans get done. Whatever they say, convert it into something you can both look at on Friday: - "Prospect more" → "Tuesday and Thursday, 8 to 10, blocked in the calendar, five new opps a week, and mutuals count the same as stock carriers." - "Better discovery" → "No product on a first call for three weeks. If they push, you say: 'I'd rather show you the two screens that matter to your cycle time than all forty — give me ten more minutes of questions first.'" - "Quantify it" → "Nothing advances past stage two without their paid losses, their leakage estimate, and their current days-from-FNOL-to-close written in the pain field. In their words, with a name next to it." Then your half, out loud: *"I'll sit on your first two discovery calls this week and debrief within ten minutes of hanging up. And I'll go pull the list of regionals in the Southeast that aren't mid-migration so you've got something to backfill the accounts that are frozen."* Coaching that only assigns work to the rep reads as a warning, not a partnership.
- 9
Close with the standard, not a pep talk
"So: Tuesday and Thursday mornings blocked, no product on a first call for three weeks, and a dollar figure on every stage two. I'm on your Harborline call Wednesday. We meet Friday at four and we look at opps created — opps, not deals. And to be straight with you: a third quarter like the last two changes the nature of this conversation. I don't think that's where we're going, but I'd be doing you a disservice not to say it." Then: **"What did you hear me commit to?"** Their summary tells you whether any of it landed. Do not finish with "you've got this" — that tells the rep the last thirty minutes were theatre and nothing has to change by Monday.
- 10
If they never admit anything
Some versions of this end with the rep still holding the line: it's the migrations, it's the mutuals, it's price. Don't force a confession — you'll get a fake one and it'll cost you the next three months. "Alright. We disagree on cause. Let's test it instead of arguing about it. Run no-product first calls for three weeks and hit five new opps a week. If it's genuinely the territory, that will change nothing, and I'll take the segment-design fight upstairs myself with your data in my hand. If it does change something, we've learned what we're actually dealing with. Either way we know more in three weeks than we know right now." That turns a stalemate into an experiment, keeps the relationship intact, and gives you a clean decision point with a date on it.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Two quarters is a pattern, not bad luck, and I'm not going to pretend otherwise. But I didn't book this to read you your attainment — you know it better than I do. I want to work out what's actually going wrong, because I think it's one thing and not five. Fair?
Buyer
Fair. But I'll be honest, I think you already know what it is. My patch is eleven regional mutuals and four stock carriers, and three of the four are eighteen months into a core replacement. Every conversation ends the same way — 'we've got no IT bandwidth until 2027, come back after go-live.' That's not a me problem.
Rep
Understood. What else?
Buyer
Cat season. The hail event in April pulled Keystone's whole claims leadership onto storm response. My VP of Claims Ops there stopped answering for six weeks. Same with Harborline. You can't run a sales cycle when the buyer is deploying independent adjusters at three times internal cost.
Rep
What else?
Buyer
The mutuals. Every one of them tells me surplus is policyholder money and there's no technology line the way a stock carrier has one. And then there's price — we're twenty percent over the challenger. Oh, and every SIU Director I talk to got burned by a fraud analytics vendor two years ago, drowned in false positives, shut it off. I'm selling into a room that's already decided.
Rep
So the list is: mid-migration accounts, cat season, mutual budgets, price against the challenger, and the SIU fraud-vendor hangover. That's the whole list? Nothing sixth?
Buyer
That's the list.
Rep
Then let me give you the one that's real before I push on any of it. Cat season cost you six weeks of calendar and it's not arguable — I watched two of your accounts go dark in April. That's a legitimate headwind. Now let's take the migration one, because if your whole patch is frozen until 2027 I need to go fight about territory design, and I'd rather know today. Priya's segment mix is almost identical to yours. She booked sixteen first calls last quarter, you booked fifteen — you're identical at the top. She moved nine of sixteen to a second call. You moved three of fifteen. Help me understand that.
Buyer
Her accounts are bigger. She's got two nationals with a real Director of Claims Transformation who has a budget and a mandate. I'm talking to a Chief Claims Officer at a mutual who's also effectively the COO and has four other jobs.
Rep
I pulled that too. Of her nine second calls, six were mutuals under $400 million in written premium. Same buyer profile as yours. So what do you make of that?
Buyer
…I don't know. Maybe she's getting luckier on timing.
Rep
Maybe. Let me play you ninety seconds and you tell me. This is minute nine of your Keystone Mutual first call. Their VP of Claims Operations says, quote, 'we're supposed to close auto in twelve days, we're sitting at twenty-six, and the board asked about it in November.' Listen to what happens next. [plays] You opened the SIU scoring screen. Give me three questions you didn't ask.
Buyer
…What the fourteen extra days are costing them. Whether it's showing up in DOI complaints or non-renewals. And what their ALAE per claim looks like on the files that sit longest. I know. I know those are the questions. I had the deck open and I wanted to show him the thing I thought would land.
Rep
Okay — that's useful, because you can name them. That means this is execution, not a skill gap, and it's a much shorter fix. Let me say the other thing that's sitting between us. I am not building a file right now. If part of this is that after the Cardinal Casualty loss you stopped picking up the phone for a few weeks, that's fixable and I've fixed it before. So — walk me through the last three weeks of Q3. What did Tuesday morning look like?
Buyer
Tuesday I'd be… working Meridian, mostly. Building the leakage model for their chief actuary, then reworking it because he wanted it back-tested against closed claims. That ate most of September.
Rep
That's a deal, not a Tuesday. You created eleven new opps in ninety days — seven of them in month one. Here's where I've landed. Cat season is real and it cost you six weeks. But the thing killing you is that you're going to product at minute nine instead of making the Chief Claims Officer say what twenty-six days costs them — so every deal becomes a feature comparison and you lose to the challenger on price. And because you only built eleven opps, you couldn't afford to walk away from Meridian in week two, which is what you should have done. Does that match what you see?
Buyer
Partly. I still think the migration thing is bigger than you're giving it credit for.
Rep
Then let's test it rather than argue about it. What do you want to change first — you pick.
Buyer
No product on a first call. For three weeks. And I'll block Tuesday and Thursday mornings for pipeline, eight to ten, five new opps a week. If the migration story is real, that won't move anything and you'll owe me a territory conversation.
Rep
Deal, and I'll take that fight upstairs myself if the data says so. My half: I'm on your Harborline discovery Wednesday and I'll debrief within ten minutes of the hang-up, and I'll pull you a list of Southeast regionals that aren't mid-migration to backfill. One more rule — nothing moves past stage two without their paid losses, their leakage estimate and their current FNOL-to-close in the pain field, in their words. Friday at four we look at opps created, not deals. And straight with you: a third quarter like the last two changes this conversation. I don't think that's where we're going. What did you hear me commit to?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Every account in my patch is mid-migration to a new policy admin platform. There's no IT bandwidth until 2027 — that's not a selling problem, that's a market timing problem."” | Take it seriously for thirty seconds, then test it against a peer on the same segment. If their first-call rate matches and their second-call rate is a third of the peer's, the migration isn't stopping meetings — it's stopping them at the same point every time, which is a discovery problem wearing a market costume. Then coach the counter they should be running on the call: a core migration is a reason to talk now, not later, because claims service degrades during a 24–36 month replacement. The question they should be asking a VP of Claims Operations is 'what has your cycle time done since the project kicked off?' Have the rep say that line out loud in the 1:1 before they say it to a carrier. |
| “"Half my territory is mutuals. They all say surplus is policyholder money and there's no technology budget line."” | Concede that mutual buying behaviour is genuinely different — planning cycles are tighter and board thresholds are lower. Then ask the rep a question they probably can't answer: 'On the last three mutual losses, what did they tell you their expense ratio target was for next year, and when does their planning cycle close?' If they don't know, budget wasn't the objection, it was the exit line. Coach the reframe: it's a combined ratio conversation, not a tech spend. Every point of loss ratio and every dollar of expense ratio comes out of the same surplus, and slow claims cost them in complaint handling and agent defection. Then size phase one under the board approval threshold. |
| “"We're twenty percent over the challenger. I'm losing on price and no amount of discovery fixes a price gap."” | Don't argue. Count. 'Five of your eight losses say price. Of those five, how many have a paid losses figure, a leakage percentage, or an ALAE per claim number written in the CRM?' It'll be one, or none. Then: 'So we don't actually know if we lost on price. We know they said price, which is what a Chief Claims Officer says when nothing you showed them landed against a number they own.' The fix is the stage-two rule — no advance without their numbers in their words. Price objections at carriers are almost always unquantified-value objections in a nicer suit. |
| “"Every SIU Director I meet got burned by a fraud analytics vendor two years ago. They shut it off. I'm walking into a closed door."” | Agree — the burn is real and widespread, referral rates hover in the low single digits and most prior tools drowned SIU in false positives. Then ask what the rep did with it on the call. The move is to invert it: ask what the precision was, what the referral threshold was set at, and offer to back-test on last year's closed SIU-confirmed files. Most of those failures were threshold and workflow, not the model. If the rep can't describe that conversation happening, the objection killed the call because they had no answer, not because the door was closed. That's a roleplay rep, not a territory problem. |
| “"The deals I did work were real. Meridian just got killed by their chief actuary at the last minute — that's out of my hands."” | Ask when actuarial first appeared in the deal. If the answer is 'week nine,' that's the coaching point: the chief actuary was always going to be in the room and the rep didn't ask who else has to bless the number until the proposal was out. Then make it a habit, not a lecture — 'from now on, on every first call, the question is: when this gets to a business case, whose signature does it need and what number do they need to see?' Also worth naming gently: one deal absorbing six weeks of a quarter is a pipeline problem masquerading as a loss. |
| “"They said send something over and they'd route it to the innovation team. That's still a live deal."” | This is the one to be blunt about, because it inflates pipeline and hides the real coverage number. The innovation team is where claims vendors go to die. Coach the exact line for next time: 'Happy to — before I do, is cycle time actually a priority for you this year, or is the pressure coming from somewhere else, like severity or retention?' If they name a real pressure, book time with them and whoever owns that number. If they don't, it's a stall and it should come out of the forecast this week. Then re-run coverage with those deals removed and show the rep the honest number. |
Questions reps ask about this call
- What makes a sales coaching roleplay for insurance teams different from a generic one?
The excuses are different and so is the coaching. A rep selling claims technology has genuinely hard headwinds — core migrations that freeze accounts for two years, cat season pulling claims leadership onto storm duty, mutuals with no discretionary technology line, and SIU Directors who turned off the last fraud analytics tool. A generic coaching roleplay lets the rep say 'bad territory' and the manager say 'work harder.' An insurance-specific one forces the manager to test each claim against segment data and forces the rep to defend it in the industry's own language: paid losses, leakage percentage, ALAE per claim, days from FNOL to final payment.
- Who plays which role in this scenario on DrillCall?
You practise as the manager. The AI plays the rep who has missed two quarters selling into carriers — cooperative on the surface, defensive underneath, with four or five pre-loaded and partly true grievances. The AI is instructed not to volunteer the real problem (thin discovery, and prospecting that stopped in week three) and to give a fast, hollow 'you're right, I need to prospect more' if you press too early. You only get the real root cause if you drain every excuse, concede the true one, and put a number in front of them.
- How do I stop the roleplay turning into an argument about territory?
Bring data into the scenario before you start. The drill works best when you've decided in advance what the peer comparison looks like — same segment mix, near-identical first-call rate, second-call conversion a third as good. That single comparison ends the territory debate without you having to say 'that's not the real issue.' The rule inside the roleplay is that you never rebut an excuse with an opinion, only with a number or a recording, and you concede the one that's genuinely true out loud and by name.
- What does a good outcome look like at the end of the call?
One root cause named plainly, one behaviour the rep proposed themselves, and a check-in with a date on it. Not a nine-point plan. In this scenario a good landing usually looks like: no product on a first call for three weeks, two blocked prospecting mornings with a weekly opp target, and a stage-two rule that nothing advances without the carrier's paid losses, leakage estimate and current cycle time written in the rep's own notes. Plus something you committed to — sitting on two discovery calls, or pulling a backfill account list — because a plan that only assigns work to the rep reads as a warning.
- What are the most common ways managers fail this roleplay?
Four, in order of frequency. Rebutting the first excuse the moment it lands, which buries the fourth one — usually the closest to the truth. Opening with small talk when both people know why the meeting exists. Coaching a theme ('your discovery needs work') instead of playing minute nine of a real call and asking which three questions were skipped. And accepting a flat admission at minute six, before any number has been discussed — that's the rep managing you out of the room, not a breakthrough.
- How often should sales managers run this drill?
Before any 1:1 where you already suspect a pattern rather than a bad month, and once a quarter as maintenance. The specific muscle it builds — asking 'what else?' three times without flinching, then sitting in ten seconds of silence after handing over an uncomfortable number — decays fast under pressure. Most managers can describe the sequence perfectly and still cannot hold the silence in a live conversation, which is exactly what makes it worth rehearsing.