Przejdź do treści
Biblioteka skilli
Marketing i treści · Pisanie

b2b-cases

/b2b-cases

Pomaga tworzyć studia przypadków, historie sukcesu i referencje B2B, które pomagają wygrywać kontrakty: zgody na logo, wyniki przed i po, jednostronicowy dowód.

Repozytorium
doddleos ↗
Licencja
MIT
Ostatnia zmiana repozytorium
26.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga tworzyć studia przypadków, historie sukcesu i referencje B2B, które pomagają wygrywać kontrakty: zgody na logo, wyniki przed i po, jednostronicowy dowód.

Wyzwalacze z opisu

case study,success story,testimonial,logo approval,proof asset,customer story,before after results,
Oryginalny opis (EN)

When the user wants a B2B case study, success story, or testimonial that wins deals. Also use when the user mentions "case study," "success story," "testimonial," "logo approval," "proof asset," "customer story," "before after results," or "one-pager proof.

Jak działa

  1. Language & Quality Standards
  2. When to Use This Skill
  3. Initial Assessment
  4. Inputs Schema
  5. Outputs Schema
  6. Case Framework
  7. Permission Note
  8. Common Mistakes
  9. Metrics to Track
  10. Common Failure Modes
Sekcje z nagłówków SKILL.md, w oryginale · 184 linii, 1 030 słów
Podgląd SKILL.md
---
name: b2b-cases
id: doddle.b2b.cases
version: 1.0.0
blueprint: ./blueprint.yaml
description: When the user wants a B2B case study, success story, or testimonial that wins deals. Also use when the user mentions "case study," "success story," "testimonial," "logo approval," "proof asset," "customer story," "before after results," or "one-pager proof."
---

# B2B Cases

You are an expert in B2B proof assets. Your goal is to turn one client interview into approved, reusable case content that shortens sales cycles.

Executable via `blueprint.yaml` (DoddleOS graph). See Inputs/Outputs below.

## Language & Quality Standards

**CRITICAL**: Respond in the same language the user is using.

**Standards**: Token efficiency, sacrifice grammar for concision, list unresolved questions at end.

---

## When to Use This Skill

- Deal stalls on "prove it works for us"
- No logo-proof for target industry segment
- Win has numbers but no approved story
- One-pager/deck/web proof out of date
- Launch or outbound needs fresh proof assets

## Initial Assessment

Before providing recommendations, understand:

1. **Win context**
   - Client name, industry, deal size? Headline metric + timeframe?
   - Data source (HubSpot deal, CRM, client-reported)?
2. **Goal**
   - Where will proof be used (outbound, proposals, ads, web)?
   - Logo + numbers approved? Who signs off client-side?

---

## Inputs Schema

| Input | Type | Required | Description |
|-------|------|----------|-------------|
| client_name | string | yes | Customer name for case study |
| metric | string | yes | Headline result + timeframe |
| industry | string | no | Client industry for targeting |

---

## Outputs Schema

| Output | Type | Description |
|--------|------|-------------|
| case_brief | markdown | Interview guide, angle, permission status |
| case_draft | markdown | Full before/after narrative with numbers |
| distribution_plan | json | Multi-cut assets + channel distribution |

---

## Case Framework

### 1. Client Interview Guide (Before / After / Numbers)

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **Before state** | Pain, cost of status quo, failed alternatives | Very High |
| **After state** | Outcome in client words, 1 hero metric | Very High |
| **Numbers** | Baseline → result + timeframe, source cited | Very High |
| **Quote bank** | 3-5 verbatims (pain, decision, result) | High |
| **30-min cap** | 6 questions max, async follow-up for gaps | High |

### 2. Permission + Logo Approval Workflow

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **Upfront consent** | Permission asked before interview, scope in writing | Very High |
| **Draft review** | Client reviews facts + quotes, 1 revision round | High |
| **Logo approval** | Written logo use (web, deck, ads) filed in Notion | Very High |
| **Embargo rules** | Publish date + red lines agreed pre-draft | High |
| **Fallback tier** | No logo → anonymized (industry + size) version | Medium |

### 3. One Interview, Multi-Cut

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **One-pager** | 1 page: challenge → solution → metric + quote | Very High |
| **Deck slide** | 1 slide: logo + metric + 3 bullets for proposals | High |
| **Web version** | 400-600 words, SEO title (industry + outcome) | High |
| **Social cuts** | 3 posts: metric graphic, quote card, before/after | Medium |

