The problem
Enthuza Cycles sits right at the Silver Comet trailhead in Rockmart, with a steady stream of riders passing by. But rental bookings came in by phone and walk-up, busy weekends risked handing the same bike to two people, and there was no way to tell whether the shop's Facebook ads were actually putting riders on bikes.
What I built
- A custom website with an online rental booking flow: riders pick bikes, sizes, and add-ons, choose a pickup time within the shop's real business hours, and sign a liability waiver — no account required, with payment taken in person at pickup.
- Real-time availability that locks the fleet at booking time, so the same bike can't be double-booked on a busy Saturday.
- A staff back-office to manage reservations, the bike fleet, business hours and closed dates, and rental add-ons — plus a private visitor dashboard.
- Automated, branded emails for every step (confirmation, changes, pickup, cancellation) and instant new-booking alerts to the owner.
- Facebook (Meta) Pixel plus server-side Conversions API that records a purchase on every completed booking, so the shop can finally see which ads bring in riders — alongside Google Analytics, all consent-gated behind a cookie banner.
- Privacy-first, cookieless visitor analytics and an SEO build-out aimed at the Atlanta-to-Rockmart day-trip crowd.
For the engineers: Blazor Server on .NET 9, PostgreSQL/EF Core, Postmark transactional email, consent-gated Meta Pixel + Conversions API and GA4, database-level overbooking locks; shipped to a PM2-managed Linux VM via GitHub Actions.
The result
The new site and Facebook ad campaign drove enough new business that the shop brought on extra help to keep up with it.
Have a similar problem?
Twenty minutes, no obligation — tell me what your version of this looks like and I'll tell you what I'd build first.