Quolo.Case Study - A vibe-coded product, rebuilt so the business could run on it
Quolo rebuilt a vibe-coded booking product so the business could run on it, and still looks after the system and the decisions it has to support.
- Client
- Ocean Ops
- Year
- Service
- Rebuild, system design, ongoing technical partnership
Overview
Ocean Ops came in with a product that had already found its niche, and a first version that had been put together quickly. It looked like the thing the business needed. It was not yet something the business could rely on.
The work was a rebuild, not a cleanup of the existing screens. We spent time on the operation before we changed the software. A rebuild that does not know the work just makes a cleaner version of the same gap. The guest conversation, the booking, and the exceptions that show up on the day had to belong to one system. We did not hand back a stack of features and call that a product.
What the client has now is a system the business can keep running as it grows, and a studio that did not step out after the launch. We still maintain the technical side. We also stay in the decisions about what the product should do next. That is the difference from a studio that ships a rebuild and leaves.
What we did
- Studied the operation before touching the code
- Rebuilt the system as one piece of work
- Guest conversation, booking, and day-of exceptions in one product
- Still maintain the technical side
- Still advise on what the product should do next