Your case study
Verified proof on MitHub
In this video
Everything the video says.
Lesson 1From knowledge to a specific solution
Reality
You now know how to follow the money, diagnose, prove value and operate.
The problem
Knowledge is not a solution. Companies pay for a specific answer to their specific problem.
What it costs
General advice gets polite nods and no contract.
The idea
Turn everything you learned into one concrete solution: this problem, this system, this expected result.
How to do it
- State the problem with its number, from your diagnosis.
- Describe the system you will build, in plain words.
- Say what result you expect, how you will measure it and when.
Example
"Inquiries wait two days for a first call. We will build an automatic first contact within minutes, and measure how many become conversations in 30 days."
Your turn
Write your specific solution in three sentences: problem, system, expected result.
Lesson 2What a case study looks like
Reality
Most "case studies" are testimonials full of adjectives.
The problem
"Great service, highly recommended" proves nothing about what you can do.
What it costs
Without a structure, your best work reads like everyone else's.
The idea
A real case study tells the same story as this course: situation, path, result — with numbers.
How to do it
- The situation: the company, the problem and what it was costing.
- The path: the diagnosis, the system you built and the iterations.
- The result: the number before, the number after, and the time it took.
- The evidence: data, screenshots, and the client's own words.
Example
"A business with several locations was answering inquiries after two days. After the diagnosis we built automatic first contact. In 30 days, more inquiries became conversations — here is the before and after."
Your turn
Draft the outline of your case study using the four parts above.
Lesson 3How a case study gets published on MitHub
Reality
On MitHub, a case study is not a document you write alone. It is proof that has been verified.
The problem
Anyone can claim a result. Companies have learned not to believe claims.
What it costs
An unverified case study hurts you and everyone else on MitHub.
The idea
A case study is only real and visible on MitHub when every step of the chain is met.
How to do it
- In some cases, the client also records a video testimonial. Not always.
- If any step is missing, it is not published.
Example
A company hires you, you deliver the system, we audit the work internally, the company confirms it is satisfied and agrees to publish — and your case study goes live on MitHub.
Your turn
Look at your draft case study. Which steps of the chain does it already meet, and which are still missing?
What the video doesn't have time for.
Why a verified case study beats a CV
A CV says what you know. A verified case study shows what you did, for whom, and what changed — and someone other than you confirms it. That is the proof companies believe.
The four parts, with the questions to answer
- The situation: who was the company, what was broken, and what was it costing?
- The path: what did the diagnosis show, what did you build, and how did you iterate?
- The result: the number before, the number after, and how long it took.
- The evidence: data, screenshots and the client's own words.
How it gets published on MitHub
If any step is missing, it is not published. Sometimes the client also records a short video testimonial — not always.
Common mistakes
- Adjectives instead of numbers: "great results" proves nothing.
- Naming a client or sharing data without their permission.
- Hiding what did not work. The iterations are part of the proof.
What to do next
Draft your case study while the project is still running. Keep the before number, the iteration log and the client's words as you go — writing it at the end is much harder.
Your specific solution, written as a case study ready to be verified.