case-study-builder
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCase Study Builder
案例研究生成器
Everyone wants social proof. Nobody makes time to create it. You finish a project, the client's happy, you move on — and six months later you're in a sales call with nothing to show.
This skill fixes that. Give me the raw details. I'll produce three formats you can use immediately.
人人都想要社交证明,但没人抽时间去制作。你完成了一个项目,客户很满意,你就转向下一项工作——六个月后你在销售电话上却拿不出任何可展示的成果。
这款Skill可以解决这个问题。给我原始细节,我会生成三种你可以直接使用的格式。
Mode
模式
Detect from context or ask: "Quick writeup, full case study, or full asset package?"
| Mode | What you get | Best for |
|---|---|---|
| 1 format: paragraph summary for proposals | Fast social proof, proposal inserts |
| 3 formats: proposal blurb, social proof pull-quote, sales story | Active pitching, LinkedIn, website |
| 3 formats + blog-ready case study + FAQ variant + campaign assets | Content marketing, SEO, sales enablement |
Default: — use if they say "just need something fast." Use if they want to turn the win into a marketing asset.
standardquickdeep根据上下文识别或者询问用户:"需要简短速记版、完整案例研究版还是完整资产包版?"
| 模式 | 你将获得 | 适用场景 |
|---|---|---|
| 1种格式:适用于提案的段落摘要 | 快速生成社交证明、提案插入内容 |
| 3种格式:提案简介、社交证明引用语、销售故事 | 活跃推广、LinkedIn、官网展示 |
| 3种基础格式 + 可直接发布的博客版案例研究 + FAQ版本 + 营销活动资产 | 内容营销、SEO、销售赋能 |
默认模式: — 如果用户说"只需要快一点的内容"就用模式。如果用户希望将成功案例转化为营销资产就用模式。
standardquickdeepContext Loading Gates
上下文收集门槛
Before generating anything, collect all 8 fields:
| Field | What to Collect |
|---|---|
| 1. Client | Industry, company size/stage, named or anonymized? |
| 2. Before | What was broken or painful? Any numbers? |
| 3. Actions | What did you specifically do? Scope, timeline, role |
| 4. After | REQUIRED: at least one specific number |
| 5. Timeline | How long to achieve the result? |
| 6. Quote | Direct client quote if available |
| 7. Naming | Can we name the client, or must we anonymize? |
| 8. Use case | Where will this be used? (proposals / website / LinkedIn) |
Outcome Extraction Protocol — enforced on Field 4:
If the user says "results were good" or "things improved," stop and ask:
"I need at least one number to make this credible. Pick one:
- Revenue change (e.g., 'closed 3 new clients worth $15K')
- Time saved (e.g., 'cut from 10 hours to 2 hours/week')
- Lead volume (e.g., 'went from 0 to 5 inbound leads/month')
- Rough estimate is fine — it doesn't have to be exact."
Do not draft until Field 4 has at least one number.
生成任何内容之前,请收集齐以下8项信息:
| 字段 | 需要收集的内容 |
|---|---|
| 1. 客户 | 所属行业、公司规模/发展阶段、可公开名称还是需要匿名? |
| 2. 前期状况 | 当时存在什么问题或痛点?有没有相关数据? |
| 3. 执行动作 | 你具体做了什么?服务范围、时间周期、你的角色 |
| 4. 后期成果 | 必填:至少1个具体数字 |
| 5. 时间周期 | 用了多久取得该成果? |
| 6. 客户评价 | 如有客户直接引语请提供 |
| 7. 命名规则 | 我们可以公开客户名称,还是必须匿名处理? |
| 8. 使用场景 | 这些内容将用在哪里?(提案/官网/LinkedIn) |
成果提取规则 — 针对第4项字段强制执行:
如果用户说"结果很好"或者"情况有所改善",停止生成并询问:
"我需要至少一个数字来保证内容的可信度,可以从以下类型选一个提供:
- 收入变化(例如:'新增3个客户,带来1.5万美元收入')
- 节省的时间(例如:'每周耗时从10小时减少到2小时')
- 线索量(例如:'每月 inbound 线索从0增长到5个')
- 粗略估算也可以,不需要完全精确。"
第4项字段没有至少一个数字之前,不要起草任何内容。
Phase 1: Situation Analysis
第一阶段:情况分析
Before drafting, reason through:
- Result strength: Is the outcome a Tier 1 (hard metric), Tier 2 (soft metric), or Tier 3 (proxy)? This determines how confident the language should be.
- Hero check: Is the story told from the client's perspective, or yours? Client = hero, you = guide.
- Tension check: What made this hard? Without a challenge, there's no story — just a list.
- Format match: Which use case did they specify? That determines which format to optimize.
Tier system for results language:
| Tier | Type | Example | Language |
|---|---|---|---|
| 1 | Hard metric | "Revenue +40%" | State directly |
| 2 | Soft metric | "Team finally aligned" | "For the first time in years..." |
| 3 | Proxy metric | "Enabled Series A close" | "Contributed to..." |
| 4 | Directional | "Noticeable improvement" | "Significant improvement in..." |
起草内容之前,先梳理清楚以下几点:
- 成果强度: 产出的成果属于层级1(硬指标)、层级2(软指标)还是层级3( proxy 指标)?这将决定表述的笃定程度。
- 主角核查: 故事是从客户视角还是你的视角讲述?客户=主角,你=引导者。
- 冲突核查: 这个项目的难点是什么?没有挑战就没有故事,只是一份清单。
- 格式匹配: 用户指定的使用场景是什么?这将决定优化的格式方向。
成果表述的层级体系:
| 层级 | 类型 | 示例 | 表述方式 |
|---|---|---|---|
| 1 | 硬指标 | "营收+40%" | 直接陈述 |
| 2 | 软指标 | "团队终于达成对齐" | "多年来首次..." |
| 3 | proxy 指标 | "助力完成A轮融资" | "为...做出了贡献" |
| 4 | 方向性指标 | "有明显改善" | "在...方面有显著提升" |
Phase 2: The Hero Principle
第二阶段:主角原则
The client is the hero. You are the guide.
Before writing, flip the framing:
❌ Wrong: "I built a content system that generated leads."
✅ Right: "Sarah went from scrambling to fill her pipeline to getting 3 inbound inquiries per week — all from a content system we built in 6 weeks."
Every format should be written from what the CLIENT experienced, not what YOU delivered.
客户是主角,你是引导者。
写作之前,先调整表述框架:
❌ 错误:"我搭建了一套内容系统,带来了很多线索。"
✅ 正确:"Sarah 再也不用为填充销售管道发愁,现在每周能获得3个主动咨询——全部来自我们花6周搭建的内容系统。"
所有格式的内容都要从客户的体验角度撰写,而不是从你交付了什么的角度。
Phase 3: Generate Three Formats
第三阶段:生成三种格式
Format 1: Two-Liner (Proposals & Bios)
格式1:两行式(用于提案和个人简介)
Formula:
[What was done] + [scale/scope] + [for who] + [result or timeframe][Strong action verb] [what was delivered] for [specific client descriptor].
[Outcome metric] in [timeframe].Example:
Built a full content system for a Series B SaaS founder with no marketing team. 0 to 3 inbound leads/week in 6 weeks.
公式:
[完成的动作] + [规模/范围] + [服务对象] + [成果或时间周期][Strong action verb] [what was delivered] for [specific client descriptor].
[Outcome metric] in [timeframe].示例:
为没有营销团队的B轮SaaS创始人搭建了完整的内容系统。 6周内实现每周 inbound 线索从0到3的增长。
Format 2: Story Version (LinkedIn & Sales Calls)
格式2:故事版(用于LinkedIn和销售电话)
Structure — 4 paragraphs, 150–250 words:
**Set the scene:** [Their situation when you arrived — 2-3 sentences with stakes]
**Show the complexity:** [What made this hard — 2-3 sentences]
**What happened:** [Specific actions taken — no feature lists, just moves]
**What changed:** [Outcome — the number + the transformation]结构 — 4段,150-250词:
**Set the scene:** [Their situation when you arrived — 2-3 sentences with stakes]
**Show the complexity:** [What made this hard — 2-3 sentences]
**What happened:** [Specific actions taken — no feature lists, just moves]
**What changed:** [Outcome — the number + the transformation]Format 3: Full Case Study (Website & Portfolio)
格式3:完整案例研究(用于官网和作品集)
markdown
undefinedmarkdown
undefinedCase Study: [Client Name or Descriptor]
Case Study: [Client Name or Descriptor]
The Challenge
The Challenge
[2-3 paragraphs: situation, stakes, what wasn't working]
[2-3 paragraphs: situation, stakes, what wasn't working]
The Approach
The Approach
[Phases or steps — what happened and in what order]
[Phases or steps — what happened and in what order]
The Results
The Results
[Metrics, before/after comparison, named outcomes]
[Metrics, before/after comparison, named outcomes]
Key Details
Key Details
- Client: [Named or "A [descriptor] company"]
- Industry: [Sector]
- Timeline: [Duration]
- Scope: [What was delivered]
- Client: [Named or "A [descriptor] company"]
- Industry: [Sector]
- Timeline: [Duration]
- Scope: [What was delivered]
What Made This Different
What Made This Different
[Unique angle, unexpected obstacle, or pivotal insight]
[Unique angle, unexpected obstacle, or pivotal insight]
Client Quote
Client Quote
"[Testimonial — or placeholder if not yet collected]" — [Name], [Title]
---"[Testimonial — or placeholder if not yet collected]" — [Name], [Title]
---Phase 4: Self-Critique Pass (REQUIRED)
第四阶段:自我校验环节(必填)
After generating all three formats, evaluate:
Two-liner:
- Does it have a specific number? (Not "improved results" — a real metric)
- Is it 2 sentences or fewer?
- Would someone scanning a proposal stop and read it?
Story version:
- Is the client the hero (not the author)?
- Is there genuine tension — something that made this hard?
- Does the closing paragraph include the key metric?
Full case study:
- Does the Results section lead with numbers?
- Is the Challenge section specific enough that a similar prospect recognizes their situation?
- Is the client quote (or placeholder) present?
Flag any failure: "The story version has no tension — add one obstacle or unexpected challenge before the 'What happened' paragraph."
生成所有三种格式之后,评估以下内容:
两行式:
- 是否包含具体数字?(不是"成果提升"这种模糊表述,而是真实的指标)
- 是否不超过2句话?
- 扫读提案的人会不会停下来看这段内容?
故事版:
- 客户是不是主角(而不是作者)?
- 是否有真实的冲突点——也就是项目的难点?
- 结尾段落是否包含核心指标?
完整案例研究:
- 成果部分是不是以数字开头?
- 挑战部分是不是足够具体,能让同类潜在客户认出自己的处境?
- 是否有客户评价(或占位符)?
任何不满足的情况都要标记: "故事版没有冲突点——在'发生了什么'段落之前添加一个障碍或意外挑战。"
Phase 5: Distribution Plan
第五阶段:分发方案
| Format | Best locations | When to use |
|---|---|---|
| Two-liner | Proposals, email bios, LinkedIn About section | Any sales context |
| Story | LinkedIn post, podcast intros, sales call opener | Weekly content |
| Full case study | Website portfolio page, PDF download, RFP response | Late-stage buyer research |
| 格式 | 最佳发布位置 | 使用时机 |
|---|---|---|
| 两行式 | 提案、邮件签名、LinkedIn 个人简介部分 | 任何销售场景 |
| 故事版 | LinkedIn 帖子、播客介绍、销售电话开场 | 每周内容输出 |
| 完整案例研究 | 官网作品集页面、PDF 下载素材、RFP 响应 | 买家决策后期调研阶段 |
Output Structure
输出结构
markdown
undefinedmarkdown
undefinedCase Study: [Client Descriptor] — [Date]
Case Study: [Client Descriptor] — [Date]
Situation Summary
Situation Summary
[2-sentence analysis from Phase 1]
Result tier: [1/2/3/4]
[2-sentence analysis from Phase 1]
Result tier: [1/2/3/4]
Format 1: Two-Liner
Format 1: Two-Liner
[Final copy]
[Final copy]
Format 2: Story Version
Format 2: Story Version
[Final copy]
[Final copy]
Format 3: Full Case Study
Format 3: Full Case Study
[Full markdown]
[Full markdown]
Self-Critique Notes
Self-Critique Notes
- Two-liner: [pass/issue]
- Story: [pass/issue]
- Full: [pass/issue]
- Two-liner: [pass/issue]
- Story: [pass/issue]
- Full: [pass/issue]
Distribution Plan
Distribution Plan
[Where to use each]
[Where to use each]
Next Step
Next Step
[If no quote collected → run testimonial-collector]
[If strong story → suggest LinkedIn post from story format]
---
**Cross-reference:** If a client quote was captured here, run `testimonial-collector` to properly format and score it for your testimonial library.
---
*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*[If no quote collected → run testimonial-collector]
[If strong story → suggest LinkedIn post from story format]
---
**交叉参考:** 如果在此处收集到了客户引语,请运行 `testimonial-collector` 来对其进行标准化格式处理并打分,存入你的推荐语料库。
---
*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*