You had a great call. Your contact is engaged, the scope is confirmed, the price is accepted. Then: “I just need to run this by my manager.” And the deal goes quiet. What killed it isn’t the manager, it’s the 10-minute conversation that happened in the hallway that you had no part of and no visibility into. The decision-maker loop is the framework that changes that.
The Sales Development Playbook describes this as one of the most common and most preventable causes of deal loss: the champion who was excited on the call but wasn’t equipped to sell the idea internally. They bring your proposal to a review and get three questions they can’t answer. The approver asks for a comparison with another vendor. The budget discussion reveals a constraint your champion didn’t know about. The deal dies in a meeting you weren’t invited to.
The decision-maker loop doesn’t prevent that meeting from happening. It changes what your champion brings into it.
The three moves
The loop has three components, ideally deployed before the proposal is sent, not after it stalls.
Move 1: Equip the champion. Give your contact the language and materials to advocate for you internally.
Move 2: Offer to present directly. Make it easy for the approver to hear the reasoning from you rather than through interpretation.
Move 3: Establish a decision timeline. Build a specific date into the process so the review doesn’t drift indefinitely.
Most deals that stall in internal review don’t die because the approver said no. They die because nobody was actively moving them forward. The decision-maker loop gives your champion the tools and the motivation to be that person.
How to identify the real decision-maker early
Ask at the end of the first call, framed as a planning question:
“So I can make sure the proposal covers everything it needs to, who else is involved in a decision like this?”
Their answer gives you the org-chart information you need. If they name an approver, continue:
“Would it make sense to include [approver] in the conversation at any point? I’ve found that when the decision-maker can ask questions directly, reviews tend to move faster.”
Some champions will want to control the process internally. Others will welcome the offer, it reduces their burden of translation. Either response is useful information.
Move 1: The champion enablement brief
Before you send the proposal, give your champion a one-page brief they can share internally. Not your full proposal, the internal audience doesn’t need your methodology and service description. They need the business case.
A champion brief includes:
- The problem in business terms. Not “SEO strategy” but “organic traffic is declining 18% year-over-year, which is reducing inbound leads.” One paragraph.
- The proposed approach. 3 to 5 bullets covering what will be done and in what sequence.
- The investment and ROI framing. What the expected return is relative to the cost, quantified wherever possible.
- Risk reduction. Case studies, guarantees, a milestone-based payment structure, or references that reduce the approver’s perception of risk.
- Timeline. Key milestones and the decision date.
Script for delivering it:
“I’ve put together a one-page brief that covers the business case in terms your [CFO/CEO/team] would want to see. It’s designed to be shared, not as a sales document but as internal context. Does it make sense to send that alongside the proposal?”
Most champions say yes. The brief does the selling you can’t do in the room.
Move 2: Offering the direct presentation
The offer to present directly accomplishes two things: it gives the approver access to the reasoning without the telephone-game distortion of secondhand summary, and it tells your champion that you’re willing to take the burden of the internal sale off them.
Script:
“If it would be useful, I’m happy to do a 20-minute call with [approver] directly, either alongside you or separately. A lot of times it’s easier to get questions answered in real time than to go back and forth through email. Would that be helpful?”
Frame it as serving the champion, not going around them. If they agree, prep for that meeting specifically, the approver’s concerns will be different from the champion’s. Know their role, their typical objections, and the language they respond to.
If the champion declines the offer, respect it. You’ve signaled willingness; don’t push. But do ask: “What does [approver] typically need to see to move forward on something like this?” The answer shapes the proposal and the brief.
Move 3: Establishing the decision timeline
Without a named decision date, the internal review has no endpoint. It drifts until a competing priority displaces it or the momentum dies.
Script:
“Once you share the proposal internally, what’s a realistic timeline for getting a decision? Is this a week, two weeks, a specific meeting where it would be reviewed?”
If they name a meeting: “Great, when is that meeting? I’ll hold my calendar accordingly.”
If they’re vague: “Would it work to put a soft date on it? I want to make sure I don’t have a competing project start in the same window. Could we say [date] as your decision point?”
Combine this with a plan for checking in: “I’ll follow up [3 days before the decision date] to see if there’s anything else I can provide.”
Script 1: The full setup at the end of the discovery call
“Before I put the proposal together, a couple of things I want to make sure we have covered. First, who else needs to be part of this decision on your end? And second, once you share it internally, what’s the typical timeline for a decision like this? I want to structure the proposal for the right audience and make sure I’m holding calendar for the right window.”
Script 2: When the champion reveals an approver mid-conversation
“That’s useful to know, what does [approver] typically look at when evaluating something like this? I want to make sure the proposal speaks to what matters to them directly.”
Script 3: When the deal has already gone quiet during internal review
“Wanted to check in on where the proposal stands internally. Is the review still on track for [date we discussed], or has the timeline shifted?”
One sentence. No pressure. Sent to the champion, not to the approver directly unless you have a separate relationship with them.
What to do when the answer is “it’s still in review”
This is the most common response to the check-in. The appropriate follow-up: “Thanks for the update, is there anything I can add or clarify that would help move it along?”
That question gives the champion a direct path to ask you for something, a comparison, a revised scope, an answer to a specific question the approver raised. It keeps you helpful rather than pressuring.
The loop’s underlying logic
The decision-maker loop isn’t about controlling a process you’re not part of. It’s about giving the people who are part of it everything they need to succeed on your behalf. When you equip your champion well, establish a real timeline, and make direct access easy, you’ve done the maximum a seller can do when they’re not in the room. Everything after that depends on your champion, which is why building that relationship during the sales conversation is as important as any closing technique.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
