NEMT Software: Custom Build or Buy Tobi and RouteGenie
Buy. Under roughly 40 trips a day on one broker contract in one county, Tobi or RouteGenie solves your problem for a few hundred dollars a month and vans beat software every time at that size.
On this page
Buy. Under roughly 40 trips a day on one broker contract in one county, Tobi or RouteGenie solves your problem for a few hundred dollars a month and vans beat software every time at that size. Building becomes defensible past 150 to 200 trips a day across three or more broker and payer relationships.
What the off the shelf products actually do well
Non-emergency medical transportation lives or dies on two numbers: billable trips per vehicle per day, and the share of those trips paid on first submission. Before anyone talks about building, note that the products in this market solve both for small operators, competently and cheaply.
Tobi and RouteGenie cover scheduling, recurring standing orders, driver dispatch and a driver app, and they are inexpensive. MediRoutes is strong on routing. NEMT Cloud Dispatch covers the basics. Further up, TripSpark, Ecolane and Trapeze serve transit authorities and larger paratransit operations with genuinely mature optimisation. WellRyde exists inside the broker world itself. Around them, Office Ally and Availity handle clearinghouse submission and remittance, and every one of these has real operators running on it today.
The standards are settled too. The professional claim is the 837P, the remittance comes back as an 835, eligibility runs on 270 and 271, and the transportation codes and their origin and destination modifier pairs are published rather than negotiated. Any product working in this space handles the happy path.
Buy, and do not call us, if this is you:
- Under about 40 trips a day, one county, one dispatcher.
- One broker contract, with no fee for service Medicaid line alongside it.
- A denial rate your biller can explain in one sentence.
- Standing orders that rarely change once set.
- No facility asking to enter its own trips at 5am.
Where they stop: broker reconciliation and the no show evidence chain
Here is the workflow no product in this category models properly, and it is where your margin goes.
ModivCare, MTM, Access2Care, Veyo and the state fee for service line each hand you trips differently. Some push a nightly file, some expect a portal pull, some send changes by email to a shared inbox your dispatcher checks between radio calls. A trip cancelled on the broker side at 11pm is still on your board at 6am, and your driver runs a leg you will never be paid for. Products do have broker integrations, and they work until they do not, because your integration sits on the vendor's roadmap rather than yours. When your state changes brokers mid contract, you wait.
What a build does is treat every broker as a normalised adapter into one canonical trip record carrying the broker trip identifier, your internal leg identifier, member identifier, level of service, authorisation number and reconciliation state. Then a job runs every fifteen minutes and diffs the broker's current picture against your board: cancelled on their side but still assigned here, level of service downgraded from wheelchair to ambulatory, mileage mismatch on the return leg. Your dispatcher works a short exception list instead of four portals.
The second gap is evidence. A no show costs you a dry run and gets denied unless you can prove the driver was there, waited the contractually required time and attempted contact. Most driver apps capture an arrival timestamp and a tap. What they rarely produce is a package that survives an audit, and they almost never enforce the specific wait rule in your specific contract, which might be ten minutes for one broker and fifteen for the state line. A custom app enforces it at the moment of truth: geofenced arrival with accuracy recorded, a wait timer the driver cannot shorten, a logged call attempt through a recorded number, a timestamped photo, and an automatic exception to dispatch before the driver rolls.
The third gap is claim construction. The origin and destination modifier is a two character pair, the first character for where the trip started and the second for where it ended, so a residence to hospital leg codes differently from a skilled nursing facility to hospital leg. Get it wrong and the denial looks identical to fifteen other denial types. Products let you map codes statically. They do not know that a particular payer started rejecting a combination three weeks ago, which your biller currently learns through pattern recognition and a sticky note.
The arithmetic: cost per vehicle or per trip versus cost to build
Vendors in this market price per vehicle or per completed trip. Run both against your own volume.
At roughly $75 per vehicle per month across 40 vehicles, that is $36,000 a year, which is nothing against a build. At a per trip model of $1.50 and 300 trips a day, you are at about $164,000 a year, which is a different conversation entirely. Get your contract clear on which model you are on and what it looks like at double your volume.
Then price the leaks the subscription does not touch. Take 300 trips a day at your average ambulatory rate and apply the share you write off to denials and undocumented no shows. For most operators at that size the annual figure runs into six digits, which is two dispatchers and a van. Add the dispatcher hours spent re-keying trips between broker portals at the end of every shift, and the biller hours spent reworking claims six weeks after the trip.
The crossover sits near 150 to 200 trips a day, or three or more broker and payer relationships, whichever arrives first. Below it the product is cheaper than the engineering and buying vehicles returns more. Above it the write off line alone exceeds what a build costs, and it recurs every year while a build is a one time asset with a maintenance tail.
What a custom build actually costs
A focused first release covering the canonical trip model, one or two broker adapters with reconciliation, a dispatch board that replaces the spreadsheet, a driver app with geofenced arrival and the wait timer evidence chain, and 837P generation with 835 posting runs $60,000 to $130,000 and ships in 12 to 16 weeks. That is enough to stop the two biggest leaks. A full platform adding multi broker integration at scale, continuous optimisation, a facility portal, intake automation and claim scoring against your own remittance history runs $150,000 to $400,000 phased across 6 to 12 months.
- Data migration. Budget 10 to 25 percent of build cost. Trip history is easy. Standing orders and recurring templates are the hard part, because a template nobody updated is exactly what generates six weeks of denied no shows, and every ambiguous one needs a human decision before cutover.
- Year two onward. Budget 15 to 20 percent of build cost annually. Brokers change file formats and portals, states re-procure, and a portal scrape adapter costs roughly double a clean interface to maintain rather than to build.
What else drives it up: privacy posture, meaning business associate agreements, audit logging on every protected health information read, encryption at rest and access controls that survive a real audit. And offline tolerance in the driver app, because vans go through dead zones and the app must queue signatures and timestamps without duplicating trips.
The four situations where building wins
Two of these should hold before you commission anything.
- Regulatory fit. Federal rules require state Medicaid programmes to ensure transportation to and from providers, and each state implements that differently, which is why your broker rules, wait times and documentation requirements differ by contract. Layer on privacy obligations and physician certification statements with expiry dates, and the compliance evidence has to be generated by the system rather than assembled by your biller. Products treat contract rules as settings. At three contracts they are logic.
- Scale economics. Past 150 to 200 trips a day, per trip pricing and the denial write off move against you at the same time.
- A workflow that is your competitive advantage. Your best dispatcher holds the real routing model in her head: which dialysis centre runs late on Tuesdays, which building has a faster service lift, which driver should never take the memory care facility. Encoding that as data rather than folklore is what keeps on time performance when she takes vacation.
- Integration sprawl. Count them: scheduling, three broker portals, the clearinghouse, the driver app and payroll. Once three or more must agree about one leg, a person becomes the integration, and that person is currently your growth constraint.
How to decide in a week
Run this on your own data before booking another demonstration.
- Monday. Pull forty denials from last quarter and classify each by root cause: modifier pair, authorisation, eligibility, undocumented no show, cancelled on the broker side. If more than half fall into two buckets, you have a fixable systems problem rather than a billing problem.
- Tuesday. Take one day's board and count the legs that changed on the broker side after your dispatcher last looked. That is your dead mile rate.
- Wednesday. Pick five no show denials and try to assemble the appeal packet from what you hold: arrival timestamp, geolocation, wait duration, call attempt, photo. Count how many you could actually defend.
- Thursday. Ask your vendor in writing whether you are priced per vehicle or per trip, what it costs at double volume, and what happens if your state changes brokers next year.
- Friday. Decide. Two of the four conditions plus a failed Wednesday means build. Otherwise stay and buy another van.
There is an honest middle path most operators skip. Keep the off the shelf tool for scheduling and build only the reconciliation and billing layer above it, reading through its interface. That is often a $60,000 to $90,000 project that recovers more money than a full replacement and never puts your dispatch board at risk. Take it if it fits.
Whatever you choose, pay for discovery before code. That phase should end with a signed product requirements document covering the trip, leg, authorisation and claim models, the broker adapters, the evidence chain and the acceptance criteria. You own it and can take it to any firm.
Digital Heroes writes that specification first and the client owns the repository from the first commit, with the system running in your own cloud account. We hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law rather than ours. More than fifty specialists, over 2,000 projects, and a named team you meet before signing, verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. We run our own products, ShopScore, HeroCheckout and Section Vault. We are the wrong firm for a 30 trip a day operator, and wrong for anyone who wants a fixed price before the broker contracts have been read.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Grand View Research valued the global field service management market at USD 4.43 billion in 2022 and projects it to reach USD 11.78 billion by 2030, a 13.3% CAGR, driven by growing field operations in telecom, utilities, construction and energy. Source: Grand View Research (2023) →
- PTC identifies the leading causes of failed first visits as parts unavailability (the single most-cited complaint, named by 51% of field service executives), technicians lacking the required equipment or skills, and insufficient time allocated to the job - making parts logistics and skills-based dispatch the highest-leverage fixes. Source: PTC (2023) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
Frequently asked questions
How much does custom NEMT software cost to build?
A focused first release with the canonical trip model, one or two broker adapters, a dispatch board, a driver app with the evidence chain, and 837P generation with 835 posting runs $60,000 to $130,000. A full platform adding multi broker integration, optimisation, a facility portal and claim scoring runs $150,000 to $400,000. Add 10 to 25 percent for migration and 15 to 20 percent annually thereafter.
How long until drivers are using it?
Twelve to 16 weeks to a first release, and never build all of it before any of it reaches a driver's hands. Put the driver app in one vehicle group first, then widen. Standing order migration usually sets the real date, because every recurring template with an ambiguous history needs a human decision before you can run a live day on the new board.
Who owns the code and the trip data if we commission a build?
You should own the repository, the infrastructure runs in your cloud account, and a documented handover is in scope from the start. At Digital Heroes the client owns the code from the first commit. Ask any developer what happens if you want to move off them in year two. A clean answer means they expect the software to outlive the relationship, which is the correct expectation.
What happens if our state changes brokers mid contract?
With a product you wait for the vendor's roadmap. With a build you write another adapter, which is a scoped piece of work you can start the week the award is announced. Ask any developer specifically what they do when a broker has no interface and the answer is a portal, because the real cost of a scrape adapter is maintenance rather than the initial build.
Can we keep Tobi or RouteGenie and build only the billing layer?
Yes, and for many operators it is the better trade. Leave scheduling where your dispatchers already know it, then build the reconciliation job, the evidence capture and claim construction with validation against your own remittance history. It recovers money without putting the dispatch board at risk, and it is a much smaller commitment than a full replacement.
How do we prove a no show when the broker denies it?
With records captured at the moment rather than reconstructed later: geofenced arrival with location accuracy, a wait timer the driver cannot shorten, a logged call attempt with duration, a timestamped photo, and an exception raised to dispatch before the driver leaves. Build that chain first, because it converts an automatic write off into a recovery line and also prevents the dry run itself.
What is the difference between dispatch software and a broker portal?
A broker portal is the payer's record of what it authorised and expects. Dispatch software is your record of what you are actually running today. Neither reconciles against the other, which is why trips cancelled at 11pm are still on a board at 6am. The reconciliation between the two is the thing worth building and the thing nobody sells you.
Does the origin and destination modifier really cause that many denials?
It causes a large share of the ones that look mysterious. The pair is two characters, the first for where the leg started and the second for where it ended, so the same vehicle running the same distance codes differently depending on whether the pickup was a residence, a skilled nursing facility or a dialysis centre. Static code mapping cannot keep up with payer specific behaviour.
Is artificial intelligence useful in this category or is it a sales line?
Two narrow uses earn their place. Extracting signature dates, diagnoses and certification periods from physician certification statements that arrive as faxes and phone photos, so you are warned before a certification lapses. And classifying free text denial remarks into actionable buckets so your biller works appeals by category. Neither should ever submit a claim on its own.
What should we ask a developer before hiring them for NEMT work?
Ask them to explain why a facility to facility leg codes differently from a residence to hospital leg, without looking it up. Then ask how they model trip, leg, authorisation and claim, because those are four objects with four lifecycles and anyone who models a trip as one row will build something that cannot handle a will call return.
What should I have ready before I contact a development agency about field service software?
Bring your current workflow, not a feature list: how a job moves from first call to paid invoice today, where it breaks, what tool you use now with its monthly bill, and the workaround spreadsheets your team maintains. Add your integration list (accounting system, payment processor, phone system) and an honest budget range. A good agency can scope accurately from that in one or two calls, while a vague request for an app like ServiceTitan costs you weeks of discovery.
Can I get my customer and job history out of ServiceTitan or Jobber if we switch to custom software?
Yes. Jobber and Housecall Pro both provide CSV exports of clients, jobs, and invoices, and ServiceTitan data comes out through its API and report exports, though attachments and full audit history take extra work. Budget 2 to 4 weeks of migration effort inside the project for cleaning, mapping, and verifying records, and run both systems in parallel for at least two billing cycles before cutting over.
Is Housecall Pro enough for a growing HVAC or plumbing company, or do we need custom software?
Housecall Pro holds up well to roughly 10 to 20 technicians on standard residential jobs, with its Essentials plan listing around $129 per month for up to five users. The ceiling appears with commercial work: multi-visit projects, progress billing, equipment service history, and inventory are thin, which is when owners start managing the business in exported spreadsheets. Use the spreadsheet count as your signal: three or more recurring workarounds mean the tool no longer fits.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Should I hire a freelancer or an agency to build my field service software?
An agency in almost every case, because a field service build spans a mobile app, a dispatch web console, a backend, offline sync, and accounting integrations, which is four or five specialties one person rarely covers. A freelancer is the right choice for a single integration or a well-scoped add-on under $15,000. The solo-built field service systems Digital Heroes inherits fail most often at handover, when the freelancer has moved on and nobody can safely modify the sync engine.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other field service management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Vivaan.
Senior Backend Engineer · Node · Delhi · 2 posts on the site
Published · Last updated .
