NEMT Software Buyer's Guide: Features, Pricing, Fit

A ten-van NEMT operation running on spreadsheets, a whiteboard and three broker portals burns 1.5 to 2 dispatcher FTEs to move about 2,000 one-way trips a month. Software that automates trip intake and assignment costs $350 to $1,300 a month at that fleet size, at published rates. That gap — not the feature list — is the buying decision, and most vendors will talk about everything except it.

This guide compares what NEMT dispatch platforms actually do, what they cost, and how to tell in a 45-minute demo whether a product survives contact with a Modivcare trip file. Everything below was verified against vendor-published material in July 2026; where a vendor does not publish something, the table says "not published" rather than guessing.

Disclosure: Bambi is a Platinum sponsor of NEMTrepreneur. Inclusion in this guide is not a paid placement, and the same evaluation criteria and the same "not published" standard were applied to every vendor here, sponsor included.

The capabilities that actually separate products

Every platform here will show you a scheduling grid and a map with vans on it. That is table stakes. The dimensions that decide whether you keep the software after year one are narrower:

• Automated broker trip intake. Does the system pull trips from your broker — Modivcare, MTM, Verida, Access2Care, American Logistics, Safe Ride, Alivi — over a real integration, or does someone download a spreadsheet and paste it? This is the largest labor line in NEMT dispatch.
• Multi-vehicle-type dispatch. Ambulatory, wheelchair and stretcher tiers carry different vehicle requirements, load times and rates. A system that treats a van and a stretcher unit as interchangeable builds routes you tear apart by hand.
• Will-call and same-day handling. Discharge calls and will-call return legs are where OTP goes to die. Ask how the system re-optimizes a live route mid-shift.
• Standing orders. Dialysis and behavioral-health recurring trips are the profitable base of most books. Templates that survive a mid-series schedule change matter more than they sound.
• Route optimization with multi-loading. Grouping riders headed the same direction is the difference between six and nine trips per van per day.
• Driver app with navigation and attestation. Turn-by-turn, offline behavior in dead zones, and signature capture at the point of service.
• Billing and claim export. Broker-compliant invoices, and 837P or CMS 1500 output where you bill Medicaid directly.
• Audit trail and HIPAA posture. GPS-stamped trip verification, role-based access, and a signed Business Associate Agreement. A vendor that hesitates on the BAA is telling you something.
• Open API and telematics. If you already run Samsara or Verizon Connect, duplicate GPS is duplicate cost.

How the main platforms compare

Verified from each vendor's own site, July 2026. "Not published" means the vendor does not state it publicly — not that the capability is absent.

Two structural notes worth more than any feature row. First, isi-technology.com now redirects to routegenie.com — same company, so do not treat them as two quotes. Second, WellRyde is a Modivcare product. If Modivcare is also your largest broker, you are handing your dispatch data, OTP record and capacity signal to a counterparty you negotiate rates against. That may be a fine trade for the integration depth. Decide it deliberately.

Four more names are absent above because nothing about them could be verified from vendor material. TripMaster from CTS Software is a long-standing paratransit and NEMT product, but its site was unreachable during research. Momentm's Nova serves the agency and enterprise end of the market and publishes no fetchable detail or pricing. NovusMED blocks crawlers entirely. Kaizen Health appears in trip-source lists as a coordination network rather than a fleet dispatch platform, and its current public site presents a consumer health-records product — treat any provider-side dispatch claim as unverified until you see it demonstrated.

What NEMT software costs, and what drives the number

Most vendors here do not publish pricing; four of the eight above do. That is the whole reason "request a demo" exists as a button.

The four pricing models

Per vehicle, per month. The dominant model. Bambi publishes $69 per vehicle per month with everything included and no contract; Tobi Cloud publishes a starting rate of $60. Predictable and easy to budget, and it punishes you for spare units — a backup wheelchair van that runs eight days a month still bills full freight.

Per managed trip, plus a platform fee. MediRoutes publishes $150 or $250 per month plus $0.50 per managed trip, with unlimited vehicles. A managed trip is one one-way leg, so a round trip counts twice. Read the fine print: no-shows, cancellations at the door and unperformed trips are still billed. In a market with a 12% no-show rate, that is a surcharge on trips you never collected on.

Tiered flat SaaS. NEMT Cloud Dispatch publishes $49.99 for one vehicle, $149.99 for up to five, then $39.99 per additional vehicle. Tiers reward you at the top of a band and penalize you the month you add the van that pushes you into the next one.

Per driver or per seat. Common at the enterprise end and rarely published. Ask whether dispatchers, billers and read-only managers all consume paid seats. That is where a $60 quote becomes a $200 quote.

The costs that are not on the quote

