Most advisory engagements are underpriced before they start. The pricing error is not a negotiation failure or a lack of market knowledge — it is a scoping failure. When the boundaries of an engagement are unclear, the work expands to fill whatever space the client makes available, and the advisor absorbs the cost of that expansion without compensation.
I have priced engagements correctly and incorrectly. The pattern that separates them is not confidence or experience alone. It is the quality of the scope document. An engagement that starts with a clear, agreed specification of what success looks like, who has authority to make decisions, and what conditions trigger the engagement's end will hold its economics through delivery. An engagement that starts with a general understanding, a handshake, and mutual good intentions will not.
This article is about what an advisory scope needs to specify, and why the elements that advisors most often skip are precisely the ones that create the underpricing problems they encounter.
Why Scoping Errors Cause Underpricing
The relationship between scope and price runs in both directions. A tighter scope enables a more defensible price. A vague scope makes any price feel arbitrary — to the client, and sometimes to the advisor.
When scope is unclear, clients fill in the ambiguity with their own expectations. Those expectations are almost always more expansive than the advisor intended. A client who hears "I'll advise on your hiring process" may understand that to include reviewing every job description, attending interview debrief sessions, coaching the hiring manager, and being available for ad-hoc questions throughout the search. The advisor who said those words may have meant something far more limited: a framework conversation, a template review, and access to their judgment on specific questions.
Neither party is lying. The gap is a scoping failure.
The advisor absorbs the gap because walking back scope mid-engagement is more costly than delivering the extra work. The client relationship matters. The reputation matters. The next engagement matters. So the advisor delivers what the client expected and is paid for what the advisor intended, and the economics do not work.
A second failure mode is underpricing relative to the actual risk the engagement carries. Advisory work often involves access to sensitive information, decisions that affect organizational direction, and accountability for outcomes that the advisor does not control. Pricing that is calculated against hourly effort does not capture this risk. Pricing that is calculated against a clear scope that specifies decision authority and accountability structure is much easier to defend.
The Advisory Scope Specification
After working through enough underpriced engagements to understand the pattern, I now use a five-element framework for specifying advisory scope before agreeing to price anything. I call it the Advisory Scope Specification. The five elements are: problem statement, success criteria, access requirements, decision authority, and termination conditions.
Each element does specific work. None of them are optional. Skipping any one of them creates the predictable problems that advisory engagements encounter.
Element One: Problem Statement
The problem statement is not a restatement of the client's opening request. It is a precise description of the underlying condition the engagement is designed to address.
A client may come with a request: help us find a better approach to customer acquisition. The problem statement beneath that request might be: the company's customer acquisition cost has increased 60% over 18 months and the founding team does not have diagnostic frameworks for understanding why or what to change.
These are not the same thing. The request describes what the client wants. The problem statement describes what the engagement needs to solve. Advising toward the request without understanding the problem statement leads to advice that addresses the presenting symptom rather than the actual condition.
Writing a clear problem statement also surfaces scope limitations early. If the actual problem is beyond the advisor's relevant experience, or if it requires organizational access that is not being offered, or if it requires a commitment from the client that has not been made, the problem statement makes that visible. Better to discover this before agreeing to price than during delivery.
Element Two: Success Criteria
Success criteria are the specific, observable conditions that indicate the engagement has accomplished its purpose. They are not aspirational goals. They are not general improvements. They are the specific things that will be true, or measurably different, when the work is done.
The discipline of writing success criteria forces both parties to confront whether the engagement's purpose is actually achievable within the time and access available. Clients often want engagements to produce outcomes that depend on organizational will and execution capacity that the advisor cannot control. "The team will be aligned on the go-to-market strategy" is not a success criterion an advisor can guarantee. "A documented go-to-market strategy will exist, and the leadership team will have reviewed and approved it" is.
The distinction matters for pricing and for termination. If the engagement's success criteria are met — if the deliverable exists, if the review has happened, if the decision has been made — the engagement is complete. The advisor's obligation is fulfilled. Without explicit success criteria, completion becomes a judgment call that the client is usually better positioned to defer than the advisor.
Success criteria also protect advisors from the moving-target problem. Clients' views of what constitutes success can shift as an engagement progresses, particularly if the original problem turns out to be more complex than anticipated. A documented success criterion can be renegotiated — but renegotiation requires acknowledgment that the original scope is changing, and that acknowledgment creates a natural checkpoint to discuss whether the price should change with it.
Element Three: Access Requirements
Access requirements specify the people, information, systems, and time that the advisor needs from the client organization in order to do the work.
This element is the one advisors most often skip, and it is the one that most frequently causes engagements to stall or underperform. An advisor who needs access to the founder for substantive conversation cannot do the work if the founder is available for thirty minutes per month. An advisor who needs to understand the financial model cannot do the work if the CFO is not willing to share the relevant data. An advisor who needs to interview department heads cannot do the work if those interviews require senior approval to schedule.
Documenting access requirements shifts accountability appropriately. If the engagement requires two hours of founder time per month and that time is not available, the engagement cannot proceed as scoped. The advisor has not failed. The access condition has not been met. The scope needs to change, or the price needs to change, or both.
Access requirements also include response time expectations. If the advisor needs feedback on a recommendation within five business days in order to maintain the engagement's momentum, that expectation should be documented. Engagements that stall in the client's review queue often do so not from malice or disengagement but from competing priorities that were never weighed against the advisory engagement's requirements.
Element Four: Decision Authority
Decision authority specifies who within the client organization can make the decisions that the advisory engagement is designed to support, and whether that authority actually sits with the people who are engaging the advisor.
This element is the most politically sensitive to raise and the most important to resolve before work begins.
Advisory engagements frequently fail not because the advice is wrong but because the person receiving the advice does not have the authority to act on it. An advisor retained by a division head to recommend organizational changes may produce excellent recommendations that the division head agrees with and cannot implement because those changes require board approval that was never secured. The engagement is technically complete — the advice was delivered — but nothing changes, and the engagement is retrospectively judged as unsuccessful.
Clarifying decision authority also surfaces situations where the advisor's access is insufficient for the work. If the engagement requires influencing decisions that sit above the client's authority level, the advisor needs to know whether they will have access to the people with that authority, or whether their role is to equip the client to make that case upward. These are different engagements. The first requires direct access to the decision-maker. The second requires understanding the political dynamics at the level above the client.
Element Five: Termination Conditions
Termination conditions specify the circumstances under which the engagement ends — both the conditions that represent successful completion and the conditions that represent appropriate early termination.
Most advisory contracts specify end dates. Fewer specify what actually signals that the engagement's purpose has been accomplished, or what conditions would make continued engagement counterproductive.
Completion termination is straightforward: the success criteria have been met. The engagement is done.
Early termination conditions are more nuanced. They might include: the key sponsor leaves the organization; the company's strategic direction changes in ways that make the original problem statement irrelevant; access requirements prove impossible to meet over multiple consecutive periods; the engagement encounters information suggesting it was retained under materially false premises.
Documenting early termination conditions protects both parties. The advisor has a defined basis for ending an engagement that has become unworkable without making it a personal rupture. The client understands in advance what conditions might cause the advisor to recommend ending the work. These conversations are easier to have when the conditions are specified in advance than when the advisor raises them mid-engagement as a surprise.
The Difference Between Scope and Deliverables
A common mistake in advisory scoping is conflating scope with deliverables. Deliverables — the documents, frameworks, presentations, and recommendations that the advisor will produce — are an output of the scope, not a substitute for it.
A scope document that lists deliverables without specifying the underlying five elements is an incomplete scope. It tells both parties what will be produced but not what success looks like, who has the authority to act on it, what access is required to produce it, or when the engagement is over.
This confusion is especially common in transitions from consulting to advisory work. Consulting engagements are naturally deliverable-centric: the project produces a report, a model, a system. Advisory engagements are judgment-centric: the advisor's value is their ongoing perspective, not a discrete artifact. Scoping advisory work with a deliverables list imports the consulting framework into a context where it does not fit well.
Pricing After Scoping
The relationship between scoping and pricing is direct. An engagement with a clear problem statement, defined success criteria, specified access requirements, documented decision authority, and explicit termination conditions is much easier to price accurately than an engagement without any of these elements.
The price should reflect four things: the scope of the problem being addressed, the time and access the engagement requires, the risk the advisor is carrying, and the value of the outcome if the engagement succeeds. An advisor who has worked through the Advisory Scope Specification knows all four of these well enough to price honestly.
Pricing conversations become more straightforward when both parties have reviewed the scope together. The client understands what they are buying. The advisor understands what they are committing to deliver. Negotiation happens at the scope level — if the price is too high, the scope can be adjusted — rather than at the level of general impressions and goodwill.
Underpricing, in this frame, is usually a symptom of insufficient scope definition rather than insufficient pricing courage. An advisor who is uncertain about what the engagement requires is also uncertain about what it costs to deliver. That uncertainty translates into conservative pricing that leaves margin on the table and creates engagements that overdeliver relative to their economics.
A Note on Scope Revision
Even a well-specified scope will encounter situations that the original document did not anticipate. The client's organization changes. The problem turns out to be different from the presenting description. New information surfaces that changes what success looks like.
Scope revision is normal. What matters is that it is acknowledged explicitly rather than absorbed silently. When the engagement's conditions change materially, both parties should recognize that change, assess whether it affects the scope specification, and agree on whether the price changes with the scope.
An advisor who absorbs scope changes silently does two things: they train the client to expect unlimited flexibility, and they move the engagement progressively further from the economics that made it viable. Both outcomes make the engagement harder to sustain and harder to replicate.
Scope revision is a normal, professional act. It is not a failure. The advisor who asks for a scope revision conversation when conditions change is protecting the integrity of the engagement — and the relationship — more than the one who absorbs the change without comment and becomes quietly resentful.
Starting the Next Engagement
The practical test of the Advisory Scope Specification is whether the next engagement starts differently than the last one. Not perfectly — no scope document survives contact with a complex client organization without requiring revision. But differently: with clarity about the problem, defined success criteria, documented access requirements, explicit decision authority, and specified termination conditions.
An advisory practice that develops this discipline as a habit does not eliminate underpricing entirely. But it eliminates the primary cause of it: starting engagements without a shared understanding of what the work actually requires.