[ Case study ]
Slip assignments, transient bookings, and seasonal billing lived on a whiteboard, a spiral notebook, and an aging spreadsheet; double-booked transient slips happened monthly, and billing disputes started with 'the whiteboard said.'
CLIENT a 300-slip freshwater marina — FOCUS Model the dock as it is
Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.
Freshwater marinas run on two economies: seasonal slips billed in the spring, and transient overnight stays that peak in summer. This 300-slip marina on a busy lake also winters boats in dry storage, so one physical dock supports three revenue models. The harbor master is the operation's brain — he walks or drives the dock from dawn, assigns every arrival, and knows each slip's quirks by heart. Those quirks never made it into any system; the authoritative records were a whiteboard map, a spiral notebook, and a spreadsheet that disagreed with both.
Slip assignments, transient bookings, and seasonal billing lived on a whiteboard, a spiral notebook, and an aging spreadsheet; double-booked transient slips happened monthly, and billing disputes started with 'the whiteboard said.'
We proposed modeling the dock as it physically is — every slip an asset with its own length, power, and position constraints — rather than forcing a tidy numbered grid onto irregular reality. The harbor master's tool is one scrollable dock map with drag-to-assign and instant conflict warnings, built for a golf cart, glare, and one free hand. Assignments and stays feed one ledger with two billing calendars: seasonal and transient rules post to the same record, ending the spreadsheet reconciliation ritual. Nothing about his workflow moves; the whiteboard's authority simply becomes digital, shared, and disputable with evidence.
Just as important is what we ruled out, and why:
Every slip is an asset with its real constraints, so assignments respect the physical dock instead of a tidy database abstraction.
The harbor master's view is a single scrollable dock map with drag-to-assign and instant conflict warnings, designed for glare and gloves.
Seasonal and transient billing post to one ledger with their own rules, ending the spreadsheet reconciliation ritual.
Delivered by the systems pod — engineer over 8 weeks, with working increments reviewed with the client every week.
Obstacle
A season of hand-kept records became the source of two billing disputes after cutover — the old whiteboard had been amended without dates, and both parties recalled it differently.
Handled: We digitized the surviving photos and notebook pages into an archived ledger marked as pre-system, so disputes could at least cite a record instead of a memory.
Obstacle
The first dock-map build tested beautifully indoors and failed at the dock — glare washed out the screen, and assigning required pinch-zoom and two hands.
Handled: We rebuilt it as a single vertical scroll with oversized targets, tested it standing in the sun mid-season, and shrank nothing else about it.
Obstacle
A transient stay that opened before season end and closed after it broke the billing rules — the two calendars disagreed about which rate schedule owned the stay.
Handled: We settled it with the owner as a stated rule — the opening day's calendar applies — encoded it as a test, and added it to the billing runbook.
The headline: all slips and transient stays booked through the tool, with billing from the same ledger — Whiteboard → dock-map booking, read from Booking conflict log. A second check: double-booked transient slips since cutover at 0.
The harbor master runs the dock from the same golf cart, but the map in his hand now remembers what the whiteboard forgot. Arrivals are assigned in seconds, conflicts warn before they happen instead of at the fuel dock, and the phrase the whiteboard said has left the vocabulary. The owner closes each season from one ledger instead of three records and a negotiation. Winter storage billed from the same ledger, and the office answers billing questions by opening the record instead of reconstructing a season.
The result was read from Booking conflict log against the pre-engagement baseline over the stated window, with a guardrail check on double-booked transient slips since cutover. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.
What we would do differently
We would digitize the whiteboard's history before cutover — a season of hand-records became the source of two billing disputes, and an earlier import would have settled them.
[ Related service ]
[ Related builds ]
0 pilot-ready productBooking MVP live with the first pilot cohort scheduled and samples reconciled through the ops console
Status calls self-serve portalHouseholds onboarded at contract signature, with stage changes visible within minutes of ops updating the board
[ Next step ]
Next case study
