This is the build we would run for a charter or rental operator moving off phone-and-email bookings: the exact feature set, a 12-week timeline, and the outcomes we design toward. It is a documented plan, not a report of a past client's numbers.
Most charter and rental operators run on a shared inbox, a spreadsheet of rates and a WhatsApp thread with skippers. Guests wait hours for an availability answer, marketplaces take a cut of the bookings that do close, and nobody can see which weeks are soft until they are gone.
One system that owns availability, pricing and payment — then a site designed around finishing a booking on a phone. Operations tooling comes with it, because a booking platform your team refuses to use is just a prettier inbox.
Six phases, each with its own deliverables and a sign-off milestone. Pick a phase to see exactly what lands and what has to be approved before the build moves on.
We document how you actually take bookings today: rate cards, seasons, deposits, cancellation policy, turnaround, crew constraints. Output is a booking-rules spec that the build is measured against.
You sign off the booking-rules spec — the document every later phase is tested against.
Targets are agreed with you in week one against your current baseline, then reported monthly. We do not publish invented percentages — these are the four numbers the build is judged on.
Shift volume off commission marketplaces onto your own site, where the margin stays with you.
Replace inbox-and-spreadsheet coordination with one dashboard and automated guest comms.
Fill mid-week and shoulder-season gaps with pricing rules and targeted landing pages.
Reduce abandoned bookings with a short mobile flow and a low-friction deposit.
Enter your own numbers. The projection below uses your inputs and the assumptions listed in the methodology note — nothing here is a client figure we invented.
$13,608
From moving 35% of marketplace volume to direct booking.
168 hrs
Automating confirmations, balances and documents removes ~60% of per-booking admin.
+86
A 18% checkout-completion uplift on 480 bookings.
$117,288
Commission recovered plus revenue from the added bookings, before admin savings.
This is a projection model, not a report of achieved client results. Every figure is derived from the numbers you enter above, combined with three stated assumptions: 35% of marketplace volume moves to direct booking in year one, automation removes 60% of per-booking admin time, and the short mobile deposit checkout lifts completed bookings by 18%. Revenue effects are shown gross, before the build cost, payment processing fees and your own operating costs.
On a real engagement we replace these assumptions with your week-one baseline — enquiry-to-booking time, mobile checkout completion, direct-versus-marketplace split and admin hours per booking — measured from your own systems and reported monthly after launch.
The same six moments in a booking, run the old way and run on the platform. This is the operational change the twelve-week build delivers.
Guest emails, waits for someone to check a spreadsheet — often hours, sometimes a day.
Live calendar returns availability and a price instantly, day or night.
Back-and-forth on price, then a bank transfer chased manually.
Deposit paid at checkout, balance auto-requested before departure.
Rate card in a spreadsheet, peak pricing applied from memory.
Season and peak rules held in one place, applied automatically.
WhatsApp threads decide who skippers what, with turnaround guessed.
Departure board and crew assignment with turnaround buffers enforced.
Confirmations, reminders and documents typed by hand.
Automated confirmations, reminders, waivers and manifests.
No view of soft weeks or lost enquiries until the season ends.
Funnel, utilisation and channel reporting in the dashboard.
Every baseline below is taken from your own data in week one. We publish the framework, not invented percentages — the targets are what the build is held to once your numbers are in.
It is a documented blueprint of the build we run, not a report of a past client's numbers. The process, feature set and timeline are what we deliver; the shipped marine websites you can review today are Philippine School of Yachting and Sailing.ph, both linked from this page.
Twelve weeks from kickoff to launch for a single-operator fleet: two weeks on booking rules, two on UX, four on the engine and payments, two on content and integrations, two on testing and staff training. Multi-operator platforms are phased, with a first release in roughly twelve to sixteen weeks.
Scope decides it. Integrating a proven booking engine into a new site typically runs a few thousand dollars; a custom availability and pricing engine with an operator dashboard starts higher and is quoted in phases. The quote form on this page returns a fixed range for your fleet.
Yes, wherever your current system offers an export or an API. Vessels, rates, upcoming bookings and customer records are imported during weeks nine and ten, then verified against the old system before a planned cutover date so no live booking is lost.
They are tested explicitly before launch. The availability engine holds inventory the moment a deposit starts, refunds and partial payments are supported in the payment flow, and weather cancellations use a rebooking path with the credit rules you set during discovery.
Four numbers agreed in week one against your own baseline: enquiry-to-booking time, mobile checkout completion, share of direct bookings and admin hours per booking. They are reported monthly, alongside the biggest funnel drop-off we are fixing next.
Share your budget, timeline and the booking features you need. We reply with a scoped version of this twelve-week plan and a fixed price range.
Share your fleet size, rate structure and current booking process. We'll return a scoped version of this blueprint with a fixed price range.