Discuss an Employer Cost Question With Transparent Assumptions

An employer benefits leader who opens with "give us a savings number" is testing something deeper than the number itself. The real question is whether you will speak from evidence or from guesswork. Give a figure without a baseline and the plan holds you to it later, at renewal, when actual results do not match what you promised. The stronger move is to build an analysis path that finance can check line by line, not a projection assembled on the spot to satisfy the moment.

Why This Conversation Goes Wrong

Most market access managers stumble here because the question sounds simple. A benefits leader wants a number, so the instinct is to give one. But a savings estimate without a defined population, a utilization baseline, and a time period is not an answer. It is a guess dressed up as an answer, and a sharp finance team finds the gap fast.

The pressure gets worse because the leader may be comparing your response to a competitor who offered a number, real or not. Silence feels like weakness, so managers reach for round figures, best case scenarios, or numbers borrowed from a different plan population. Once you say a figure out loud, it becomes the reference point for the rest of the relationship. Walking that back later costs more credibility than saying, up front, that the number depends on data you do not yet have.

How to Prepare

Before the conversation, know exactly what your organization can and cannot say about cost outcomes. Pull the approved health economics materials for the product and read the methodology section, not just the summary slide. Know which studies the figures come from, what population they studied, and what assumptions drove the model. If a figure came from a claims analysis in a commercial population, say so, and do not let a listener assume it applies to a self insured employer group with a different size or risk profile.

Prepare a short list of questions you need answered before any number can be built. What population definition does the plan use. What time period does finance want, a rolling twelve months, a plan year, something else. What utilization data does the plan already have, and what would it take to see a relevant slice of it. Write these down. Walking into the room with prepared questions instead of a rehearsed pitch shifts the conversation from a demand for a number to a joint scoping exercise.

Decide in advance when you need a health economics and outcomes research specialist or a medical resource in the room. A market access manager can explain the shape of an approved model and its assumptions. A specific question about a subgroup, a comorbidity, or a modeling technique usually needs someone with that training. Knowing the line between what you can answer and what needs a specialist keeps you from overstating your own authority. If you want a closer look at matching your evidence package to how a payer's finance team actually reviews it, see Align an Evidence Package With a Payer's Review Format.

What to Say

A fictional review meeting shows how this plays out.

The benefits leader says, "We need a savings number before we can move forward."

The market access manager replies, "Before we can put together a number that will hold up, we need your utilization baseline and clear assumptions about the population. We can walk you through the data your finance team typically accepts, and we can review the approved materials that explain how the methodology works. What time period and population does your team use for this kind of analysis."

The leader answers, "Finance wants a twelve month view with written assumptions attached to every input."

The manager responds, "That works well with what we have. We can map your twelve month period against the studies in our approved materials and flag where the population matches and where it does not. Anywhere it does not match, we will mark that as an assumption, not a fact, so your team can decide how much weight to put on it."

This exchange does three things. It answers the request without inventing a number. It hands the leader a next step instead of a dead end. And it sets the expectation that some inputs will be labeled as assumptions rather than facts, which is exactly what a finance team needs to run its own sensitivity checks.

Mistakes to Avoid

A few habits sink this conversation even when the manager means well.

1. Offering a range just to fill the silence. A range still implies precision you do not have, and the plan remembers the low end as a promise.
2. Quoting savings figures from a different population or plan design without saying so out loud. A number from a commercial claims study does not automatically transfer to a self insured group with different demographics.
3. Treating every question as one you can answer alone. Pulling in a health economics specialist late, after you have already improvised an answer, is harder than pulling one in early.
4. Leaving the room without a written record of what was assumed, what was supplied by the plan, and what is still unknown. Without that record, the next meeting starts from zero again.
5. Promising a result instead of a process. Employers respond better to a documented path they can inspect than to a guarantee they will later hold you accountable for.

How to Practice and Score It

This conversation rewards preparation more than charisma, which makes it a good one to rehearse before it happens for real. DealSpeak lets you run this exact scenario, an employer benefits leader pressing for a savings number, against an AI counterpart that pushes back the way a real finance leaning stakeholder does. You can find it alongside other Pharmaceuticals practice conversations built around this kind of pressure.

Score your own performance on a few concrete points. Did you avoid stating a savings figure before a baseline existed. Did you ask about population definition and time period within the first few exchanges. Did you name the source and limits of any approved material you referenced. Did you identify, out loud, when a question needed a health economics specialist rather than guessing at an answer yourself.

Try the harder version of this conversation too, where the benefits leader interrupts with a hypothetical number and asks you to confirm or deny it on the spot. Practicing how to decline that trap calmly, without sounding evasive, is worth more than practicing the easy version where the leader accepts your questions right away. If you manage a team, run this scenario with your group and compare how each person handles the moment the leader pushes for a hard commitment. The differences show up fast, and they tell you who needs more reps before the real meeting.

After the meeting, write down every assumption as supplied by the plan, supported by an approved source, or still unknown, and practice saying that breakdown out loud until it feels natural. That habit keeps the conversation honest the next time a stakeholder presses for certainty you cannot give. Once the plan agrees to move forward, the next conversation usually turns to who owns implementation on their side, a topic covered in Map Implementation Owners After an Access Discussion.