The project
3 min read
The challenge
Amaze is a podcast and video studio. Customers book studio time by the session, add equipment and crew, and pay by card or invoice. Bookings ran through a third-party scheduler that knew nothing about the CRM that runs the business, so prices, availability and invoices had to be reconciled by hand.
Your approach
I worked solo across scope, architecture, build, tests and deploy. The website (Next.js, React, Tailwind, Payload CMS) became a thin, styled client of the CRM, and the CRM stayed the source of truth.
A seven-step mobile booking wizard: package, location, setup, add-ons, details, date and time, confirm.
A live quote that mirrors the server calculation. The browser sends item IDs, never prices, and a "price changed" state replaces silent new totals.
A slot engine that combines opening hours, exceptions, minimum notice, existing bookings and Google Calendar. Bookings run in a serializable transaction, so a double booking fails with a clear conflict state.
Card payments, invoice sync and instalments, with idempotent, race-safe money writes.
Token-based self-service rescheduling from the confirmation email, and explicit booking statuses.
How the CRM drives the website
Nothing in the booking flow is hard-coded. I opened a dedicated public booking API on the CRM, so the team manages the whole offer in the CRM and the website only displays it.
Packages, studios (with photos and galleries), add-ons and prices come from the CRM API. The website caches them for 60 seconds, so a change in the CRM goes live in about a minute, with no deploy.
Availability, promo and referral codes, and company lookup by tax ID run live against the CRM on every request, with no cache.
The browser never calls the CRM directly. Next.js route handlers proxy each call server-to-server with a shared secret, pass on the real client IP and apply a rate limit per endpoint (for example, 3 booking submissions per hour per IP).
Lead forms work the same way: the CRM defines the fields of each form and the website renders them. If the CRM is down, submissions go to a retry queue, and the team gets an alert when the queue grows.
Tracking and analytics
I set up custom tracking through Google Tag Manager, so the team manages GA4 and ad tags in GTM without code changes.
Google Consent Mode v2 starts with all consent denied. The cookie banner updates analytics and marketing consent separately, and the choice persists between visits.
Every key action pushes a named event to the dataLayer: booking, WhatsApp, phone, maps and social clicks, and the contact, custom quote, referral and newsletter submissions.
One registry lists every tracked link and form. A deploy check blocks any new link or form that has no tracking entry, so a redesign cannot break tracking silently.
The result
Customers now get a real price and real availability on their phone, and every booking lands in the CRM linked to the right client and project, with its calendar event and invoice. Nothing needs to be copied by hand, and anything that fails shows as a visible to-do for the team. Playwright runs the full journey on desktop and mobile, including slot conflicts and promo codes, and every bug fix starts with a failing test.






