CORAA Update: Three Systems in Parallel

CORAA is our in-house reservation and operations system. It replaces our SaaS Peek-Pro, GAPA (former reservations system), and a lot of Google Sheets we used to rely on.

The current reality is that we are still operating three systems in parallel. CORAA handles new bookings; the legacy system is used only for specific special cases and email confirmations; Google Sheets supports specific reporting views.

This is hard. It's taking longer than planned. The reporting layer of CORAA isn't done, which is why the parallel setup exists.

I've reduced my gym training volume significantly in the last 6 months to focus on this transition. Not because I want to, but because the window to get CORAA to a state where we can fully cut over is narrow.

This is the unglamorous part of AI-enabled operations. The transition period is brutal. Everyone at LDK has to hold more context than they should. Our developers are working hard on the reporting layer. Everyone's patience is being tested.

But I'd rather post about this now than celebrate it as a retrospective once it's done. Because the honest version of "we're building in-house tooling" is: three systems running at once, a deadline that keeps sliding, and a founder who's traded gym time for focus time.

Trust is built in this phase, not in the victory lap.

Huge shout-out to the entire team!

---

Originally published on LinkedIn on May 8, 2026.