Client Snapshot

Meekins Transportation – a community mobility company providing non-emergency transportation for seniors and medically challenged riders: medical appointments, pharmacy runs, errands, hurricane evacuation. Their promise is We Drive, You Thrive. The operation behind that promise ran entirely on paper.

The Challenge: The Owner Was the Failover System

Every part of the business was analog, and every part was disconnected from every other part.

Ride schedules lived on a paper calendar. Customers lived in a spreadsheet. Leads lived on a paper list. Drivers learned their assignments through an email sent out for the day. Billing was separate from all of it. Nothing in that stack could see anything else in it.

The predictable thing happened. A driver would get caught out on an existing transport, a ride would come up with no one to cover it, and there was exactly one mechanism to fix it: the owner drove it herself. That’s not a staffing gap. That’s a business whose contingency plan is its founder’s calendar – and the direct cost of it is that the person who should be growing the company is instead in a vehicle, covering a scheduling failure that a system would have caught.

The growth side was no better. Meekins’ real opportunity isn’t one rider at a time – it’s relationships with assisted living communities, senior housing, rehab facilities, healthcare providers, and veterans organizations, each of which refers riders continuously. But partner cultivation was ad hoc. There was no record of who had been contacted, no follow-up that didn’t depend on someone remembering, and no way to plan a day of outreach that made geographic sense. Partnerships were pursued the way rides were dispatched: by hand, from memory.

The Approach: One System, Front to Back

1. A ride request becomes a scheduled ride, automatically. Requests come in through the website scheduling form as leads. Once waivers are signed, the lead is converted to a customer and a project is created for the ride – no manual re-entry, no transcription onto a calendar. Rides enter the business as structured records instead of handwriting.
2. Drivers are assigned in the system, with the ride’s requirements attached. Driver assignment happens as a task carrying everything the driver needs for that specific ride – the rider’s needs, the details, the context. No morning email digest. No paper handoff. And because assignments are visible, a conflict is something the system surfaces rather than something the owner discovers when a rider calls.
3. Drivers log time on the ride itself. Hours are captured against the actual transport rather than reconstructed later, which makes hourly compensation accurate and makes the true cost of a ride visible for the first time.
4. Billing moved in. Invoicing now runs from the same system that holds the ride, the customer, and the driver time – instead of living downstream of a spreadsheet.
5. Partner development got a route, and a memory. Referral partners are sourced through Lead Finder and added to the system as leads, with automated campaigns nurturing them by relationship type. Face-to-face relationship building is still exactly that – face-to-face – but the daily sales route is now mapped rather than improvised. That single change increased the number of partner touchpoints reachable in a day by 300%. Same rep, same day, three times the doors, because the drive between them stopped being a guess.

The Outcome

• 42 customers converted into the system, rebooking on recurring schedules — a book of business that now exists as records rather than a spreadsheet someone maintains.
• 300% more partner touchpoints per day — not through more staff, but through mapped routing that removed dead miles from the outreach day.
• The owner is out of the failover seat. Ride assignment is visible and structured, so a conflict is a scheduling event the system catches — not an emergency the founder personally drives.
• Driver time is accurate. Hours are logged against rides as they happen, making compensation correct and ride cost knowable.
• Partner relationships are an asset, not a memory. Every referral partner is a record with a history, in a nurture campaign, instead of a name someone hopes to follow up with.

The Takeaway

Meekins didn’t need better software. They needed any system – one place where a ride, the customer who booked it, the driver running it, the hours it took, and the invoice for it were all the same object instead of five disconnected artifacts. Once that existed, the owner stopped being the failover for a broken dispatch process and started being able to build the referral network the business actually runs on. This realignment is still young. What’s already true is that the company can see itself.