Pricing conversations start in Stage 1

Your price gets set in the first conversation, not the proposal. By the time you write a number down, the buyer has already decided what the work is worth.

They decided it based on the problem you helped them name.

Why proposals get squeezed

A services leader looks at a lost deal or a thin margin and blames the proposal. Priced too high. Priced too low. Wrong rate card. Bad negotiation.

Sometimes. More often, the deal was priced the moment the buyer framed it as a commodity. "We need some developers for a migration" will always be compared on rates. "We need to get off the old system before the people who know it retire, or we'll miss the date the board signed off on" won't.

Same work. Very different price.

The problem sets the price

A buyer pays in proportion to what the problem costs them. Not what the work costs you.

If the problem is mild, the budget is small, and any vendor will do. If the problem threatens a target the CFO committed to, a launch the CEO announced or an audit finding with a deadline, the budget is real, and the buyer cares more about who than how much.

So the most important pricing move you make is in Stage 1. It's the hypothesis you lead with, the questions you ask and how clearly you help the buyer see the cost of doing nothing. More on that in most quarters are lost in Stage 1.

What sellers do that cheapens the deal

They lead with capabilities. "We do cloud migrations" invites a comparison with every other firm that does cloud migrations. The buyer reaches for the cheapest one.

They skip the committee. A director with a small budget and no access to the economic buyer can only approve a small number. Get to the person who owns the bigger problem.

They rush to scope. The buyer says "send me a rough estimate," and the seller does, before anyone knows what the problem costs. That number becomes an anchor nobody can move.

And they let the buyer define the work. When the buyer writes the scope, they write it as tasks. Tasks get priced as hours.

A scenario

Say two firms meet the same VP of engineering at a software company. Both hear that the platform team is stretched on a cloud move.

The first firm proposes four engineers for six months and sends a rate card. The VP compares it to two other quotes and pushes on rates.

The second firm asks what happens if the move slips. The VP says the company promised customers a new feature that only works on the new platform, and sales has it in their forecast. The firm asks who else cares about that. The VP names the CRO.

The second firm proposes the same four engineers, framed around protecting the launch date, with the CRO and VP in the room. The conversation is about risk, not rates. And the price holds.

What leaders should change

Coach sellers to name the cost of doing nothing in every first meeting. It's the single question that moves price more than any other.

Stop sending rough estimates before discovery. Offer a short working session instead. It moves the deal forward and protects the price.

Review early-stage deals, not just late ones. If the pipeline meeting only talks about proposals and closes, you're reviewing after the price is set. The weekly pipeline meeting for small firms can fix that.

And reward sellers for margin, not just bookings. If they're paid on top line alone, they'll trade price for speed every time.

The proposal is a receipt

A good proposal confirms what the buyer already agreed to in conversation. The problem, the owner, the cost of doing nothing and the outcome.

If the proposal is the first place the buyer sees why the work matters, it's too late. They're reading it next to two others and looking at the bottom line.

Win the framing in Stage 1, and the number takes care of itself.