Bookings, payments and calendars that reconcile themselves
A booking and payments backend for a Melbourne firm, taken from local development to a live domain inside a three-month engagement.
- Client
- Atlas Counsel Pty Ltd — Melbourne, Australia
- Role
- Full-Stack Engineer (Freelance, Hybrid)
- Timeline
- Jun 2026 – Aug 2026
- Status
- Live
The problem
Booking systems break at the seams. The calendar says one thing, the payment provider says another, and someone spends their Monday morning working out which is true. The failure is rarely in any single integration — it is in the fact that nobody made them agree.
Atlas Counsel needed bookings, availability and payment confirmation to stay in sync without a human reconciling them.
What I built
I delivered the backend behind thesolutionistagenda.com, integrating a payment gateway and the Google Calendar API so that a confirmed payment, a held slot and a calendar event are three views of one fact rather than three systems drifting apart.
Before writing the integrations I designed the relational schema underpinning clients, bookings and transactions. Modelling that up front is unglamorous and it is the reason scheduling and payment records stayed consistent as the product grew.
Taking it to production
I deployed and configured the production stack myself on a Hostinger VM, running Uvicorn behind an Nginx reverse proxy, and took the project from local development to a live domain within the engagement.
For a client this size, "it works on my machine" is not a deliverable. The deliverable is a URL that stays up.
Stack
Need something like this built?
I take on freelance briefs and part-time engineering work from Melbourne, Australia.