Red Flags Part 5: The Proposal Came Too Soon

There is a sentence that used to make me feel like I was winning.

“Can you just send over a proposal?”

Early in my career, I heard that sentence and did what most hungry salespeople do.

I took it as progress.

A proposal felt like movement. It gave the conversation weight. It gave me something concrete to work on. It made the opportunity feel real.

So I built the thing.

And not some lazy one-page estimate either. I built the thoughtful version: recommendations, structure, timelines, pricing, and a clean explanation of how I saw the problem and how I would approach solving it.

At the time, I thought I was proving value.

Looking back, I was handing over the thinking before the buyer had earned it.

And then I waited.

Sometimes they disappeared entirely. Sometimes they came back weeks later with questions that made it painfully obvious they had not read it. Sometimes they used it to compare me against three cheaper options they had already planned to call. Sometimes they sent it up the chain to someone I had never met, who had no context for the conversation and no reason to care.

That is when I learned something I wish someone had told me earlier.

A proposal request is not always a buying signal.

Sometimes it is legitimate.... the buyer has done the work, the decision process is clear, the budget exists, and the proposal is simply the next step.

But sometimes it is something else entirely.

It is procurement checking a box. It is a junior contact trying to look productive. It is someone collecting free strategy under the polite cover of “send me something to review.”

That is what makes this red flag tricky.

The proposal is not the problem.

The timing is.

If they ask for a proposal before you understand the business problem, the decision process, the budget reality, the timeline, and who actually has the authority to move, you are not selling.

You are guessing.

Salespeople hate admitting that because the request feels good. It feels like the deal is advancing, gives you something to work on. It gives your manager something to see and makes the pipeline look active.

But a proposal sent too soon is usually not momentum.

It is a loss of control.

I watched a rep once spend half a week building a custom recommendation for a prospect who had been “very interested.” Great first call. Lots of energy. Lots of compliments.

The buyer said all the things salespeople like to hear.

Then came the ask.

“Send me something I can review.”

So the rep did.

Beautiful proposal. Smart strategy. Strong pricing. Clear next steps.

The prospect went quiet.

When they finally resurfaced, the response was basically, “Thanks, this helped us think through our options.”

That is a sentence that should come with a warning label.

Because what they really meant was:

“Thank you for doing the thinking. We are going to shop the execution.”

That is the trap.

You think you are proving value.

They are extracting it.

And once your expertise becomes an attachment, it is very easy for the conversation to become about price.

No context.

No urgency.

No relationship.

Just a number sitting next to someone else’s number.

That is not where good selling happens.

A real proposal should confirm a conversation that has already been qualified. It should not be forced to carry the entire weight of one that never happened.

Before you send it, you should know who is making the decision, what problem they are actually trying to solve, why now matters, what happens if they do nothing, who else is involved, what a good outcome looks like, and whether they are looking for a partner or simply collecting pricing.

And if those questions make them uncomfortable, pay attention.

A serious buyer will usually respect the process.

The wrong buyer will rush past it because the process is exactly what exposes them.

Here is the line I wish I had learned sooner:

“I’m happy to put together the right recommendation. Before I do, I need to understand a few things so I am not sending you something generic.”

That one sentence will save you hours.

The right prospect will lean in.

The wrong one will get annoyed that you are not handing over the work before they have earned it.

Good.

That annoyance is information.

Because the person who will not answer basic questions before the proposal is often the same person who will later say your recommendation missed the mark.

The person who will not discuss budget is often the same person who disappears after seeing pricing.

The person who will not give you access to the decision-maker is often the same person who says, “I just need to run this by my boss,” after you have already spent hours building the plan.

The proposal was never the problem.

The missing conversation was.

This is Part 5 of the Red Flags series.

Part 1 was about spotting bad clients before you sign them.

Part 2 was about weeding the ones already sitting in your pipeline.

Part 3 was about liking them too much to see clearly.

Part 4 was about Prince Charming’s off switch.

This one is for every salesperson who has ever spent too much time building a beautiful proposal for someone who was never really in the deal.

Your turn.

Have you ever sent the proposal too soon and regretted it?

Or better question — what do you make sure you know before you agree to send one?

Andrea Goodman

Appointments By Design

High-touch business development partner for B2B companies in facility services, trades, and beyond. We open doors to decision-makers—not just calendars.

www.apptsbydesign.com

LinkedIn

Learn More