# Firm Case Study Paragraph

> Writes one case study paragraph of 120 to 180 words (challenge, action, result) matched to this client by selection and never by alteration, with a 40-word version, the permission status, results only as the past client approved them and a permission request to send if needed. Use for "run firm-case-study-paragraph", "write a case study for the proposal", "add proof to my proposal", "which past project fits this client", "short case for the RFP", "relevant experience paragraph", "ask my old client for permission to cite", part of the Claude for Consultants · Team in Claude Pack by 90n.

- Skill: `polar-bear-org/firm-case-study-paragraph` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/firm-case-study-paragraph`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/firm-case-study-paragraph/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/firm-case-study-paragraph

---


# Case Study Paragraph

## When To Use
A model can write the client a flawless method section. It cannot write about the time you did this for someone with the same problem. That is the one part of a proposal only you can supply, so it has to be true, short and cleared for use. Run this when a theme or a section of the proposal needs a past engagement behind it.

## When Not To Use
When you cannot yet say which proof the proposal calls for, begin with Win Themes. If nothing in your past work honestly resembles this client, say so in the Consulting Proposal and offer a smaller first phase; do not stretch a case.

## Inputs
- Your notes on the past engagement: the situation, what you did, what changed
- Results as the past client approved them, and what they agreed to (named, anonymised, not yet asked)
- This client's situation in three lines, and where the paragraph will sit
If you have none of this, I ask five short questions about the past engagement and mark the paragraph "first draft, permission not confirmed".

## Approach
Challenge, action, result is a common practitioner convention. The paragraph fits the new client by selection: it chooses which true detail leads and says the rest more briefly. It never fits by alteration. The trap is the mirror, a past engagement bent until it describes one that did not happen. One follow-up question about a bent case and the reader stops believing the rest of the document.

## Workflow
1. Ask, in one go: which past engagement do you have in mind? What did that client agree to: named, anonymised, or not yet asked? What does this prospect most need to recognise in it?
2. Challenge, one or two sentences: the past client's situation by role and problem ("the operations lead of a past client faced [problem]"). No size, sector or type unless that client approved the detail.
3. Action, two or three sentences: what you did, specifically, including the moment the direction changed. No past-client staff are named without permission.
4. Result, one or two sentences: only as approved, with base and period where they gave them. Not approved yet means a [placeholder] and "ask". Work that was delivered but never measured says what was delivered and stops there.
5. Bridge, one sentence: what you would do the same way for this client, as an intention and never as a promise of the same result.
6. Trim to 120 to 180 words, then write a 40-word version from the challenge and result. If permission reads "not yet asked", draft a short request for you to send, quoting the exact words and figures that would appear.

## Output Format
```markdown
# Case Paragraph
Past engagement: [internal name] · Written for: [prospect role and need] · Date: [date]
## Permission
[Named, approved / anonymised, approved / not yet asked] · Agreed by [past client role] on [date]
## Paragraph (120 to 180 words)
[Challenge] [Action] [Result as approved] [Bridge, as an intention]
## Short version (40 words)
[Challenge and result]
## Sources
| Statement | Source | Approved for use |
|---|---|---|
| [result line] | [notes, email, date] | [yes / no / ask] |
## Permission request (if not yet asked)
[A few lines for you to send, quoting the words and figures that would appear]
## Decision
[You] confirm the permission status and the result line with [past client role] before [the date the proposal goes out].
```

## Done When
- Each statement can be traced to your notes, and each result to what the past client approved
- The prospect's situation changed the order of details, not the facts
- Both versions are within their word limits and the permission status is stated

## Quality Bar
- The past client appears by role and problem; no size, sector or type unless approved
- One result with its base and period, or none; never "typically" or "results like these"
- The bridge states an intention, never a promised outcome
- Only work that happened, with results as approved; I never invent a reference or a result, and you clear the wording with the past client yourself.

## Next
Run firm-ai-use-statement (AI Use Statement) to say plainly how AI will be used in the work.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

