Software that runs the whole dive center, not just the booking page.

It is one system for the work a dive center repeats every day: bookings, boat and trip capacity, diver records, certification levels, digital waivers, rental gear, gear service dates, crew assignments, and payments. The point is not a prettier booking page. It is that the booking, the diver, the gear, and the boat all read from the same record, so the desk, the dock, and the boat stop disagreeing.

Buy a maintained dive platform when it handles your bookings, waivers, gear, and trips with reasonable setup and its pricing makes sense. Build custom when the way you run trips, courses, and service is itself the advantage, when a critical connection to your other systems cannot be done cleanly any other way, or when several sites, boats, and teams create a coordination problem no single platform reconciles. If your trip rules are still changing every week, settle them first and wait.

Capacity has to live in one place. Every sale, whether it comes from your website, the desk, or an agent, writes to the same trip and the same seat count, and the trip closes when it is full. A booking page that does not update the manifest, or a desk sale that does not update the website, is how the same seat gets sold twice. The first release should prove this on one real trip before it covers every trip type.

Yes. The booking confirmation carries a link to the waiver and any medical questions, the diver signs on their own phone, and the signed waiver, with its timestamp, sits on the booking. Staff see, before the day starts, who still has paperwork outstanding, so the morning is spent on safety briefings and gear checks instead of chasing signatures. Medical flags go to staff review; the software never clears a medical question on its own.

Each diver record holds their certification level, the certifying agency, and any renewal or expiry date your shop records. Courses and dives can require a minimum level before booking, and the roster flags anyone who does not meet it. Certifying agencies differ, so the system records what your shop defines and checks against your shop's own rules. It never invents agency rules, and it never certifies a diver: only instructors and agencies do that.

Every rental unit is one physical thing with a lifecycle: checked out to a named diver, due back on a date, and sent for service when it comes back damaged or when its service date arrives. Overdue gear surfaces on its own instead of waiting for someone to notice. Tanks and regulators carry their own inspection and service due dates, set by your shop, so a unit due for service is visible before it is handed out or filled.

Cancellation has to be one action, not a round of phone calls and spreadsheet edits. The trip record holds who paid, how much, and what was collected, so deposits, rebookings, and refunds all come from the same numbers. Decide the policy before the software is scoped: who gets moved first, what happens to deposits, and who tells the divers. Software carries the policy out; it cannot settle an undecided one.

Yes, if every channel writes to the same trips and the same orders. Agent and hotel bookings carry their commission for settlement, and a trip that fills online is full at the desk a moment later, without anyone re-typing it. If a channel keeps its own list, the double booking problem comes back through that channel.

Both come from the same booking data, not from a second round of typing. The manifest lists who is on the boat, their certification level, and their outstanding paperwork. The gear prep list comes from the same divers and their rental needs, including sizes your shop records. When a booking changes, both lists change with it.

Yes. A course is a sequence, not a single booking: sessions, rosters, instructor assignment, and per-student progress, with prerequisites checked at enrolment. A student who has not finished the earlier step shows up as unfinished, not as a silent gap in the roster. Your instructors define the course structure and the pass standard; the software tracks where each student stands against it.

Moving your data over is its own scoped job, agreed before paid work starts. Spreadsheets, booking exports, and paper lists are reviewed column by column, duplicates are resolved, and the import is checked against real trips before the old tools are retired. History matters here: a returning diver should arrive with their record intact, not as a brand new customer.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. A software company earns its fee when the work needs coordination across bookings, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole trip. If your need is one screen or one fix, hire the freelancer.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the trip workflow agreed at the start: one booking, from website to manifest to gear list, with a waiver signed and a service date flagged. Progress is reported in plain language: what changed, what is next, and what it costs. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.