Testing Utilization Assumptions in a Capital Equipment Evaluation

A projected utilization number can travel a long way from where it started. Someone hears an estimate in a hallway conversation, repeats it in a meeting, and by the time it reaches a capital packet it reads like a verified fact. As a capital sales representative, you are often the person in the room who can see this happening in real time, and the conversation about where a number came from is one you need to handle well, because the way you handle it shapes whether your proposal holds up under later scrutiny or gets picked apart by a committee member who asks the one question nobody prepared for.

Why this conversation goes wrong

The pressure in these calls usually points in one direction. A finance director or program sponsor wants a number in the proposal because a committee meeting is coming up and a clean projection makes the business case easier to write. You want the deal to move forward, so there is a pull to just say yes and drop the figure into the document. That instinct is understandable, and it is also how a soft assumption becomes a hard commitment.

The problem shows up later, not in the moment. If the packet says the system will handle a certain number of cases a week and that number never gets validated, your equipment becomes the explanation when volume falls short, even though volume depends on referral patterns, staffing, and scheduling decisions that were never yours to control. A capital sales representative who lets an unverified number sit unlabeled in a proposal is not being agreeable, they are creating a problem that will land back on them in a renewal conversation or a reference call a year later.

How to prepare

Before a planning call where utilization is likely to come up, get clear on what your equipment specifications actually say and where projections end and customer data begins. Approved specifications describe throughput, cycle time, and capacity under stated conditions. They do not describe how many patients a given hospital will actually schedule, because that depends on referral volume, staffing levels, room availability, and decisions made by people who are not on your call.

Think through the questions you need answered before any number goes into a document. Where did this figure come from. Which service line or department owns the data behind it. What time period does it cover, a current month, a projected first year, a steady state that assumes staffing is already in place. What could change between now and when the equipment arrives, a new hire, a room conversion, a referral agreement that has not been signed yet. If you cannot answer those questions from the call itself, you are not ready to let the number move forward.

It also helps to decide in advance how you will phrase the ask. You are not challenging the customer's numbers. You are asking them to name the source so the committee sees something they can trust rather than something they later have to defend without backup.

What to say

Here is how this plays out on a real call. A finance director named Renata is building a capital packet and wants a number that will make the proposal land well with her committee. She says, "Our physician sponsor thinks the system will handle thirty cases a week once it's up and running. Can we put that figure in the proposal."

You respond, "I can include that as your working assumption and note where it came from. Before it goes into the packet, I want to make sure we have the right people behind it. Who can confirm current volume, the expected start date, and whether a staffing change or a second room affects that number."

Renata pauses and explains that the figure came out of a conversation with the physician sponsor, and that scheduling has not actually reviewed it yet. You say, "That's useful to know, and it's a good reason to loop in the service line lead and whoever owns the schedule. Let them either confirm the number or tell us what would need to be true for it to hold. That way your committee sees what's confirmed and what's still an estimate, instead of one number with no context behind it."

Notice what happened in that exchange. You did not refuse to help, and you did not argue with the number. You asked who stands behind it, and you offered a path that makes the proposal stronger, not weaker, once it reaches the people who will vote on it.

Mistakes to avoid

The most common mistake is silence. A representative hears an unverified number, senses that pushing back might slow the deal down, and just writes it into the proposal without comment. That feels like the path of least resistance in the moment, and it is the version of this conversation that causes the most damage later.

The second mistake is overcorrecting into a lecture about the difference between specifications and projections. Nobody on a planning call wants a tutorial. State the ask plainly, get the source named, and move on.

The third mistake is treating this as a one time fix instead of a habit. If you clarify one number but let a second, related assumption slide through unlabeled later in the same packet, the committee still ends up with a document that mixes confirmed data and guesses without knowing which is which. Apply the same standard to every figure that shows up in the conversation, not just the first one that catches your attention.

The fourth mistake is confusing this skill with a different kind of clinical boundary conversation. Naming the source of a planning number is not the same task as keeping a device education session inside its approved use, which is its own discipline covered in Keeping an Approved Use Refresher Focused on Device Education. Both require you to hold a line calmly, but the line itself is different, and mixing up the two scripts in a live call will show.

How to practice and score it

Build a short worksheet with three utilization figures pulled from different sources, a physician estimate, a finance projection, and a scheduling department's current count. For each one, write down four things. 1. The source of the number. 2. The time period it covers. 3. The customer owner who is accountable for confirming it. 4. The event or decision that could change it before the equipment is installed.

Run the worksheet as a role play with a manager or a peer playing the finance director. Have them push for a number to go straight into the packet, and watch whether you slow down and name the source before agreeing to anything. A manager scoring the exercise should check whether you asked who owns the data, whether you avoided implying that the equipment guarantees a result, and whether you gave the customer a real next step instead of just declining the request.

DealSpeak is built for exactly this kind of rehearsal, since a live planning call gives you one shot to get the phrasing right and a practice run lets you make the mistakes somewhere that does not cost you a relationship. If you want more scenarios built around this industry, the Medical Devices practice conversations library includes related situations, including What to Say When a Nurse Reports a Device Alertwhich covers a different but related skill, staying precise under pressure when someone else's urgency is pushing you toward a quick answer.

Utilization numbers are useful to a capital committee only when everyone knows what stands behind them. Your job is not to inflate or deflate the estimate, it is to make sure the label matches the evidence. Get that habit right and your proposals hold up long after the call ends.