Planning an Evaluation Across Several Health System Sites

A health system account executive who treats a rollout across eight clinics as a single conversation usually loses the deal, or worse, wins it and then watches the pilot fall apart when the second site behaves nothing like the first. Every system you sell into is really a collection of sites, each with its own staff, its own workflow habits, and its own person who has to approve before anything moves. Planning an evaluation across several locations, out loud, in front of the buyer, is a skill you can practice and improve, not a talent some reps happen to have.

Why This Conversation Goes Wrong

Reps walk into multi site discussions assuming the buyer sees the system as one operating environment. They ask questions built for a single site deal, like how many users and when can we start. The buyer, meanwhile, is thinking about eight different clinics with eight different sets of local habits, staffing levels, and comfort with new tools. A rural clinic with two nurses and one shared workstation does not run like a downtown site with a dedicated informatics team. When you skip past that difference, you end up proposing an evaluation plan that fits none of the actual sites.

The second failure mode is authority. The person in the room may run one department or one region, not the whole system. If you ask for a systemwide rollout date before you know who actually owns that decision, you put the buyer in a position where they either overpromise on behalf of colleagues they do not control, or they quietly disengage because the ask felt off. Either way, you lose credibility fast, and you rarely get it back in the same conversation.

What to Learn Before You Sit Down

Before you propose any sequence, get clear on four things. First, which sites the buyer wants to include in an initial look, and why those sites and not others. Second, who represents each site, by name and by role, so you know if you are talking to someone with real authority or someone gathering information for someone else. Third, what already varies across sites today, staffing, patient volume, existing tools, so you do not accidentally propose a plan that assumes uniformity where none exists. Fourth, what the organization actually wants to learn from an initial review before it expands to more locations.

Write these down before the call if you can. If you already have background from a discovery call, review it and note where you are guessing versus where you have a direct answer. Walking in with real questions, instead of a generic systemwide pitch, is what makes this conversation feel like a partnership instead of a sales push. It also sets up an honest way to measure results later, which matters more than most reps realize. The post Defining Honest Measures for a Healthcare Pilot covers how to define numbers the buyer will actually trust once the pilot sites report back.

What to Say

Here is how this can play out with a buyer who has already flagged that her sites are not uniform.

Renee says, "We have eight clinics, but our rural sites run pretty differently from the ones in the city."

Marcus asks, "Which differences actually matter for how we evaluate this, and who can walk me through each setting?"

Renee says, "I would want to start with two clinics and bring in their operations leads before we go further."

Marcus says, "Let us write down exactly what those two sites need to show us, who signs off before we add a third site, and which group reviews the findings across locations."

Notice what Marcus does not do. He does not ask for a systemwide number. He does not assume the two starting clinics represent the other six. He turns Renee's comment about differences into a direct question about which differences matter, then turns her answer into a concrete next step with named owners and a named review group. That is the whole skill in miniature, listen for what varies, ask who can speak to it, and write down the criteria for moving forward instead of assuming everyone agrees on what success looks like.

Mistakes to Avoid

A few habits sink this conversation more than any other single thing.

1. Promising one timeline for the whole system before anyone has agreed on how the first sites will be judged.
2. Treating the largest or most sophisticated site as the template and assuming smaller or rural sites will simply adapt.
3. Skipping the question of who approves moving from phase one to phase two, which leaves the evaluation open ended with no clear finish line.
4. Failing to name the forum, whether that is a steering committee or a single director, where results from different sites get compared.
5. Bringing up cost or contract terms before the buyer has defined what the initial sites need to prove.

Any one of these makes the buyer feel like you are selling a generic package rather than responding to their actual organization. People running multi site health systems have seen vendors do this before, and they notice quickly when a rep has not done the work to understand how their sites differ.

How to Practice and Score This Conversation

This conversation rewards rehearsal because the mistakes are specific and repeatable. Practice with a counterpart who plays a buyer pushing for an immediate systemwide quote, and see whether you slow down to establish the evaluation sequence and local owners before responding to that pressure. Have the counterpart introduce one local constraint, a staffing gap, an older system at one clinic, anything real, and score whether you factor it into the initial review instead of brushing past it. Ask the counterpart, playing the buyer, to name the forum where findings across locations will get compared, and check whether you ask for that if it is not offered.

A manager scoring this exchange should look for three things in the notes that come out of it, the names of the initial sites and their local owners, the open constraints that the first phase is meant to test, and the buyer's own criteria for expanding beyond those sites. If those three things are missing from the opportunity record, the evaluation plan is not really a plan yet, it is a hope.

You can find Healthcare practice conversations built around exchanges exactly like this one, where pressure to generalize across a whole system runs into the reality that every site is different. If a privacy officer joins one of these evaluation calls with questions about data handling at a specific site, the approach in Responding to a Privacy Officer’s Data Questions applies directly. Running this scenario a few times with DealSpeak before you take it into a real account meeting is the fastest way to build the habit of asking about differences before you propose a plan.

The goal is not to memorize a script. It is to build the reflex of asking what varies, who owns each site, and how the buyer will judge the first phase, so that reflex shows up automatically when the real conversation gets more complicated than this one.