Skip to content
03 / CASE STUDIES

Three systems.
Three unknown variables.

Real cases from our practice, anonymized. What happens when software has been built but nobody is responsible for running it – and what it takes to make it run.

Closed padlock on a dark background
Photo: Kedibone Isaac Makhumisane / Unsplash
RTT / SYSTEM FILE 001● OPEN → ● SECURED
Business Operations · Dashboard

The numbers were confidential. The address wasn't.

A self-built dashboard with all KPIs and OKRs – visible to anyone who knew the address.

Open file →
Three people learning together on laptops
Photo: Brooke Cagle / Unsplash
RTT / SYSTEM FILE 002● SINGLE SERVER → ● SCALABLE
Education · Learning platform

The AI set it up. We made it scalable.

A Moodle platform, set up by an AI, moves from a single server to a Kubernetes cluster.

Open file →
Hand holding a smartphone in the dark
Photo: Gilles Lambert / Unsplash
RTT / SYSTEM FILE 003● INCOMPLETE → ● READY
Mobile app · Vibe coding

The app was finished. Almost.

A vibe-coded app without a backend, without sync between devices, without hosting and without a way into the stores.

Open file →
RTT / NEXT STEP

Building it isn't running it.

We review first, before we take on responsibility.

Request an Operations Check ↗