When they ask for a proposal before a call

"Sounds interesting. Can you send over a proposal?" It feels like a win. The buyer is engaged, they're asking for something concrete, and the deal seems close.

It usually isn't. A proposal written before a conversation is a guess with a price on it. It gets compared, filed and forgotten. The reply deserves a better answer than a PDF.

What the request usually means

Sometimes the buyer genuinely has a defined need and wants numbers to compare. That happens, and it's often a sign another firm is already involved.

Often it's a way to stay in control. A proposal lets them evaluate you without giving up an hour.

And sometimes it's a soft brush-off. Asking for a proposal sounds more polite than saying no, and it puts the work on you.

It can be a price check too. A buyer with an incumbent sometimes wants a second number to take into a renewal talk. Your proposal becomes a bargaining chip in someone else's deal, and you never hear back.

You can't tell which from the email. That's the reason to talk first.

Why a blind proposal loses

A proposal without a conversation is built on your assumptions, not their problem. It'll be too broad, too narrow or priced against the wrong scope.

It turns you into a line item. The buyer compares your price to someone else's and the cheapest credible number wins.

And it ends the conversation. Once the document is sent, the next move belongs to them. Many proposals never get a reply. The stalled proposal post covers what that silence means.

The reply to send

Say yes to the proposal. Then ask for a short conversation to make it accurate.

Happy to put one together. So it's useful and not a generic document, could we take twenty minutes first? I want to understand the scope of the migration, the timeline you're working against, and who else has a say in it. If that's not possible, send me a few lines on each and I'll work from that.

It doesn't refuse. It explains why the call helps them. And it offers a fallback, so a buyer who won't talk can still give you something real.

Most buyers take the call. The ones who refuse even the written questions tell you something about the deal.

When they won't take a call

Sometimes a buyer insists. A procurement process, a tight deadline, or a firm rule about vendor meetings.

Then send something short. One page that restates their problem as you understand it, offers two or three scoped options with ranges, and names the assumptions you made.

End it with a question about the assumptions, not a request to meet.

I've assumed the migration covers both regions and that the cutover has to happen before the fiscal year ends. If either is wrong, the scope changes a lot. Which one is closer to right?

That keeps the thread alive and invites a correction, which is usually where the real conversation starts.

What the call should cover

Keep it to twenty minutes and use the time well. Confirm the problem in their words. Find out what's driving the timeline. Ask who else will read the proposal and what they care about.

Then send the proposal within a day or two, written in the language they used. It'll read like it was written for them, and it was.

Open the proposal with their problem, in their words, before a single line about your firm. A buyer who sees their own sentence on page one keeps reading. A buyer who sees your capabilities slide first starts comparing prices.

The point

A request for a proposal is a request for help deciding. Give them that help by getting the conversation first, and the proposal that follows has a real chance. For more on what that first conversation should cover, see qualifying in the first conversation and pricing conversations start in Stage 1.