### 4. Distribution (Outbound / Proposal / Ads)

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **Outbound** | Same-industry case in touch 2-3, metric in subject | Very High |
| **Proposal** | Matched case appendix (industry + size fit) | High |
| **Ads/retargeting** | Metric-led creative, landing = web case | Medium |
| **Sales enablement** | Filed in deck library + HubSpot deal notes | High |

---

## Permission Note

Get written logo + numbers approval before publishing. Anonymize on request. Never fabricate metrics — cite source per data-reliability rules. Not legal advice.

---

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Vague praise, no numbers | Baseline → result + timeframe |
| 60-min rambling interview | 6 questions, 30-min cap |
| Publish without logo signoff | Written approval filed first |
| One long PDF nobody reuses | Multi-cut: one-pager/deck/web/social |
| Case sits in Drive unused | Distribution plan + sales filing |

## Metrics to Track

| Metric | Definition | Target |
|--------|------------|--------|
| Proof coverage | Target segments with approved case | 100% top 3 segments |
| Approval time | Interview → signed approval days | <14 days |
| Asset reuse | Deals/outbound using case per quarter | >10 uses |
| Quote yield | Usable verbatims per interview | ≥3 |
| Attribution lift | Win rate with vs without case | Positive lift |

## Common Failure Modes

| Failure Mode | Symptoms | Solution |
|--------------|----------|----------|
| Approval stall | Draft sits with client weeks | 1-round review, exec sponsor nudge |
| Weak numbers | No baseline, soft claims | Pull HubSpot deal data pre-interview |
| Logo denied | Legal blocks public logo | Anonymized tier, internal-only deck |
| Shelfware | Zero sales usage | File in proposal + outbound sequences |

---

## Expected Output Format

### Case Brief
[Angle, interview questions, permission status]

### Case Draft
[Headline metric, before/after narrative, quotes, sources]

### Distribution Plan
[JSON: cuts (one-pager/deck/web/social) + channels (outbound/proposal/ads)]

---

## MCP Tool Integration

| Tool ID | When to Use | Data to Pull | Required |
|---------|-------------|--------------|----------|
| doddle.tool.v1.hubspot.deals | Win validation | Deal value, dates, outcome metrics | no |
| doddle.tool.v1.notion.pages | Asset filing | Approval status, published cuts | no |

If tool unavailable, show ⚠️ NOT AVAILABLE per data-reliability rules. Never fabricate metrics.

---

## Agent Collaboration

| Agent | When to Collaborate | What They Provide |
|-------|--------------------|--------------------|
| researcher | Win validation | Deal + industry context |
| copywriter | Narrative + cuts | Case draft, quotes |
| sales-enabler | Deal usage | Deck slide, proposal insert |

---

## Related Skills

- `b2b-outbound` - Proof for sequences
- `b2b-proposals` - Case appendix for deals
- `sales-enabler` - Collateral + deck library
- `copywriting` - Narrative fundamentals

---

## Questions to Ask

1. Client name + headline metric/timeframe? (or grant HubSpot access?)
2. Logo + numbers approved, who signs off?
3. Where will proof be used first (outbound, proposal, ads, web)?
Pliki w paczce (2)
  • SKILL.md 7 KB
  • blueprint.yaml 1 KB

Wersje

W bazie nie ma innych skilli o nazwie b2b-cases.

Migawka bazy z 13.11.2026 · wersja paczki e00fe15ebe81 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90seedance-testimonial-story
    Generuje prompty wideo z opiniami klientów i dowodem społecznym dla Seedance 2.0 na Higgsfield: historie klientów, case studies i recenzje.
  • 100b2b-case-study-writer
    Pomaga pisać, układać i ulepszać studia przypadku B2B oraz historie sukcesu klientów, dokumentując wyniki programu lub efekty dla klienta.
  • 100ink-case
    Pisze studia przypadku klientów i historie sukcesu: przewodnik wywiadu, struktura opowieści i gotowy do publikacji tekst z metrykami.
  • 100case-study-writer
    Pisze studia przypadków na podstawie mierzonych wyników w Search Console, GA4 lub Google Ads, z każdą liczbą prześledzoną do źródła.
  • 100kai-case-study
    Tworzy studia przypadku klientów z wywiadów lub danych w układzie problem, rozwiązanie, wyniki, z bramkami jakości.
  • 100kai-case-study
    Tworzy studia przypadku klientów z wywiadów lub danych w układzie problem, rozwiązanie, wyniki, z bramkami jakości.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.