Published September 11, 2026 · Altvina Insights · 5 min read

The Scope Conversation That Is Quietly Losing You Deals

Most "too expensive" replies in professional services are not price losses at all. They are scope-language losses, where the buyer understood the number and not what it bought, and filled the gap with their own worst case.

The reply reads the same way every time it lands. They went a different direction. The pricing came in above what they had budgeted. Keep in touch.

It gets filed under price. The next proposal goes out a little cheaper, and that one loses too.

My position: most price losses are scope-language losses

My best explanation, and I am happy to be argued out of it: In small-firm professional services, the buyer usually understood the number just fine. What they could not see was what the number bought. So they filled that in themselves, and people fill a gap like that with the most expensive version they can picture: meetings that never end, a second phase nobody mentioned, an invoice in March for something they assumed was covered.

Then they say no on price, because price is the polite reason. It needs no explanation and it does not insult anyone's work. Nobody writes back to say your scope section made them nervous.

Most of my career before Altvina was in technology and telecom, where a statement of work got read line by line by people whose actual job was to find the hole in it. That trains a specific reflex. You stop asking whether your scope is accurate and start asking what a suspicious stranger could read it as.

Three phrasings that open the gap

1. Deliverables written as activities

Weekly working sessions. Discovery interviews with your leadership team. Ongoing collaboration through launch. All of that describes how the time gets spent, which is your side of the deal, not theirs. A buyer reading a list of activities has no idea what they will own at the end.

The plain rewrite names the thing that exists at the end, and when. Something closer to: by October 3, you have a written intake and handoff map for your two busiest service lines, in a format your ops lead can edit. Same work, but now the buyer can picture owning something.

2. Open-ended language

"Ongoing support as needed" is read two ways, and both of them cost you. The cautious buyer reads it as unlimited and assumes you have padded the price to cover yourself. The optimistic buyer reads it as unlimited and finds out in month three that it was not. Either way somebody feels misled.

Give it edges instead. Support means email replies within one business day and a standing thirty-minute call each week for eight weeks. That sentence promises less and reads better, which sounds backwards until you sit with it.

3. Nothing is explicitly excluded

This is the one small firms resist hardest, because an exclusions line feels like handing the buyer a reason to walk. I read it the other way. When nothing is excluded, everything is arguably included, so the buyer prices the whole imaginable job and compares that to your number. Three honest lines under "Not included, and where it would go" do more for trust than another paragraph about your approach.

One pattern shows up often: the tighter proposal, the one that admits its own edges, gets fewer clarifying questions and a faster yes. Not always. Often enough that I would test it before I discounted anything.

Why price keeps getting the blame

Loss reasons are self-reported, by someone who wants the exchange over with. And scope clarity is invisible when it works: nobody tells you that a clean exclusions section is why they relaxed and signed. They just sign, and you chalk it up to relationship or price or timing.

And so the feedback loop points the wrong way. Firms sand down their rates for years while the actual leak sits in one paragraph they have never reread as a stranger.

Where I am wrong about this

Sometimes price is price. When the budget is a quarter of your number, no rewrite saves it. Where you are the third bid on genuinely commoditized work with a procurement form attached, the language barely matters. And a founder who is simply too expensive for the market they are selling into has a positioning problem, not a proposal problem.

Clearer scope will also lose you some deals faster. A buyer who wanted an unlimited retainer at a fixed fee will find out sooner and leave. I think that is a good trade. You may not.

What would change my mind

The way to find out is specific. Take the next ten proposals, name the artifact and the date, put edges on the support language, add the exclusions. When the close rate holds flat and the sales cycle does not shorten, and the same too-expensive replies arrive at the same rate, then my explanation is wrong for that firm and the problem lives upstream in who is being pitched.

I would also change my mind if the tighter version reliably invited harder haggling on rate. A fair counterargument says specificity hands a buyer line items to attack. I have not seen it play out that way, but I would want to know if it did for you.

The one-page check

Open the last proposal you sent and lost. Read only the scope section, out loud, in the voice of the buyer's finance person, who does not like you yet.

Go through and count the sentences that name something that exists when the engagement ends. Then find the sentence a nervous reader would take as "this could go on forever." Usually that is all it takes to see it.

You do not need a new pricing model. You need the proposal to answer the question your buyer was too polite to ask out loud.

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.