Work
Hospitality

An operations system for a fishing lodge

A bass-fishing lodge in Mexico and its booking company

A lodge that hosts 400 to 550 anglers a season, run by a small team across the US and Mexico. The operations system is built around the people guests already know, with rules the team wrote themselves. The revenue engine is being built out now.

400 to 550

anglers a season

Built

The problem

The lodge takes up to 30 anglers at a time through a season that runs from September to June. Bookings, billing and the office run from the US; the lodge runs in Mexico.

Invoicing runs through two companies, so any money design has to reconcile across both. And the guests are loyal to the people they know, which the system must never get in the way of.

What we built
  • Discovery with the owner, the operations lead in Mexico and the office manager
  • The operations system, built from the office's own billing exports and returning-guest list
  • A money design that reconciles across both invoicing companies
  • The team's own rules, built into the system as design law
  • The revenue engine, now being built out on top of the operations system
Design rules

The rules the system was built to.

01.

Every surface has a human path. Guests who want the people they know can always reach them.

02.

The booking calendar stays human-built. The system mirrors it.

03.

Trip credits stay with the office, off the system.

04.

The Mexican side of the operation stays with the team on the ground.

Have a process eating hours every week?

Book a 30-minute review. We'll tell you straight whether agents, a GTM engine or neither is the right fix.