The Independent Consultant's Pricing Memo Stack: 5 AI Templates That Close 6-Figure Engagements

The independent management consultant pricing their work in hours has, on most engagements, already lost the deal. Six-figure engagements are not bought in hours; they're bought against a defined outcome the client cares about, at a price the client can defensibly approve, with risk allocations both parties can live with. Pricing in hours invites the client to second-guess the hourly rate; pricing against value invites them to evaluate the work.

This is also how the large consultancies — McKinsey, Bain, BCG, Deloitte — have always priced their serious engagements. The independent consultant who learns the same language is not pretending to be a large firm. They're competing in the same procurement process, where pricing structure is one of the variables clients use to decide whether a consultant is a peer of the work or a vendor priced into the conversation.

This guide is the five-memo pricing stack independent consultants use to move client conversations onto the right terrain. The Consultant Proposal Generator and the Consultant Executive Summary Generator handle the writing layer. The structure — the discipline of producing the five memos at the right moment in the sales cycle — is the consultant's craft.

A note on scope. This article is general guidance for independent management consultants and solo strategy advisors. It is not legal or tax advice. The specific commercial terms of a consulting engagement — scope of work, intellectual property, indemnification, payment terms — warrant your attorney's review. The drafting framework below is about positioning; the underlying contract is its own document.

Key takeaways

• Hourly pricing is the wrong unit for serious engagements — it invites the client to second-guess the rate; value-based pricing invites them to evaluate the work.
• The 5-memo stack: discovery summary (free, post-first-call), diagnostic proposal (fixed-fee defined phase), diagnostic report (deliverable), implementation engagement proposal, retainer/advisory memo.
• Each memo is a forcing function on the consultant's thinking and a calibration point with the client. Skipping memos saves writing time and costs proposal-fit clarity.
• The diagnostic engagement ends at a defined decision point — implementation is a separate conversation, not an automatic continuation. This is what allows the client to authorize a large fee.
• Memos are positioning documents; contracts are documents of record. Never confuse them. Engagements of meaningful size warrant attorney review of the underlying contract.

At a glance: the 5-memo stack

#	Memo	When sent	Pricing	Purpose
1	Discovery summary	Post-first-call (~24 hours)	Free	Calibrate the consultant's read with the client's situation
2	Diagnostic proposal	When the client agrees there's a problem	Fixed fee, defined phase	Propose a discrete diagnostic engagement with a decision point
3	Diagnostic report	End of diagnostic engagement	Included in memo 2 fee	Deliver the findings, recommendations, and the decision the client needs to make
4	Implementation proposal	If diagnostic recommends action	Fixed fee or milestones — not hourly	Propose the engagement that executes against the diagnostic's recommendations
5	Retainer / advisory	After implementation closes	Monthly or quarterly fixed retainer	Define ongoing advisory scope as a separate commercial product

The five-memo stack

Each memo serves a specific stage of the engagement-development conversation. Sending the right memo at the right time signals fluency. Sending the wrong one — particularly sending hourly rate sheets when the client is ready for a value memo — signals the consultant is not the peer of the work.

Memo 1 — The discovery summary

Sent after the first 30-minute conversation with the prospective client. Not a proposal. A summary of what the consultant heard, what they think the underlying problem is, and what the next step should be.

Structure:

1. What you said (three to five bullets). The client's situation, in their words.
2. What I think is actually going on (three to five bullets). The consultant's read on the underlying problem, separated from the surface symptom. This is where the work starts; this is also where the consultant demonstrates that they listened.
3. What I'd want to do next, if you're interested (one paragraph). A specific recommended next step — a deeper diagnostic, a focused engagement on the highest-leverage piece, an introduction to someone better-suited if the work is outside the consultant's wheelhouse.
4. What I don't think this is (one paragraph). The honest call on what isn't the problem, or what work the client is asking for that wouldn't actually move the needle.

The discovery summary is a free artifact. It costs the consultant 30 minutes of writing time. It earns trust before the proposal arrives because the client reads it and sees themselves understood — or, when the consultant is wrong, calibrates the consultant's read against the actual situation. Either outcome is useful.

Memo 2 — The diagnostic proposal

Sent when the client agrees there's a substantive problem to look at. Not the full engagement proposal — a proposal for a defined diagnostic phase with a fixed scope, fixed price, fixed timeline, and a clear set of deliverables at the end.

Structure:

