agentleFS
mardab96mardab96/b2b-lead-generation-claude-skills/won-deal-to-case-study/SKILL.md

won-deal-to-case-study

Skill5 starsChanged 4 months agoMITView on GitHub

Turns a closed-won deal into a publishable case study plus the customer email that asks permission, using CRM notes and call records instead of a blank page. Use when a company has good results and no proof, or when case studies keep getting postponed.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the permission email.

    line 37
  2. Distinctive:

    If the CRM record is too thin to reconstruct a before state, say so and write the interview questions instead of a draft.

    line 44
  3. Distinctive:

    Do not build the story around your product.

    line 46
  4. Distinctive:

    Do not publish, send or share anything.

    line 83
  5. Distinctive:

    Do not invent quotes. Ever.

    line 84
  6. Distinctive:

    Do not use a customer's name, logo or results without documented permission.

    line 85
  7. Distinctive:

    Do not present your own projections as their outcomes.

    line 86
  8. Distinctive:

    Do not include commercially sensitive details, pricing or named individuals without checking what the contract allows.

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Won Deal to Case Study

Use this skill when

The results exist and the proof does not.

Almost every B2B company has this problem in the same shape: several customers are demonstrably happy, everyone agrees a case study would help, and nobody writes one, because writing one from scratch takes a week and interviewing the customer takes a scheduling miracle.

Most of the material is already in the CRM. This assembles a draft from it, marks every gap the customer needs to fill, and writes the email that asks them.

Required input

  • The deal: what they bought, when, and what the situation was before.
  • Whatever exists in writing: CRM notes, call transcripts, the original proposal, onboarding messages, support threads.

Strongly improves the result:

  • any number they have said out loud, even approximately
  • what they tried before you
  • the internal objection they had to overcome
  • who the champion was and what their role is

Analysis workflow

  1. Reconstruct the before state from the record: what was actually happening when they started looking, in specifics. This is the part that makes a case study readable and the part most drafts skip.
  2. Find the trigger. Nobody buys because of a slow-burning inefficiency; they buy in the week something forced the issue. Locate that week.
  3. Separate what you can evidence from what you would like to claim. Every number goes in one of two buckets: stated by the customer, or not stated. There is no third bucket.
  4. Reconstruct what changed, in their operational terms rather than in product features.
  5. Mark every gap where the story needs the customer's own words, and be specific about which sentence you are asking them for.
  6. Draft the case study with the gaps visible as placeholders, so nobody accidentally publishes an inference as a quote.
  7. Decide what the story is actually about before writing a word of it. A case study about your product is a brochure; a case study about a company that had a problem and now does not is something a stranger reads to the end.
  8. Write the permission email. It is short, it says what you will publish, it offers approval before anything goes live, and it makes declining easy.
  9. Note who at your end owns chasing the approval, because this is the step where case studies die.

Decision rules

  • Nothing gets published without the customer's approval. This is not a style preference; using a company's name and results without consent is a legal and relationship risk.
  • A number that the customer did not say is not their number. Model numbers can appear, labelled as estimates, or not at all.
  • If the CRM record is too thin to reconstruct a before state, say so and write the interview questions instead of a draft.
  • An anonymised case study is a real option, and often the fastest one when a customer's legal team is slow.
  • Do not build the story around your product. The buyer reading it is looking for their own situation, and the product is the least interesting part.

Output format

The draft

Situation, trigger, what they tried, what changed, and where they are now. Every unverified claim visibly marked. Every place needing a quote marked as a gap.

Evidence table

ClaimSourceVerifiedNeeds customer confirmation

What to ask the customer

Five questions maximum, each aimed at a specific gap in the draft, written so they can be answered in one sitting.

The permission email

Ready to send. Names what you want to publish, offers approval, gives an easy no.

The anonymised version

One paragraph showing what the story looks like without the name, for when approval is slow or refused.

Practical example

A closed-won deal from four months ago. The CRM has the discovery notes, the proposal and an onboarding thread.

The notes reconstruct a clear before state: two people manually reconciling orders across three systems every Monday. The trigger is in the discovery notes, a missed month-end close that a board member noticed.

There are two numbers in the record. One is theirs: "about a day and a half a week" from the discovery call. The other is yours: a projected saving from the proposal, which does not go in the draft at all.

The gaps are marked: what Monday looks like now, and whether the month-end problem recurred. Those become two of the five questions. The permission email asks for fifteen minutes or a written reply, whichever is easier, and offers full approval rights before publication.

Guardrails

  • Do not publish, send or share anything. This produces a draft and an email.
  • Do not invent quotes. Ever. A plausible quote attributed to a real person is fabrication.
  • Do not use a customer's name, logo or results without documented permission.
  • Do not present your own projections as their outcomes.
  • Do not include commercially sensitive details, pricing or named individuals without checking what the contract allows.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.