The Engagement: Proposal to Trusted Advisor

Consulting Galaxy · Branch: Foundations (cn-foundations) · ⬜ White Belt: Analyst · ~8 focused hours · Mastery gate ≥ 85%

You have, somewhere, produced a piece of analysis you were genuinely proud of, and watched it change nothing. Nobody argued with it. Nobody found a flaw in it. It simply sat in an inbox, or got a polite nod in a meeting, and the decision it was built to inform got made some other way, for some other reason, by people who were never quite persuaded to act on what you gave them. That experience is not a fluke of one unlucky memo. It is the single most common failure mode in advisory work, and it has almost nothing to do with the quality of the thinking. A consultant is not hired to be right in private. A consultant is hired to make a client confident enough to act (on a recommendation, on a number, on a plan that costs money and careers if it is wrong), and that confidence is not a mood you create in the last meeting with a good slide. It is built, or quietly destroyed, at every single stage of an engagement: in the proposal that first argued you deserved the work, in the contract that defined exactly what you owed, in the small moment three weeks in when you either absorbed a client's off-scope request for free or handled it like a professional, in the number a junior analyst got wrong and a senior one caught before the client ever saw it, in the feedback that made the junior analyst better instead of merely told them they were wrong, and in the one conversation, late in the engagement, where telling the client the truth cost your own firm money.

If that's happened to you, you're in large company. It's the commonest failure in advisory work, and it has almost nothing to do with the quality of the thinking. A consultant isn't hired to be right in private. A consultant is hired to make a client confident enough to act on a recommendation, a number, or a plan that costs money and careers if it's wrong. And you can't create that confidence with a good slide in the last meeting. It gets built, or destroyed, at every stage of an engagement. It starts in the proposal that first argued you deserved the work, and in the contract that defined what you owed. It shows three weeks in, when a client asks for something off-scope and you either absorb it for free or handle it like a professional. It's there in the number a junior analyst got wrong and a senior one caught before the client saw it, and in feedback that made the junior analyst better instead of merely telling them they were wrong. Then, late in the engagement, comes the one conversation where telling the client the truth costs your own firm money.

What follows maps that whole arc, from proposal to trusted advisor. You've already met how a consultant thinks: structure, hypothesis, answer first. Now you'll see how a consultant is retained and run, and how they come to be trusted, so that thinking gets put to work for a real, paying, anxious client.

You'll learn what a good proposal argues and how it differs from a sales pitch, and how a Statement of Work turns a persuasive pitch into a document you can be held to. You'll build a fee from people and time instead of pulling it from the air. You'll see why scope creep is the commonest way a good engagement goes bad, and the routine that stops it. And you'll learn how an engagement team is organized and delegated to. You'll see how its work is quality-controlled, and how to give feedback that changes behavior instead of recording an opinion.

At the heart of it is the trust equation, a deceptively simple piece of arithmetic. It explains why the most technically brilliant person in the room is sometimes the least trusted. It also explains why the highest-leverage thing an advisor can do is act, visibly, against their own short-term interest.

Here's the argument in two sentences. Trust is engineered in the paperwork and in the small decisions. The big pitch can't manufacture it. You'll spend about eight hours coming to believe it. The proposal and the SOW count. So does the change-control conversation. So do the QC pass and the feedback you give a junior teammate. So do the fee you quote and the fee you don't ask for when the right answer is "you need less of us." Trust compounds or leaks at every one of these, and none of them is the dramatic moment a beginner imagines great consulting is made of.

By the end you'll be able to read a proposal and say what it is and isn't arguing. You'll run a scope-creep request through a real test instead of a gut feeling, and compute by hand why one advisor is trusted more than a more "impressive" rival. And you'll reason through an ethics dilemma to the action that protects the relationship. A relationship, like a filing, is only as strong as the care you put into it when nobody but you would notice a cut corner.

Learning objectives

By the end, you can:

1. Map an engagement end-to-end: problem statement → proposal → signed SOW → workplan and workstreams (each carrying a day-one hypothesis) → analysis and QC → the "so what" → the deck, and state, at each stage, what gets produced and who on the team owns it.
2. Read and draft a consulting proposal: name the six things a good proposal argues (situation, complication, objective, approach, team, timeline and fee) and explain why a proposal is an argument for being hired, not a sales brochure or a contract.
3. Read and draft a Statement of Work (SOW): state the components that make it the contract-grade reference the whole engagement is run against (deliverables, in-scope/out-of-scope, assumptions and dependencies, acceptance criteria, change control, governance) and distinguish it cleanly from the proposal that preceded it.
4. Price an engagement at concept level: build a fee from person-weeks × blended day rate by role, and choose defensibly among fixed-fee, time-and-materials, and value-based structures given who should bear the estimation risk.
5. Run the scope-creep discipline: test any mid-engagement request against the SOW's deliverables list, and route an out-of-scope ask to a quantified change order instead of silent absorption or a flat refusal.
6. Describe how an engagement team is actually run: the typical Partner/Principal → Engagement Manager → Associate/Consultant → Analyst ladder; delegate a task by matching it to a level with explicit success criteria and a check-in cadence; and enforce quality control (the two-person rule, the pyramid check, the fact-check pass) as a non-negotiable discipline rather than a courtesy.
7. Give and receive feedback that changes behavior: apply the Situation–Behavior–Impact (SBI) model in real time, in both directions on the team, and distinguish it from a saved-up annual review.
8. State, compute, and apply the trust equation (Maister, Green & Galford): Trust = (Credibility + Reliability + Intimacy) / Self-Orientation, and define each term precisely, compute a worked comparison between two advisors, and explain why lowering self-orientation is the single highest-leverage lever in the formula.
9. Reason through the ethics of advice: independence, conflict-of-interest disclosure, the "advisor's dilemma" of recommending less work when that is the honest answer, and when the professional response is to walk away from an engagement.
10. (Productivity objective: the duality below.) Use AI as a research and drafting amplifier for proposals, SOWs, delegation plans, and fee benchmarks, while keeping every commercial commitment, every scope boundary, and every judgment about who is ready for what task fully in your own hands.

The duality, stated once. Objectives 1–9 are the understanding objective the mastery gate rewards: you earn the belt by explaining the engagement's mechanics and reasoning correctly through a scope, delegation, or ethics scenario by hand. Objective 10 is the productivity payoff you keep afterward: knowing where an AI tool can draft a useful first pass on the paperwork of an engagement, and exactly where your own judgment about scope, people, and the client relationship must never be delegated to it. A tool can draft a proposal skeleton. It cannot decide what you owe a client, or whether a teammate is ready for a task, or whether the honest recommendation costs your firm money: those judgments are what this belt certifies.

Prerequisites & connections

Builds on. CN0.01 (The Consulting Mind) teaches the problem-solving cycle the engagement map here assumes: define, structure, prioritize, analyze, synthesize, recommend. It also states, once, the scope the whole consulting galaxy works within. Partner-level judgment is compounded from hundreds of live engagements, and no curriculum can manufacture it. What you get here is the teachable floor beneath that judgment, meaning the structures, the paperwork, the team habits and the relationship mechanics a great advisor stands on. Nothing else is assumed. This opens the White Belt and needs no finance background to follow, though its arithmetic (fee build-ups, weighted averages, simple ratios) asks for the same comfort with numbers that Phases 0 to 2 of the Finance galaxy assume.

