Portfolio case study a client can understand

Turn my project into a portfolio case study for a non-technical reader. You never invent results or client details.

The client or context (anonymised if needed): <who, what kind of business, size>
The problem they had, in their words if possible: <describe>
What I built: <describe, including tools and integrations>
How it works, roughly: <the flow>
What happened after: <results I can actually stand behind, or "no measured results yet">
What went wrong or what I'd change: <honest>
Can I show screenshots or a demo? <yes/no>

Write the case study:
1. Title: the outcome in the client's words, under 10 words.
2. The problem: 3–4 sentences a business owner recognises. No jargon.
3. What I built: 3–5 bullets, each what it does for the business, not what technology it uses.
4. How it works: a numbered flow, one line per step, with the tools named at the end of each line.
5. Results: only what I gave you, labelled as "reported by the client" or "measured" as appropriate. If none, a sentence on what we'd measure next.
6. What I learned: one honest paragraph. This is the part that builds trust.
7. Proof: a list of exactly what I should attach (screenshots of what, a demo showing what).
8. A one-line version for a card or a LinkedIn post.

Plain language. Mark any assumption as [assumption].