embrk is a charter management app for yacht owners and operators, live on iOS. It holds the fleet, the routes, the guest experience and the commercial picture in one place, built for people running charters from a phone rather than an office.
Charter operations are usually spread across spreadsheets, weather apps, chat threads and paper agreements. embrk pulls those into a single product where a boat, a route and a booking are connected records rather than separate files.
Product Strategy · UX/UI · Mapping and Routing · Data Modelling · Release Engineering
Routes are built by tapping the map or dropping pins, then ordered into stops that carry their own type: port, picnic, swimming, overnight. The plan reads as a sequence rather than a set of coordinates.
A charter itinerary is the product the guest actually buys, so it was designed as a first class object rather than a note attached to a booking.
Every vessel carries its full specification: length, guests, cabins, year, engines, engine hours, cruising and max speed, fuel and water capacity, berth and draft.
Operators are asked these numbers constantly. Holding them as structured fields means they can be surfaced to a guest, printed into an agreement or filtered on, instead of being retyped every time.
The same vessel record generates a shareable guest guide with imagery, description and specification, distributed by link or QR code. No separate CMS, no second app to maintain.
That is the difference between an operations tool and something an operator will actually keep updated: the admin work produces the guest experience as a byproduct.
Live conditions are built in: temperature, wind speed and direction, Beaufort scale, sea state. Weather is not a reference lookup in this business, it is what determines whether a charter runs and which route is sensible.
Putting it next to the route removes the app switching at exactly the moment the operator is deciding.
Revenue, bookings and utilisation are reported across seven, thirty and ninety day windows and by year, drawn from the same records that run the operation.
Analytics are only trustworthy when they are a byproduct of the workflow rather than a separate spreadsheet someone maintains by hand.
An operations product is worthless until it holds real data, and that first hour is where most abandonment happens. Setup is a visible checklist with progress: add the first boat, upload the company logo, create an agreement template, set pricing, share the guest link.
Each step leaves the operator with something usable rather than a partially filled form.
embrk shipped to iOS as a working charter management product covering fleet records, route planning, guest facing guides, live conditions, agreements and revenue reporting.
One app replacing the spreadsheet, the weather app, the photo album and the paperwork that charter operators were running the business on.
Continue
Next project