1. The question the diagnostic answers. One sentence. "By the end of this diagnostic, you will have a defensible answer to [specific question]."
2. What the diagnostic includes. Stakeholder interviews (numbered), data review, analyses, workshops. Numbered, specific, finite.
3. What it doesn't include. Implementation, change management, ongoing advisory. The diagnostic is a discrete project. Naming what it doesn't cover prevents scope creep mid-engagement.
4. The deliverables. Specifically named — a written diagnostic report of a defined length, a one-day workshop, a recommendations summary. Not "ongoing analysis."
5. The timeline and the fee. Fixed fee. Specific dates. No hourly footnotes.
6. The decision point at the end. The diagnostic concludes with a defined decision — proceed to implementation, pause, escalate, or end. Naming the decision point in the proposal sets up the next phase to be a separate conversation, not an automatic continuation.

A defensible diagnostic proposal is two pages. The Consultant Proposal Generator produces this format from a one-page context input.

Memo 3 — The diagnostic report itself

The deliverable at the end of memo 2's engagement. Written as a memo, not a deck. The "memo culture" practiced in some technology and finance environments has been winning back boardrooms in part because long decks lose the thread; a well-structured memo carries the reader.

Structure:

1. The headline finding. One sentence at the top.
2. The evidence behind the finding. A page or two, organized as the chain of reasoning. Not "we did 12 interviews and ran three analyses"; rather, "here is the question, here are the three things we learned that bear on it, here is what they imply."
3. What it means. The implications. The decisions the client needs to make next.
4. Recommendations. Specific, prioritized, with the consultant's conviction level on each (high, mixed, low) and the trade-off each recommendation accepts.
5. What we're less sure about. The honest section. The questions the diagnostic didn't fully resolve, and what would.

The diagnostic report is the artifact the client will reference for months. It travels — to their board, to their team, to their successor. Write it accordingly. The Consultant Strategy Memo Generator produces this format.

Memo 4 — The implementation engagement proposal

If the diagnostic concludes with a recommendation to act, the implementation engagement is the next conversation. This is where the larger fee lives, and where hourly pricing reflexes are most expensive for the consultant.

Structure:

1. The outcome the engagement delivers. Not "advisory support" — a specific, measurable outcome the client can articulate at the end.
2. The phases. Named, sequenced, with start and end dates. Each phase has its own deliverables and its own decision point.
3. What the client provides. Time of named executives, access to data, access to teams. The implementation depends on the client doing their part. Name it.
4. The fee structure. Fixed fee, milestone-based payments, or hybrid. Hourly is almost never the right answer here. Naming the structure in the proposal pre-empts the procurement conversation that would otherwise default to hourly.
5. The exit criteria. When is the engagement done? Naming the end conditions makes the engagement bounded, which is what allows the client to authorize a large fee in the first place.

A defensible implementation proposal is three to five pages. Longer proposals signal uncertainty.

Memo 5 — The retainer / advisory memo

For ongoing work after an implementation engagement closes. A separate memo, sent as a separate proposal — not a default add-on.

Structure:

1. The specific advisory relationship. Monthly conversation, quarterly review, ad-hoc access — pick one structure and define it.
2. What's included and excluded. Travel, presentations to the board, project-specific work beyond the advisory scope are usually excluded and priced separately.
3. The fee. Monthly, quarterly, or annual fixed retainer.
4. The termination terms. 30-day notice either way. Clean.

A retainer is a different commercial product from a project. Treating it as a separate memo, with separate signing, keeps the relationship defensible and prevents scope creep.

Why this stack works

A few observations that make the stack worth the discipline:

• Each memo is a forcing function on the consultant's thinking. Writing memo 1 well requires hearing the client clearly. Writing memo 2 well requires defining the work. Each memo refines the consultant's view before the next conversation, which is what produces the conviction clients pay for.
• Each memo is a calibration with the client. The client reads the memo and either accepts the consultant's framing or adjusts it. Either response is information. A consultant who skips the memos is a consultant who arrives at proposals with avoidable misalignment.
• The stack moves the conversation off hours. Once the client has accepted memo 1's framing and memo 2's diagnostic, the conversation about implementation is about outcome, scope, and timeline. Hourly rates feel out of place in that conversation — which is the point.

What this approach is not

A few honest limits:

• It doesn't replace a real referral network. Independent consultants don't acquire serious clients on memo quality alone. The memos are how relationships convert; the relationships are the upstream condition.
• It doesn't fit every engagement type. Hands-on operational work, deep technical assessments, and specialist diagnostic work sometimes price defensibly in time-based units. The five-memo stack is a default for strategy consulting engagements. Specialist consulting often has its own conventions.
• It doesn't replace your attorney. The commercial terms behind the proposal — IP, indemnification, scope-of-work clarity, dispute resolution — warrant your attorney's review on engagements where the dollar stakes are real. The memos are positioning documents; the contract is the document of record.

