How We Helped a NEMT Provider Expand Multi-State

Most NEMT expansion stories are told as fleet stories: more vehicles, more contracts, more states. This one is a back-office story, because the back office was the thing actually deciding whether this company could grow. It is the narrative version of the case study on our site — same client, same facts, told the way it unfolded.

A note on honesty before we start: the client is anonymized because their operation is their competitive advantage, and we publish no numbers we cannot stand behind — so there are no invented trip counts, revenue figures, or manufactured quotes in this story. The scope, the timeline, and the multi-state expansion are exactly as stated.

Where did they start?

A single-state NEMT operation on the East Coast with a growing fleet and a problem every operator will recognize: the phones never stopped. Rider calls, driver calls, broker portal updates, will-calls, scheduling changes — all of it landed on a small office team that was simultaneously trying to bill trips and keep credentials current.

Growth was happening, but it was making things worse, not better. Every new vehicle added call volume, dispatch complexity, and billing work to a team that was already at capacity. That is the quiet trap of NEMT growth: the fleet scales linearly, but the office work compounds — and every new market multiplies it again.

Why was the back office the bottleneck?

Because in NEMT, the office is where trips are won and lost. A broker trip not confirmed in the portal goes to another provider. A rider who cannot reach anyone becomes a complaint. A driver without clear assignments burns hours. A completed trip billed late or wrong becomes a write-off. None of these failures show up in the fleet — the vans are fine — but together they cap how big the company can get, because the owner ends up refereeing office chaos instead of building the business.

What did they hand over?

Rather than outsourcing one task, the owner handed us the entire operational layer:

• All inbound calls — riders, drivers, facilities, and brokers, answered in the company’s name
• Driver management and routes — assignments, acknowledgments, and day-of coordination
• Dispatching and scheduling — 24/7, inside their existing software
• Broker relationships and trip intake — portal management and daily communication with brokers
• Trip assignment with driver notification — no trip left unassigned, no driver left uninformed
• Patient and driver follow-ups — confirmations, will-calls, and callbacks
• Billing — trip claims submitted clean and followed to payment

Two design choices mattered enormously. First, we worked inside the client’s existing platform and broker portals from day one — the owner never lost visibility of a single trip. Second, it was one team with full context: the person answering a rider call could see dispatch, and the person working a claim knew the trip’s history. Nothing was lost between vendors, because there were no other vendors.

What actually changed?

The owner’s week changed first. With calls, dispatch, broker portals, and billing off their plate, their time went where fleet growth actually comes from: vehicles, drivers, and market expansion. Over the following two years, that reallocated time compounded into results:

• One state became a multi-state operation — with the same outsourced back office scaling alongside, and no office hiring spree required.
• Broker trust grew. Clean portal management and reliable trip acceptance meant brokers assigned more trips as confidence built, month after month.
• Private patients became repeat callers. Phones answered by name, every time, turned one-off rides into standing business.
• On-time performance held through the growth. Dispatch discipline — realistic assignment, confirmed acknowledgment, proactive re-routing — meant no late drivers and no waiting patients as volume climbed.

Why did brokers assign more trips?

Nothing exotic: consistency. Brokers reward providers whose portals are current, whose trips get accepted reliably, and whose service does not degrade on nights, weekends, and holidays. Because the dispatch board and the phones were staffed around the clock — sick days and holidays included — the client looked, from the broker’s side of the portal, like the most dependable option on the list. Multi-state expansion raised the stakes here rather than lowering them: every new market meant new broker relationships judging the operation from scratch.

What is the proof it worked?

The metric we point to is the one that cannot be dressed up: retention. Two-plus years into the engagement, we still run the same complete scope today. In an industry where vendors are replaced the first quarter they slip, a client keeping their entire back office with one partner through a multi-state expansion is the realest evidence we can offer — more honest than any number we could put in a headline.

What would your version look like?

Every engagement starts the same way regardless of size: a free operations audit of your current setup, a scoped first week so you can judge quality on real work, then coverage that grows with you. Some operators hand over the phones first; others start with after-hours dispatch and expand from there. The complete scope this client runs — calls, dispatch, brokers, billing as one team — is laid out on our NEMT back office page, and the condensed version of this story lives in the case study.

Frequently asked questions