Skip to main content

Platforms & products

Multi-tenant booking and payments platform

In preview

We built the software that takes a rental from the first click to the keys coming back, for a company with five locations. It is in preview, and the company switches over to it on January 1, 2027.

A booking and payments platform that runs a rental business from the first click to the returned keys: availability, server-side pricing, Stripe payments, signed paperwork, counter check-in and returns, staff training, and a public API. It is built so other rental companies can run on it too. It is in preview, with customer switchover set for January 1, 2027.

Client
Multi-location rental operator
Engagement
Architecture, full build, and launch preparation
Status
In preview
Discipline
Platform engineering
What we built
  • Booking & payments
  • Signed paperwork
  • Check-in & returns
  • Auto reminders
  • Staff training
  • Public API
Stack
  • Next.js 16
  • Supabase / Postgres
  • Row-level security
  • Stripe
  • Twilio
  • Resend
  • TypeScript
  • Playwright

Before

The operator rents motorhomes, trailers, pontoons, jet skis, UTVs, e-bikes, mopeds and more from five locations in four states, and runs every booking through an off-the-shelf booking tool, with separate tools for calls, tasks, and email around it. They wanted one platform the business owns: one that prices a booking correctly, takes a deposit, charges the balance, collects a signed agreement, checks equipment out and back in, and trains the staff who use it. It also had to be built so other rental companies can run on it, with each company's data walled off from every other. We designed and built it from the ground up.

What made it hard

01

Every rental company on the platform had to be invisible to every other, enforced in the database itself through row-level security rather than trusted to application code.

02

Money left no margin for error. Prices, deposits, balance charges, refunds, and tax are all calculated on the server, with a ceiling on every charge, so a total cannot be changed by mistake at the counter.

03

Two renters could never book the same unit, so every booking path had to hold a lock while it checks availability.

04

Renters should never see the platform underneath. Booking and self-service had to live on the operator's own domain, in its own brand.

05

The business keeps taking bookings on its current tool until switchover, so the new platform had to be proven without touching live revenue.

What we built

01

Booking: a hosted booking flow with holds, waitlists, quotes, extensions, reschedules, and one-way rentals, dates correct in each store's time zone, and a lock on every booking path that prevents double-booking.

02

Payments: server-side pricing (seasonal, weekend, and per person), Stripe deposits, off-session balance charges, refunds, and promo codes, plus a daily reconciliation against Stripe and a monitor that flags any money total that does not add up.

03

Customer portal: a private booking link where renters pay, sign the rental agreement (stored with a tamper-evident fingerprint), and manage their booking, all on the operator's own domain.

04

Counter and fleet: a daily manifest, check-out and check-in with a signed-waiver gate and condition photos, inspections, maintenance work orders, late-return fees, and transfers between locations.

05

Back office: an 80-screen staff dashboard covering the calendar, bookings, inventory, customers, payments, pricing, reports, and staff, plus a shared inbox where AI live chat answers first and hands off to a person.

06

Built to be sold to other rental companies: database-level isolation for each company, a signup and onboarding wizard, a console for running the platform, an embeddable booking widget, and a documented public API with scoped keys and signed webhooks.

07

Automation and training: 22 scheduled jobs for inventory holds, deposit releases, reminders, late fees, and abandoned-booking recovery, every email and text through one notification layer, and a training academy of 16 tracks and 34 lessons with certificates.

08

Proof before launch: about 10,900 automated tests, 254 Stripe payment scenarios run in test mode on every change, a check that fails any test which still passes when the code is broken, and automatic rollback if errors spike after a release.

09

Security reviews, including an audit run by 95 AI reviewers and a register of 256 findings, each re-tested by a reviewer told to disprove it. A cross-company data exposure and a privilege escalation were found and closed before any customer used the platform.

Results

125Screens built

80 for staff, 15 for renters, and 8 for running the platform as a business, plus the booking and setup flows. Built across 1,197 reviewed changes since February 2026.

10,900+Automated tests passing

Plus 254 Stripe payment scenarios in test mode and 21 end-to-end browser suites. Changes run them before they ship.

244Database migrations

Each company's data is walled off in the database, built up across 244 migrations with 94 matching rollback scripts.

Where it stands

In preview. Customer switchover is set for January 1, 2027, and no real customer has paid through it yet: of the 127 bookings made by August 2026, 121 were tests and 6 were the owner's own walkthroughs.