Gathering Service Inputs for a Capital Equipment Business Case

A capital equipment deal can stall over one sentence from finance or supply chain, asking you to name a service cost you cannot confirm yet. As a capital sales representative, you sit between a customer who wants a single number and an internal process that only produces real terms once a scope exists. Handling this well means guiding the customer toward the decisions they still need to make, not filling the gap with a guess that quietly becomes a commitment.

Why this conversation goes wrong

Service cost questions show up late in a capital evaluation, usually after the clinical team has already picked a configuration and finance is building the business case for the committee. Everyone in the room wants to move fast, and a rough number feels like progress. That is exactly the moment representatives get pulled into estimating multi year service costs off the top of their head, because saying "I don't know yet" feels like it slows the deal down.

The problem is that a verbal number said in a meeting has a way of becoming the number the CFO uses in a spreadsheet, even when you meant it as a placeholder. Once that happens, your authorized commercial team ends up negotiating against a figure you never approved, and the customer feels misled if the real terms come in higher. The fix is not to refuse the conversation. The fix is to separate what the customer needs to decide from what only an authorized quote can confirm, and to keep that distinction clear out loud, every time.

How to prepare

Before you walk into any capital conversation where service planning might come up, know four things cold. Know which equipment configuration is actually under review, because service scope depends on it directly. Know which department owns the operating budget, since biomedical engineering, facilities, and finance often have different priorities and different authority. Know what your company's process is for producing authorized service quotes, including who to loop in and how long it typically takes. And know what response time expectations the customer's location realistically requires, since a rural site and a downtown hospital campus are not the same conversation.

This kind of preparation overlaps with the stakeholder work described in Building a Stakeholder Map Before a Capital Device Demonstrationbecause the person asking about service cost is rarely the only person who needs the answer. Supply chain wants the number for a spreadsheet. Biomedical engineering wants to know how fast a technician shows up. Finance wants the service terms separated cleanly from the equipment price so the total cost of ownership calculation holds up under review. If you walk in already knowing who owns which question, you can route each one correctly instead of trying to answer all of them yourself in the room.

What to say

Supply chain lead Morgan opens with the question you should expect. Morgan says, "Can you just tell our CFO what annual service is going to run us over the next five years." That is a reasonable ask from Morgan's seat, and it deserves a real answer, just not a guessed one.

Representative Priya responds without hedging or stalling. Priya says, "I can get you real coverage options and route a request for authorized commercial information so this holds up in your review. To make that comparison useful, I need three things from your side. Which configuration is currently under review, what service scope does your team actually want evaluated, and who owns the operating budget for this."

Morgan thinks it over and says biomedical engineering wants a clear answer on response time commitments, and finance wants the service terms broken out separately from the equipment price so they are not blended into one number. Priya writes both requests down on the spot and tells Morgan she will schedule a call with her service and commercial contacts once the scope is confirmed, so the quote reflects what the hospital is actually planning to buy.

Notice what Priya did not do. She did not say a number to make the moment easier. She did not promise a timeline she could not confirm with her own team first. She treated Morgan's question as real and worth answering, and she moved it to the people and process that could answer it correctly.

Mistakes to avoid

A few patterns show up again and again in these conversations, and each one creates a problem later in the deal.

1. Giving a rough number "just for planning purposes." Rough numbers do not stay rough once they land in a business case document. Treat every figure you say out loud as something the customer might act on.
2. Answering the question you were asked instead of the question underneath it. Morgan asked about a five year cost, but the real need was two separate inputs, response time and budget separation. Dig for that before answering.
3. Letting the request sit without a next step. If you say you will route something, name the person, the scope, and roughly when the customer should expect to hear back. A vague promise is worse than no promise.
4. Treating this as a stalling tactic instead of a real information gap. Customers are not usually trying to trap you. They genuinely need these inputs to build a business case, and your job is to help them get accurate ones.
5. Skipping the internal handoff. If you promise service and commercial contacts a conversation with defined scope, actually set it up. A representative who gathers requirements and then drops them loses credibility fast, and the next request gets harder, not easier.

How to practice and score it

The skill here is not memorizing a script. It is reflexively separating discovery questions from commitments under time pressure, in the moment, without sounding like you are avoiding the question. That is hard to build by reading about it, and it is exactly the kind of exchange worth rehearsing out loud before it happens with a real customer.

A useful drill is to take a vague request, something like "what will this cost us long term," and turn it into four concrete discovery questions on the spot. Ask about the configuration under review, the coverage scope the customer wants evaluated, who owns the budget decision, and what timeline the customer is working against. Do this until it becomes automatic rather than something you have to think through live.

If a manager is scoring this, the thing to listen for is any sentence where a cost gets stated as if it were confirmed before the actual commercial review has happened. That single habit is what turns a helpful conversation into a liability. A manager should also listen for whether the representative names a clear next step and a real person, rather than a general promise to follow up. Practicing this scenario, along with adjacent ones like the request covered in Responding When Facilities Requests a Site Assessmentbuilds the same underlying habit, treating a request for information as a routing problem, not a pricing problem. DealSpeak's Medical Devices practice conversations let you run this exact exchange with an AI counterpart and get direct feedback on whether you held that line.

The close

Service cost questions are not a trap, they are a sign the customer is doing real work on their business case. Your job is to help them ask the right questions of the right people, not to answer for a process that has not run yet. Get that distinction right consistently, and the deal moves faster because the numbers that eventually show up are ones everyone can trust.