What AI does, and what it doesn't

The Consultant Proposal Generator and Consultant Strategy Memo Generator handle the writing layer for each memo — the structural fidelity to the format, the consistent voice, the discipline of leaving out the wrong things.

AI does not:

• Form the consultant's view. The headline finding, the recommendations, the conviction — those are the consultant's, formed from the work.
• Price the engagement. What the work is worth to the client is a judgment the consultant makes, informed by market, the specific situation, and the consultant's positioning. AI does not set the number.
• Replace the consultant's professional accountability. Every memo goes out under the consultant's name. The work product is the consultant's, and the responsibility for accuracy is the consultant's.

How to start

Pick the next live opportunity you have. Write memo 1 — the discovery summary — and send it before the proposal arrives. The next opportunity after that, do the diagnostic-proposal step before the implementation conversation. Refine over your next three to five engagements. By the third or fourth, the stack feels natural and the conversion rate on the right kinds of clients has noticeably moved.

A consultant who runs this stack as a discipline ends up with a body of memos that, taken together, is a portfolio of how they think. That portfolio is part of how the next client decides to hire them.

Next steps

• Consultant Proposal Generator — for memos 2 and 4.
• Consultant Strategy Memo Generator — for memo 3 (the diagnostic report) and memo 5 (advisory).
• Consultant Executive Summary Generator — for the headline-and-implications layer that opens every memo.
• Management Consultant Claude Plugin install guide — to run the whole stack from inside Claude.

Frequently asked questions

How should independent consultants price their work?

By the engagement value rather than the hourly rate. The five-memo stack moves the client conversation from "how many hours" to "what outcome and at what defined scope." Each memo in the stack (discovery summary → diagnostic proposal → diagnostic report → implementation proposal → retainer memo) corresponds to a distinct point in the engagement-development cycle and is priced on the work product, not on time spent.

What is a diagnostic engagement in management consulting?

A diagnostic engagement is a discrete, fixed-fee, fixed-timeline project with defined deliverables (typically a written diagnostic report and a one-day workshop) whose explicit goal is to produce a defensible answer to a specific business question and a clear decision point at the end. It's a bounded engagement that may or may not be followed by an implementation phase — the boundedness is what makes it commercially defensible at a serious fee.

Why do consulting firms use memos instead of hourly rates?

Because the memos create a calibration with the client at each stage of the engagement. The discovery summary (after the first call) calibrates the consultant's read with the client's situation. The diagnostic proposal calibrates the scope of the work. The diagnostic report calibrates the recommendation. Hourly rates skip the calibration and invite second-guessing of the rate rather than evaluation of the work.

What is a discovery summary memo?

A free, post-first-call summary that captures what the consultant heard, what they think the underlying problem is (often distinct from the surface symptom), what they'd recommend doing next, and what they don't think the problem is. It's two pages, costs 30 minutes of writing, and earns trust because the client reads it and sees themselves understood — or calibrates the consultant against the actual situation. Either outcome is useful.

How do I transition an existing client from hourly to value-based pricing?

Use the diagnostic-engagement structure as the bridge. The next time the client has a defined question ("what should we do about X?"), propose a fixed-fee diagnostic engagement rather than hours. The structure of that engagement — defined scope, defined deliverable, defined decision point — makes the price comparable to what the client would otherwise pay in hours, but reframes the conversation around outcome.

Can AI write consulting proposals?

AI handles the writing layer — applying the memo structure, drafting clean prose in the consultant's voice, structuring the deliverable around the decision the client needs to make. The consultant forms the recommendation, prices the engagement, names the load-bearing assumptions, and signs the proposal. AI doesn't replace the consultant's view of the work.

Do I need a contract for a small consulting engagement?

Yes — even small engagements warrant a written agreement covering scope, deliverables, fee, timing, IP, confidentiality, indemnification, and termination terms. The memos in this stack are positioning documents, not contracts. For engagements of meaningful size, your attorney's review of the underlying contract is the appropriate due diligence, regardless of how polished the memos look.

---

This article is general guidance for independent management consultants. It is not legal, tax, or commercial-terms advice. The specific contract terms behind any engagement warrant review with your attorney; the pricing structure that fits your work depends on the engagement type, the client, and the market.