Reference
Frameworks: the intellectual foundation of proposal and SOW writing
Part of the Proposal Sow Writing skill · loaded on demand from SKILL.md
Contents
- SPIN Selling (Rackham, 1988)
- The Challenger Sale and insight selling (Dixon and Adamson, 2011; Adamson, Dixon and Toman, 2012; Adamson, Dixon, Spenner and Toman, 2015)
- Engagement economics (Maister, 1993, and public descriptions of strategy-firm practice)
- Fee models: the decision guide in depth
- Scoping, phasing and change control
- How the three foundations combine in one pursuit
This file gives each foundation as published, step by step, with the reasoning. Read it when you need to apply a method with judgment rather than follow the SKILL.md summary, when a client or colleague challenges the approach, or when a pursuit is not behaving the way the summary predicts.
1. SPIN Selling (Neil Rackham, 1988)
Origin and research basis
Neil Rackham and his research firm Huthwaite spent twelve years observing more than 35,000 sales calls in more than 20 countries, coding the behaviours of the sellers and correlating them with call outcomes. The book "SPIN Selling" (McGraw-Hill, 1988) reports what they found. The setting matters: the research was about large sales, which Rackham defines by their characteristics rather than a dollar figure: multiple meetings, multiple decision-makers, a long cycle, a high price relative to the buyer's discretionary budget, and a lasting relationship after the sale. Advisory engagements fit every criterion.
The core finding
Techniques that had been taught for decades because they worked in small sales (opening with benefits, handling objections, pressing for the close) had no positive effect in large sales and often a negative one. Buyers in large sales who reported that the seller used many closing techniques were less likely to buy. What correlated with success was the quality of the investigating stage: the questions the seller asked, and in what order.
The four stages of a call
Rackham divides any sales call into four stages. Preliminaries (the opening) have little effect on large-sale outcomes and should be brief. Investigating is where the sale is won or lost. Demonstrating capability comes only after needs are explicit. Obtaining commitment ends the call.
For the last stage, Rackham draws the distinction between an advance and a continuation. An advance is a specific action by the buyer that moves the sale forward: a meeting with the decision-maker, agreement to share data, a commitment to review a scope document by a date. A continuation is the buyer agreeing that the conversation was useful and that they will be in touch. Successful sellers plan the advance before the call and ask for it. In advisory pursuits, the most reliable advances are access (data, people, a site visit), a scoping session with the economic buyer, and an agreed date for a proposal presentation.
Implied and explicit needs
The mechanism of SPIN depends on a distinction that is easy to state and easy to ignore. An implied need is a statement of a problem, difficulty or dissatisfaction ("our margins are under pressure", "the board keeps asking about the branch network"). An explicit need is a statement of want or desire for a solution ("we need to recover 100 basis points without losing our top accounts"). In small sales, implied needs predict success. In large sales they do not; only explicit needs do. The reason is the value equation: a large purchase is justified only when the buyer's perception of the problem's seriousness outweighs the cost of the solution. Implied needs describe the problem; they do not size it. The SPIN sequence is a method for growing the buyer's perception of the problem until it outweighs the fee, and for having the buyer say so.
The four question types
Situation questions collect facts and background about the buyer's current state. The research found that successful sellers ask fewer of them, because buyers find them tedious and they reveal that the seller has not done the homework. Ask only those whose answers you cannot get elsewhere, and phrase them to show preparation ("I saw the 10-K shows freight at 2.1 percent of revenue; is that all outbound?").
Problem questions ask about difficulties, dissatisfactions and pain: where the plan misses, what takes too long, what the board keeps asking. These surface implied needs. Experienced sellers ask more of them than novices, and they ask them about areas the seller can address.
Implication questions take a problem and explore its consequences and effects: what it costs, who else is affected, what happens if it continues, what it prevents. This is where the buyer's perception of seriousness grows. Rackham found these to be the questions most strongly associated with success in large sales and the least frequently asked, because they are harder to prepare and can feel uncomfortable. They are the questions that turn "freight recovery is low" into "unrecovered freight is 5.5 million a year and it is why we cannot fund the branch refresh."
Need-payoff questions ask about the value or usefulness of a solution: what it would be worth, what it would make possible, how the buyer would know it had worked. They do two things. They turn implied needs into explicit ones by having the buyer describe what they want. And they have the buyer articulate the benefit, which the research shows is far more persuasive than the seller articulating it. They also rehearse the buyer for the internal selling they must do when the seller is not in the room.
Features, advantages and benefits
Rackham's analysis of the demonstrating-capability stage distinguishes features (facts about the offering), advantages (how a feature could help) and benefits (how a feature meets an explicit need the buyer has stated). In large sales, features are neutral, advantages are mildly positive early and negative later (they invite objections because the buyer has not yet felt the need), and benefits are strongly positive. The practical rule for a proposal: describe the engagement only in terms of the explicit needs the client stated. A methodology diagram is a feature. "The pocket-price waterfall gives you margin by transaction, which is what you said you needed to defend the top 200 accounts" is a benefit.
What SPIN does not do
SPIN assumes the buyer knows their problem, or can be led to it by questions. It is a method for developing needs the buyer already has. It has no mechanism for the case where the buyer's understanding of their problem is wrong, which is the case the Challenger research addresses.
2. The Challenger Sale and insight selling
Origin and research basis
Matthew Dixon and Brent Adamson, with colleagues at the Corporate Executive Board (CEB), published "The Challenger Sale: Taking Control of the Customer Conversation" (Portfolio/Penguin, 2011). The research base was a survey of more than 6,000 sales representatives across 90 companies and multiple industries, run during and after the 2008 recession, when CEB's member companies wanted to know why some sellers kept performing when conditions turned. Gartner acquired CEB in 2017, and the research continues under the Gartner name.
The five profiles
Cluster analysis of the behaviours produced five profiles: the Hard Worker (goes the extra mile, self-motivated, process-driven), the Relationship Builder (generous with time, builds advocates, gets along with everyone), the Lone Wolf (follows instinct, self-assured, hard to manage), the Reactive Problem Solver (reliable, detail-oriented, focused on post-sale delivery) and the Challenger (has a different view of the world, understands the customer's business, loves to debate, pushes the customer). Two findings drove the book. First, in complex solution sales, Challengers were close to 40 percent of star performers overall and close to half of stars in the most complex environments. Second, Relationship Builders were the least likely to be stars: 7 percent of high performers. The relationship approach that most professional-services firms instinctively use is, on this evidence, the weakest.
Teach, tailor, take control
Challengers are defined by three behaviours.
Teach for differentiation. The Challenger brings the customer a new perspective on their business, an insight that the customer did not have and that reframes their problem. The test of the insight is that it leads to action and, specifically, to the seller's distinctive capability. CEB's phrase is "commercial insight": commercial because it connects to something the seller can sell, insight because it changes what the customer believes.
Tailor for resonance. The Challenger adapts the message to the individual stakeholder's economic drivers and priorities, not just to the company. The CFO, the operations sponsor and the CEO need different versions of the same insight.
Take control of the sale. The Challenger is comfortable with tension, pushes back on the customer, and is willing to discuss money, timing and scope rather than deferring to the customer's process. CEB's finding was that customers reward this; deference is read as lack of conviction.
Constructive tension
The book is explicit that the Challenger is not aggressive. The tension is constructive: the seller challenges the customer's thinking with evidence, in the customer's interest, and remains willing to be wrong. In a proposal, the tension takes the form of a reframe: "you asked for cost reduction; here is why price leakage is the larger and faster problem."
The commercial teaching choreography
CEB's model for delivering an insight has six steps, and it maps closely to the structure of an insight-led proposal:
- The warmer: demonstrate that you understand the customer's world by describing the challenges you see at companies like theirs. Builds credibility without asking questions the customer has answered many times.
- The reframe: introduce the insight, the unexpected perspective that connects their challenges to a bigger problem or opportunity they had not considered. This should surprise.
- Rational drowning: quantify the reframe with data, often the customer's own, so that the new perspective becomes undeniable.
- Emotional impact: make it personal. A story of a company that missed this, or the consequences for the people in the room.
- A new way: describe what a company that acted on the insight would do, without yet mentioning the seller.
- Your solution: show how the seller's offering makes the new way possible, better than alternatives.
The ordering is the point. Sellers who lead with their solution (step six) never get the customer to step two. In a proposal, steps one to four are page one; step five is the approach; step six is the team and why-us section, which is why credentials go last.
"The End of Solution Sales" (Adamson, Dixon and Toman, HBR, July-August 2012)
The article extended the research to the customer side. Customers had become better at defining their own solutions, researching options and engaging suppliers late. High-performing sellers responded in three ways: they targeted organisations in flux (emerging demand, a new leader, a missed target) rather than those with established, well-defined demand where the seller is one of several quotes; they sought out sceptical change agents rather than friendly informants; and they coached those change agents on how to buy rather than asking them about their process. Each of these is a qualification rule for advisory pursuits.
"The Challenger Customer" (Adamson, Dixon, Spenner and Toman, 2015)
The follow-up book studied the buying group. Complex purchases involved, on average, more than five stakeholders, and the difficulty of reaching consensus among them was the main reason deals stalled. The research distinguished mobilizers (Go-Getters, Teachers, Sceptics), who can drive consensus, from talkers (Guides, Friends, Climbers), who share information but cannot. Sellers instinctively gravitate to talkers because they are pleasant; mobilizers are harder to work with and the ones who matter. The sceptic is often the best mobilizer: they test the insight hard, and once convinced they defend it internally.
How Challenger and SPIN fit together
SPIN develops needs the client already has; Challenger supplies needs the client did not know they had. In an advisory pursuit they run in sequence: SPIN discovery surfaces the client's own view and its cost, and gives you the data for rational drowning; the Challenger reframe then shows why that view is incomplete. A proposal that runs SPIN only will match the client's brief precisely and be undifferentiated from the other bids. A proposal that runs Challenger only will be an interesting opinion the client has no explicit need to buy.
3. Engagement economics
Maister's professional service firm (David Maister, "Managing the Professional Service Firm", 1993)
Maister's book is the standard public account of how professional firms make money. Three ideas carry the economics of any engagement.
The pyramid ratio (staff to partners). A firm's profitability depends on the ratio of junior to senior staff on its work. Maister's identity is: profit per partner = (profit / fees) x (fees / staff) x (staff / partners), that is, margin x productivity x pyramid ratio. Productivity itself is billing rate x utilisation. The consequence for an engagement: at a fixed fee, the more of the work that can be done well by junior people, the higher the contribution; and the partner's time is the scarcest and most expensive input, so the engagement should be designed so that the partner does only what the partner must do.
The three engagement types. Maister describes a spectrum. Brains engagements ("we are smart") solve novel, high-risk problems for which the client wants the most creative minds; they are senior-heavy, low pyramid ratio, and relatively insensitive to fee. Grey-hair engagements ("we have done this before") apply experience to a problem the firm has seen; a broader base is possible and the client is more fee-sensitive. Procedure engagements ("we do it efficiently") apply a well-developed method; the base is broadest and the client is most fee-sensitive. Firms drift from brains to procedure over time as problems become familiar, and their pyramids and fee models should drift with them. The practical rule for staffing: classify the engagement honestly, then staff for that type. A grey-hair engagement staffed as a brains engagement loses money; a brains engagement staffed as a procedure engagement loses the client.
Under-delegation. Maister observes that senior people in the average firm spend a large share of their time on work a junior could do with training. It is the commonest source of engagement losses that look like "the partner had to get involved."
Strategy-firm practice (public descriptions)
Public accounts of how strategy firms staff and run engagements (Rasiel, "The McKinsey Way", 1999; firm career pages; alumni descriptions) agree on the shape. A typical engagement team is a partner or senior partner who owns the client relationship and the answer, on the engagement part-time; an engagement manager who runs the work day to day, full-time; and two to five consultants and analysts each owning a workstream. Engagements are broken into phases of a few weeks each, and each phase ends with a steering committee at which the client can stop, redirect or continue. Analysis is hypothesis-driven from the start (see hypothesis-stress-testing), which is why the proposal can describe the key questions rather than a generic method. The fee is stated by phase, so that the client is buying a decision at a time rather than a long commitment.
The unit of engagement economics is the consultant-day. A day has three prices: the rack rate (what the firm bills a standard client), the loaded cost (salary, benefits and allocated overhead divided by the number of billable days a person is expected to deliver in a year, commonly 180 to 220), and the contracted rate (rack after any discount). Contribution is fee less loaded cost of days actually worked; the firm's floor for contribution margin is a management decision, commonly 35 to 50 percent for strategy work before firm overhead not already loaded into rates.
Partner time is real cost. A common distortion is to book partner days at zero because the partner is "not on the budget"; this overstates contribution and hides the fact that the client is paying for, and expecting, the partner's judgment.
Estimating consultant-days
The estimate is built bottom-up from the work, then checked top-down against the pyramid and the calendar. The bottom-up procedure:
- List the analyses and activities by phase (from the key questions: each question needs one or more analyses; each analysis needs data, a method and an output).
- For each, estimate days by role. Rules of thumb that hold across most advisory work: a structured interview costs half a day including preparation and write-up; a transaction-level analysis on a clean extract costs three to five analyst-days for the first cut and two more for each iteration; a steering committee document costs the engagement manager two days and the partner half a day; a workshop costs two days of preparation for every day of delivery; a handover with training costs as much as building the thing being handed over.
- Sum by role and phase, then add contingency to the phase with the most unknowns (usually the one that depends on client behaviour: a pilot, a roll-out, a negotiation).
- Check top-down: does the sum fit the calendar with full-time people? A phase that needs 40 consultant-days in three weeks needs three consultants, not two. Does the pyramid ratio suit the engagement type? A grey-hair engagement with more partner days than analyst days is mis-staffed.
- Check against precedent: what did the last comparable engagement actually take, not what was budgeted?
The most frequent estimation errors are omitting the client's time (interviews, data cleaning, steering committees all consume the client's calendar, and the client's calendar is the usual critical path), under-counting iteration (the first analysis is never the last), and counting the partner's selling time as delivery time.
Negotiating on scope, not price
When the client asks for a lower number, the firm has three honest responses and one dishonest one. The honest three: remove scope (a pilot site, a workstream, the handover training) and say exactly what is removed and what decision the client loses; change the fee model (move a phase to time and materials, or offer a hybrid with a success component) so that the client's certainty and the firm's risk are re-balanced; or change the timeline (a longer engagement with a smaller team costs less per week and sometimes less in total, but delays the decision). The dishonest response is to hold the scope and cut the price, which means either the original price was padded or the firm has decided to deliver at a loss; both damage the next negotiation. Prepare the scope trade-offs before the pitch, with the day count of each, so the answer to "can you do it for 400?" is immediate and specific.
Procurement adds a fourth conversation: rate cards, discounts to rack and comparisons across bidders. Answer in the units they use (a discount to rack, a blended daily rate) while keeping the client sponsor on the units that matter (value at stake, decision dates). Never let the blended rate become the object of the negotiation; it is an output of the pyramid, and lowering it by adding junior days changes the work.
4. Fee models: the decision guide in depth
Every fee model is an allocation of two risks: the risk that the work takes more effort than estimated (scope risk), and the risk that the outcome is less valuable than expected (value risk). The client and the firm can each bear either, and the fee model says who does.
Time and materials. The firm bills days at contracted rates; the client bears scope risk and gets control (they can stop at any time). Use for diagnostic or discovery phases where scope is honestly unknown, for staff augmentation, and for clients who want to direct the work. Add a cap (a not-to-exceed figure) when procurement requires certainty; the cap converts the top of the range to firm risk. The weakness is that it rewards effort rather than outcome, and the firm has no incentive to be efficient beyond reputation.
Fixed fee by phase. The firm quotes a price for a defined scope and bears the estimation risk. Use when the scope is well-defined, the deliverables are nameable, and the firm has done similar work (a grey-hair or procedure engagement). The firm protects itself with three things: a contingency in the day estimate for the least certain phase; assumptions and client obligations in the SOW that convert client-caused delay into a change event; and change control. Phasing matters most here: a fixed fee for the whole engagement forces the firm to estimate phase three before phase one has produced the facts. Fix each phase and re-scope the next at the gate.
Retainer. The client pays a periodic amount for access and a standing capacity: advisory time, board preparation, a monthly review. Use for ongoing relationships where the value is availability and judgment rather than deliverables. State what is included (days per month, response time) and what is not (project work, which is scoped separately). Retainers decay unless the firm shows use; a quarterly value review is standard.
Value-based fee. The fee is set by reference to the value at stake rather than the effort, typically as a fraction of annual value. It requires a credible sizing (see value-driver-modeling) and a client who accepts the sizing. It does not by itself require measuring the outcome; the fee is fixed, but its level is justified by value rather than days. This is the usual form for brains engagements.
Success fee, or performance fee. Part of the fee is contingent on a measured outcome. Four conditions must hold or the model fails: the outcome is measurable with data both parties trust; a baseline is agreed before work starts; attribution is agreed (which initiatives count, what happens when the client changes something else at the same time); and the measurement window and payment timing are defined. The firm should also insist that the fixed component covers delivery cost; otherwise the firm is investing its own capital in the client's execution, over which it has no control. Cap the upside so procurement can approve it, and hand the measurement design to kpi-architecture.
Hybrid. A fixed base plus a success component is the commonest form of value sharing in practice. Design the base to cover cost plus a modest margin, and the success component to bring the total to the value-based level if the outcome is achieved.
The three price anchors
Whatever the model, the price should be set against three reference points and the firm should know where it sits relative to each.
The floor is delivery cost divided by one minus the minimum acceptable margin. Below it the firm is subsidising the client; the only reason to go there is a deliberate investment in a relationship, and that decision belongs to the managing partner, stated as such, not hidden in a discount.
The reference is the rack-rate total: days times standard rates. It is what the firm would charge a client with no negotiating position, and the discount to it is the number procurement will ask for. Discounts above 15 to 20 percent to rack signal that either the rates or the day count were not believed in the first place.
The ceiling is a fraction of the annual value at stake. The fraction depends on how much of the value the engagement itself delivers: a diagnostic that identifies value but leaves the client to capture it supports a fee of perhaps a tenth of one year's value; a design-and-pilot engagement that proves the value in the client's own P&L supports up to a third; implementation support that captures the value can go higher, usually with a success component. Above the ceiling the client's rational response is to do the work internally or to buy it cheaper from someone with less insight, and the proposal has failed the value equation Rackham describes.
Choosing among them. Ask three questions in order. Is the scope well-defined? If no, time and materials with a cap for the first phase, then fixed fee for the rest. Is the outcome measurable, attributable and baselined? If no, no success component. Does the client want certainty or control? Certainty points to fixed; control points to time and materials. Then check the price against the three anchors (cost floor, rack reference, value ceiling) whatever the model.
5. Scoping, phasing and change control
Scoping
Scope is the list of questions the engagement will answer and the list it will not. The discipline comes from problem-framing: the issue tree gives the questions, and the scope is a pruned tree. Three rules produce scopes that hold. Objectives are few (three at most) and each is traceable to an explicit need the client stated. Deliverables are named as decisions the client will be able to make, with the artefact that supports the decision in brackets, because documents are easy to argue about and decisions are not. The out-of-scope list is written with the same care as the in-scope list, and it names the things the client is most likely to ask for later.
Phasing
Phases exist so that both parties can make decisions with information they did not have at the start. A phase should be long enough to produce a fact base and short enough that the client is not committing blind: three to five weeks is typical. Each phase ends with a steering committee at which the firm presents findings and a recommendation on the next phase, and the client decides. The fee is divisible at the same points, and the payment schedule has an instalment at each gate, so that cash follows decisions.
Client obligations and assumptions
Every consultant-day in the estimate rests on assumptions about what the client will provide: data by a date, access to people, a counterpart with authority, decision turnaround at gates. Write each one down, because each one that is not met costs days, and an assumption stated in the SOW converts a client-caused delay from a firm loss into a change event.
Responding to an RFP versus a sole-source pursuit
An RFP inverts the sequence: the client has written the scope, and discovery is limited to a question period and perhaps one meeting. Three adjustments. First, answer the RFP's structure exactly (procurement scores compliance) but put the insight in the executive summary, which is the one section every evaluator reads; a compliant response with no reframe competes on price. Second, use the question period for Implication and Need-payoff questions, in writing, because the answers go to all bidders and the client's own numbers become common ground. Third, if the RFP's scope is wrong (it asks for a branch consolidation study when the problem is pricing), bid the scope as written and add a short, priced alternative; declining to bid the stated scope loses; bidding only the stated scope wins the wrong engagement.
A sole-source pursuit has the opposite risk: without a competitor, the discipline of the economics sheet is the only thing that stops the price drifting toward the client's budget signal rather than the value at stake, and the discipline of the SOW is the only thing that stops the scope drifting toward everything discussed.
Change control
The purpose of change control is not to refuse changes; it is to make scope growth a decision that someone with authority takes knowingly. The procedure: any request that touches scope, timeline or team is logged within two business days; the engagement manager sizes it in days and fee at contracted or rack rates (say which in the SOW); the effect on timeline and gates is stated; the steering committee, or the client sponsor for small items below a threshold, approves, declines or defers; and the SOW is amended by a short change order. The threshold matters: a request under, say, five consultant-days can be approved by the sponsor; anything larger goes to the steering committee. Silence is how margin leaks: an engagement that absorbs ten small requests without logging them has given away a week of a consultant's time and has no record of why.
6. How the three foundations combine in one pursuit
The sequence in an advisory pursuit is: qualify (Challenger: organisations in flux, find the mobilizer), discover (SPIN: situation, problem, implication, need-payoff; end with an advance), reframe (Challenger: commercial insight with the client's data), scope (engagement economics: objectives, phases, gates, deliverables, obligations), staff and cost (pyramid, days, loaded cost, contingency), price (fee model, three anchors), write (insight-led proposal, then SOW), and close (Challenger: take control; SPIN: advance). Each foundation covers a failure the others cannot. SPIN prevents selling before the need is explicit. Challenger prevents selling the same thing as everyone else. Engagement economics prevents winning work the firm cannot afford to deliver.