• Implementation and onboarding. Bambi's pricing page pegs typical industry setup fees at $500 to $5,000 and states it charges none. Treat any four-figure implementation fee as negotiable.
• Per-integration charges. MediRoutes includes one third-party integration and charges $100 per year for each additional one; its $150 tier includes one broker integration, the $250 tier unlimited.
• Payment processing. MediRoutes publishes a 3.5% card fee and a $35 check fee, with ACH free. On $60,000 of monthly private-pay revenue that is a $2,100 difference.
• Notification credits. SMS and IVR are often metered. Ask the per-message rate and the included allotment.
• Customization. NEMT Cloud Dispatch publishes $95 per hour; others quote per project.
• Contract length. Two vendors above advertise no contract. Anything longer than 12 months is you absorbing the vendor's churn risk.

Worked total cost: 10 vehicles, 2,080 trips a month

Ten vehicles, eight one-way trips per vehicle per day, 26 service days — 2,080 managed trips a month.

The crossover is arithmetic, not opinion. Per-vehicle pricing beats per-trip pricing whenever your vans are busy: at six or more one-way trips per vehicle per day, a $69 flat rate is cheaper than $250 + $0.50 per trip at any fleet size. Drop to four trips per vehicle per day — rural, long-distance, or a fleet padded with spares — and per-trip wins until you pass roughly 15 vehicles.

Manual dispatch versus software: the break-even math

The honest version of this comparison is not "software saves you money." It is that software converts dispatcher hours and billing leakage into a fixed subscription, and the conversion rate is lopsided. Here is the model at ten vehicles, with every assumption stated so you can substitute your own.

Assumptions: 2,080 one-way trips a month. Fully loaded dispatcher cost of $25 per hour including payroll taxes and benefits at 173 hours a month, so $4,325 per dispatcher. Average reimbursement of $32 per one-way trip, about $66,600 of monthly revenue. All-in vehicle operating cost of $0.62 per mile. These are modeling assumptions, not published figures — replace them with yours.

Against software at $350 to $1,290 a month, the return is between six and twenty-two times. Which means the interesting question is not the ten-van case — it is the small one.

Where break-even actually sits. At $60 to $69 per vehicle per month, the software has to recover about $2.50 to $2.75 per vehicle per service day. One prevented no-show at $32, or four saved deadhead miles, covers a vehicle for a week and a half. On arithmetic alone, break-even is one or two vehicles.

The catch: at one to three vans the owner is the dispatcher, so there is no payroll line to cut. That labor saving does not show up in your bank account — it shows up as your evenings back. Cash break-even at that size comes only from deadhead and billing accuracy, roughly $800 to $900 a month on a three-van book, which still clears a $150 to $210 subscription. Software becomes non-optional at the point you would otherwise hire your first full-time dispatcher: around 45 to 55 trips a day, or five to seven vans at normal utilization. Buy before that, not after — migrating 400 standing orders while short-staffed is its own punishment.

Manual dispatch also hides a compliance problem: you cannot audit what you did not record. If your trip log lives on a whiteboard, a broker recoupment audit is a coin flip. Our guide to NEMT revenue auditing covers what a defensible record looks like.

Booking and intake: where the hours actually go

Operators shop for dispatch and then discover dispatch was never the bottleneck — intake was. Trips arrive from four or five channels in different formats: broker portals, facility schedulers calling the office, standing-order templates, private-pay riders, same-day discharge calls. Every channel that lands as a phone call or a downloaded CSV is a channel someone re-types. In order of labor impact:

• Direct broker integration for the brokers you actually hold contracts with. A vendor that integrates with eleven brokers and none of yours integrates with zero brokers.
• A facility portal so dialysis centers and discharge planners enter their own trips. Bambi publishes a facility trip portal; RouteGenie and MediRoutes publish rider-side booking. Verify who can enter what, and whether those users consume paid seats.
• Recurring trip templates that handle a mid-series address change without regenerating the series. Our walkthrough of pre-scheduled trip automation gets into the failure modes.
• Duplicate and eligibility screening at intake, before the trip hits a route.

Rider and driver apps: tracking, ETAs and attestation

Real-time trip status does two jobs: it cuts the "where's my ride" call volume that eats your dispatchers, and it produces the timestamped record you need when a broker disputes a trip.

On the rider side, MediRoutes publishes a "Where's My Ride" notification feature, RouteGenie a rider app with booking, tracking, driver contact and trip rating, and Bambi GPS tracking with live ETAs. Ecolane, WellRyde, Tobi Cloud and Traumasoft do not publish rider-notification specifics. Ask which channel notifications use — SMS, app push, or IVR voice call — because a 78-year-old dialysis patient is not installing your app.