Feeds forward. CN1.01 to CN1.03 take two steps named here, the hypotheses per workstream and "the so what", and teach their mechanics in full: MECE issue trees, hypothesis-driven analysis and the Minto-style answer-first synthesis. The engagement map here is the skeleton those nodes put flesh on. CN7.02 returns to team and client leadership at the delivery stage, covering client working sessions, steering committees and stakeholder management up and down. It's the direct sequel once you're inside a live engagement instead of opening one. CN7.03, the Partner Capstone, asks you to run an entire engagement solo under time, including a steering-committee-style interim update and client pushback. Everything here about the engagement's shape, the fee, the team and the relationship gets used there.

What's handed off, and not re-taught. The consulting galaxy adds to the Finance galaxy and never duplicates it, and the boundaries here are kept just as strictly. The mechanics of MECE issue trees, hypothesis-driven problem solving and case math belong to CN1.01 to CN1.02 and CN2.01. Here, "the day-one hypothesis" and "the workstream" appear as steps in the map, without instructions for building one. The full mechanics of the answer-first pyramid (governing thought, MECE support, SCQA framing) belong to CN1.03, the "So What" crown, and to M10.03 (The Communication Toolkit), which already teaches Barbara Minto's Pyramid Principle in depth. "The so what" shows up here only as the named final step of the engagement arc, with a pointer onward for the craft. Deck and storyline design belongs to the future Presentation galaxy. All you'll hear about the deck here is that the recommendation must come answer-first. The Finance galaxy's own elective links in both directions. E11.03 (The Consulting Case-Interview Lab) and its case CL-11.3 are the Cycle-2 on-ramp into this galaxy. If that's where you arrived from, this is "the whole kitchen" the taster promised. If you continue past CN0, you'll meet issue trees, case math and full cases again, taught to a deeper bar.

Core teaching content

The engagement as the unit of work

An engagement is the unit of work everything in consulting assumes: a bounded piece of advisory work, sold, scoped, staffed, delivered and closed, for one client, over a defined stretch of time. Its shape is remarkably constant across firms, industries and case types. So hold the whole arc in view before zooming into any one stage, the same way you'd look at a full income statement before studying any one line:

Problem statement → proposal → signed SOW → workplan and workstreams (each with a day-one hypothesis) → analysis, exhibits, and QC → synthesis (the "so what") → the recommendation and the deck → delivery, feedback, and, if it went well, the next engagement.

Two things about this arc are easy to miss on a first look.

First, it doesn't end at the deck. An engagement that produces a brilliant recommendation and is never asked back has only half-succeeded. You do the work well so that you become the advisor the client calls before the next problem becomes a crisis. Being right this once is only part of that. Second, the arc isn't a straight line. A workstream's early analysis routinely kills the day-one hypothesis that spawned it and sends the team back to re-hypothesize, and a scope conversation can reopen mid-engagement when new facts surface. The care you apply at each stage stays constant, even when a stage gets visited twice. Below, you'll walk the arc stage by stage: what each stage is for, what a professional produces there, and where the relationship is won or lost.

The proposal: what a consultant is actually arguing

A proposal is neither a brochure nor yet a contract. It's a specific, falsifiable argument that this firm, with this team, using this approach, in this time, for this fee, is the right choice to solve this client's problem. If you could send it to any client with the names swapped, it has already failed, however polished it looks. A good proposal argues six things, in this order, because the order is itself part of the argument:

1. Situation: the client's business context, in the client's own language and numbers, which proves you understood the business before you pitched a solution to it.
2. Complication: the specific problem, quantified wherever you can, such as falling margin, a stalled market entry or a merger integration going over budget. A generic category ("we help companies grow") doesn't count.
3. Objective: what a good outcome looks like and by when, stated as a decision the client will be able to make. A document you'll hand over is the wrong framing.
4. Approach: the workstreams you propose and the day-one hypotheses each will test. Give enough to prove you have a plan and deliberately stop short of the full analysis. A proposal that gives away the whole answer for free has priced itself at zero.
5. Team: who is staffed, and the specific experience that makes them credible for this problem. A generic list of past clients proves nothing.
6. Timeline and fee: the phases, the milestones and the commercial terms (priced below), stated plainly enough that nobody is surprised later.

Notice what's missing from that list: a guarantee of the answer. A proposal that knows the conclusion before the work starts is either lying or hasn't scoped a problem worth paying to solve. A sound proposal commits to a process (this team, this approach, this timeline) and to a day-one hypothesis to test. You'll drill the same habit in full later. Hypothesize, then let the analysis confirm or kill it. Here it first appears as a commercial promise. You're selling a reliable way of finding the answer, and the answer itself comes out of the work.

Scope creep: the small print where engagements actually die

Scope creep is a slow pile-up of small requests, each reasonable on its own, that fall outside the signed SOW and get absorbed without a change order. Weeks later the team has done 20% more work for the original fee and the schedule has slipped. Nobody can point to the moment it went wrong, because there wasn't one. It's the commonest way a well-run engagement turns into a resented one, on both sides. The client feels nickel-and-dimed if charged for what felt like a small ask, and the firm feels exploited if it wasn't charged. Refusing every request fails. So does saying yes to everything to "keep the relationship warm". What works is a test, run every time against the SOW's own deliverables list:

1. Is this explicitly in-scope? If yes, it was already priced in. Do it. No conversation needed.
2. Is this explicitly out-of-scope, or simply not mentioned? Silence is not an inclusion. An out-of-scope or unaddressed request is a candidate for a change order. Quantify the extra person-weeks and fee, using the same build-up as the SOW itself, and put the choice plainly to the client. They can add the scope and the fee together, trade it for something already in scope, or decline it and move on.
3. Who has the conversation? The Engagement Manager, and never the analyst fielding the request on the ground. It takes someone with the standing to say "yes, and here is what changes" without it reading as either a favor or a confrontation.

You'll meet scope creep again when the trust equation arrives, and that's no accident. Absorbing scope silently feels generous. What it really teaches the client is that the SOW isn't a real document, and that wears away reliability (doing what you said, on the terms you said it), one of the things trust is built from. A transparent change order builds more trust, even one the client sometimes declines, because it proves the paper trail means something.

The workplan and the weekly rhythm

In practice the SOW's timeline becomes a workplan. The engagement is broken into workstreams, each with its own day-one hypothesis (you'll learn to build those later) and its own exhibits and deliverables, sequenced against milestones. Most engagements then settle into a weekly rhythm that repeats until delivery. A Monday planning touchpoint asks what each workstream needs to answer this week and what data or access is still outstanding. A mid-week check asks whether any workstream is stuck, and whether a hypothesis needs killing and replacing before more time is sunk into it. A Friday client touchpoint is a short, informal update, much lighter than a presentation, so the client is never surprised by what the final deck says.

