Inside a Bohaus Sprint: A Fishing Charter

The situation

The client is an owner-led fishing charter. One boat, the owner as captain, a mate, and a part-time booker who also answers the phone. Offshore full days, inshore half-days, private charters and the occasional shared trip. Bookings come in by phone, text, social messages and a contact form, and land in a paper calendar or a shared phone calendar.

The full-day private charters sell themselves in season. The gaps are elsewhere. A party of two wants a shared trip, but there is no easy way to match them with other small parties, so they book somewhere else. Afternoon half-days go unsold. When weather cancels a trip, rebooking takes a round of calls, and some customers simply ask for a refund.

The owner also keeps hearing the same question from people turned away on busy weekends: is there a second boat? The honest answer is that nobody knows whether the demand is real.

What the sprint finds

In Discover, we pull a season of bookings from the calendar, the texts and the deposit records, and we ask the captain and the booker how a trip goes from first inquiry to the dock.

The pattern is clear. Demand is uneven, and the business keeps no record of the demand it turns away. Busy-weekend inquiries are declined by text and forgotten. Small parties are not pooled. Rebooking after weather depends on how much time the booker has that day.

In Diagnose, online booking with a waitlist and shared-trip rules ranks first. It fills seats that are already leaving the dock empty and, just as important, starts capturing the data the second-boat question needs.

We set measures before anything changes: seats filled per trip, unsold half-days, weather rebookings kept, and waitlist demand by date and trip type.

What it builds

In Build, we set up online booking on a charter platform such as FareHarbor or a similar tool, connected to the website, the Google Business Profile and the social pages.

Customers see real availability and pay a deposit to hold the date. Shared trips are sold by the seat, with a rule that confirms the trip once a minimum number of seats sell and keeps offering the rest until departure. Small parties asking for a private trip on a slow day are offered a shared seat instead. Sold-out dates open a waitlist that records date, party size and trip type.

Weather cancellations trigger a message with a link to pick a new date, so most rebooking happens without a phone call. Reminders go out before each trip with what to bring and where to park.

Hand over

In Hand over, the booker learns the platform in depth: trip types, seat rules, the waitlist and refunds. The captain gets a short session on reading the day's manifest on a phone. A playbook covers weather calls, no-shows and who owns the system.

The owner gets a dashboard of the measures set at the start, plus a 30/60/90-day roadmap. The roadmap includes a review at season's end. If the waitlist shows steady turned-away demand on the same days, a second boat, a partner captain or added trip times can be tested on those days before anything is bought.

What changes

More trips leave full. Small parties get a seat instead of a no. Weather days cost less, because customers move their trip instead of canceling it. The booker answers fewer texts asking whether a date is open.

And the expansion question gets answered with the business's own data, not with the impression left by one busy Saturday.

What this means for your business

Measure before you expand. The booking system that fills today's seats is also the one that tells you whether you need more capacity.

For a fishing charter, that is seats and the waitlist. For a marina, launch requests by day. For a moving company, booked jobs against estimates sent.

That is a Bohaus Sprint: six weeks, fixed scope, four phases (Discover, Diagnose, Build, Hand over), and one live system inside the tools you already use, with a trained team, a playbook, a dashboard and a 30/60/90-day roadmap.