case-study-writing
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCase Study Writing
B2B案例研究撰写
Create compelling B2B case studies with research and visuals via inference.sh CLI.
通过inference.sh CLI工具,结合调研与可视化内容创作有说服力的B2B案例研究。
Quick Start
快速开始
bash
curl -fsSL https://cli.inference.sh | sh && infsh loginbash
curl -fsSL https://cli.inference.sh | sh && infsh loginResearch the customer's industry
调研客户所在行业情况
infsh app run tavily/search-assistant --input '{
"query": "SaaS customer onboarding challenges 2024 statistics"
}'
undefinedinfsh app run tavily/search-assistant --input '{
"query": "SaaS客户入职流程挑战2024统计数据"
}'
undefinedThe STAR Framework
STAR框架
Every case study follows: Situation -> Task -> Action -> Result
| Section | Length | Content | Purpose |
|---|---|---|---|
| Situation | 100-150 words | Who the customer is, their context | Set the scene |
| Task | 100-150 words | The specific challenge they faced | Create empathy |
| Action | 200-300 words | What solution was implemented, how | Show your product |
| Result | 100-200 words | Measurable outcomes, before/after | Prove value |
Total: 800-1200 words. Longer loses readers. Shorter lacks credibility.
每份案例研究均遵循:情境(Situation)→ 任务(Task)→ 行动(Action)→ 结果(Result)
| 章节 | 篇幅 | 内容 | 目的 |
|---|---|---|---|
| 情境 | 100-150词 | 客户身份、业务背景 | 搭建故事场景 |
| 任务/挑战 | 100-150词 | 客户面临的具体难题 | 引发读者共情 |
| 行动/解决方案 | 200-300词 | 落地的解决方案及实施方式 | 展示产品价值 |
| 结果 | 100-200词 | 可量化的成果、前后对比 | 证明实际价值 |
总篇幅:800-1200词。过长会流失读者,过短缺乏可信度。
Structure Template
结构模板
1. Headline (Lead with the Result)
1. 标题(以成果为核心)
❌ "How Company X Uses Our Product"
❌ "Company X Case Study"
✅ "How Company X Reduced Onboarding Time by 60% with [Product]"
✅ "Company X Grew Revenue 340% in 6 Months Using [Product]"The headline should be specific, quantified, and state the outcome.
❌ "X公司如何使用我们的产品"
❌ "X公司案例研究"
✅ "X公司如何通过[产品]将入职时间缩短60%"
✅ "X公司借助[产品]在6个月内实现营收340%增长"标题需具体、量化,明确展示成果。
2. Snapshot Box
2. 快照信息框
Place at the top for skimmers:
┌─────────────────────────────────────┐
│ Company: Acme Corp │
│ Industry: E-commerce │
│ Size: 200 employees │
│ Challenge: Manual order processing │
│ Result: 60% faster fulfillment │
│ Product: [Your Product] │
└─────────────────────────────────────┘放置在顶部供快速浏览:
┌─────────────────────────────────────┐
│ 公司:Acme Corp │
│ 行业:电子商务 │
│ 规模:200名员工 │
│ 挑战:手动订单处理 │
│ 成果:履约效率提升60% │
│ 使用产品:[你的产品] │
└─────────────────────────────────────┘3. Situation
3. 情境
- Who is the customer (industry, size, location)
- What relevant context existed before the problem
- 1-2 sentences of company background
- 客户基本信息(行业、规模、地域)
- 问题出现前的相关业务背景
- 1-2句公司简介
4. Task / Challenge
4. 任务/挑战
- Quantify the pain: "spending 40 hours/week on manual data entry" not "had data problems"
- Show stakes: what would happen if unsolved (lost revenue, churn, missed deadlines)
- Include a customer quote about the frustration
- 量化痛点:用“每周花费40小时处理手动数据录入”替代“存在数据问题”
- 明确影响:说明问题未解决的后果(营收损失、客户流失、错过截止日期)
- 加入客户关于痛点的引用
5. Action / Solution
5. 行动/解决方案
- What was implemented (your product/service)
- Timeline: "deployed in 2 weeks" / "3-month rollout"
- Key decisions or configurations
- Why they chose you over alternatives (briefly)
- 2-3 specific features that addressed the challenge
- 落地的具体方案(你的产品/服务)
- 实施周期:“2周内部署” / “3个月逐步推广”
- 关键决策或配置细节
- 简要说明客户选择你的原因(对比竞品)
- 2-3个解决核心痛点的具体功能
6. Results
6. 结果
- Before/after metrics — always quantified
- Timeframe — "within 3 months" / "in the first quarter"
- Unexpected benefits beyond the original goal
- Customer quote about the outcome
- 前后对比数据 — 始终量化呈现
- 时间周期 — “3个月内” / “第一季度内”
- 超出初始目标的额外收益
- 客户关于成果的引用
Metrics That Matter
关键指标呈现
How to Present Numbers
数据展示方式
❌ "Improved efficiency"
❌ "Saved time"
❌ "Better results"
✅ "Reduced processing time from 4 hours to 45 minutes (81% decrease)"
✅ "Increased conversion rate from 2.1% to 5.8% (176% improvement)"
✅ "Saved $240,000 annually in operational costs"❌ "提升了效率"
❌ "节省了时间"
❌ "取得了更好的结果"
✅ "处理时间从4小时缩短至45分钟(减少81%)"
✅ "转化率从2.1%提升至5.8%(增长176%)"
✅ "每年节省运营成本24万美元"Metric Categories
指标分类
| Category | Examples |
|---|---|
| Time | Hours saved, time-to-completion, deployment speed |
| Money | Revenue increase, cost reduction, ROI |
| Efficiency | Throughput, error rate, automation rate |
| Growth | Users gained, market expansion, feature adoption |
| Satisfaction | NPS change, retention rate, support tickets reduced |
| 分类 | 示例 |
|---|---|
| 时间 | 节省时长、完成周期、部署速度 |
| 成本 | 营收增长、成本降低、投资回报率(ROI) |
| 效率 | 吞吐量、错误率、自动化率 |
| 增长 | 用户增长、市场拓展、功能使用率 |
| 满意度 | NPS变化、留存率、支持工单减少量 |
Data Visualization
数据可视化
bash
undefinedbash
undefinedGenerate a before/after comparison chart
生成前后对比图表
infsh app run infsh/python-executor --input '{
"code": "import matplotlib.pyplot as plt\nimport matplotlib\nmatplotlib.use("Agg")\n\ncategories = ["Processing Time", "Error Rate", "Cost per Order"]\nbefore = [4, 12, 8.50]\nafter = [0.75, 1.5, 2.10]\n\nfig, ax = plt.subplots(figsize=(10, 6))\nx = range(len(categories))\nwidth = 0.35\nax.bar([i - width/2 for i in x], before, width, label="Before", color="#ef4444")\nax.bar([i + width/2 for i in x], after, width, label="After", color="#22c55e")\nax.set_ylabel("Value")\nax.set_xticks(x)\nax.set_xticklabels(categories)\nax.legend()\nax.set_title("Impact of Implementation")\nplt.tight_layout()\nplt.savefig("results-chart.png", dpi=150)\nprint("Chart saved")"
}'
undefinedinfsh app run infsh/python-executor --input '{
"code": "import matplotlib.pyplot as plt\nimport matplotlib\nmatplotlib.use("Agg")\n\ncategories = ["Processing Time", "Error Rate", "Cost per Order"]\nbefore = [4, 12, 8.50]\nafter = [0.75, 1.5, 2.10]\n\nfig, ax = plt.subplots(figsize=(10, 6))\nx = range(len(categories))\nwidth = 0.35\nax.bar([i - width/2 for i in x], before, width, label="Before", color="#ef4444")\nax.bar([i + width/2 for i in x], after, width, label="After", color="#22c55e")\nax.set_ylabel("Value")\nax.set_xticks(x)\nax.set_xticklabels(categories)\nax.legend()\nax.set_title("Impact of Implementation")\nplt.tight_layout()\nplt.savefig("results-chart.png", dpi=150)\nprint("Chart saved")"
}'
undefinedCustomer Quotes
客户引用
What Makes a Good Quote
优质引用标准
❌ "We love the product." (vague, could be about anything)
❌ "It's great." (meaningless)
✅ "We went from processing 50 orders a day to 200, without adding a single person to the team."
— Sarah Chen, VP Operations, Acme Corp
✅ "Before [Product], our team dreaded Monday mornings because of the report backlog.
Now it's automated and they can focus on actual analysis."
— Marcus Rodriguez, Head of Analytics, DataCo❌ "我们喜欢这个产品。"(模糊,适用于任何场景)
❌ "它很棒。"(无实际意义)
✅ "我们的日订单处理量从50单提升至200单,且未新增任何团队人员。"
—— Sarah Chen,Acme Corp运营副总裁
✅ "在使用[产品]之前,团队每个周一都要面对堆积的报告,苦不堪言。现在报告实现自动化,他们可以专注于真正的分析工作。"
—— Marcus Rodriguez,DataCo analytics主管Quote Placement
引用放置位置
- 1 quote in the Challenge section — about the frustration/pain
- 1-2 quotes in the Results section — about the outcome/transformation
- Always attribute: full name, title, company
- 挑战章节1处引用 — 关于痛点与困扰
- 成果章节1-2处引用 — 关于成果与转变
- 始终标注:全名、职位、公司
Quote Formatting
引用格式
markdown
> "We went from processing 50 orders a day to 200, without adding anyone to the team."
>
> — Sarah Chen, VP Operations, Acme Corpmarkdown
> "我们的日订单处理量从50单提升至200单,且未新增任何团队人员。"
>
> —— Sarah Chen,Acme Corp运营副总裁Research Support
调研支持
Finding Industry Context
行业背景调研
bash
undefinedbash
undefinedIndustry benchmarks
行业基准数据
infsh app run tavily/search-assistant --input '{
"query": "average e-commerce order processing time industry benchmark 2024"
}'
infsh app run tavily/search-assistant --input '{
"query": "2024年电子商务订单处理时长行业基准"
}'
Competitor landscape
竞品格局
infsh app run exa/search --input '{
"query": "order management automation solutions market overview"
}'
infsh app run exa/search --input '{
"query": "订单管理自动化解决方案市场概况"
}'
Supporting statistics
支撑数据
infsh app run exa/answer --input '{
"question": "What percentage of e-commerce businesses still use manual order processing?"
}'
undefinedinfsh app run exa/answer --input '{
"question": "仍在使用手动订单处理的电商企业占比多少?"
}'
undefinedDistribution Formats
多渠道分发格式
| Format | Where | Notes |
|---|---|---|
| Web page | /customers/ or /case-studies/ | Full version, SEO-optimized |
| Sales team, email attachment | Designed, downloadable, gated optional | |
| Slide deck | Sales calls, presentations | 5-8 slides, visual-heavy |
| One-pager | Trade shows, quick reference | Snapshot + key metrics + quote |
| Social post | LinkedIn, Twitter | Key stat + quote + link to full |
| Video | Website, YouTube | Customer interview or animated |
| 格式 | 分发渠道 | 注意事项 |
|---|---|---|
| 网页 | /customers/ 或 /case-studies/ | 完整版,适配SEO |
| 销售团队、邮件附件 | 专业排版,可下载,可选 gated(需留资获取) | |
| 幻灯片 | 销售沟通、演示场景 | 5-8页,侧重可视化 |
| 单页简报 | 展会、快速参考 | 快照+核心指标+引用 |
| 社交媒体帖文 | LinkedIn、Twitter | 核心数据+引用+完整版链接 |
| 视频 | 官网、YouTube | 客户访谈或动画形式 |
Social Media Snippet
社交媒体片段示例
Headline stat + brief context + customer quote + CTA
Example:
"60% faster order processing.
Acme Corp was drowning in manual fulfillment. 4 hours per batch. 12% error rate.
After implementing [Product]: 45 minutes per batch. 1.5% errors.
'We went from 50 orders a day to 200 without adding headcount.' — Sarah Chen, VP Ops
Read the full story → [link]"核心数据 + 简短背景 + 客户引用 + 行动号召
示例:
"订单处理效率提升60%。
Acme Corp曾深陷手动履约困境:每批订单耗时4小时,错误率12%。
使用[产品]后:每批订单耗时45分钟,错误率1.5%。
'我们的日订单处理量从50单提升至200单,且未新增任何团队人员。' —— Sarah Chen,运营副总裁
阅读完整故事 → [链接]"Writing Checklist
撰写检查清单
- Headline leads with the quantified result
- Snapshot box with company, industry, challenge, result at top
- Challenge is quantified, not vague
- 2-3 specific customer quotes with attribution
- Before/after metrics with timeframe
- 800-1200 words total
- Skimmable (headers, bold, bullet points)
- Customer approved the final version
- Visual: at least one chart or before/after comparison
- 标题以量化成果为核心
- 顶部包含公司、行业、挑战、成果的快照信息框
- 挑战已量化,而非模糊描述
- 2-3个带标注的具体客户引用
- 带时间周期的前后对比数据
- 总篇幅800-1200词
- 内容易读(标题、加粗、项目符号)
- 最终版本已获客户确认
- 包含至少1个图表或前后对比可视化内容
Common Mistakes
常见误区
| Mistake | Problem | Fix |
|---|---|---|
| No specific numbers | Reads like marketing fluff | Quantify everything |
| All about your product | Reads like a sales pitch | Story is about the CUSTOMER |
| Generic quotes | No credibility | Get specific, attributed quotes |
| Missing the "before" | No contrast to show impact | Always show the starting point |
| Too long | Loses reader attention | 800-1200 words max |
| No customer approval | Legal/relationship risk | Always get sign-off |
| 误区 | 问题 | 解决方法 |
|---|---|---|
| 无具体数据 | 读起来像营销空话 | 所有内容尽量量化 |
| 过度聚焦自家产品 | 读起来像销售话术 | 故事核心是客户,而非产品 |
| 通用化引用 | 缺乏可信度 | 获取具体、带标注的引用 |
| 缺少“之前”的数据 | 无法体现实际价值 | 始终展示初始状态 |
| 篇幅过长 | 流失读者注意力 | 控制在800-1200词以内 |
| 未获客户确认 | 存在法律/合作风险 | 始终获取客户签字确认 |
Related Skills
相关技能
bash
npx skills add inference-sh/skills@web-search
npx skills add inference-sh/skills@prompt-engineeringBrowse all apps:
infsh app listbash
npx skills add inference-sh/skills@web-search
npx skills add inference-sh/skills@prompt-engineering浏览全部应用:
infsh app list