The Conceptual Agreement: Three Things to Agree On Before Quoting a Price
Most consultants quote prices too early. The result is predictable: objections, negotiations, and race-to-the-bottom discounting. Weiss's Conceptual Agreement framework eliminates all three.
Here's a scene that plays out thousands of times a day in professional services. A prospect reaches out: "We need help with X. Can you send us a proposal with pricing?" The consultant, eager to move the deal forward, spends two days writing a proposal, sends it over, and waits.
Then comes the reply: "Thanks — this looks thorough. But the budget we had in mind was about half of what you quoted."
The consultant now faces a terrible choice. Discount and signal that the original price was inflated. Hold firm and risk losing the deal. Offer a reduced scope that feels like a compromise to both parties. None of these options are good — because the conversation was broken from the start.
The problem isn't the price. The problem is that the consultant quoted a price before establishing what the engagement was worth. They jumped to "how much" before agreeing on "what for," "how we'll know it worked," and "what that outcome is worth to you."
Alan Weiss, in Value-Based Fees, built the Conceptual Agreement framework to fix exactly this sequence error. It's the most practical pricing tool in the professional services literature — and it requires you to agree on three things before a number ever appears.
Element One: Objectives
What Will This Engagement Actually Produce?
Weiss draws a sharp distinction between objectives and activities. Most proposals are stuffed with activities: "We'll conduct six workshops. We'll interview twenty stakeholders. We'll deliver a comprehensive report." Those are tasks. They describe what the consultant will do. They say nothing about what the client will get.
Objectives describe outcomes. Not "conduct an assessment" but "produce a board-ready maturity score that reveals your three highest-priority capability gaps." Not "facilitate a strategy session" but "align your leadership team on three strategic priorities for the next twelve months." Not "provide ongoing advisory" but "reduce your time-to-decision on technology investments from six months to six weeks."
The distinction matters because activities are commodities. Any competent consultant can conduct six workshops. The market price for "six workshops" is discoverable and comparable. But the market price for "aligning your leadership team on three strategic priorities" is tied to what that alignment is worth to the specific organization — and that's a completely different conversation.
When you agree on objectives with the client before quoting, you accomplish something subtle but powerful: you shift the evaluation criteria from "is this a good price for these activities?" to "is this a good investment for these outcomes?" The first question invites comparison shopping. The second invites value assessment.
In practice, establishing objectives requires asking better questions in discovery conversations. Not "What do you need?" (which invites a task-based answer) but "What would be different in your organization six months from now if this engagement is wildly successful?" That question forces the prospect to articulate outcomes — and those outcomes become the foundation of everything that follows.
"Conduct six workshops" is an activity. "Align leadership on three strategic priorities" is an objective. One is a commodity. The other is worth whatever alignment is worth to that organization.
Aim for three to five objectives per engagement. Fewer than three suggests the scope is too narrow to justify a significant fee. More than five suggests you're trying to do too much in a single engagement and should consider phasing the work.
Element Two: Measures of Success
How Will We Know the Objectives Were Achieved?
Once you've agreed on what the engagement will produce, the next question is: how will both parties know it worked? This isn't a trick question — it's a genuine alignment exercise that prevents the two most common post-engagement disputes: the client who says "I expected more" and the consultant who says "I delivered what was agreed."
Measures of success can be quantitative or qualitative, but they must be observable. Both parties should be able to look at the measure and agree — without argument — whether it was met.
Quantitative measures are ideal when available: "Maturity score increases from 42 to at least 55." "Leadership alignment survey shows 80%+ consensus on priorities." "Time-to-hire reduced by 20% within 90 days of implementation." Numbers don't argue.
Qualitative measures work when the outcome is behavioral: "The leadership team uses the strategic framework in their quarterly planning sessions." "Hiring managers follow the new interview protocol for all senior-level candidates." "The board receives a structured readiness report before every technology investment decision." These are observable — someone is either doing the thing or not — even if they're not numerical.
The act of defining success measures together does two things. First, it prevents scope creep. When both parties agree upfront on what "done" looks like, the engagement has natural boundaries. Second, it gives you the material for a case study. If the measures were met, you have a documented success story with specific outcomes — the kind of evidence that makes future sales conversations easier.
Most proposals skip this element entirely. The consultant quotes activities, the client approves, and both parties carry different — unstated — definitions of success in their heads. The result is a successful engagement that feels like a disappointment because the client imagined something the consultant never intended. Measures of success prevent that collision.
Element Three: Value
What Is Achieving These Objectives Worth?
This is where the Conceptual Agreement becomes a pricing framework. After agreeing on objectives and success measures, you ask the question that changes everything: "If we achieve these objectives and meet these success measures, what would that be worth to your organization?"
The value conversation feels uncomfortable at first. Most consultants have never asked a client to quantify the worth of an outcome. But the discomfort is precisely the point — this is the conversation that separates value-based pricing from cost-based pricing.
Value can be expressed in multiple currencies:
- Revenue impact. "If we align leadership on strategic priorities, how much faster could you execute? What's a quarter of faster execution worth in revenue?"
- Cost reduction. "If we reduce your time-to-hire by 20%, what does that save in recruiter fees, lost productivity, and vacant-position costs?"
- Risk mitigation. "If we identify and address your three highest-priority capability gaps before they become crises, what's the cost of those crises avoided?"
- Competitive advantage. "If your organization reaches maturity Level 3 while your competitors remain at Level 2, what market opportunities does that open?"
Weiss considers a 20:1 ROI the minimum acceptable ratio. If the engagement produces $500,000 in value and you charge $25,000, the client receives a 20:1 return. At that ratio, the fee is an obvious bargain — no negotiation necessary.
The beauty of this approach is that it reframes the entire pricing conversation. Instead of "Is $25,000 a lot of money for consulting?" the question becomes "Is $25,000 a good investment for a $500,000 outcome?" The first is a cost question. The second is an ROI question. And ROI questions are much easier to answer yes to.
Not every prospect will engage with the value conversation. Some will insist on hourly rates or budget limits. That's information too — it tells you that this prospect evaluates services as costs rather than investments, which means they'll always pressure your pricing downward. You can still work with them, but you should go in with eyes open about the relationship dynamic.
The prospects who do engage with value — who think in terms of outcomes and ROI rather than hours and budgets — are almost always better clients. They're more strategic, more decisive, and more likely to expand the relationship over time. The Conceptual Agreement doesn't just improve pricing. It filters for better clients.
Putting the Three Elements Together
The Conversation That Replaces the Proposal
The Conceptual Agreement isn't a document. It's a conversation that happens before any proposal is written. In practice, it follows this flow:
Discovery phase: You ask questions to understand the prospect's situation. What's working? What isn't? What have they tried? What would success look like? This typically takes one or two conversations.
Objectives alignment: You summarize what you've heard and propose specific objectives. "Based on our conversation, here's what I believe this engagement should achieve..." The prospect confirms, adjusts, or adds objectives until both parties agree.
Success measures alignment: For each objective, you agree on how success will be measured. "If we achieve objective one, what will look different? What data or behaviors would confirm it?"
Value articulation: You help the prospect quantify what achieving these objectives is worth. This is a collaborative exercise — you bring the framework, they bring the organizational knowledge.
Fee presentation: Only now do you present your fee. And when you do, you present it as a fraction of the agreed value, using Weiss's Choice of Yeses — three options at three price points, presented top-down from premium to base.
Notice what's different about this sequence: by the time the prospect hears a price, they've already agreed on what the engagement will produce, how they'll know it worked, and what that outcome is worth. The fee isn't a surprise to be negotiated. It's a fraction of a value they've already articulated.
Hermann Simon's data reinforces why this works. Price is the most powerful profit lever — a 1% increase in price yields approximately a 10% increase in profit. But price increases only stick when the buyer perceives commensurate value. The Conceptual Agreement builds that value perception systematically before the price appears.
Never quote a fee until you've agreed on objectives, measures, and value. That one discipline — resisting the urge to name a number before the foundation is set — will change your average deal size, your close rate, and your relationship with every client who says yes.