Turn founder interviews and verified client outcomes into four-part Storytelling Case Study posts within a people-led content system. Use for B2B founder or executive LinkedIn case studies, interview planning, and evidence-based revisions.
Installs into .claude/skills of the current project.
Are you the author of Sangines Storytelling Case Study?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/getedgehq-sangines-storytelling-case-study)
---
name: sangines-storytelling-case-study
description: "Turn founder interviews and verified client outcomes into four-part Storytelling Case Study posts within a people-led content system. Use for B2B founder or executive LinkedIn case studies, interview planning, and evidence-based revisions."
---
# Storytelling Case Study Content Engine
Based on Marvin Sanginés's public method. Not affiliated with or endorsed by Marvin Sanginés.
## When to use
Use this skill when a B2B founder, executive, or Content Strategist needs to turn lived experience and client outcomes into a credible LinkedIn transformation story. It also supports planning the weekly podcast-style conversation that supplies those stories, reviewing drafts, and placing case studies inside a broader content calendar.
The deliverable is a four-part post, accompanied by an internal evidence record, interview follow-ups, and a practical handoff. Adapt to the requested scope: an existing transcript needs extraction and editing; a planning request needs an interview brief; a revision request needs a stronger draft and an explanation of material changes. Do not pretend an interview occurred or expand a writing assignment into publishing, messaging prospects, or buying ads.
Sanginés reports that this format drives about 60% of notus inbound leads. That is a self-reported result for his business, not a forecast for the user. His separate revenue attribution claim refers to his personal LinkedIn profile. Preserve this distinction whenever discussing the method's performance. Read the provenance notes in [references/sources.md](references/sources.md) before quoting results or explaining the attribution.
## Procedure
1. **Set the reader and commercial context.** Identify the ideal customer, their recognizable problem, the founder's offer, and the intended next step. Use the system foundation in [references/method.md](references/method.md#system-foundation). If context is absent, state a working assumption and ask only for information that changes the story selection.
2. **Choose a supportable transformation.** Find a client story with a concrete starting situation, meaningful intervention, and observable outcome. Check comparability to the intended reader rather than choosing the largest number. Apply the selection rules in [references/method.md](references/method.md#story-selection-and-evidence).
3. **Prepare the weekly conversation.** Build an agenda from recent work, audience questions, prior comments, and relevant creator posts. Draft questions around missing story evidence. Use [references/method.md](references/method.md#interview-engine) and the interview fields in [templates/output-template.md](templates/output-template.md).
4. **Extract lived detail.** Work from the recording, transcript, notes, or supplied material. Ask follow-ups about constraints, actual actions, discoveries, and changes of direction. Reflect the founder's meaning back for correction. Follow the interviewing guidance in [references/method.md](references/method.md#interview-engine); use existing archival material when it already contains the necessary substance.
5. **Build the evidence record.** Separate supported facts, founder interpretations, proposed wording, and unresolved questions. Record timeframes and metric definitions. Apply [references/method.md](references/method.md#story-selection-and-evidence) and fill the internal record in [templates/output-template.md](templates/output-template.md). Missing results remain missing until verified.
6. **Write the emotional opening.** Choose a recognizable problem, significant outcome, or surprising fact. Use a time contrast when supported by the evidence. Check that the opening earns attention through relevance and truth using [references/method.md](references/method.md#four-part-post).
7. **Establish the client's starting point.** Show who the client was, what they wanted, and the obstacles. Lead with the challenge most familiar to the reader. Follow [references/method.md](references/method.md#four-part-post), keeping the client central rather than opening with agency credentials.
8. **Tell the process as a sequence of changes.** Name meaningful stages with nouns and show what happened within each. Include a real turning point or adjustment where available. Use [references/method.md](references/method.md#four-part-post) and compare the weak and improved drafts in [examples/worked-examples.md](examples/worked-examples.md).
9. **Make the outcome specific.** Combine supported quantitative change, qualitative improvement, and continuing benefits. Limit broad leadership claims and use an ongoing relationship close only when true. Apply the outcome and edge-case rules in [references/method.md](references/method.md#four-part-post).
10. **Return the draft for review.** Preserve the founder's voice, resolve factual gaps, and revise from their feedback. Run [checklists/review-checklist.md](checklists/review-checklist.md). Keep unresolved evidence questions outside the publishable copy; withhold unsupported claims rather than disguising them with confident language.
11. **Package and learn.** Deliver the post and internal handoff using [templates/output-template.md](templates/output-template.md). Place the story in the aspirational pillar alongside tactical, insightful, and personal content. Recommend measurement of relevant audience response and qualified conversations using [references/method.md](references/method.md#distribution-and-learning). Treat distribution and paid amplification as separate actions requiring their own task authorization.
## Files in this skill
- [SLUG.txt](SLUG.txt): Canonical package identifier.
- [SKILL.md](SKILL.md): Entry point, routing, and working procedure.
- [references/method.md](references/method.md): Detailed public method, decision rules, adaptations, and citations.
- [references/sources.md](references/sources.md): Fetched public sources and provenance limitations.
- [examples/worked-examples.md](examples/worked-examples.md): Two invented transformations with weak drafts, improved posts, and rule analysis.
- [templates/output-template.md](templates/output-template.md): Interview brief, evidence record, post structure, and handoff fields.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail checks and repairs for recurring failures.