Building Ridereserve from
one real booking problem.

Ridereserve did not start as a pitch deck. It started because Colonial Trolley had a real operational problem: high-intent customers were finding the business, but the booking process still needed a cleaner way to collect details, organize follow-up, and keep the back office from becoming the bottleneck.

That is the best kind of product pressure. Not theoretical users. Not a generic dashboard looking for a market. A real transportation business with real inquiries, real events, and real administrative work that had to get handled every week.

The Colonial Trolley site solved the front-facing problem first. It made the service clearer, answered customer questions earlier, and gave people a better path to raise their hand. In May 2026, Google Search Console showed 172 clicks and 2,310 impressions, including searches like "trolley rental near me" and "trolley service near me." That kind of traffic is useful only if the workflow behind it can keep up.

Corey Scafidi said that about the combined site and workflow, and it is exactly the line that made the SaaS direction feel worth pursuing. A website can create demand. A product has to absorb it, organize it, and make the next action easier.

Right now, Ridereserve is used exclusively by Colonial Trolley. That is intentional. A narrow pilot keeps the product honest. Every feature has to answer a real question: does this help capture better booking information, reduce manual back-and-forth, or make it easier for the operator to understand what is happening in the business?

The work now is separating what is Colonial Trolley-specific from what other transportation operators probably need too: structured inquiries, event details, booking status, customer communication, reporting, and the simple feeling that nothing important is stuck in an inbox.

That is the same way I think about my CRM project. Build around a real workflow first. Watch where the friction repeats. Then package the useful parts without dragging every custom edge case into the product.

The lesson is not that every client project should become software. Most should not. The lesson is that small business software gets better when it begins with a business that actually has to use it tomorrow morning.