case study · Automation

JetsCheck — Booking Automation

Cloud-function automation running the booking lifecycle, status updates and client email without manual work.

At a glance
4
booking stages moved on automatically
2
channels: email and push notifications
1
data contract shared across the platform
JetsCheck — Booking Automation — full page design
Scroll inside the frame to see the full page.
01 · The brief

What Impact Jets needed

A marketplace only works if the busywork runs itself. JetsCheck needed the booking lifecycle, status updates and client communication to happen automatically — not in someone’s inbox.

02 · What I built

How it works

A set of Firebase Cloud Functions powering the booking autoflow: as a charter request moves from quote to accepted to confirmed, statuses update on their own and the right people are notified at the right moment.

  • Booking statuses update on their own: request, quote, accepted, confirmed
  • Clients and operators notified at the right moment
  • Automated booking and marketing emails
  • Push notifications through FCM
03 · Tech stack

What it runs on

The tools behind the build and the job each one does.

01Cloud FunctionsServer-side triggers that move a booking on as its data changes.
02FirestoreThe booking records the functions watch and update.
03Firebase Cloud MessagingPush notifications to the right people at each step.
04Transactional emailBooking and marketing emails sent without anyone pressing send.
05Shared data contractThe same booking model used by the app, the dashboard and the functions.
The result04 · Outcome

What it delivered

The platform handles its own follow-up. Bookings progress, clients stay informed, and the team is freed from manual status-chasing and one-by-one emails.

  • Booking statuses update automatically through the lifecycle
  • Automated booking and marketing emails
  • Push notifications via FCM
  • Wired to a shared cross-codebase data contract
05 · Check it yourself

Don’t just take my word for it

Open the project and see it working. The stack and numbers on this page were checked against the live build on 15 September 2026.

  • Private back endA private build with no public link — the screens on this page are from the working product.
How it ran

The same process for every project

One person from first call to launch. See the full process

  1. 01Brief and scopeWe agree what it has to do, who it is for and what counts as done.
  2. 02DesignLayouts for the key screens, shaped around what turns visitors into customers.
  3. 03Build and testBuilt, checked on phones and desktops, and connected to the tools the business uses.
  4. 04Launch and supportLive on the real domain, with 12 months of support included.
Usually replies within a day
let’s talk

Have a project like this?

Tell me what you’re trying to build and I’ll walk you through exactly how it would run — a clear scope and a fixed price.