<aside> 📋 Frequency: Trigger-Based | Time: 45 min | Trigger: When an engagement produces a measurable outcome

</aside>

Measurable outcomes evaporate if you don't capture them while the engagement is fresh. Six months after closing, you won't remember the specific before-state, the constraint you diagnosed, or the number that changed. This SOP converts a completed outcome into a structured proof asset while the details are still accurate — before the client contact moves on and the context is gone. Run it before the Client Offboarding Process is complete.

Prerequisites

• The engagement SOW or project brief — the documented before-state and stated objective
• The measurable outcome: a specific metric, timeline, capacity change, or revenue shift that can be stated without revealing confidential client details
• Client permission to document the outcome (explicit or implied by your engagement terms) — confirm before writing
• Your proof library (a folder, doc, or equivalent) where tagged case studies are stored and retrievable

Procedure

1. Document the before-state in your own words: what was broken, constrained, or unmeasured before the engagement started. Pull from the SOW or your intake notes — not from memory alone.
2. Document the outcome specifically: the metric that changed, the timeline it changed in, and the mechanism that drove the change. If the outcome is directional rather than numeric, describe the observable condition that shifted.
3. Run the Case Study Builder skill with the client's industry, the before-state, the constraint diagnosed, the intervention applied, and the outcome as input. Review the output for a structured, anonymized case study draft.
4. Edit for accuracy and anonymization. Confirm no identifying details remain unless the client has explicitly approved named attribution. Replace firm names with descriptors ("a boutique consulting firm") and scrub any proprietary specifics.
5. Save the finalized case study to your proof library. Tag it by vertical, constraint type, and outcome category so it's retrievable when you need it for proposals, speaking submissions, or content.
6. Flag the case study for the Content Publishing Rhythm — a strong before-and-after can anchor a thought leadership post with minimal additional drafting.

Expected Outcome

A structured, anonymized case study saved and tagged in your proof library — ready to reference in proposals, content, and speaking submissions.

<aside> ⚠️ Common mistakes:

— Waiting until "after the engagement is fully closed" to run this SOP. The trigger is the measurable outcome, not the offboarding date. Run this before the final session so the client can confirm the numbers while they still have them front of mind.

— Writing the case study around what you did instead of what changed. Prospects don't buy methodology — they buy the before-and-after. Lead with the constraint and the outcome, not the framework you used.

</aside>