The Live Proposal: Why You're Losing Deals in the Send Button

Nearly every time I've let someone decide on their own instead of giving them the proposal on the call, it didn't work out the way I wanted. So I try very hard to do the proposal live, because then I can watch how they're reacting to certain pieces and read what their face is saying. I'm not leaving anything up to chance. I want to know what's not landing and what I might need to tweak to get them across the finish line.

When you send a proposal and walk away, you've given up the one thing that actually closes deals, which is the ability to see the reaction and respond to it in the moment. They might misread a line or take something the wrong way, and now that misread is exactly what they think you meant. If you'd been in the room when you brought it up, you'd have caught the flicker on their face and corrected it right there.

A sent proposal is a silent channel, and silent channels convert at zero.

Quick Take

• The deals that fall apart are usually the ones where you let the prospect decide alone with a document instead of walking them through it live, because a PDF can't answer the question they're quietly forming.
• You should never email a full strategy. A detailed proposal can walk out the door, get handed to a cheaper agency, and become a free spec to underbid you on. Stay high-level on the "how."
• The one exception: if they paid for the proposal, give everything away, because at least they already paid you for the thinking.
• Live, you read the reaction, and the moment you see a flinch you call it out directly instead of pretending you didn't see it.
• Most objections come dressed as pricing even when pricing isn't the real issue. Your job is to find the underlying reason, because you can't handle an objection you've misnamed.

The Silent Channel Problem

Think about what a sent proposal actually is. It's a document moving through a channel where no information comes back to you. You don't see the prospect's face when they hit the pricing slide. You don't hear the question they ask their business partner after the call. You don't know which line made them quietly decide the answer was no. The proposal goes out, and then you wait, and waiting is not a sales motion.

Here's why that matters more than most agency owners think. People rarely understand a proposal exactly the way you meant it. They read fast, they bring their own assumptions, and they fill gaps with whatever story already lives in their head. When you're in the room you can catch a misread the instant it happens and say "let me back up, that's not quite what I meant." When you've sent the document, the misread hardens into the truth, and you never even find out it happened. You just get a polite "we decided to go another direction," or more often, nothing at all.

That's the part that makes ghosting so frustrating. You don't get to learn anything. If you'd delivered the same proposal live and watched them go cold at a specific moment, you'd know exactly which item didn't sit right, and you'd have had a shot at fixing it. Off a sent PDF, you can't even tell which piece lost the deal. The whole thing reads as one flat "no" with no detail attached.

So the live proposal isn't about being more polished or more persuasive. It's about keeping the channel open so reaction can flow back to you while you can still do something about it.

What Goes In a Proposal, and What You Leave Out

There's a real tension here, because the same detail that makes a proposal feel thorough is the detail that gets you shopped. Inside the proposal, spend most of your time on what can be accomplished and a simple version of how you'd get there. Never go deep into the exact steps you'd run to do it.

The risk you run by putting everything in there is straightforward. They can take that proposal, hand it to a different agency, and ask "can you execute this for cheaper?" That second agency won't necessarily get the same results, because the thinking is what creates the results and you didn't hand over the thinking, just the steps. But people do this all the time to vet agencies against each other, and a detailed proposal makes it easy. You've basically written the spec for someone else to underbid you on.

So leave out the fine details and go high-level on strategy. The line is something like "this is the direction we'd take it" rather than "here is the exact sequence of moves." You're showing them you know the path without drawing them the map.

There's one clean exception, and it's worth building offers around. If they pay for the proposal, you can give everything away. When you've got a paid engagement where the final output is the proposal itself, hand over all of it, because even if they walk away with the full strategy, they already paid you for that work. A paid diagnostic flips the whole risk. The thing you'd normally guard becomes the thing you're selling.

This is also where weak positioning shows up. Positioning gets shaky when your claims don't match how the work actually gets done. If you sell speed but the proposal describes biweekly update meetings, the prospect feels the mismatch even if they can't name it. If speed is the promise, the proposal should sound like speed: "we meet once a week, we drop the meeting when we don't need it, and you get an async weekly update so nothing ever slows down." The "how" you reveal, even kept light, has to back up the word you're trying to own.

Reading the Room: The Tells Before the Ghost

When you're presenting live, people rarely ghost right away, which is exactly why live matters so much. The ghost is usually the end of a process that started with signals you could have caught. The most reliable one is pricing. You'll see them tense up when you bring up the number, or they'll keep circling back to it through the rest of the call. That hesitation is data, and it's data you only get because you're watching.

There's a subtler tell that's easy to misread, so it's worth slowing down on. Sometimes a prospect starts asking questions that seem to go deeper, and you assume they're engaged. Often they are. Questions about whether you're the right fit and whether you actually understand what they're doing are good questions, and they usually mean someone's seriously evaluating you. But there's another kind of question that feels similar and means the opposite. When someone starts asking questions that seem aimed at extracting value out of the proposal rather than figuring out if you're the right option, that's the tell. They've stopped evaluating you and started mining you. They want the thinking, and they're using the call to pull more of it out of you for free.

Learning the difference between "help me decide if you're right" and "give me more I can use without you" is most of what reading the room comes down to. The first kind of question you lean into. The second kind you handle carefully, because you've slipped from a sales conversation into a free consulting session.

Calling Out the Flinch in the Moment

Here's the move most people are too polite to make, and it's the whole reason you went live in the first place. When you see the flinch, you call it out directly. You don't file it away and hope it resolves itself. You name it.

You can say something as plain as "hey, it doesn't look like that sat well with you, let's go back a step, what didn't feel right there?" Ask probing questions, but be direct enough that they can't smile and wave it off. Another version that works when you sense you may have caused the confusion yourself: "I might've misspoke there, and I want to make sure we're on the same page, so what do you think about this?" You're giving them an easy door to walk through, but you're also making the issue impossible to ignore.

