// case studies
Selected work.
A small list. We work on three projects per quarter, so the list doesn’t grow fast. Each one is real, named where the client lets us, anonymized where they don’t.
rot8 selected work is a curated set of engineering case studies — fintech, marketplace, consumer, and native mobile products built by our senior team for startups and product teams across Europe. We anonymize clients by default, with stage and raise context, and use real names only when the client signs off in writing.
// the cases
Studies.
- 01case study
Pivoting from web-app to native Mac + Windows in 2 months
- Problem
- Client's board ratified a feature set the existing web-app couldn't deliver inside the browser's runtime ceiling.
- Outcome
- Native Mac and Windows applications shipped in 8 weeks, sharing one core layer with the existing back-end. All four board-committed features shipped at full fidelity.
- Custom software
- Native desktop
- 8 weeks
- Series A
- 02coming soon
Native iOS launch for a consumer health Series A
- Problem
- Consumer health app launch with hard App Store milestone.
- Outcome
- Coming soon.
- Consumer health
- Native iOS
- Series A
- 03coming soon
Embedded engineering pod for a marketplace seed-stage scale-up
- Problem
- Roadmap exceeded hiring capacity at a fast-moving marketplace.
- Outcome
- Coming soon.
- Marketplace
- Embedded team
- Seed
// why anonymized
The shape is what matters. The brand is decoration.
Most of our clients are pre-Series-B startups for whom the existence of a partner studio is competitively sensitive. We default to anonymized case studies — “European Series A fintech, $12M raised” — because that's what serves clients best. When a client wants their name on a study, we use it; that decision belongs to them, not us.
What we never anonymize
- The shape of the problem
- The technical work we did
- The outcome and the metrics
- The timeline and engagement model
// aggregates
Engagement breakdown across all shipped work.
// how to read these
Each study follows the same shape so you can compare.
- The problem — what was broken, what was at stake, what the deadline was.
- The shape of the engagement — which service shape we ran (Sprint / Ship / Embed / Rescue), team composition, timeline.
- The technical work — architecture decisions, key tradeoffs, stack choices, integrations. Real engineering detail, not “we used React.”
- The outcome — shipped product, business metric, what the client did with the result.
- The handoff — how the engagement ended, what the client owned at the end.
// next step
Three projects this quarter. Two remain.
Apply with the four-step form. We respond inside 48 hours, every time, with a real reply from a named founder.