What to say when a prospect says "just send me a proposal"

The first meeting went well enough. Then, before you have learned much about the problem, the prospect says, "Just send me a proposal." It sounds like progress, and sometimes it is. Just as often it is the politest way to end a meeting, or a request for a number to put next to someone else's.

Is "just send me a proposal" a buying signal or a stall?

It can be either, and the words alone won't tell you. What tells you is how the prospect answers one or two questions about the decision behind the request.

There are three common meanings. The first is genuine: they have a problem, they think you can solve it, and they need a figure for a budget or a board paper. The second is a brush-off: "send me something" is easier to say than "not interested", especially in markets where a direct no feels rude.

The third is a comparison. They already have a preferred supplier and procurement wants more than one quote. You are there to make the numbers look tested.

You can usually tell them apart by asking about timing and process. A genuine buyer will tell you who decides and by when. A brush-off goes vague ("we'll review it internally").

A comparison buyer often mentions their current provider, and if that is the situation, the conversation you need is the one in our guide on what to say when a prospect is happy with their current provider.

Why sending a proposal too early usually loses

A proposal written before you understand the buyer can only compete on price, because price is the only part you can make specific. Everything else is boilerplate, and the buyer can tell.

Think of an insurance broker asked to "just send a quote" for an SME's group medical cover after a short call. Without the staff list, the claims history or a sense of what the owner actually worries about, the broker can only price a standard plan. The SME puts that number next to two others, and the cheapest wins or nobody does.

There is a second cost. Once the document leaves your inbox, you lose control of how it is read. It gets forwarded to a finance director you have never met, skimmed between meetings and judged on the last page.

If the price then draws an objection, you are handling it by email, which is the hardest place to do it. Our guide to handling a price objection covers what to say when that happens.

What to say instead: three replies that work

Agree to send it, then ask for what you need to make it worth reading. You are not refusing the request. You are offering a better proposal in exchange for a few minutes, which is an easy trade for a buyer to accept.

When they say it in the meeting. Keep it light and specific:

"Happy to. So it's useful to you and not a generic price list, can I check three things before I go away and write it? What's prompting you to look at this now, who else will read it, and what would make you say this one is worth taking forward?"

Three questions is the limit. Any more and it starts to feel like an interrogation, and a prospect who was trying to end the meeting will end it anyway.

When they push for a number. Some buyers, often finance people, want a ballpark before they give you more time. Give one, with its assumptions attached:

"Fair enough. For a firm your size, this usually lands somewhere between [low figure] and [high figure] a year, depending mainly on [the main cost driver]. I'd rather not put a firm number in writing until I've seen [the missing information], because otherwise you'd be comparing my guess with someone else's guess."

A range answers the question honestly. It also tells you something: if the bottom of your range ends the conversation, you have both saved a week.

When the request arrives by email. Reply the same day, keep it short, and ask for a call rather than three answers in writing:

"Thanks, [Name], glad the meeting was useful. I'll put a proposal together, and to make sure it fits your situation rather than being a standard quote, could we take 20 minutes this week? I'd like to confirm the scope, who'll be involved in the decision, and your timing. Would Thursday at 10 or Friday at 3 suit?"

What to send instead of a full proposal

If you cannot get the conversation you need, send a short summary rather than a full quote. One page that shows what you heard, the options and the open questions will do more for you than ten pages of guesses.

A useful one-page summary has five parts:

• What you heard: their situation and the problem, in their words.
• What they want to change: the outcome they described, and by when.
• Two or three options: each with a price range and what it depends on.
• Open questions: what you need to confirm before you can firm up a price.
• A next step: a proposed date to go through it together.

This does two things a full proposal cannot. It tests whether you understood them, and it gives the buyer something to correct, which is far easier than explaining their business from scratch. A SaaS account executive who sends a finance director a one-page scope note headed "Have I got this right?" often gets back corrections and detail that the first call never surfaced.

How to get your proposal reviewed live with the buyer

Book the walk-through before you send the document, not after. Once the proposal is sitting in their inbox, the reason to meet has gone.

The simplest way is to make the meeting part of the delivery:

"I'll have it with you by Thursday. Can we hold 30 minutes on Friday to go through it together? A few of the costs depend on choices only you can make, and it's quicker to settle those live than over email."

If they still want it by email only, send it with a covering note that asks one specific question, such as which of the two options is closer to what they had in mind.

A question gives them a reason to reply. "Let me know if you have any questions" gives them none, and it is how most proposals go quiet. If yours does, our guide to following up on a proposal picks up from there.

What The Pharaoh's Pitch says about early proposal requests

Chapter 3 of The Pharaoh's Pitch, on knowledge and wisdom, treats an early demand for a final price as a question of authority. Its argument is that you first earn the right to be listened to, and only then the power to close. As Ivan Yong puts it:

Authority must precede power. The same dynamics must occur in the selling process.

The chapter's own example is this exact situation. The author describes competing to sell an e-learning platform to a large educational institute. After the demonstrations, the person in charge jumped straight to asking for a final quote, with no discussion of how the software would be implemented or where it might not fit their existing processes. In the author's words:

I was adamant in standing by my belief that if my client does not invest time in the due diligence of the software, I will not provide a final quote.

He eventually declined the request for proposal with a polite letter. The institute later postponed its implementation, which he took as a sign that it recognised his assessment, and he says the episode earned him authority with the client and with his own management.

You will rarely need to walk away. The principle holds at any size, though: a price given before the buyer has done the work is a price given without authority, and it gets treated as a commodity number.

Chapter 5, on leadership, adds the other half. It argues that buyers facing a significant purchase are looking for guidance, and it is wary of the "client is always right" habit, which it says makes the salesperson subservient and leaves out the leadership.

Sending exactly what was asked for, the moment it was asked for, can feel like good service. Asking three questions first is the more useful kind.

The same chapter says this leadership should be light, with the client still the main driver. That is why the replies above offer a choice of times and a range of prices rather than conditions.

Chapter 4 shows what skipping this step costs. A team lost a university deal, after all the work of writing the proposal and flying in consultants, because nobody worked out what the Dean personally hoped to gain from the project, what the book calls his personal win.

A proposal can be complete and still miss the one thing the decision-maker cares about. The questions you ask before writing are how you find it, and if you want to rehearse them, Niles' role-play tool can play the prospect who keeps saying "just send it over" and then debrief you on how you handled it.

You can prepare for this moment before the meeting, too. Our guide on how to prepare for a first sales meeting covers the questions to have ready so the proposal request arrives after discovery, not instead of it.