That last habit deserves the most attention. If you save every finding for the final meeting, you're running a real risk of a bad surprise in the room. Later you'll learn the full practice of "pre-wiring" a steering committee, so that nothing in the final meeting is heard there for the first time. For now, keep the simpler version in mind: frequent, informal, candid updates are cheaper than one large risky reveal.

A related habit is the ghost deck, and you'll meet its mechanics properly later. It's a skeleton of the final presentation's structure and exhibit titles, built early and refined weekly, even before the numbers inside it are final. It forces the team to know at every stage what argument it's building toward, so nobody piles up analysis and hopes a narrative appears at the end. Building the ghost deck is a structuring skill (CN1). Running the weekly rhythm that keeps it true to the evidence is an engagement-management skill, and that's the one you're learning here.

Running the team: roles, delegation, and the discipline of QC

Most engagement teams, across firms, settle into a version of the same ladder:

Delegation works when you match a task to the level that can execute it with the appropriate amount of oversight. Zero oversight is abandonment. It produces silent errors and missed deadlines. Constant oversight is hovering, which wastes the senior person's time and stunts the junior one's growth. The formula has three parts. Match the task to a level. Give an explicit, one-line success criterion: "done" means the weighted-average margin reconciles to the underlying revenue mix, and a number merely appearing doesn't count. Then set a check-in cadence, such as a daily five-minute stand-up plus a mid-week deeper review. Hand a task over with none of the three and you haven't delegated it. You're hoping.

Quality control (QC) catches errors before a client ever sees them, and it applies however senior or confident the person who made the error is. In fact the most expensive mistakes are disproportionately made by the most confident person in the room, because confidence suppresses the instinct to double-check. Three QC habits are non-negotiable:

• The two-person rule. Any number or claim that will reach the client gets a second reviewer before it ships. There's no exception for seniority, and none for "I already checked it myself twice." A different pair of eyes catches a different class of error from the same person rereading their own work.
• The pyramid check. This confirms that the top-line message (the "so what") is supported by the exhibits assembled beneath it. Checking each fact in isolation isn't enough. A slide can contain twelve true numbers and still support a false conclusion if they were put together carelessly, so the pyramid check reviews the assembly as well as the arithmetic.
• The fact-check pass. Trace every cited figure back to a named source before it ships. The AI-Augmented Analyst branch teaches the same Trace and Match routine for checking an AI's output, and it applies with equal force to a human teammate's slide. A wrong number from a colleague is as dangerous to the client relationship as a hallucinated one from a model, and the review that catches it is identical.

Worked Example 3 shows this discipline catching a real, reconcilable error before it reached a client.

{
  "skill": "Drafting a delegation plan and a QC checklist for a new workstream",
  "use": "Use AI to turn a workstream's objective into a first-pass task breakdown — who owns what, at what level, with what success criterion and check-in cadence — and a QC checklist naming which numbers or claims need a second reviewer, as a scaffold the Engagement Manager then edits and owns.",
  "tools": ["Chat assistants — Claude, ChatGPT", "A workplan or project-tracking tool's built-in AI drafting feature"],
  "prompt": "This workstream's objective is: <OBJECTIVE>. My team, by role only (no real names): <ROLES>. Draft a task breakdown assigning pieces of this workstream to the right level, with a one-line success criterion and a check-in cadence for each. Then draft a QC checklist naming every number or claim in this workstream that should get a second reviewer before it reaches the client.",
  "verify": "The draft cannot know your actual team's real skill level, current workload, or this specific client's sensitivities — re-match every task to the real people on your team (not the generic levels the model assumed), and add any QC item specific to this engagement that a generic checklist would miss.",
  "diy": "You must already know the delegation formula (task matched to level, explicit success criteria, a real check-in cadence) and the two-person QC rule (this section) to judge whether a draft under- or over-delegates. AI proposes a scaffold; you dispose of whatever does not fit your actual team.",
  "market": "US"
}

Feedback that actually changes behavior

QC catches an error once. Feedback is what stops it coming back, and most beginners get it wrong in one of two directions. Some feedback is so vague nobody can act on it ("good job, just tighten it up"). Some gets saved for a single end-of-engagement review, by which point the behavior has repeated for weeks and the specific moment is long forgotten. A far more effective structure, taught widely as SBI (Situation, Behavior, Impact), forces the specificity vague feedback lacks:

• Situation: name the specific moment and context ("in Wednesday's QC review of the market-sizing slide…").
• Behavior: describe the observable action ("…you used a simple average of the three product lines' margins…"). Leave character judgments such as "you were careless" out of it.
• Impact: state the effect it had, concretely ("…which would have overstated the blended margin by nearly two points on a slide the client would have used to set a price point").

Timing is what makes SBI change behavior. Given in real time and close to the moment, it's specific and low-stakes enough to land as coaching. Saved for a formal review, the same content reads as an accusation and arrives too late to help the work it describes. By then six weeks of small moments have blurred together, so it's rarely specific enough to count as SBI at all.

Feedback isn't a privilege of seniority, either. Say you're the junior on the team and a client touchpoint ran long without reaching a decision. Telling the Engagement Manager straight away, in specific terms, offers upward the same check that QC offers downward. A team that only gives feedback down its hierarchy is missing half the signal available to it.

The ethics of advice: independence, conflicts, and the courage to say less

Self-orientation is more than a relationship-building tactic. It's the mechanical seed of the whole professional ethic of advice. Take it seriously, instead of treating it as a nice sentiment, and three specific practices follow:

Independence. A recommendation must be argued from the analysis and never bent toward whatever outcome benefits the firm. The commonest temptation is to recommend a larger or longer engagement than the facts justify, because a follow-on phase is easier revenue than winning a new client from scratch. Willpower alone won't hold that line, so make it structural. Separate the person who scopes and prices the next phase from the incentive to inflate it, and hold every follow-on recommendation to the same evidentiary bar as the first one.

Conflict-of-interest disclosure. Sometimes a firm's relationship with one client creates a real or perceived conflict with another. The commonest case is being asked to advise a client on a question where the firm already advises that client's direct competitor. The rule is to disclose, and never to settle it silently on your own. Disclosure is typically resolved in one of two ways. The first is an ethical wall: separate, non-overlapping teams with no shared access to either client's confidential information, if both clients knowingly consent to proceed on that basis. The second is declining one of the two engagements, if a wall can't credibly protect confidentiality or either client is unwilling to proceed. Once a real conflict exists, neither resolution is optional. Picking the wrong resolution is rarely what goes wrong. Skipping the disclosure that would have surfaced the choice is.

The advisor's dilemma. The hardest and highest-leverage test of independence comes when the analysis says the client needs less of you. A proposed follow-on phase might cost more than it would save. A program might need to stop. A smaller, cheaper engagement might serve the client better than the one already being pitched. Saying so costs the firm money the moment it's said. By the trust equation's own arithmetic, it's also one of the highest-leverage trust-building acts available, because self-orientation is a denominator and this is the clearest possible proof that it's low. Worked Example 4 walks through this decision with real, reconciled numbers.

