Happy Soul Travel
A retreat organiser gets a new platform in place of the system from years ago: booking gets simpler, and the team manages trips, booking e-mails and overviews itself instead of through a developer.
- role
- Lead developer
- phase
- building and introducing
- stage
- Not live yet: built and in testing with the client
- stack
- Laravel 13 Livewire 4 Flux UI Pest
What was going on
Happy Soul Travel organises yoga, wellness and spiritual retreats. Bookings, requests, invoices and trip information ran through a system of its own from years ago, and almost every change needed a developer. I am building the platform that replaces it: the team manages trips, destinations, booking e-mails and overviews in it themselves.
What made it hard
Moving years of bookings, clients and trips out of the old system without losing anything
A booking form that stays simple with two, three or four travellers and on a phone
Prices that depend on trip length, trip type and room type, clear in one overview
Letting the team manage what now goes through a developer
How I approached it
First the data and the business rules of the old system mapped out, then a new platform alongside it, with a test environment where the team works with real situations. I handle the team's feedback in short rounds, each with a release note. The new design comes from a design studio Happy Soul Travel hired itself; I build it in.
Built and in testing: the team works in the test environment and gives feedback
The team manages trips, destinations, booking e-mails and overviews itself
It goes live once the new design is built in; until then the old system keeps running
Need something like this?
One route: analysis, building and introducing, and maintenance if you want it. It starts with a thirty-minute intake.