How to handle objections before the proposal

The symptom

The proposal meeting turns into live objection handling, and the team is good at it.

Price comes up. Then timeline. Then someone asks whether the firm has done this exact thing before, in this sector, at this size. The partner has an answer for all three and delivers them cleanly. Nobody gets defensive. Nobody fumbles a number.

Then the meeting ends with everyone agreeing to reconvene...and the invite goes out the next morning for a date two weeks away.

The debrief calls it a good meeting. Strong questions, which gets read as an engaged buyer. Handled well, which gets read as a win. Both readings are available and both miss what happened in that hour, which is that the buyer discovered three things they now have to go resolve somewhere the firm won’t be present.

Why it keeps happening

Objections show up at the proposal because that’s the first moment the decision becomes real enough to be worth objecting to. Until then it’s interesting, and nobody bothers objecting to something interesting. A proposal carries a number and a start date, and interesting turns into something that’s about to happen to a budget, a calendar, and somebody’s standing.

So far the observation is sound. The error is what firms build on top of it. They accept the proposal meeting as the natural venue for objections and prepare accordingly: the rebuttal slides, the pricing defense, the comparison sheet, the rehearsal the night before where the team runs the hard questions at each other until the answers come out smooth.

Preparing to handle objections in the room is a reliable way to make sure they arrive in the room. That venue gives the buyer the least capacity to absorb an answer and the most convenient way to postpone the whole decision.

We’ve prepared beautifully for the objections. In the room. At the exact moment nobody could act on the answers.

What the buyer is doing at the Safety gate

Weighing whether they can carry the choice into rooms where they’ll have to answer for it.

An objection raised in the proposal meeting is an unresolved risk arriving at the moment of commitment. You can answer it perfectly and the buyer still walks out holding a concern they found late. Late discoveries carry a particular smell. Nobody concludes you lied. They conclude this is the sort of thing that surfaces at the end, which quietly opens a question about what else might.

The same answer delivered six weeks earlier, unprompted, reads as candour. Identical content, different meaning, because you volunteered it at a point when nothing was forcing you to.

Then there’s the carrying problem. An objection the buyer only heard answered out loud is one they can’t take anywhere. They can’t forward a good answer. They won’t reproduce it accurately for a CFO three days later, and any model summarizing your proposal for someone who never met you will repeat what’s on the page and nothing that was said in the room.

The correction

Start with the three objections this firm gets most often. Get them from the people who get them. The partners and salespeople sitting in those meetings can tell you what the last dozen buyers pushed back on; a workshop where everyone brainstorms what buyers might worry about cannot. Twenty minutes gets the real three on paper, and two of them will be the two everyone already knew.

For each one, name the earlier interaction that handles it and the form the answer takes. A piece of content that goes out before the first meeting. A reference conversation set up at week two rather than week eight. A scoping session where the awkward question gets asked by you. A written note after a meeting: here’s what we didn’t get to, here’s our answer, raise it with your team.

Then make it a gate. Before any proposal leaves the building, each of the three has to have been addressed in writing at some earlier point in the relationship. Discussed doesn’t count. Written, sent, sitting in an inbox where somebody who wasn’t in the room can read it without a translator.

One of the three won’t cooperate, and it’s usually price. There’s no method for pre-empting a number the buyer hasn’t asked about except raising it yourself. So raise it. Early, as a range, with what moves it in either direction. An awkward price conversation in week two costs a fraction of the same conversation in week nine, and the week two version is the one where nobody has to defend anything.

The strongest proposals read as a continuation of conversations already had, in the language the buyer has already seen. A new claim or a new piece of positioning showing up for the first time in a proposal is how a document turns into an argument. The objections that recur across every deal belong somewhere public, answered before anyone thinks to ask, which is its own piece of work.

Here’s the test. The proposal contains no argument the buyer is hearing for the first time.

Before and after

Before. Week nine, in the proposal meeting: “You’re right that we haven’t done this exact build in your sector. Let me walk you through why that matters less than it looks.”

After. Week three, in a note after the scoping call: “One thing worth raising with your team before we go further. We haven’t built this exact system in your sector. Here are the two closest, here’s what transfers and what doesn’t, and here’s someone at each who’ll take your call. If it’s disqualifying, better we both find out now.”

What backfires

Pre-empting objections nobody has. A note listing four risks the buyer never considered reads as a firm arguing with itself, and the credibility goes on installing doubt that wasn’t there.

Raising price early and then refusing to name anything is the other one. A range with conditions attached is candour. “It depends on scope” is a stall wearing candour’s clothes, and every buyer has heard it before.

Run this on your own material

Take the last proposal meeting you sat in. Write down every objection that came up, in the buyer’s words, including the ones that arrived disguised as questions.

Now go back through the file and find where each could have been answered four weeks earlier. The scoping call. The meeting notes. The follow-up email nobody sent. For most of them there’s a specific date on which the same answer would have landed as useful information rather than a defense.

A few can’t be moved. Mark those and leave them alone. What remains is a sequence for the next deal, built from what a real buyer asked instead of a guess about what buyers ask.

Signals you’ve cleared it

Advance when the proposal meeting runs short and administrative. Questions about start dates, staffing, how invoicing works. The buyer using your written language back at you, sometimes with a colleague who was never in an earlier meeting. A proposal that gets forwarded before it gets debated.

Hold when a new objection appears in the room, however well it gets handled. Hold when the answer to a predictable question lives only in a partner’s head and has never been written down, because it can’t travel to the people who weren’t there. And hold when the buyer opens the price conversation. That was your move to make, and it’s late.

Where this connects

Story from the Field · The Decision You Could Survive, on exposure surfacing at the moment of commitment.

Research Library · Entry 14, professional-services buying and the committee.

Next move · Go to How to know when to make the ask.