When to walk away. Everything above assumes the conflict or pressure can be managed within the engagement. Occasionally it can't. A client may insist on shading a finding, or on misrepresenting data to a regulator or board, or may push the team past what disclosure and walls can resolve. The professional response is rare and always a last resort. It is to say so plainly and, if the situation isn't corrected, to end the engagement. A firm that can't reach that decision, even in principle, has no real independence. It has a policy that holds only until it becomes inconvenient.

From analysis to the deck: the hand-off you do not re-teach here

Formally, the engagement's arc ends at the recommendation and the deck. That step is named here and its mechanics are left for later, because doing them properly takes a full stretch of craft on its own. What you owe the client at this final stage is simple to state and hard to do. Answer first. State the recommendation before the supporting analysis. Structure the support so it's exhaustive and non-overlapping (MECE). And never let a client sit through twenty minutes of build-up before learning what you think they should do. The how (governing thought, MECE grouping, the SCQA opening, the pyramid itself) belongs to the synthesis crown of the consulting branch and to the Communication Toolkit in the finance program. The design of the deck that carries it belongs to the future Presentation galaxy. Here you only need to place "the so what" correctly on the map and insist that it comes first. Leaving the craft for later is a deliberate and well-marked hand-off. Nobody forgot it.

Where this leaves you

Now hold the whole arc together. A proposal argues for the work in six specific moves. A signed SOW turns that argument into the reference the whole engagement is managed against, especially against a client's later, reasonable-sounding request that falls outside it. A fee is built from people and time, and confidence plays no part in it. Its commercial structure puts the estimation risk where it belongs. A team is delegated to and quality-controlled with the same rigor whether the claim comes from a first-week analyst or from the partner who sold the work. And feedback given in the moment and in both directions makes the team better instead of merely grading it.

Under every one of those mechanics is one variable you can engineer on purpose: self-orientation. It's the one term in the trust equation that divides, and the one you control completely in every interaction. That holds however talented or well-resourced the rest of the team happens to be. Trust is engineered in the paperwork and the small decisions, and the big pitch can't manufacture it. Every mechanic here, from the SOW's change-control clause to the courage to recommend less work, is that sentence put into practice.

Common mistakes & how experts think differently

1. "The proposal is a sales document, so oversell it." A proposal that promises more than the SOW and the team can deliver isn't persuasive. It's a credibility problem with a delay built in. The moment reality falls short of the pitch, the credibility term of the trust equation takes all the damage at once. Experts write a proposal as good as what will be delivered and no better. They let the six-part argument (situation, complication, objective, approach, team, timeline and fee) do the persuading.
2. "Scope creep is just being helpful: say yes to the client's small ask." Every "yes" outside the SOW becomes either a transparent change order or a silent tax on the team's time and the engagement's quality. There's no third option where it's free. Experts run the in/out-of-scope test every time and treat "yes, and here is what changes" as the generous move. "Sure, no charge" teaches the client the SOW was never a real document.
3. "Delegate by handing over the task and disappearing" (or its mirror image, hovering over every step). Both break the same formula. Experts match the task to a level that can execute it, state an explicit one-line success criterion up front, and set a real check-in cadence. For them, delegation is a design decision made before the work starts, and the amount of attention it gets is settled then.
4. "Feedback is an annual-review event." By the time a formal review happens, the specific moment is gone and the behavior may have repeated for weeks, so the feedback arrives too diffuse to act on. Experts give SBI feedback close to the moment. They keep it about behavior and never about character, and they expect it to flow up the team as well as down.
5. "Trust-equation intimacy means being friendly with the client." This is the commonest misreading of the formula. Intimacy is the emotional safety to share something risky (a business in real trouble, a mistake, an unresolved fear) without fear of exposure or judgment. A client can attend every dinner you host and never once feel safe enough to tell you the number is worse than the board has been told. That gap is what the term measures.
6. "The QC pass is optional once the team is senior enough to trust." Seniority doesn't retire the two-person rule. If anything it raises the risk, because the most confident person in the room is often the least likely to recheck their own work. Experts apply the same QC routine (two-person rule, pyramid check, fact-check pass) whoever authored the number. To them, "I'm sure, I checked it myself" is a reason to check again.
7. "A good advisor always has the answer in the room and never says less-of-us." The instinct to always propose more work and never admit a gap is the self-orientation the trust equation punishes. A confident wrong answer, given in place of a candid "I don't know yet, and here's when I will", carries the same failure signature the AI-Augmented Analyst branch teaches for a model's plausible but wrong output. Fluent confidence is no evidence of correctness, whether it comes from a person or a machine. Experts treat "you need less of us" as the highest-trust sentence available, because it costs the speaker money to say.
8. "Ethics is a form you sign once, at onboarding." Independence and conflict management come back for review every time the scope, the client contact, the fee structure or the firm's other client relationships change. Experts re-run the conflict-of-interest question at every material change in the engagement, and treat "we already cleared this" as the start of the question.

All eight share a thread. The expert never treats "being trusted" as a personality trait or a mood to project in the room. Trust is the visible output of a set of unglamorous habits: a precise SOW, a candid fee build, a real QC pass, timely feedback, and self-orientation kept deliberately low even when that costs money. Keep them up consistently for long enough and the client stops needing to double-check you. In working terms, that's what "trusted advisor" means, and it's what all the paperwork above was teaching.

Worked examples

Worked example 1: Pricing a proposal and pricing a scope-creep request (India, ₹)

A boutique strategy firm is scoping a 10-week national profitability diagnostic for Suvidha Retail, a synthetic Indian retail chain. All figures here are illustrative and internally consistent, and none of them is a real firm's real rates. The proposed team is an Engagement Manager at 0.3 FTE, two Consultants at 1.0 FTE each and one Analyst at 1.0 FTE, over the full 10 weeks, 5 working days per week. Illustrative blended day rates are EM ₹1,25,000, Consultant ₹60,000 and Analyst ₹35,000. Three weeks in, the client asks for a 3-city market-expansion sizing that was never in the original deliverables list. Should the firm quietly do it, refuse it, or run it through the change-control clause?

Solution. Step 1: build the fee role by role. Fee (by role) = FTE × weeks × day rate × days/week.

• EM: 0.3 × 10 = 3.0 person-weeks. Weekly rate = ₹1,25,000 × 5 = ₹6,25,000. Fee = 3.0 × ₹6,25,000 = ₹18,75,000.
• Consultants (2, each 1.0 FTE): 1.0 × 10 × 2 = 20.0 person-weeks in total. Weekly rate = ₹60,000 × 5 = ₹3,00,000. Fee = 20.0 × ₹3,00,000 = ₹60,00,000.
• Analyst: 1.0 × 10 = 10.0 person-weeks. Weekly rate = ₹35,000 × 5 = ₹1,75,000. Fee = 10.0 × ₹1,75,000 = ₹17,50,000.

Step 2: sum the build-up. Total fee = ₹18,75,000 + ₹60,00,000 + ₹17,50,000 = ₹96,25,000, which is ₹96.25 lakh, just under ₹1 crore. That's the number the proposal's fee line gets defended against, role by role, if the client ever asks how it was built.

Step 3: run the scope-creep test on the mid-engagement ask. Is the 3-city expansion sizing in the original deliverables list? No. The SOW's deliverables were a national profitability diagnostic across two workstreams, and market-entry sizing for new cities was never named. However reasonable it sounds on the call, it fails the in-scope test. So it's a change-order candidate, which rules out both a free add and a flat refusal.

