Surround sound, which means reaching every person who can stop an enterprise purchase before the decision is made, is the practical answer to a structural fact: large purchases are refused in more places than they are approved.
Following the problem downstream tells you what the purchase is worth. Surround sound tells you who has to agree before that value can be realized. The two pieces of work run together, because each person you reach carries a different part of the same problem.
Why a Single Thread Fails
A deal carried by one contact depends on three things staying true at once: that person remains in their role, keeps their budget, and argues the case accurately when you are absent. Each of those is outside your control, and over a long enterprise cycle at least one of them usually changes.
There is a quieter failure underneath that one. A single contact cannot repeat a claim they never heard. If the case for the purchase includes an answer to a security question, and the security question was never discussed, then the person who holds that question receives nothing when the proposal reaches them. They do the only responsible thing available and ask for more time.
Who Can Stop an Enterprise Purchase
The list varies by organization, and the shape of it is consistent. Five groups appear in almost every enterprise purchase, and each one can halt it for reasons that have nothing to do with whether your capability is good.
- The person who controls the budget. Measured on what the spend returns and on what else it displaces. The question they carry is whether this purchase beats the other things the same money could do.
- The technical evaluator. Measured on whether the thing works inside the existing estate. They carry integration, data flow, and the question of what breaks on the day it goes live.
- The manager whose team will use it. Measured on throughput and on their people's output during the change. They carry adoption, retraining, and the cost of a transition that lands badly.
- Whoever answers for security and privacy. Measured on exposure. They carry the review, the data handling questions, and an effective veto that is rarely described as one.
- Procurement and legal. Measured on terms, risk, and comparability. They carry the paper, and they are the group most often met last and most capable of resetting a timeline.
There is often a sixth presence worth naming: someone who prefers the supplier already in place. They may have selected the incumbent, built the integration, or simply have no appetite for a migration. This person rarely objects in a meeting. They raise a requirement late.
Each Person Carries a Different Cost
This is where surround sound connects to the claims. The same problem costs each of these people something different, and the thing that persuades one of them is background noise to another. A figure about annual penalty exposure moves the person who controls the budget. The manager whose team will use the system is moved by what happens to their throughput during the transition.
So the deliverable is one Power Message per person, which means one claim each, attached to the cost that particular person carries and provable to that particular person's standard. The technical evaluator wants a demonstration. The person who controls the budget wants a figure and a reference. Both are proof, and they are different proof.
Earning the Introduction
The objection sellers raise here is that asking for more contacts looks like going around the sponsor. It looks that way when the request is framed as an org chart exercise. Framed as part of the work, it reads as diligence.
The question that works is a question about the approval path. Who has to be comfortable with this before it can proceed. What has stopped a purchase like this one here before. Who was involved the last time something similar went through. Each of those invites your sponsor to describe the path, and a sponsor who describes the path has started planning the purchase with you.
The introduction gets easier to make when you bring something to it. A security questionnaire completed in advance, an integration note written for the technical evaluator, a short summary the sponsor can forward without editing. The sponsor is spending their own credibility on the introduction, so reduce what it costs them.
Do It Before the Proposal
Sequence decides whether this work helps or hurts. Mapped early, security requirements and procurement terms become inputs to the proposal. Mapped late, they arrive after commercial terms are set, and then the scope, the price, and the timeline all get rebuilt at the point in the cycle where the buyer has the least patience for a rebuild.
A deal that restarts in legal was usually mapped late. The requirement that caused it was knowable on the second call.
What the Work Produces
Three artifacts come out of it, and all three are written down.
- A map with names. Every person who can stop the purchase, what each is measured on, and whether you have met them. The blank entries are the forecast risk.
- One claim per person, attached to the cost that person carries and provable to their standard.
- A written plan naming who does what before the buyer's own deadline. That is the Plan Letter, which means the written follow-up carrying the agreed steps between the current conversation and the date the buyer needs this working.
The map is also the most useful forecast instrument a sales organization can keep, because a deal with four of five groups unmet is a deal with a known gap, and that is a different thing from a deal that feels good. Making the map a required part of a deal review turns surround sound from individual talent into something the organization does by default.
Surround Sound: Common Questions
What does surround sound mean in enterprise sales?
Surround sound means reaching every person who can stop an enterprise purchase, before the decision is made, and giving each of them a reason to proceed that is attached to the cost that person carries. It treats the purchase as a group decision with several points of refusal.
Why do single threaded deals stall?
A deal carried by one contact depends on that person staying in their role, keeping their budget, and arguing the case accurately when the seller is absent. Any one of those can change. A single contact also cannot repeat a claim they never heard, so the parts of the case that matter to security, finance, or operations never reach the people who hold those questions.
Who can stop an enterprise purchase?
Typically the person who controls the budget, the technical evaluator, the manager whose team will use the system, whoever answers for security and privacy, and procurement or legal. Any one of them can halt a purchase, and most of them are measured on different outcomes, so each needs a reason that applies to their own responsibility.
How do you get access to other stakeholders without going around your sponsor?
Ask in the form of the work. A question about who has to be comfortable with the decision before it can proceed invites the sponsor to describe the approval path, and it frames the introduction as something that protects the purchase. Bringing something useful to each conversation makes the introduction easy for the sponsor to make.
When should stakeholder mapping happen?
Before the proposal is written. Mapping late means security, procurement, and legal arrive after commercial terms are set, and their requirements then force a rebuild of the scope and the timeline. Mapping early turns those requirements into inputs.
What does surround sound produce?
Three things: a map naming every person who can stop the purchase and what each one is measured on, one claim per person attached to the cost that person carries, and a written plan that names who does what before the buyer's own deadline.
Jeff Aragon, Founder, Jozu Revenue Systems