Buyer commitments reveal momentum more reliably than seller activity ever will.
I have seen salespeople light up when a customer asks for a proposal.
“Great news. They want the numbers.”
Maybe.
A proposal request can mean the customer is seriously moving toward a decision. It can also mean they need a budget estimate, want to benchmark the incumbent, have an internal process to satisfy, or are simply curious about what you would recommend.
The request is real.
The meaning still needs to be discovered.
Imagine a technology provider pursuing a $3 million data-modernization opportunity. The customer’s transformation lead asks for a proposal covering cloud migration, data-platform consolidation, and managed support.
The seller mobilizes architects, finance, legal, delivery, and executive sponsors. The team builds a thoughtful solution, models the transition, sharpens the price, and delivers an impressive document.
The CRM moves forward. The forecast gets warmer. Leadership begins discussing the likely win.
Then the deal goes quiet.
The CFO has not agreed that the program deserves funding this year. Security has not reviewed the proposed data-residency model. Operations worries the migration will disrupt critical reporting. Procurement uses the price to challenge the incumbent. The transformation lead likes the proposal but does not own the decision.
The supplier completed an enormous amount of work.
The buyer made almost no commitment.
Seller effort can create the appearance of momentum while the buying decision remains perfectly still.
This is where pipeline reviews often become unintentionally optimistic.
We ask whether the proposal was delivered, whether the demo happened, whether the business case was sent, and whether the executive presentation went well.
Those are useful activities. They tell us what the seller has done.
They do not tell us whether the customer is changing.
Buyer psychology offers a practical caution here. Gathering information preserves options. Making a decision closes some of them. A customer can enthusiastically request detail because learning is relatively safe while commitment carries budget, reputation, disruption, and career risk.
That does not mean the buyer is misleading anyone. It means interest and intent are different things.
The salesperson pays when that difference is missed through wasted pursuit effort and a painful quarter-end surprise. The sales leader pays through forecast volatility. The organization absorbs expensive solutioning capacity. The customer can also lose, because a proposal assembled before the decision is understood may solve the visible request rather than the real problem.
A proposal should express a buying decision in progress—not substitute for one.
Before mobilizing the proposal machine, I would want to understand what changed inside the customer.
Who has agreed the problem deserves action? Who owns the business outcome? What decision will the proposal enable? Which stakeholders still need to examine the risk? What will the customer do after receiving it—and by when?
The answers do not need to be perfect. Complex decisions evolve.
But there should be some buyer movement: access to the economic buyer, shared data, stakeholder meetings, agreed evaluation criteria, committed review dates, or a jointly understood decision path.
Otherwise, sales is not progressing a deal.
It is producing a document.
The strongest evidence in a pipeline is not what the seller completed. It is what the buyer committed to do next.
If your pipeline contains plenty of proposals but too little buyer movement, it may be worth examining what your stages are really measuring. Reach out—I’m always happy to have the conversation.