Step 4: price the change order the same way. Suppose it needs one extra Consultant at 0.5 FTE for the 4 remaining weeks. Person-weeks = 0.5 × 4 = 2.0, at the same Consultant weekly rate of ₹3,00,000, so the change-order fee = 2.0 × ₹3,00,000 = ₹6,00,000 (₹6 lakh). That's about 6.2% of the original fee (₹6,00,000 ÷ ₹96,25,000 ≈ 6.23%).

Read it. Think about what quietly absorbing this would have cost. ₹6 lakh of unpriced work sounds small in the room. On paper it's a measurable margin leak. It's also the gap between "feels like a favor" and "is actually 6% of the whole engagement's fee". Raise it as a transparent change order and let the client decide whether to add the scope, trade something out or decline. That builds reliability. Doing it silently for free teaches the client that the SOW's deliverables list was decorative.

Worked example 2: The trust equation, computed by hand (US, $)

Meridian Foods Co., a synthetic US mid-market client, is choosing between two advisors pitching the same engagement. Rate each, illustratively, on a scale of 1 to 10. Advisor A: Credibility 9, Reliability 7, Intimacy 4, Self-orientation 6. Advisor B: Credibility 7, Reliability 8, Intimacy 7, Self-orientation 2. On paper, Advisor A is more "impressive", with the higher credibility. Which one does the trust equation say the client should trust more, and by how much?

Solution. Step 1: compute Advisor A's trust score. Trust = (C + R + I) ÷ S = (9 + 7 + 4) ÷ 6 = 20 ÷ 6 = 3.33.

Step 2: compute Advisor B's trust score. Trust = (7 + 8 + 7) ÷ 2 = 22 ÷ 2 = 11.0.

Step 3: read the gap. Advisor B has the lower raw credibility score, yet a trust score more than three times Advisor A's. The reason is Advisor B's self-orientation, the denominator, which is a third the size. A client choosing on "who sounds smartest in the room" would pick Advisor A and, on this model, get the less trustworthy advisor.

Step 4: show why lowering the denominator beats raising the numerator. Suppose Advisor A worked on the numerator and raised credibility from 9 to 12. That's a large jump, and one credibility alone rarely earns quickly. New trust = (12 + 7 + 4) ÷ 6 = 23 ÷ 6 = 3.83, barely moved. Now suppose Advisor A lowered self-orientation from 6 to 3 instead, by visibly turning down unnecessary billable work, admitting an early mistake and giving the client bad news early. New trust = (9 + 7 + 4) ÷ 3 = 20 ÷ 3 = 6.67, nearly double. One variable changed, and Advisor A didn't have to become any more technically impressive.

Read it. The arithmetic carries the lesson. Self-orientation divides the sum instead of adding to it, so it works as a multiplier on the entire relationship and is more than one more ingredient alongside the other three. That turns "act against your own short-term interest, visibly" from a platitude into the highest-leverage move the formula offers. It costs nothing technical to do. It only takes nerve.

Worked example 3: A QC catch: weighted average versus simple average (India, ₹)

An Analyst on the Ananta Consumer Products engagement (a synthetic FMCG conglomerate) is building a market-sizing slide and needs the company's blended gross margin across three product lines. Line 1 has revenue of ₹40 cr at a gross margin of 45%, Line 2 has ₹25 cr at 30%, and Line 3 has ₹15 cr at 60%. The Analyst's draft slide states a blended gross margin of 45%, computed as the simple average of the three margins. Running the two-person QC rule before the slide ships, the Engagement Manager stops to recompute.

Solution. Step 1: name the correct method. A blended margin across lines of different sizes must be revenue-weighted. A simple average of the three percentages won't do, because a line that's half the business should count roughly twice as much toward the blend as a line that's a quarter of it.

Step 2: compute the correct, weighted figure. Total revenue = ₹40 cr + ₹25 cr + ₹15 cr = ₹80 cr. Weighted gross margin = (40 × 0.45 + 25 × 0.30 + 15 × 0.60) ÷ 80 = (18 + 7.5 + 9) ÷ 80 = 34.5 ÷ 80 = 43.125% (43.1%).

Step 3: quantify the analyst's error. The simple average of the three margins is (45% + 30% + 60%) ÷ 3 = 45.0%, an overstatement of 1.875 percentage points (45.0 − 43.125) against the correctly weighted figure.

Step 4: see why the direction isn't fixed. Here the simple average happened to overstate the truth. The highest-margin line (60%) is also the smallest by revenue, so weighting pulls the blend down. That's a property of this data, and no general rule. A differently weighted mix can just as easily make the simple average understate the truth, and Form A item A11 shows that reversal. So don't walk away thinking "simple averages are always too high". An unweighted average of ratios across unequal bases is the wrong tool, full stop. Always re-derive the figure from the underlying totals.

Read it. On its own, 1.9 points sounds small. On a slide feeding a client pricing recommendation, it's the kind of quiet, plausible-looking error the two-person rule exists to catch before it reaches the room. It cost the EM under a minute to recompute from the totals. Compare that with the cost of the client catching it later.

Worked example 4: The advisor's dilemma (US, $)

Northgate Retail Group, a synthetic US client, hired a firm for a Phase 1 cost-transformation engagement. The fee was $650,000, and the team's own tracked results show $2,100,000 in annualized savings delivered. The client is delighted, and the firm's account team has already drafted a Phase 2 proposal at a fee of $850,000. But the team's own workplan analysis for Phase 2, done with the same rigor as Phase 1, projects only $300,000 of net new annual savings, because Phase 1 used up the easiest cost levers. Should the team present the Phase 2 proposal as drafted?

Solution. Step 1: hold Phase 1 to its own standard. Phase 1's return was $2,100,000 ÷ $650,000 = 3.23×. By any reasonable test that's a value-creating engagement, and it's the reason the client trusts the firm enough to consider a Phase 2 at all.

Step 2: apply the identical standard to Phase 2. Phase 2's projected return is $300,000 ÷ $850,000 = 0.35×. The client would be paying $850,000 for $300,000 of value. Judged by the yardstick that justified Phase 1, this isn't even a marginal case. It's value-destructive.

Step 3: name the two options and their cost. Presenting the Phase 2 proposal as drafted earns the firm $850,000 in the short term. Then the client's own finance team runs the same arithmetic, which a client this analytically engaged eventually will. At that moment the credibility and reliability built in Phase 1 are destroyed all at once. The other option is to present the true finding: a large Phase 2 isn't justified, and at most a small, targeted sustainment engagement is offered instead, if one is warranted. That costs the firm the $850,000 fee today.

Step 4: apply the trust equation to the choice. This is Worked Example 2's arithmetic in its highest-stakes form. Telling the client the truth is a direct, visible reduction in self-orientation, the trust equation's denominator. It's the most expensive sentence in the whole engagement to say out loud, and the most valuable one for a long-run relationship. The client who's told "you don't need a big Phase 2" is the client who calls this firm first, unprompted, the next time a real problem appears.

