Case study · VoyazioIn development
Nine modules, one backbone, adopted one piece at a time
Designing travel infrastructure that a small operator can adopt in a single module and a franchise network can white-label entirely, without maintaining two products.
Context
What existed
before this.
Travel operators with genuine expertise are invisible online. The stack they need, from website and booking to CRM, messaging automation and payments, costs more than the business can justify, so they keep running on WhatsApp forwards and PDF itineraries while search results send customers to an OTA.
The problem, as constraints
- A monolithic platform is unsellable to an operator who only wants a website today.
- Nine independently useful modules over a shared backend risks nine divergent codebases.
- White-label partners need the backend to be invisible without a separate build.
Approach
How we
built it.
The shape of the solution, described at the level a reviewing engineer could argue with.
Each module owns its own surface but shares tenancy, identity, and billing, so adoption can start anywhere in the stack.
The rendering layer is separated from the backend, which is what makes white-label a configuration rather than a fork.
Modules ship on independent timelines and are labelled by real readiness rather than marketed as complete.
Everything is travel-native by default instead of generic SaaS bent into the shape of the industry.
Decision records
Every call,
with what we rejected.
These are the calls that shaped the product, each with the option we turned down and the reasoning that decided it. Where one has since looked wrong, we leave it in.
Modular adoption over an all-or-nothing platform
The realistic first purchase is a website. Requiring a full platform commitment would have eliminated most of the market.
One shared backend behind a separated rendering layer
White-label demand was visible early. Forking per partner would have multiplied maintenance with every deal.
Publishing honest module readiness
Operators plan around availability dates. Labelling unfinished modules as live would have destroyed trust at the first onboarding.
Outcome
Where it
stands now.
Described in words where no measurement exists yet. Market figures carry their source.
Result
- Nine modular infrastructure layers spanning sites through to network
- Fourteen travel industry segments addressable from one backbone
- Direct and white-label distribution served by a single codebase
Status: In development. Sites and Pulse furthest along.
What it runs on
Other case studies
Turning a dead business card into a live relationship record
Engineering for an operator who does not want another GPS app
Same discipline, applied to your platform
Decision records like the ones above are a deliverable on every engagement, written as the work happens.