A security team can value your expertise, engage in detailed discussions and welcome a demonstration without being ready to buy. For the salesperson, that can be difficult to interpret. The conversations feel constructive, but the opportunity does not move.
The customer may be facing the same uncertainty. They can see a concern, yet still need to explain its significance, compare competing priorities and bring other people into the decision. The commercial task is to help them do that work with clarity.
Understand the decision behind the technical requirement
Before investing in a detailed proposal, establish what prompted the conversation. Has the customer identified a gap in coverage, struggled with an existing service or taken on responsibilities their current team cannot support? Ask what would improve if they addressed it, and who would notice the difference.
A discussion about managed detection and response, for example, should establish who will investigate alerts, who can authorise action and what support the customer expects outside normal working hours. Agreement on those responsibilities helps both sides judge whether the service fits.
Keep the discussion proportionate. Exaggerating a threat may create urgency briefly, but it does little to build the trust needed for a long-term security relationship.
Help the technical sponsor bring colleagues with them
A capable security sponsor may have limited time to prepare an internal business case. They may also need approval from finance, operations, procurement or a board member who approaches the problem differently.
Ask your sponsor who needs confidence in the decision and what each person needs to understand. Offer a concise summary they can use internally: the concern being addressed, the proposed scope, the investment, the responsibilities that remain with the customer and the alternatives considered.
Do not treat access to senior stakeholders as a test of the sponsor's influence. Explain why their involvement would improve the decision and agree the approach together.
Give assessments and proofs of value a purpose
A technical assessment can generate useful information while leaving the purchase decision unresolved. Before starting one, agree what it is intended to establish and what happens afterwards.
- Which questions must the assessment answer?
- What would count as a useful result, and who will judge it?
- What time and access must the customer's team provide?
- When will both sides review the findings and consider the next decision?
The outcome may be a narrower service, a later timetable or a decision not to proceed. Each is more useful than an open-ended exercise that consumes specialist capacity without an agreed purpose.
Make the commercial promise deliverable
Bring sales and security delivery colleagues together before finalising scope. Clarify onboarding, reporting, escalation, response responsibilities, exclusions and any dependency on third-party products or licences.
Where a vendor or channel partner is involved, establish who owns each commitment. A customer should not have to work out which organisation is responsible after the contract starts. Price the service against the work your team is actually agreeing to perform.
Make the next pipeline review more specific
Choose three opportunities that have technical interest but no clear decision date. For each, ask the owner to describe the customer's reason to act, the people involved, the approval route and the next customer-agreed action. Identify what is known and what is still assumed.
Use those gaps to guide coaching and customer conversations. Technical enthusiasm is a valuable starting point. A dependable forecast needs evidence that the customer can and intends to make a commercial decision.