We built a custom booking system for a multi-location training company running twelve US sites.

Fourteen locations were processing every booking and waiver by hand

CPR Syndicate runs CPR and first-aid certification training out of 12 US locations. Every one of those locations produces students who have to sign up, pay, sign a waiver, get reminded about their class, and get certified. All of it was being processed by hand.

The business was also paying for booking software that did a fraction of what it needed. That is the expensive version of the problem: you carry the cost of a tool and the labor of not having one at the same time. At the end of it, the owner, Justin, was the person checking the spreadsheet.

We mapped the full student journey across all twelve locations before choosing a single tool

Nothing got built until the process was on paper. We mapped the student journey end to end — signup, payment, waivers, reminders, certification — across every one of the twelve locations. Not the version that was supposed to be running. The one that actually was.

Mapping first turns the software decision from a guess into a requirements list. Once you can see where a student enters, where they stall, and which steps a person is holding together by hand, you know what the tool has to do. It also shows you the exact steps where an off-the-shelf product stops covering a business that runs twelve locations instead of one, and you only find those steps by drawing the process.

The map became the build, not a document that sat in a folder

The process map was the spec. We built a custom booking platform on top of it: Stripe checkout so students pay at signup, capacity management so a class cannot be booked past its limit, and automated confirmations so nobody has to send them.

All twelve locations run inside the same system and are tracked automatically, so the location count stopped being something a person had to keep up with by hand.

The platform has processed 1,523 bookings across 14 locations with zero errors in 687 runs

136 bookings came through in the first 14 days. Since then the platform has processed 1,523 bookings in total, 894 of them confirmed, across 14 locations tracked automatically — with zero errors across 687 runs, zero double-bookings, and 100% reminder accuracy. Justin no longer checks the spreadsheet.

The reliability number matters as much as the booking count. A booking system that drops one payment or one waiver creates more manual work than it removes, because someone has to find the gap and fix it by hand.

If you run several locations, count the manual touches on one booking before you shop for software

If you run training, classes, or appointments across several locations, follow one customer from the moment they find you to the moment they finish, and write down every point where a person retypes, forwards, checks, or chases something. That count, not your software bill, is the real cost.

Then name what your current booking tool does not cover. Whatever it misses — capacity, waivers, payment, per-location tracking — is the part your staff is covering by hand, and it is the part a replacement has to handle.

Only after that is the tool question worth answering, and the answer is not always another subscription. The map tells you whether you need to configure something you already own, buy something narrower, or build. Choosing a tool before you have the map is how a business ends up paying a monthly subscription and still doing the work by hand.