Moon Jet Group CRM
An aircraft brokerage CRM for Moon Jet Group: listings, buyers, market comps, deal pipeline, owner and buyer portals, and reporting — one shared database behind the whole brokerage.
The brief
Aircraft listings, buyer requirements, comps and offer history sat across spreadsheets and inboxes, so brokers, owners and buyers were reading different versions of the same deal.
Our approach
A single web application: one console for brokers, record-scoped portals for owners and buyers, a shared database, and server-enforced permissions, NDA records and audit history.
The outcome
Listings, buyers, comps, pipeline and reporting now live in one system that every broker, owner and buyer reads from the same source.
Case study
Moon Jet Group is an aircraft brokerage. Its brokers carry listings, buyers and transactions across timezones, and owner and buyer relationships that run for months. Aircraft Program, the AOG support platform we also built, is part of the same group.
The ChallengeBrokerage work lived across spreadsheets, inboxes and individual memory. Aircraft details, buyer requirements, comparable sales and offer history sat in separate places, so two brokers working the same deal could be working from different facts — and none of it was visible to an owner or a buyer without an email chain.
What We BuiltWe designed and developed the CRM from the ground up as a single web application. Brokers work from one console; owners and buyers get portals scoped to their own records.
- Aircraft listings with highlights, up to twelve photos, a PDF brochure and days-on-market tracking
- Buyer records with category, budget and funding filters, paginated search, and dated discussion history
- Market comps: same-model sold references within two model years and 1,000 AFTT hours, plus manual competitor listings
- A coloured deal pipeline with listing agreements, agreed prices, and a closed-deal register with year filters and CSV export
- Owner and buyer portals, messaging, and email alerts for offers, NDAs, viewings and deal stages
- Module permissions, hashed sessions, recorded NDA acceptance and an audit history for deletions
React and TypeScript on the front end, a single Cloudflare Worker for the API, D1 for records and Workers KV for uploaded photos and brochures. Every screen reads the same database, so a change made by one broker is the record everyone else sees.
Current PositionThe brokerage now runs from one system instead of a folder of spreadsheets: listings, buyers, comps, pipeline and reporting in the same place, on any device, with permissions that hold up when someone asks who can see what.