Read it. Once both phases were held to the same standard, this wasn't a close call. The arithmetic is unambiguous. The hard part is whether the team will run the same test on its own follow-on proposal that it would run on any other investment the client was considering, and whether it has the courage to act on the answer when it costs the firm money.

Worked example 5: Reading a proposal's opening for what it actually argues (India, ₹)

Two drafts of the opening paragraph of a proposal for DeccanJet, a synthetic regional Indian airline, land on an Engagement Manager's desk. Draft 1: "We are a leading advisory firm with deep aviation experience and a track record of transformative results for our clients across sectors." Draft 2: "DeccanJet is burning approximately ₹4 crore a month against a cash reserve of ₹28 crore (a runway of 7 months at the current rate), driven primarily by underutilized regional routes flown at off-peak frequency. The question this proposal answers is which of your 14 regional routes to cut, shrink, or reprice within 60 days, and by what approach we would reach that answer." Which draft is doing the job of a proposal's opening, and why?

Solution. Step 1: check the runway arithmetic in Draft 2, because a proposal's numbers must reconcile before anything else is judged. Runway = cash reserve ÷ monthly burn = ₹28 cr ÷ ₹4 cr/month = 7.0 months. The figure checks out as stated.

Step 2: name what each draft argues. Draft 1 states a category ("aviation experience," "transformative results") that could be sent, unedited, to any airline client anywhere. It argues nothing specific to DeccanJet and can't be falsified or challenged, because it commits to nothing checkable. Draft 2 states a situation: the burn and the reserve, both numbers a client can immediately confirm or dispute. Its complication carries an urgency a vague draft can't manufacture: 7 months, where a vague draft would say "a challenging environment". And its objective is a decision the client will make (which routes, within 60 days), where a weaker draft would promise a document.

Step 3: connect it to the six-part structure. Draft 2 does in miniature what the proposal section above described. Situation and complication come first, specific and quantified. They set up an objective the client will recognize as the question keeping them up at night. Not a word goes on the firm's own credentials before that.

Read it. The tell is specificity that could be checked and could be wrong. Tone and polish don't decide it, and Draft 1 might well be the more elegantly written. A proposal opening that can't be disputed, because it says nothing falsifiable, hasn't yet proven the firm understood the client's problem. A client reading Draft 1 has no way to tell this proposal apart from the one the losing firm sent.

Worked example 6: A capacity gap surfaces before it becomes a crisis (US, $)

An 8-week operating-model engagement for a synthetic US industrial client, Bridgeforge Industrial, has three workstreams. Per the workplan, their combined analysis needs 50 + 45 + 35 = 130 person-days. The team staffed against the SOW is two Consultants, full-time, for the full 8 weeks. Is the team big enough, and if not, what are the Engagement Manager's real options?

Solution. Step 1: compute the person-days available. 2 Consultants × 8 weeks × 5 days/week = 80 person-days.

Step 2: compute the gap. 130 person-days needed − 80 person-days available = 50 person-days short. The team is staffed for barely 60% of the analysis its own workplan calls for. A gap that size won't be absorbed by working a little later most nights.

Step 3: name the options. At this size of gap, "the team will just work harder" isn't one of them. (a) Add capacity: staff an extra Analyst or Consultant for some weeks. That's itself a scope-and-fee conversation if it wasn't already priced into the SOW's assumptions. (b) Extend the timeline: hold the team size and push the 8 weeks out. That's a client conversation about the delivery date, and it must never become a silent slip. (c) De-scope: cut back one workstream to narrower analysis and fewer exhibits, so it fits the 80 person-days available. Raise that with the client as explicitly as any other scope change, and don't let the team decide it quietly on its own.

Step 4: connect it to what you already know. Whichever option you choose, resolve it the way you'd resolve a scope-creep request: quantify it and put it to the client as an explicit choice. Absorbing it as unpaid overtime wears down both the work's quality and the team's goodwill.

Read it. Do this arithmetic in week one. By week six the team is already exhausted and behind. A 50-person-day gap is a calm planning conversation before the engagement starts, and a credibility-damaging crisis if it's only discovered once deadlines start slipping.

Practice set

Work each problem fully before reading its solution. All company names and figures are illustrative and internally consistent unless stated otherwise.

P1 (guided). The engagement map. List, in order, the stages of an engagement from problem statement to the deck, and name who typically owns the SOW and who typically owns a single workstream's day-one hypothesis.

Solution. Problem statement → proposal → signed SOW → workplan and workstreams (each with a day-one hypothesis) → analysis, exhibits, and QC → synthesis (the "so what") → recommendation and the deck. The SOW is owned by the Engagement Manager, who drafts and negotiates it and then manages the engagement against it, with sign-off typically from the Partner or Principal on the firm's side. A single workstream's day-one hypothesis belongs to the Associate or Consultant who leads that workstream and forms and tests it with their Analyst.

P2 (guided). Fee build-up. A 6-week US engagement staffs an Engagement Manager at 0.25 FTE ($2,400/day), a Consultant at 1.0 FTE ($1,400/day), and an Analyst at 1.0 FTE ($900/day), 5 days a week. Compute the total fee.

Solution. EM: 0.25 × 6 = 1.5 person-weeks, at a weekly rate of $2,400 × 5 = $12,000, so the fee = 1.5 × $12,000 = $18,000. Consultant: 1.0 × 6 = 6 person-weeks, at $1,400 × 5 = $7,000 a week, so the fee = 6 × $7,000 = $42,000. Analyst: 1.0 × 6 = 6 person-weeks, at $900 × 5 = $4,500 a week, so the fee = 6 × $4,500 = $27,000. Total = $18,000 + $42,000 + $27,000 = $87,000.

P3 (guided). Trust equation. Compute the trust score for an advisor rated Credibility 8, Reliability 6, Intimacy 5, Self-orientation 4.

Solution. Trust = (8 + 6 + 5) ÷ 4 = 19 ÷ 4 = 4.75.

P4. Scope-creep classification. A signed SOW's deliverables list reads: "(1) a diagnostic of current-state margin by product line; (2) a prioritized list of cost-reduction levers with sizing." Mid-engagement, the client asks the team to also benchmark the client's margins against three named competitors. Classify the request and state the disciplined next step.

Solution. Competitor benchmarking isn't named in either deliverable. Nor is it a natural part of a "current-state margin diagnostic", which is about the client's own numbers. It fails the in-scope test, so it's a change-order candidate. Next, the Engagement Manager quantifies the extra person-weeks, presents the client with the added fee or a trade against existing scope, and lets the client decide. Adding it for free is wrong, and so is refusing it outright without a conversation.

P5. Weighted average versus simple average. A retailer's three products sell: Product A: 10,000 units at ₹250; Product B: 4,000 units at ₹600; Product C: 6,000 units at ₹150. An analyst reports the "average selling price" as the simple average of the three prices. Compute the correct, revenue-weighted average selling price and the size of the analyst's error.

