🧪 Case Study¶
Learn from what already happened: your competitors' choices, other founders' public stories, and your own experiments.
| Skill | What you get | Level | Time |
|---|---|---|---|
| case-study-competitor-teardown | Learn from the enemy: 3 competitors torn down with free tools, then a Copy / Beat / Avoid list | Intermediate | 2–3 h |
| case-study-success-story-analysis | 5 comparable successes and 2 failures, bias-checked, then 3 tactics to try this month | Beginner | 60–90 min |
| case-study-award-winning-design | Design patterns shared by Apple Design Award, App Store, Google Play Best of and Product Hunt winners, checked against growth signals, then a 3-pattern apply plan | Intermediate | 2–3 h |
| case-study-write-your-own | Your results as an honest one-page case study, ready to share or contribute | Beginner | 45–60 min |
Suggested order: competitor teardown → success stories → award-winning design (when you redesign onboarding, a paywall, the store page or a launch page) → (run your own experiment) → write your own case study.
Read real ones: finished teardowns live in case-study/ at the repo root.
Share your case study. Real numbers from real products are the most valuable thing in this repo. Follow case-study-write-your-own and open a pull request or an issue.
📖 Tip: keep teardowns and case studies as Markdown in your research folder, and open them in Markdown Everywhere (free, Mac, made by the maintainer) to see how they link to your notes and decisions.