On the driver side, three details separate a usable app from a liability. Offline behavior: does the manifest persist and re-sync when the vehicle leaves coverage? Bambi publishes offline sync; the others do not state it. Attestation capture at the point of service — signature, photo or GPS-stamped confirmation — because that is the artifact that survives an audit. And whether navigation is built in or bounces the driver to a separate maps app, which is how arrivals get marked from the wrong parking lot. Assignment logic matters as much as the app; see our guide to driver and patient matching.

What you actually need at your fleet size

1 to 3 vehicles

You need trip intake, a driver manifest, a defensible trip record and an invoice you can send. You do not need route optimization across a fleet you can picture in your head. Buy the cheapest credible tier — published entry points here run $49.99 to about $210 a month — insist on no contract and no setup fee, and do not let anyone sell you an HR module for staff you do not have. What will actually hurt you at this size is a recoupment against sloppy documentation, so weight audit trail and BAA availability heavily.

4 to 15 vehicles

This is where automation earns its keep and where the wrong choice costs the most. You need real broker trip auto-import, multi-loading, will-call re-optimization, standing-order handling and multi-vehicle-type dispatch, plus reporting good enough to defend your OTP number in a rate conversation. Run the per-vehicle versus per-trip arithmetic above with your real trips-per-vehicle-per-day figure, and confirm that adding your eighth van does not trigger a tier jump.

15+ vehicles and multi-location

Now you are buying integration surface, not features: open API, telematics integration so you are not paying twice for GPS, an 837P or CMS 1500 export you control, role-based permissions across locations, and a data export you could hand to a successor system. Vendors at this end — Traumasoft, WellRyde, Ecolane, Nova, NovusMED — publish no pricing, so plan a real procurement cycle. If you also run ambulance service, a combined EMS and NEMT platform may consolidate two systems; verify the NEMT side is not a bolt-on.

Demo questions that expose weak products

Your data, their screen. Do not accept a canned demo dataset.

1. Import a real trip file from my broker, live, right now. Show me the failure log for the rows that do not map.
2. Which of my brokers do you hold a direct integration with, is it EDI or API, and who owns the connection when it breaks?
3. Show me a will-call return added at 2:40 p.m. re-optimized into a live route without rebuilding the afternoon.
4. Change the pickup address on one leg of a standing order running three times a week for six months. Show me the other 77 legs.
5. Dispatch a stretcher trip and an ambulatory trip to the same slot and show me the system refusing the wrong vehicle.
6. Generate an 837P or CMS 1500 from these completed trips, and show me the validation that catches a missing authorization before submission.
7. Put the driver app in airplane mode mid-manifest. What does the driver see, and what syncs when signal returns?
8. Show me the audit trail for one trip: who created it, every edit, every status change, with timestamps and GPS.
9. Will you sign a BAA, and can I see it before signature?
10. Export my full dataset — trips, riders, drivers, invoices — right now. What format, and is there a fee?
11. What is total first-year cost including implementation, integrations, notification credits, seats and payment processing? One number, in writing.
12. Two references at my fleet size in my state who switched to you in the last 12 months — and one who left.

Three tells. A vendor who will not import your file live does not have the integration they claim. A vendor who cannot export your data on demand is building an exit tax. And a vendor who treats HIPAA as a checkbox rather than a signed agreement has not read the rule — our HIPAA compliance guide covers what you actually owe.

Migration and exit risk

Switching costs are the real lock-in, not the contract. Before signing, get written answers on who does the historical data load and at whose expense, whether standing orders migrate as templates or flat rows, how long you run parallel systems, and what your data comes out as if you leave — a full relational export, or a PDF report pack. Contract red flags: auto-renewal with a notice window under 60 days, per-vehicle minimums that survive a fleet reduction, price escalators without a cap, and any clause making your trip data the vendor's asset.

What this actually means for your P&L

At published rates, NEMT dispatch software costs $0.17 to $0.62 per one-way trip against an ambulatory reimbursement somewhere between $25 and $45. That is half a percent to two and a half percent of trip revenue — smaller than your fuel line, smaller than your insurance line, and roughly the size of the billing leakage it is supposed to eliminate. The decision is not whether to spend it. It is whether the pricing model matches your utilization, and whether the product actually removes the manual intake step you are paying people to perform.

Next moves

1. Count your real trips per vehicle per day over the last 60 days. That number decides whether per-vehicle or per-trip pricing is cheaper for you.
2. List your active broker contracts and shortlist only vendors that name those brokers as live integrations.
3. Book three demos in one week and run the twelve questions verbatim, with your own trip file.
4. Demand one written first-year total cost per vendor, including implementation, integrations and processing fees.
5. Get the data-export answer in writing before you sign. Cheapest insurance in this category.