Cover video generated by Seedance 2.0 on Lovart.

Two fully functional booking modules shipped in two weeks as part of an ongoing retainer. Dining reservations and hotel accommodations, both live, both wired to a non-technical admin portal, both handling the kind of business logic that only comes from 27 years of operating in a very specific niche.

If your platform has real business logic behind it and your team needs a reliable partner to keep building, that is what this kind of engagement is built for. Find me on Contra or reach out at andres@redmage.cc.

Cuba Travel Services has been helping US travelers get to Cuba legally since 1999. They are a licensed, OFAC-compliant travel operator handling visas, accommodation, transfers, tours, and dining through a single booking platform, with Florida and California Seller of Travel registrations and over two decades of operational history behind them.

Michael and Lisa Zuccato run two companies simultaneously, Cuba Travel Services and a separate visa operation, with a small IT team split across both. Red Mage came in as an embedded technical partner to give that team the bandwidth to keep building without bottlenecks. The platform itself started in Lovable and lives in Supabase, and the day-to-day development work happens through Claude Code and GitHub.

The first two weeks of the engagement covered two modules: dining and accommodations.

Dining came first. The module needed a full reservation flow with an admin-facing editor, publish and delete controls, CSV export, auto-computed pricing, and cutoff logic. That last piece mattered: if a reservation falls within the cutoff window and is already in a customer's cart, the cart blocks checkout rather than letting the booking go through. Getting that behavior right required careful coordination between the reservation logic, the cart state, and the checkout flow.

Accommodations was the more complex of the two. Cuba Travel Services books hotels with two distinct pricing models: full property buyouts and per-room rates. Those are not the same thing, and the system has to handle both cleanly. On top of that, the module needed stop-sale functionality so staff can block specific date ranges for specific rooms when inventory is unavailable. Stop-sold rooms show as unavailable on the property detail page and are hard-blocked at the cart and checkout level, not just visually greyed out.

The accommodations build also included an occupancy-based pricesheet editor, a search experience with persisted state across pages, check-in and check-out time handling, a full-house confirmation dialog for buyout bookings, and email confirmations that surface all the relevant stay details. Rate data was migrated from the legacy OpenCart system and run through a parity check against the source export.

Both modules are fully manageable by non-technical staff through the admin portal. No code required to update rates, toggle availability, or manage inventory.

This is an ongoing partnership, not a one-time project. The dining and accommodations modules represent just the first two weeks of a monthly retainer. Red Mage operates as an extension of the CTS technical team, handling feature work, module builds, and the kind of detailed logic review that a team stretched across two companies does not always have capacity for. The goal is not to own the platform but to make sure it keeps moving forward.

If your platform has real business logic behind it and your team needs a reliable partner to keep building, that is what this kind of engagement is built for. Find me on Contra or reach out at andres@redmage.cc.