Never Name Your Fee First:The Three-Part Conversation That Ends Price Objections
Price objections are rarely about the price — they are a symptom of quoting before the buyer has agreed what the work is worth. Alan Weiss's Conceptual Agreement gives you the three commitments to secure before any number leaves your mouth.
Every founder of an expertise business has lived through the discount spiral at least once. You spend days building a careful proposal, the prospect goes quiet, and then the email lands: the work looks great, but the number is well above what they had in mind. Could you sharpen your pencil?
So you trim ten percent. Or you cut a deliverable. Or you offer a "lighter" version that quietly guts the engagement. Whichever path you take, you've just taught this client — and yourself — that your fees are opening bids.
Here's the uncomfortable truth: that negotiation was lost before the proposal was written. Not because the fee was wrong, but because the fee arrived before anything had been agreed. The prospect had no shared definition of what the work would change, no stated sense of what that change was worth, and no agreed way of recognising whether it happened. Against that vacuum, any number looks arbitrary — and arbitrary numbers get haggled.
Alan Weiss spent a career attacking this exact failure. In Value-Based Fees he describes the Conceptual Agreement: three commitments you and the buyer must reach, in conversation, before a fee is ever spoken. Get the sequence right and price objections largely stop happening — not because you got better at handling them, but because you stopped manufacturing them.
The Mistake Isn't the Number. It's the Order.
Why Early Quotes Always Get Negotiated
When a buyer hears a fee before agreeing on anything else, they have exactly one frame for evaluating it: comparison. What did the last firm charge? What did finance pencil into the budget? What does "consulting" usually cost? You handed them a number, but you gave them no basis for judging value — so they judged cost instead.
The Conceptual Agreement reverses the order. Before any fee appears, you and the buyer reach three explicit agreements: what the engagement will change, what that change is worth to their organisation, and how both of you will verify it happened. By the time a number enters the room, it's no longer a price to negotiate — it's a fraction of a value the buyer has personally articulated.
Each of the three agreements is a conversation, not a clause. Here's how to run them.
Agreement One: What Will Be Different
Outcomes Are the Unit of Value. Tasks Are the Unit of Cost.
Weiss is relentless about one distinction: an objective is not an activity. Open most service proposals and you'll find a list of activities — run six workshops, interview twenty stakeholders, deliver a detailed report. Every line describes the seller's effort. Not one line describes the buyer's result.
An objective states the change the client walks away with. "Run an assessment" becomes "give your board a maturity score that exposes the three capability gaps holding you back." "Facilitate a strategy session" becomes "get your leadership team committed to the same three priorities for the next twelve months." "Ongoing advisory" becomes "cut your time-to-decision on technology investments from six months to six weeks."
Why does the wording matter so much? Because activities are commodities. A buyer can price-shop "six workshops" in an afternoon — plenty of competent consultants run workshops, and the going rate is easy to find. But nobody can price-shop "a leadership team committed to the same three priorities." The worth of that outcome lives inside the buyer's organisation, which moves the entire conversation off the commodity market.
Buyers can comparison-shop your activities in an afternoon. They cannot comparison-shop an outcome that only exists inside their own organisation.
Surfacing objectives is a discovery skill. Asking "What do you need?" gets you a task list, because that's how prospects have been trained to brief vendors. Ask instead: "Imagine this engagement succeeds beyond your expectations. Walk me through what's different in your business six months from now." That question forces the prospect to describe change rather than effort — and their answer becomes the spine of everything that follows.
A useful range is three to five objectives per engagement. Below three, the scope is probably too thin to carry a meaningful fee. Above five, you're likely cramming multiple engagements into one and should phase the work instead.
Agreement Two: What That Difference Is Worth
The Question Most Consultants Have Never Asked
With the objectives agreed, you ask the question that turns the framework into a pricing engine: "If we deliver these outcomes, what would that be worth to your organisation?"
Most service founders have never said those words to a buyer. The first few times feel awkward — and that awkwardness is the tell. It marks the boundary between pricing your cost (hours, headcount, effort) and pricing the client's gain. The value conversation can run through several different currencies:
- Revenue. "With leadership aligned on priorities, how much faster do you execute? What does a quarter of faster execution translate to in revenue terms?"
- Cost. "If time-to-hire drops by 20%, what do you stop paying in recruiter fees, vacancy costs, and lost productivity?"
- Risk. "If we close your three biggest capability gaps before they turn into crises, what do those avoided crises cost today?"
- Position. "If you reach maturity Level 3 while competitors sit at Level 2, which opportunities open up that are closed to you now?"
Weiss treats a 20:1 return as the floor. If the buyer puts the value of the outcomes at $500,000 and your fee is $25,000, they're looking at a 20:1 ROI — and at that ratio the fee reads as an obvious bargain rather than a cost to grind down. Notice the reframe: "Is $25,000 a lot to pay a consultant?" is a cost question, and cost questions invite resistance. "Is $25,000 a sound investment to capture $500,000?" is an ROI question, and ROI questions are easy to say yes to.
The value conversation also works as a qualifier. Some prospects will refuse to engage with it — they'll keep steering back to hourly rates and budget ceilings. That refusal is data. It tells you this buyer processes services as expenses, not investments, and will lean on your pricing for as long as you work together. You can still take the engagement, but take it with clear eyes.
The buyers who do engage — who reason in outcomes and returns rather than hours and line items — tend to be the clients you want: more strategic, faster to decide, and more likely to grow the relationship. Run consistently, this conversation doesn't just lift your fees. It upgrades your client roster.
Agreement Three: How You'll Both Know It Worked
Evidence Neither Side Can Argue With
The third agreement protects everything the first two built. For each objective, you and the buyer define what success will look like in observable terms — measures both parties can examine at the end and agree, without debate, were met or not.
Where numbers exist, use them. "Maturity score moves from 42 to at least 55." "At least 80% of the leadership team reports consensus on priorities in the alignment survey." "Time-to-hire falls 20% within 90 days of rollout." A number settles disputes before they start.
Where the outcome is behavioural, define the observable behaviour. "The leadership team runs quarterly planning against the strategic framework." "Every senior-level candidate goes through the new interview protocol." "The board sees a structured readiness report ahead of each technology investment decision." No metric required — someone is visibly doing the thing, or they aren't.
Skipping this step is how good engagements end badly. The client carries one private picture of success, the consultant carries another, and neither picture is ever spoken aloud. Months later the consultant has delivered exactly what was promised while the client feels short-changed — a collision that explicit measures would have prevented on day one.
Agreed measures pay two further dividends. They draw a natural boundary around scope, because "done" has been defined before work begins. And every measure you hit becomes documented proof — a specific, evidenced result you can put in front of the next prospect.
Running the Sequence End to End
From First Call to Fee — Without the Proposal Graveyard
None of this is paperwork. The Conceptual Agreement is reached out loud, before any proposal exists. In practice the arc looks like this:
1. Discover. One or two conversations to understand the situation — what's working, what isn't, what's been tried, and what success would look like to this buyer.
2. Propose objectives. Play back what you heard as specific outcomes: "Based on our conversations, here's what I believe this engagement should change." The buyer confirms, edits, or adds until you're aligned.
3. Surface value. Help the buyer put a worth on those outcomes. This is collaborative: you supply the questions and the framework, they supply the organisational knowledge.
4. Fix the measures. For every objective: "What will look different if we achieve this? What data or behaviour would confirm it?"
5. Present the fee — last. Only now does a number appear, framed as a fraction of the value already on the table. Weiss's Choice of Yeses applies here: three options at three price points, walked through from the premium tier down.
Hermann Simon's research explains why the discipline compounds. Price is the most powerful profit lever a business has — roughly, a 1% price improvement produces about a 10% profit improvement. But higher prices only hold when the buyer perceives matching value, and the Conceptual Agreement is a system for building that perception deliberately, agreement by agreement, before the price exists.
So adopt one rule and keep it: no fee leaves your mouth until outcomes, value, and measures are agreed. That single act of restraint will move your average deal size, your win rate, and the quality of every client relationship that follows.