This is a format example, not real client work. It exists so you can see how our case studies are structured. It will be replaced with an actual project. See
docs/CONTENT.mdfor how to write a real one.
The challenge
Describe what was broken, in the client's own terms, and what it was costing them. Concrete beats abstract: "customers were abandoning the checkout on mobile" is better than "the site underperformed."
State the business impact if you know it. A slow site is a technical fact; lost orders are a business problem, and that's what the reader is worried about.
Our approach
Explain what you considered and what you ruled out — including the option you didn't take and why. This is the most valuable section and the one most agencies skip, because it's the part that shows judgement rather than just output.
If you recommended something cheaper than what they asked for, say so. That is a selling point.
What we built
Be specific. Name the real tools and the real decisions. Vague summaries here read as though there wasn't much to describe.
The outcome
Measured results, and only numbers you can substantiate. If you don't have metrics, describe what changed qualitatively — "their team stopped tracking orders in a spreadsheet" is a real, useful outcome.
Never invent a number. An honest qualitative result beats a fabricated percentage, and the clients most able to pay are the ones most likely to check.
Built with
- Next.js
- Shopify
- Vercel