Skip to content

README.md

Latest commit

 

History

History
56 lines (37 loc) · 2.72 KB

README.md

File metadata and controls

56 lines (37 loc) · 2.72 KB
Raw

Case Studies

Real-world stories from developers who reduced their Claude Code costs using the strategies in this repo.

What Are Case Studies?

Case studies document the full journey of a cost optimization effort: what the project looked like before, what changes were made, and the measurable results after. Unlike tips (which describe a single technique) or benchmarks (which isolate a specific variable), case studies capture the combined effect of multiple optimizations applied to a real project over time.

Good case studies include:

  • Concrete numbers -- actual token counts, dollar amounts, and percentage reductions
  • Context -- project size, tech stack, team size, and how Claude Code was being used
  • Specifics -- exactly which optimizations were applied and in what order
  • Honest assessment -- what worked, what didn't, and any tradeoffs encountered

Published Case Studies

# Title Stack Savings Date
-- Coming soon -- -- --

No case studies have been published yet. Be the first to submit one.

How to Submit a Case Study

There are two ways to contribute:

Option 1: Open an Issue

Use the Case Study Submission issue template. Fill in the prompted fields with your data. The maintainers will review it and, if accepted, convert it into a published case study file.

Option 2: Submit a Pull Request

  1. Copy the TEMPLATE.md file in this directory.
  2. Rename it to something descriptive (e.g., react-saas-app.md or monorepo-migration.md).
  3. Fill in all sections with your data.
  4. Open a PR targeting main. See CONTRIBUTING.md for general PR guidelines.

What Makes a Good Submission

  • Specific numbers over vague claims. "$8.50/day down to $3.20/day" is better than "much cheaper."
  • Before and after data. Include token counts, session costs, or monthly spend for both states.
  • Reproducible details. Describe your setup clearly enough that others with similar projects can apply the same approach.
  • Honest scope. A small but well-documented optimization is more useful than a vague claim of massive savings.

Expected Format

Every case study should follow the structure defined in TEMPLATE.md:

  1. Project Overview -- type, size, stack, team
  2. Before Optimization -- baseline costs and pain points
  3. What Changed -- specific optimizations applied
  4. After Optimization -- new metrics
  5. Results Summary -- savings percentage and implementation effort
  6. Lessons Learned -- what worked, what didn't, advice for others

Tables are preferred for before/after metric comparisons. See the template for the exact layout.