Projects where the numbers measurably moved
Every case study states the starting point, my role and the outcome — and cites a source for every figure. What cannot be evidenced is not listed here.
Why a photographer stayed invisible despite having an SEO plugin
Malex Fotografie had an SEO plugin, nine city landing pages and almost no local visibility. The cause was not marketing but the foundation: two plugins cancelling each other out, every section written into the HTML three times, and city pages that were copies of the homepage. Rebuilt across twelve stages and roughly 50 hours, with measurable results.
- 8.3 s → under 2.5 sLargest Contentful Paint, mobile (field)
- 11.6 s → 7 sLargest Contentful Paint, mobile (lab)
- 77 → 12 occurrences (−84%)display:none dead weight in homepage markup
Getting a one-person SaaS through the WordPress.org review
AudioLinter checks podcast and spoken-word recordings against the EBU R128 loudness standard and repairs them in one click — inside the WordPress editor. Behind it sit eight services in production and 36 shipped releases. The hardest part was not the audio processing but the official plugin directory review.
- 36Releases shipped
- 8Services in production
- 140Test files
Throwing away four months of my own work — and why it was right
Rackd is a tournament platform where nobody has to install anything. Two discarded attempts as a Flutter app came first. On 11 June 2026 I wrote down the reasoning for abandoning my own codebase and starting over. This case study is about the decision, not the result.
- ~90Flutter files discarded at the decision
- 384Commits in the rebuild
- 52Commits in the discarded predecessor
A course platform with payments, protected video, and an audit against myself
Faszienyoga mit Melanie sells online courses directly to participants — with checkout, protected video delivery and customer data under the GDPR. Four weeks after launch I audited the running system and found three issues I had built myself.
- 125Commits
- 22,640Lines of TypeScript
- 40Test files
When the same manual work comes back every week
Estate agencies maintain their properties in specialist software and then a second time on their own website. ImmoSync reads the standard export files those programs produce and keeps the website in sync automatically — each job in its own container that disappears afterwards.
- 382Commits
- 3Deployment variants
- On every mergeAutomated deployments