Solution. Total revenue = (10,000 × 250) + (4,000 × 600) + (6,000 × 150) = 25,00,000 + 24,00,000 + 9,00,000 = ₹58,00,000. Total units = 10,000 + 4,000 + 6,000 = 20,000. Weighted ASP = ₹58,00,000 ÷ 20,000 = ₹290. The simple average of the three prices = (250 + 600 + 150) ÷ 3 = ₹333.33, an overstatement of about ₹43.33, or roughly 14.9% above the correct figure. The error runs high here because Product B, the highest-priced line, is also the smallest by volume, so an unweighted average leans on it too heavily.

P6. SBI feedback. An Analyst submitted a market-sizing exhibit on Thursday morning, one day after the agreed Wednesday-evening deadline, with no advance warning it would be late. Write the feedback as Situation, Behavior, Impact.

Solution. Situation: "For Wednesday's workstream deliverable, the market-sizing exhibit." Behavior: "It arrived Thursday morning, a day after the agreed deadline, with no message beforehand that it would be late." Impact: "That meant the Wednesday mid-week QC review had nothing to check, and the whole workstream's timeline slipped by a day it may not get back before the client touchpoint." A forward-looking ask completes the conversation, though it isn't itself part of the SBI structure: "next time, flag a likely delay as soon as you see it coming, even before the deadline."

P7. The advisor's dilemma, by the numbers. A Phase 1 Indian engagement delivered ₹1,80,00,000 in annualized savings against a ₹40,00,000 fee. A proposed Phase 2 is priced at ₹65,00,000 and is projected, by the team's own honest analysis, to deliver ₹20,00,000 in net new annual savings. Compute both returns and state the ethical action.

Solution. Phase 1 return = ₹1,80,00,000 ÷ ₹40,00,000 = 4.5×. Phase 2 projected return = ₹20,00,000 ÷ ₹65,00,000 ≈ 0.31×, so the client would pay more than three times what the engagement is projected to return. The ethical action is to present this finding plainly in place of the drafted Phase 2 proposal, and to offer a smaller scope of work only if a justified one exists. That protects the relationship's self-orientation term, even though it costs the firm the larger fee.

P8. Delegation. A workstream needs a first-cut market-sizing model built. The team has a first-week Analyst, a two-year Consultant, and the Engagement Manager. Who should build the first cut, and what does correct delegation require beyond just picking the person?

Solution. The Consultant is the best match, experienced enough to build a defensible first cut with light oversight. A first-week Analyst would need heavy hand-holding on a task this open-ended. The task doesn't need the Engagement Manager's level, so giving it to them wastes their time. Correct delegation also needs an explicit success criterion, e.g. "a top-down and a bottom-up estimate that land within 2× of each other, with assumptions listed". It needs a check-in cadence too, e.g. a look at the structure after day one, before too much time is sunk into a flawed approach. Hand over the task without either and you haven't delegated it yet.

P9. Capacity gap. A workplan calls for four workstreams needing 40, 35, 30, and 20 person-days respectively. The staffed team is three Consultants for 7 weeks, 5 days a week. Is the team big enough, and by how much?

Solution. Total needed = 40 + 35 + 30 + 20 = 125 person-days. Available = 3 × 7 × 5 = 105 person-days. The team is short by 20 person-days. Raise the gap with the client as an explicit choice (add capacity, extend the timeline or trim a workstream) before it becomes a missed deadline.

P10. Proposal quality. Classify this proposal excerpt and explain why: "Our firm brings unmatched insight and world-class expertise to every engagement, delivering results our clients can count on." What is missing that Worked Example 5's Draft 2 had?

Solution. This is a generic credentials claim, with no argument specific to any client's situation. It names no complication, no number and no objective, and could be sent unedited to any prospective client in any industry. It lacks what made Draft 2 work: a quantified and checkable situation and complication, with a real number the client would recognize as their own problem, and an objective framed as the decision the engagement will help the client make. An adjective about the firm does none of that.

P11. Trust equation: what changed. An advisor is rated Credibility 6, Reliability 9, Intimacy 8, Self-orientation 4. Compute the trust score. Then compute the new score if self-orientation improves to 2, and state which lever moved the number more per unit of effort typically required to change it.

Solution. Current trust = (6 + 9 + 8) ÷ 4 = 23 ÷ 4 = 5.75. With self-orientation improved to 2: (6 + 9 + 8) ÷ 2 = 23 ÷ 2 = 11.5, so the score doubles. Lowering self-orientation is the higher-leverage lever per unit of effort. Raising credibility, reliability or intimacy by a few points typically takes months of consistently proven competence or care. Lower self-orientation can be shown in a single visible act, such as turning down unjustified work or admitting an error early.

P12. Spot the missing SOW component. A draft SOW lists deliverables, a timeline, and a fee schedule, but nothing else. Name two components it is missing and the specific risk each absence creates.

Solution. The first missing component is in-scope and out-of-scope language. Without it, any client request that isn't explicitly excluded can be argued as implicitly included, and the scope-creep test has nothing to stand on. The second is a change-control clause. Without it there's no agreed process for pricing and approving a scope change, so every mid-engagement ask becomes an improvised, case-by-case negotiation when it could have been a repeatable, low-drama process.

P13. Fixed-fee versus time-and-materials. An engagement's scope is genuinely hard to estimate up front: the team's honest range is 250 to 550 hours at an agreed rate of $150/hour ($37,500 to $82,500), with a most-likely estimate of 400 hours ($60,000). A firm proposes a flat fixed fee of $70,000. Whose risk does each structure put where, and which would you recommend given how wide this range is?

Solution. A fixed fee of $70,000 puts the estimation risk on the firm. If the work runs to 550 hours, the firm has priced its own time at a discount. If it runs to 250, the client has overpaid relative to actual effort. Time-and-materials puts the risk on the client, who pays only for hours used, ideally bounded by an agreed not-to-exceed ceiling near the top of the range, e.g. $82,500. The range here is wide, 250 to 550 hours, nearly 2.2× from top to bottom. So T&M with a not-to-exceed ceiling is the more defensible structure. A fixed fee set this early, on scope this uncertain, forces one side to guess badly. If the fee was set anywhere near the low end to win the work, it's usually the firm that ends up eating the difference.

P14. The two-person rule under pressure. A senior Consultant, under a tight deadline the night before a client meeting, says there is no time for a second reviewer on a number they are confident is correct. What is the disciplined response, and why does seniority not change the answer?

Solution. The two-person rule still applies. Find a second reviewer, even if it means a shorter final review or a slightly later night. The rule exists for the moments it's most tempting to skip. Seniority doesn't change the answer, because confidence is no evidence of correctness, the same lesson the AI-Augmented Analyst branch teaches about a model's fluent output. The most expensive errors are disproportionately made by the most confident person in the room, because their confidence suppressed their own recheck.

P15. Conflict of interest. A firm is approached by a new prospective client to advise on entering a market segment where the firm already advises that prospect's direct competitor on the identical question. Name the required first step and the two ways this is typically resolved.

Solution. The required first step is disclosure to both clients. The firm may not decide silently, on its own, that the conflict is manageable. It's typically resolved in one of two ways. (1) An ethical wall, meaning separate teams with no shared access to either client's confidential information, if both clients knowingly consent to proceed on that basis. (2) Declining one of the two engagements, if a wall can't credibly protect confidentiality or either client won't consent.

