The call went well. Your prospect understood the approach, liked the team, and asked for a proposal.

Then they forwarded your deck to someone who has never met you.

That person now has 38 slides, six service descriptions, and absolutely no idea why this needs to happen this quarter.

You gave your prospect homework. They were hoping you would help them buy something.

Find out which conversation happens after yours

Before you send the proposal they asked for, ask how the decision will get made. Start with the next conversation, not a demand to speak to "the decision maker."

"When you take this back to the team, who will want to weigh in?"

Then get specific. What does that person care about? What questions have stalled similar projects? Who controls the money? Who will have to change how they work?

Don't assume job title tells you the answer. A finance leader may care about timing and exposure. A practitioner may worry about an agency creating work their team can't absorb. A founder may want to know why the last attempt failed.

Ask your prospect to help you understand those concerns. They know the room. You don't.

Give them something they can actually forward

Build a short decision brief together. Your proposal can contain the detailed scope. The brief should help someone understand why that scope is worth considering.

Cover six things in plain language:

  1. The problem: What is happening in the business, in the buyer's words?
  2. The consequence: What does leaving it alone cost, delay, or put at risk?
  3. The recommendation: What do you propose, and why does it fit this situation?
  4. The evidence: What relevant work or reasoning supports the recommendation?
  5. The commitment: What money, people, information, and time are required?
  6. The decision: What specifically needs approval, and what happens next?

Keep unverified numbers out. If the buyer hasn't established what the problem costs, describe the consequence you do understand and identify the missing information.

A spreadsheet with invented upside is still fiction. The cells don't make it respectable.

Show the difference between a deliverable and a reason to buy

Here's an illustrative example for an agency helping a B2B company improve lead qualification.

The service description says: "We provide CRM optimization, funnel analysis, and sales enablement."

The decision brief says:

Marketing and sales currently apply different definitions of a qualified inquiry. Before increasing acquisition spend, we recommend agreeing on qualification rules and testing a shared handoff process. The initial engagement covers an audit of recent inquiries, working sessions with both teams, and a documented routing process. We need a marketing owner, a sales owner, and access to the agreed records. At the end, we'll review whether the process is being followed and where inquiries still stall before recommending additional work.

That gives the internal team something to evaluate. It also makes the client's participation visible before everybody says yes.

Add the actual fee, scope boundaries, schedule, and relevant proof for the real engagement. Don't promise that better routing automatically produces a particular revenue lift.

Let the champion tell you where it will get killed

Review the brief with your contact before they circulate it.

Ask: "If someone wanted to say no to this, where would they start?"

Perhaps the team has tried this before. Perhaps the budget belongs to a different department. Perhaps the person you like doesn't have enough internal support to take on another initiative.

That answer is useful. It may change the scope, the sequence, or whether this opportunity is ready at all.

Offer to join an internal discussion when it would help, with your contact's agreement. Don't go around them because you decided they lack sufficient authority. A champion who feels bypassed rarely becomes more enthusiastic.

Follow up on the decision, not your attachment

"Did you see my proposal?" asks whether a file arrived.

Try: "You expected the operations lead to review the staffing requirements on Thursday. What concerns came back?"

Now the follow-up is connected to an actual buying step. If that step didn't happen, find out why before treating the delay as an objection to price.

The sales follow-up playbook helps keep that conversation useful. Each message should help resolve something, not announce that you still exist.

Make your difference survive the retelling

If a prospect can only describe you as "smart people who seem to get it," you have more work to do.

They need a clear reason your approach suits their particular situation. DemandOS develops that answer to "Why us?" SalesOS helps your team use it inside a real buying process.

Your prospect may want to work with you. Help them make a recommendation they can stand behind when someone asks the uncomfortable questions.

They shouldn't need your personality in the room to explain your value.

Go deeper: The decision brief gets the deal forwarded. The proposal still has to close it. The Agency Proposal Playbook