The reason this works is that the alternative is so much worse. If you notice the flinch and say nothing, the objection doesn't disappear, it just goes underground and turns into the silent "no" you'll get a week later by email. Naming it out loud is the only chance you have to find out what it actually was, and you can only do that while you're both still in the room. A sent proposal gives you zero shots at this. A live one gives you as many as you're willing to take.

The Format Menu: How Light Is "Light"

There's no one perfect proposal format, and the right one depends on your agency and the deal in front of you. What matters more than the format is that whatever you pick keeps the value inside the call rather than letting it walk out the door.

The one-page proposal is great for exactly that reason. It's hard for someone to take a single page and hand it to another agency as a build spec, which means more of the value stays in the conversation where you can defend it. A one-pager forces the deep thinking to happen live, with you in the room, instead of getting written down for anyone to copy.

You don't even need a document. Sometimes the strongest version is just talking through what you'd do and explaining your thinking out loud. It could be you walking through their website pointing out specific elements you'd change, or at the extreme end, walking through their Google Analytics and showing them what the numbers are telling you. That kind of live walkthrough is hard to screenshot and shop around, and it shows your judgment in real time, which is the thing they're actually buying.

You can also do a full deck with everything you'd change laid out slide by slide, but that's the version I'd avoid when you can. A complete deck is the easiest thing in the world to forward to a cheaper shop. If you're going to use a deck, keep it high-level and save the deeper thinking for the live walkthrough, so the prospect leaves impressed but doesn't leave owning your strategy.

Underneath all of these is the same structure. Lead with the problem, so they know you understand what they're struggling with. Move to the outcome they want and tell them you believe you can get them there. Then give the solution, kept deliberately light, just enough "how" to show you've got a path without handing over the map. Problem, then outcome, then a light solution, walked through live.

Handling the Pricing Objection: Find the Real Reason

Most objections come back to pricing, but pricing is the easy thing to say, and that's the trap. People reach for a pricing objection even when price isn't really the problem, because it feels like a clean way out. They might have several issues at once. They might not be confident you can actually deliver. They might be unsure their team will get behind the decision. But almost none of that is comfortable to say out loud, so it all gets compressed into "it's a bit expensive."

If you take the pricing objection at face value, you'll do the obvious thing and discount, and discounting won't fix a problem that was never about price. You'll have given up margin and still lost the deal, because the real objection is still sitting there untouched. So I always look for the underlying reason someone's raising the question. Once you can name the actual concern, you can address the actual concern instead of guessing at it.

This is another thing you can only do live. When the pricing objection surfaces on a call, you can probe it. "When you say the price feels high, is it the number itself, or are you not yet sure this is going to work?" That single follow-up separates a budget problem from a confidence problem, and they get handled in completely different ways. A budget problem might be scope or payment terms. A confidence problem is about proof and risk reversal, and no discount on earth solves it. You can't run that diagnostic against a PDF. You can only run it against a person who's still in the conversation with you.

The Bottom Line

The proposal that closes is the one you deliver in the room, where you can read the reaction, catch the misread, name the flinch, and find the real objection hiding under the easy one. Strategy should never leave that room as a PDF, because the document can't do any of those things. It just sits there, silent, while the prospect builds whatever story they're going to build with no one there to correct it.

Keep the proposal light, keep the deep thinking inside the call, and treat the live delivery as the most important sales moment you have, because it is. If they want the full strategy in writing, that's a paid engagement, not a free spec.

If you're working through how to deliver proposals live, where to draw the line on what you give away, and how to read what a prospect is actually telling you, that's the kind of thing agency owners are working out together in the Dynamic Agency Community.

FAQ

Why do my proposals keep getting ghosted?

Often because you sent them. A sent proposal gives the prospect room to misread it, talk themselves out of it, or shop it to a cheaper agency, and you never find out which one happened. When you deliver it live you can catch the moment something goes cold and address it before it turns into silence.

Should I send a proposal or present it live?

Present it live whenever you can. The whole value of a proposal conversation is watching the reaction and handling objections in the moment, and a sent document throws that away. Sending is fine for confirming details after you've already walked them through it together, but it's a poor way to actually win the deal.

How much detail should I put in an agency proposal?

Enough to show you understand the problem and have a clear path to the outcome, but not the exact steps you'd run. Detailed step-by-step proposals get handed to other agencies with the question "can you do this cheaper," which turns your thinking into a free spec for someone else. Stay high-level on the "how" and save the deep version for the live conversation, unless the proposal itself is a paid deliverable, in which case you can give everything away because they've already paid for it.

What format should an agency proposal be?

There's no single right format, but lighter is usually better. A one-page proposal keeps the value inside the call and is hard to forward to a competitor. You can also just walk through their website or analytics and talk through what you'd change, which shows your judgment live without writing it all down. A full slide-by-slide deck is the easiest version to shop around, so if you use one, keep it high-level.

How do I handle a pricing objection on a sales call?

Don't take it at face value, and don't reach for a discount. Pricing is the easy thing for a prospect to say even when the real issue is something else, like doubt about whether you can deliver. Ask a follow-up that separates the number from the confidence, something like "is it the price itself, or are you not sure yet this will work," and handle whatever you actually uncover.

What do I do when a prospect reacts badly during a proposal?

Name it on the spot. Say something like "it doesn't look like that landed, what didn't feel right there," and ask directly enough that they can't brush it off. The reaction is the most useful thing you'll get on the call, because it tells you exactly what to fix while you can still fix it.