Harbor Booking
A booking flow for a small marina, from berth search to payment.
- Client
- Porto Eira Marina
- Role
- Lead engineer
- Year
- 2026
- Duration
- 5 months

Results
- Phone bookings
- −62%
- first season
- Conversion
- 4.1%
- search to payment
- Time to book
- 2 min
- median
The challenge
The marina took every reservation by phone and kept the season in a shared spreadsheet. In summer two people spent their mornings answering the same three questions: is there room, how much, and can I pay by card.
Berths differ in length, depth and power, prices change by season and boat length, and a double booking means a skipper arriving at night with nowhere to tie up.
The approach
I started with the staff, not the screens: a week of shadowing at the harbour office turned into a list of every rule they kept in their heads. Those rules became one pricing table staff can edit, so a new season needs no developer.
Availability is one Postgres query over date ranges with an exclusion constraint, so two bookings for the same berth and night can't both commit, whatever the web server does.
What I built
- Availability search that answers in under 100 ms on a single query.
- Seasonal and length-based prices that staff edit themselves.
- Card payments with webhooks that keep bookings and payments in step.
- A tide-aware arrival note in every confirmation email.
Our mornings used to belong to the phone. Now the harbour office opens to a list of confirmed arrivals, and Ada left us a tool we can change ourselves.
More web app work

Web app · Frontend engineer
Ledgerly
A bookkeeping dashboard that turns bank feeds into clear monthly reports.
- TypeScript
- tRPC
- Tailwind