P16. Trust-equation diagnosis from a client complaint. A client says, "I respect your team's expertise, but I don't feel like you really understand our business, and I'm not sure I'd tell you if something were actually going wrong." Which trust-equation variable is deficient, and, given current ratings of Credibility 8, Reliability 8, Intimacy 2, Self-orientation 3, compute the current trust score and the score if intimacy improved to 7.

Solution. The complaint describes low intimacy. The client doesn't feel safe sharing something risky. That holds however competent or reliable the team is rated. Current trust = (8 + 8 + 2) ÷ 3 = 18 ÷ 3 = 6.0. With intimacy improved to 7: (8 + 8 + 7) ÷ 3 = 23 ÷ 3 ≈ 7.67. That's a meaningful jump with no change at all to technical competence. The fix for this complaint is time spent understanding the client's business and vulnerabilities. Another impressive exhibit won't help.

Applied mini-project

Run one engagement's opening, on paper, end to end.

You're the Engagement Manager for a synthetic 8-week engagement of your own invention. Pick an India or US client and industry, and keep every figure synthetic and internally consistent. Produce, in order:

1. A one-page proposal using the six-part structure: situation, complication, objective, approach with 3 workstreams and a one-line day-one hypothesis each, team, and timeline and fee. The situation and complication must include at least one real, checkable number, such as a burn rate, a margin or a growth rate, and your later fee build-up has to be consistent with it in scale.
2. A SOW skeleton for the same engagement, with deliverables, in-scope and out-of-scope bullets (at least 2 of each), assumptions and dependencies, a change-control clause, and governance covering sign-off and meeting cadence.
3. A fee build-up by role (FTE × weeks × day rate × days/week for each of at least 3 roles), reconciled to a total. Add a one-line justification for your commercial structure, whether fixed-fee, T&M or value-based, given how well defined your scope is.
4. One scope-creep scenario of your own, run through the in/out-of-scope test against your own SOW, with a quantified change-order estimate if it fails.
5. A trust-equation self-assessment. Rate a synthetic advisor (yourself, in character) on Credibility, Reliability, Intimacy and Self-orientation for this engagement at the 3-week mark, and compute the trust score. Then write two sentences on which variable you'd move first and how, with the arithmetic showing the effect of that change.

Deliverable and self-check. One short document, roughly one to two pages, containing all five items above. Score yourself 2 points each for the following. (a) The proposal's situation or complication contains a real and checkable number. A generic claim scores zero. (b) The SOW contains all six required components, beyond deliverables and fee. (c) The fee build-up arithmetic reconciles. Recompute it; don't eyeball it. (d) The scope-creep scenario is classified correctly against your SOW's actual deliverables list, and not against what you now wish you'd written. (e) The trust-equation arithmetic is correct both before and after the proposed change. Pass at 8/10 with no zero on any item.

No Case-Engine case or drill set is mapped to this material in the galaxy plan, so the gate is the mastery quiz alone (below). Your reps live in the mini-project for now. You'll get them again in the Partner Capstone once you've completed the branch. There they come at far greater depth and under time.

Reading & resources

Use everything below as an anchor to learn from and check against. None of it replaces the judgment you're building. Free unless marked. Level tags run from beginner to advanced.

The trusted-advisor relationship, the spine of the whole engagement:

• David Maister, Charles Green & Robert Galford, The Trusted Advisor: the trust equation in full, with the book's own worked illustrations of credibility, reliability, intimacy, and self-orientation. [Paid] [Beginner–Advanced]
• David Maister, Managing the Professional Service Firm: the economics of a PSF (leverage, team structure), and why professional norms (not just individual talent) are what make an advisory firm trustworthy at scale. [Paid] [Advanced]
• Peter Block, Flawless Consulting: the consultant–client "contract" (in the relationship sense, not the legal one), and the craft of a flawless meeting. [Paid] [Beginner–Advanced]

The engagement, the team, and the craft of the work:

• Ethan Rasiel, The McKinsey Way and The McKinsey Mind: accessible, anecdote-rich treatment of how an engagement team actually runs day to day, including staffing, feedback, and client-management moments. [Paid] [Beginner]
• Barbara Minto, The Pyramid Principle: the full mechanics of the answer-first synthesis that's only named here as a hand-off. Read it when you reach CN1.03 or M10.03; you don't need it yet. [Paid] [Advanced]
• Conn & McLean, Bulletproof Problem Solving: the 7-step problem-solving cycle that CN0.01 introduces and the engagement map here assumes. A natural companion read. [Paid] [Beginner–Advanced]

Feedback and delegation (free, practitioner-oriented):

• The Center for Creative Leadership's public write-ups on the SBI (Situation–Behavior–Impact) feedback model: the short, practical original source for the model taught here. [Free] [Beginner]
• Harvard Business Review: the standing anchor for delegation, feedback and professional-services management. Search its archive by topic as each one comes up. [Mixed free/paid] [Beginner–Advanced]

Scope, fees, and change control (free, practice-oriented):

• Public project- and program-management bodies of knowledge (the kind of material behind a PMP-style curriculum) cover scope statements and change control in a form you can carry straight into a consulting SOW, even though the version taught here is consulting-specific. [Free overviews / paid full certification] [Beginner]
• Management Consultancies Association (MCA)-style professional codes of conduct: publicly available codes of ethics and independence from consulting industry bodies are a useful, free anchor for the independence and conflict-of-interest rules taught here. [Free] [Beginner–Intermediate]

Do this, not just read: find a real, publicly available consulting-firm case study or a client testimonial write-up, and try to reverse-engineer its likely original proposal. What situation and complication would have opened it, and what was the fee structure probably built on, given the described scope? Then look for the spot where a change-order conversation most likely happened without ever being mentioned. Fifteen minutes of that will teach you more about the paperwork behind a polished case study than another chapter of theory.

Teach it back & journal

Feynman prompt. Explain to a friend who thinks "consulting is just smart people giving smart advice" why a technically brilliant recommendation can still fail to land. Use the sentence "the client is not buying the analysis, the client is buying the confidence to act on it." Then walk them through the trust equation by hand with two advisors of your own invention, one more "impressive" and one with lower self-orientation. Show with real arithmetic, and not just an assertion, why the equation says to trust the second one more. If your friend can predict, unprompted, that the most trust-building thing an advisor can do is tell a client they need less work, you've got the mechanism across.

Journal prompt. Think of a real service relationship in your own life, such as a doctor, a lawyer, a financial advisor or even a mechanic, where you either trusted them completely or never quite did. Be specific about which. Rate them as candidly as you can on Credibility, Reliability, Intimacy and Self-orientation, and compute their trust score. Find the single variable that was really driving your feeling. It may not be the one you'd have guessed before doing the arithmetic. Then write a paragraph on two questions. Which of the habits you've worked through here (a precise scope boundary, a transparent change order, real-time specific feedback, or a visible act of low self-orientation) would most change how a client experiences working with you? And what's the one concrete thing you'll do differently the next time someone trusts you with their problem?

This module's flashcards and mastery quiz are wired into the app: see the node's Quiz and Reviews.