How Institutional Sales Teams Handle an Insurer's Duration Question

An insurance CIO who asks about duration after a rate move is not asking for a prediction. Most of the time the question is a test of discipline, a way to see whether your team makes promises it cannot keep or whether it does the work of understanding the liability side of the balance sheet first. Institutional sales teams that handle this well slow the conversation down. They find out which liability assumptions, benchmark, and reporting window the insurer actually uses before they describe any strategy material. The portfolio team can supply a formal, documented response later. Your job in the room is to ask the right questions and avoid saying anything that sounds like a guarantee.

Why This Conversation Goes Wrong

The instinct under pressure is to reassure. Rates just moved, the CIO sounds worried, and the easiest thing to say is that the strategy is built to handle exactly this kind of environment. That answer feels helpful in the moment and causes real damage later. You have no idea what the insurer's actuary assumes about liability duration, what the investment committee considers an acceptable range, or whether the CIO is really asking about a hard match to liabilities, a volatility limit, or a stress testing requirement. A generic claim that the strategy is defensive answers a question nobody asked and commits your firm to a standard you never confirmed.

There is a second failure mode that looks more careful but causes the same problem. Some reps try to dodge the question entirely, saying they will have to check and get back to the CIO. That reads as unprepared, and it wastes the one moment when the CIO is willing to talk about their actual assumptions. The better move is to engage immediately, but to engage with questions instead of claims.

How to Prepare

Before you ever get this question, know the difference between three things the CIO might mean by protect us. They might mean a liability match, where the portfolio's duration is meant to track the actuarial liability duration within a set range. They might mean a volatility constraint, where the committee has a stated tolerance for how much the portfolio value can move. Or they might mean a stress testing requirement, where the concern is how the strategy performs under a specific rate shock scenario the committee has already modeled. Each of these has a different owner on the insurer's side, usually the actuary, the risk lead, or the investment committee itself, and each requires a different kind of follow up material.

Know your own approval boundaries before the call. Find out what your compliance and portfolio management teams have already approved for external distribution on duration positioning, and know who on your side needs to review anything before it goes out. If you do not know this cold, you will either overpromise in the room or stall when the CIO asks for something concrete. Reviewing how to ask Mandate Discovery Questions That Earn an Institutional Follow Up is a good way to sharpen this kind of discovery instinct before a live call, since the same discipline of naming the unknown and asking one precise question applies here.

What to Say

The CIO opens with, "If rates rise again, will this protect us?" Do not answer the question as asked. Say, "I cannot tell you what rates will do next, and I would not want to promise something on that basis. Can you tell me what duration your actuary is using for the liabilities right now, and what range the committee treats as acceptable?"

The CIO responds that the actuary is actually in the middle of revising the assumptions, and the committee has not settled on a new range yet. This is useful information, and it changes what you should offer. Say, "That timing matters. I can get you approved materials that walk through how the strategy's risk process actually works, but I do not want to hand those over as a promise about future rate moves. Would it help if your actuary and risk lead told us directly which measures they want us to speak to, so the materials answer the real question instead of a general one?"

If the CIO pushes further and asks something like, "So you cannot tell me if we are protected," resist the urge to fill the silence with reassurance. Say, "I can tell you how the strategy has behaved and what process governs it, and I can get you the people who can speak to the specific measures your committee cares about. What I will not do is tell you this protects you against a scenario nobody has defined yet." That last sentence is the one most reps are afraid to say out loud, but it is the sentence that builds trust. A CIO who has sat through a rate cycle before will recognize it as the honest answer, not a dodge.

Mistakes to Avoid

The biggest mistake is answering the emotional question instead of the technical one. The CIO is anxious about a rate move, and it is tempting to soothe that anxiety directly. Soothe it by showing process, not by making a claim about future performance.

The second mistake is failing to write down what you heard. When the CIO mentions that the actuary is revising liability duration assumptions, that is a specific, dated fact. Record the exact phrasing the CIO used, the named assumptions, any decision date the committee has set, and every person who needs to review material before it goes external. Without that record, the follow up you promised turns into a vague email that goes nowhere.

The third mistake is promising specific documents before you know they are approved for distribution. Say you can get approved materials, not that you will send the risk report by tomorrow. If your compliance process requires a named reviewer, say so, and set the diligence action as getting that reviewer's input rather than guessing at a delivery date.

The fourth mistake is treating this as a one time exchange. A duration question like this often surfaces again in a different form during due diligence, particularly around a larger structural change. If your insurer client is also weighing something like an OCIO transition, it helps to understand how to Set Governance Before an OCIO Transition Discussion, since the same instinct to name assumptions and confirm reviewers before promising material applies there too.

How to Practice and Score It

Give a practice partner three versions of this same question, worded differently. One should reference a benchmark, one should reference liability duration directly, and one should reference a general market outlook. In each case, the rep has to name the unknown out loud, ask exactly one clarifying question, and end the exchange with a specific diligence action, not a vague promise to follow up.

A manager scoring this should check three things. Did the rep avoid making any statement that sounds like a prediction about rates or a guarantee about protection. Did the rep ask a question specific enough that the answer would actually change what happens next. And did the rep leave the CIO with a concrete next step, naming a person or a document rather than a general offer to help. DealSpeak sessions built around this scenario let you run the same insurer question multiple times with different follow ups, which is the only real way to build the instinct to ask before you answer. You can find more scenarios like this among the Asset Management practice conversations.

This is not a hard conversation once you stop trying to answer a question you were never equipped to answer. Ask what the CIO actually means by protection, write down what they tell you, and hand off the technical answer to the people who own it. Do that consistently and the CIO learns to trust your process even when you cannot promise them an outcome.