When Wheel Easy, a mobile tire and auto service, moved from its Wix site to its own booking system, customers started booking only the times a technician was actually free and paying when they booked, and each technician's Google Calendar began filling itself. The case study reports that the move increased revenue, improved fuel efficiency for technicians and ended chasing payments after the job.
This is what we built for them, what changed, and what we took from it.
What was wrong with the Wix site?
Wheel Easy's technicians drive to the customer's home or work. That one fact shapes everything: the booking isn't for a bay in a shop, it's for a technician's time and a drive.
The Wix site couldn't be shaped around that. The booking experience couldn't be customized, and it did nothing to help the business plan its technicians' days. Wheel Easy needed two things at once:
- booking that's easy for customers, and
- scheduling that keeps the operation efficient.
On top of that, both customers and technicians needed reminders before every appointment, so nobody misses one.
What did we build?
We built a web booking system with three parts: customer booking, technician calendars and payments. Our work covered use case analysis, design, development, testing, launch and ongoing maintenance.
How do technician calendars fill themselves?
Each technician sets their weekly availability, and customers can only book the times that are open. Every booking creates an event in that technician's Google Calendar automatically. If a technician needs time off, they block it right in Google Calendar, without signing in to anything else.
The calendar runs on Eastern time and handles Canada's daylight saving changes. That sounds like a detail, but a booking system that gets the clock change wrong sends a technician to a driveway an hour early or late, twice a year, and the November change lands in the middle of fall tire season.
Who gets reminders?
Booking confirmations and appointment reminders go out automatically to the customer and to the technician. That keeps both sides on schedule and cuts down on no-shows.
How do customers pay?
Customers pay for the appointment online through Stripe Checkout, by card, Apple Pay or Google Pay. The business no longer handles payments by hand, and the money comes in before the appointment.
What changed for Wheel Easy?
| Before (Wix site) | After (own booking system) |
|---|---|
| Booking couldn't be customized | Booking built around a technician driving to the customer |
| No help planning technicians' days | Customers can only pick open times; each booking lands in the technician's Google Calendar |
| Payments handled by hand | Customers pay at booking through Stripe Checkout |
The results, as the case study states them:
- Revenue went up. The move to a custom booking system increased Wheel Easy's revenue.
- Better for technicians and customers. Improved fuel efficiency for technicians, and a better booking experience for customers.
- Better cash flow. Customers pay when they book, so there's nothing to chase after the job.
- Still running. The system has run the business every day for over two years, and we keep adding to it.
Dennis Ho, CEO of Wheel Easy Inc., put it this way:
"I came to them with just a vision of what I wanted to create. Their ability to understand and structure the project, clearly communicate the technical aspects, set and meet timelines, and keep improving and polishing the product has been a dream scenario for a non-technical founder like myself."
What did we learn?
The technician's day is the product. For a mobile shop, a booking is a promise that a specific person will be at a specific address at a specific time. A generic form or website builder records a request; it doesn't know who is free or where they are. Booking only open slots, per technician, is what makes the calendar trustworthy.
Meet technicians where they already are. Bookings land in each technician's Google Calendar, and they block time off there too, without signing in to anything else.
Time zones and daylight saving belong in the first version. Tire swaps cluster in spring and fall, and the November clock change falls in the fall rush. Getting Eastern time and daylight saving right is part of the core, not a later fix.
Reminders go to both sides. A reminder only to the customer covers half the risk. The technician gets one too.
Payment at booking changes cash flow. When the customer pays as they book, there is nothing to chase after the job, and the business stops handling payments by hand.
A system like this keeps changing. It has run every day for over two years, and we are still adding to it. Plan for ongoing work, not a one-off launch.
What happened next?
What we learned building Wheel Easy became DispatchEngine, our booking and dispatch software for mobile mechanics and fleet-service shops in Ontario. It takes the same ideas (online booking with payment, technicians who can only be booked when they're free) and adds service zones by postal code, so customers only see the days a technician covers their area.
Sources
- appsterpiece.com/work/auto-repair-booking, read 17 November 2026