How Much Does NEMT Software Cost in 2026?
A custom non emergency medical transportation platform runs $60,000 to $400,000, with a canonical trip model, dispatch board, driver app and claim generation at the lower end and multi broker reconciliation, continuous optimisation, facility portal and claim scoring at the upper.
On this page
A custom non emergency medical transportation platform runs $60,000 to $400,000, with a canonical trip model, dispatch board, driver app and claim generation at the lower end and multi broker reconciliation, continuous optimisation, facility portal and claim scoring at the upper. The decision that moves the number most is how each broker hands you trips. A clean interface is a contained piece of work. A broker that only offers a portal needs a scrape adapter, which costs roughly double to build and carries permanent maintenance because it breaks whenever they redesign a page. Three brokers with three interfaces and three brokers with two portals are very different projects.
The bands a non emergency medical transportation build falls into
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 application 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 in our delivery experience. That is enough to stop the two biggest leaks.
A full platform adds multi broker electronic data interchange at scale, continuous optimisation, a facility scheduler portal, voice intake, claim scoring against your own remittance history and a real reporting layer. That runs $150,000 to $400,000 phased across 6 to 12 months.
There is also a middle path most operators skip. Keep Tobi or RouteGenie for scheduling and build only the reconciliation and billing layer on top, reading through its interface. That is often a $60,000 to $90,000 project which recovers more money than a full replacement and never puts your dispatch board at risk.
What drives a transportation build up
- Broker and payer count, and how each one talks. Every relationship is its own adapter, its own quirks and its own test cycle. A portal scrape adapter costs roughly double a clean interface integration, and the real cost is maintenance rather than build.
- Privacy posture. Business associate agreements, audit logging on every protected health information read, encryption at rest, and access controls that survive a real audit. This is engineering time and it is not optional.
- Offline tolerance. Vans go through rural dead zones, so the driver application must queue signatures and timestamps and reconcile on reconnection without duplicating trips. Getting that wrong creates phantom trips, which is worse than losing them.
- State fee for service rules. Running Medicaid fee for service alongside broker work means a second set of billing rules and a second reconciliation path.
- Migration of standing orders. Recurring templates for dialysis and treatment patients carry rules that live in the vendor's schema, and they are the hard part of migration, not trip history.
What keeps the number down
Take the reconciliation and billing layer alone if it fits. It is the cheapest project in this category that returns real money, and it tells you within a quarter whether a full replacement is warranted.
Start with the brokers that offer interfaces and leave the portal one until phase two. You will have learned what your canonical model actually needs by then, and the scrape adapter will be built once rather than twice.
Do not build route optimisation in release one. It depends on learned load times and will call lag distributions computed from your own history, and until the driver application has been capturing timestamps for a few months there is nothing to learn from.
Keep the driver application narrow. Geofenced arrival, an enforced wait timer, logged call attempts and a timestamped photo is the whole evidence chain. Everything else is convenience and can wait.
A worked example that adds up
An operator running around 40 vehicles at 300 trips a day, across three broker relationships of which two offer interfaces and one offers only a portal, plus a state fee for service line. Phase one, 15 weeks:
- Discovery and canonical modelling of trip, leg, authorisation and claim as four objects: $14,000
- Canonical trip record and dispatch board replacing the spreadsheet: $30,000
- Two broker interface adapters with a reconciliation job running every 15 minutes: $28,000
- Driver application with geofenced arrival, enforced wait timer, logged call attempts and photo: $34,000
- 837P generation and 835 remittance posting: $26,000
Phase one subtotal: $132,000.
Phase two, across the following nine months:
- Third broker portal scrape adapter with a maintenance harness: $30,000
- Continuous optimisation using learned load times and will call lag distributions: $58,000
- Facility scheduler portal for self service trip entry: $28,000
- Voice intake agent restricted to create and read: $32,000
- Claim scoring against remittance history with a pre submission review queue: $36,000
- Certification document extraction with expiry flagging: $24,000
- Reporting on on time performance, denial categories and unbilled miles: $26,000
Phase two subtotal: $234,000. Total: 132 plus 234 equals $366,000. Note the portal adapter at $30,000 costs more than both interface adapters combined at $28,000, which is the whole argument for asking how each broker delivers trips before anyone quotes.
How the spend phases
Discovery is two weeks and its most important output is the object model. Trip, leg, authorisation and claim are four different things with four different lifecycles, and a developer who models a trip as one row will build something that cannot handle a will call return.
Phase one ships in 12 to 16 weeks, then runs parallel for two to four weeks before cutover. Budget explicit time to validate every recurring order against the broker's current authorisation before you switch, because standing orders are where migration goes wrong.
Phase two leads with the portal adapter and claim scoring, since those attack denials directly. Optimisation comes next and needs a few months of driver application timestamps behind it. Voice intake goes last, and it should launch with the strict boundary that the agent can create and read but never cancel or modify, which is what makes it safe to run overnight.
The ongoing costs nobody quotes
Portal scrape maintenance is the running cost operators most often miss, because it is invisible until it breaks. When a broker redesigns a page your feed stops, and someone has to fix it that day. Any developer who has actually built one will tell you the maintenance exceeds the build over three years.
Engineering maintenance runs at roughly a sixth of build cost annually in our delivery experience, near $61,000 on the $366,000 example. Broker rule changes, a new state contract, code and modifier changes, driver application updates on new phone models and reporting requests all arrive continuously.
Telephony and voice usage are per minute and scale with call volume. Device fleet costs are real too, since driver phones are used hard, get lost and need encrypted local storage with remote wipe.
Then there is the audit obligation. Producing an access report for a single member across a date range on request is a capability you maintain, not a feature you ship once.
Comparing a build against your current renewal
A Tobi or RouteGenie subscription is a small number and it is not the comparison. Run it on your own figures instead.
Take 300 trips a day at your average ambulatory rate and take the slice you write off to denials and to no shows you cannot document. For most operators at that size the annual number is six digits, which is two dispatchers and a van.
Then add the re keying labour. If a dispatcher spends the last two hours of every shift moving trips between broker portals and your scheduling tool, that is a quarter of a position doing data entry, every day, forever.
Then add unbilled miles. Every trip cancelled on the broker side overnight and still on your board at 6am is a leg you drive and never bill. Count last month's.
Then the one you cannot invoice: the facility relationship you lost over on time performance you could not measure, and the contract that went with it. A $366,000 platform amortised over five years plus annual engineering is roughly $134,000 a year. The denial and unbilled mile lines alone usually clear it.
When buying beats building
Buy if you are under roughly 40 trips a day, running one broker, in one county, with one dispatcher. Tobi and RouteGenie are competent products that solve that operator's problem for a few hundred dollars a month, and buying vans beats buying software at that size every time. Do not let anyone tell you otherwise.
Buy and stay bought if your broker mix is stable and single. Most of the value in a build comes from reconciling multiple incompatible trip feeds, and with one feed there is nothing to reconcile.
Take the middle path if you are somewhere between. Keep Tobi or RouteGenie for scheduling, build only the reconciliation and billing layer reading through its interface, and see what it recovers before committing to a replacement.
Build when these show up together: more than 150 to 200 trips a day, three or more broker or payer relationships, a denial rate your biller cannot explain in one sentence, a full time person whose job is moving data between two systems, and a lost contract or facility relationship over on time performance you could not measure. The clearest single signal is an operations manager's spreadsheet that the software cannot replace, because that spreadsheet is a specification telling you the vendor's model does not match yours.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- Comparesoft reports the field-service industry-average first-time fix rate is about 80%, best-in-class providers reach roughly 90%, scores below 70% put the business at risk, and providers exceeding 70% FTFR saw customer retention around 86%. Source: Comparesoft (2024) →
- EMARKETER reports that over 54% of mobile commerce transactions now happen within shopping apps rather than mobile browsers, underscoring the app channel's growing dominance of m-commerce. Source: EMARKETER (2025) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
Frequently asked questions
What is the total cost of custom NEMT software?
$60,000 to $130,000 for a focused first release covering the canonical trip model, one or two broker adapters with reconciliation, a dispatch board, a driver application with the evidence chain, and 837P generation with 835 posting, shipping in 12 to 16 weeks in our delivery experience. A full platform runs $150,000 to $400,000 across 6 to 12 months.
A 40 vehicle operator at 300 trips a day across three brokers lands near $366,000 across both phases. A reconciliation and billing layer alone on top of your existing scheduler is often $60,000 to $90,000.
What does it cost to run each year after go live?
Budget continuing engineering equal to roughly a sixth of build cost annually, around $61,000 on a $366,000 platform, consumed by broker rule changes, new state contracts, code and modifier changes, driver application updates and reporting requests.
The line operators most often miss is portal scrape maintenance, which is invisible until a broker redesigns a page and your feed stops that morning. Over three years the maintenance on a scrape adapter exceeds its build cost. Add telephony usage, driver device fleet replacement and the standing obligation to produce member level access reports on request.
How long does it take to migrate off Tobi or RouteGenie?
Twelve to sixteen weeks to a first release, then two to four weeks running parallel before cutover. The hard part of migration is not trip history, it is standing orders and recurring templates for dialysis and treatment patients, because those carry rules that live in the vendor's schema.
Budget explicit time to validate every recurring order against the broker's current authorisation before you switch. A standing order that silently kept an old pickup time produces six weeks of no shows the broker will deny.
Is Tobi or RouteGenie enough for our operation?
Below about 40 trips a day on a single broker contract, yes, comfortably. Both are competent products at a few hundred dollars a month and your capital belongs in vehicles at that size.
Above 150 to 200 trips a day with three or more broker or payer relationships the model stops matching your operation. Their broker integrations cover the biggest names on the vendor's roadmap and timeline, so when your state changes brokers mid contract or a broker changes its will call rules, you wait, and your subscription does not move a roadmap.
Why does a portal broker cost more than one with an interface?
Because a scrape adapter has to reproduce a human's path through a web application and it breaks whenever that application changes. In the worked example one portal adapter was $30,000 against $28,000 for two interface adapters combined.
Ask every prospective developer what they do when a broker has no interface. If they have not built and maintained a scrape adapter they do not know that the real cost is maintenance rather than build, and they will underquote and then resent the project.
Can we build only the billing layer and keep our current scheduler?
Yes, and it is often the smarter first move. Keeping Tobi or RouteGenie for scheduling while building reconciliation and billing on top, reading through its interface, is typically a $60,000 to $90,000 project.
It recovers denial and unbilled mile money without putting your live dispatch board at risk, and after a quarter you will know from real numbers whether a full replacement is warranted. Most operators skip this option and should not.
What does claim scoring cost and does it reduce denials?
Around $36,000 in the worked example. Every 835 remittance is parsed and stored with the claim's full attribute set, so the system learns which combinations of payer, level of service, origin type, destination type and modifier actually paid, and new claims below threshold route to a pre submission review queue with the specific reason.
It works by preventing rather than appealing. The other half of the recovery is evidence capture at the vehicle, where geofenced arrival, an enforced wait timer and logged call attempts turn no show denials from an automatic write off into a winnable appeal.
How do we cost the money we are losing today?
Take your daily trip count at your average ambulatory rate and the slice written off to denials and to no shows you cannot document. At 300 trips a day that annual figure is usually six digits, which is two dispatchers and a van.
Add re keying labour, roughly a quarter of a dispatcher position if the last two hours of every shift go to moving trips between portals. Add unbilled miles from trips cancelled broker side overnight and still on your board at 6am. A $366,000 platform amortised over five years plus engineering is roughly $134,000 a year against those.
Where does AI belong in this budget, and where does it not?
Two narrow places totalling around $56,000 in the worked example. Certification document extraction at $24,000 pulls signature dates, diagnoses and certification periods off faxed forms and phone photos, then flags certifications expiring inside 30 days so you stop running unbillable trips. Denial classification buckets free text remittance remarks so your biller works appeals by category.
A voice intake agent at $32,000 is worth it for after hours confirmations and new bookings, with a hard boundary: it can create and read, never cancel or modify. Nothing here should ever auto submit a claim.
At what point does it make sense to switch from ServiceTitan to custom software?
The switch usually pencils out once your ServiceTitan bill passes roughly $75,000 a year and your team still maintains workaround spreadsheets beside it. ServiceTitan keeps pricing quote-only, and the quotes owners share in Digital Heroes scoping calls run several hundred dollars per technician per month on annual contracts, so a 30-technician shop can spend a full custom build's budget every 12 to 18 months in fees. If ServiceTitan fits your workflow cleanly, stay; the case for custom is a workflow the product forces you to bend.
Should we start with an MVP or build the full field service platform in one go?
Start with an MVP that can run one real crew for one real week: scheduling, dispatch, job completion with photos and signatures, and invoicing. That slice typically costs $40,000 to $70,000 and ships in about 12 weeks, and technician feedback then decides phase two. Teams that built the full platform up front reworked 30 to 40 percent of it after field use in Digital Heroes experience, which is the most expensive way to discover what dispatchers actually need.
How much does it cost to build custom field service management software for a small business?
For a company running 5 to 25 technicians, a focused first version with scheduling, dispatch, a technician mobile app, and invoicing typically runs $40,000 to $80,000 in Digital Heroes delivery experience. A full platform with offline mode, a customer portal, GPS tracking, and accounting sync lands between $90,000 and $180,000. The two biggest cost drivers are offline sync depth and integration count, so pin both down in scoping and the quote holds.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
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.
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.
What security and compliance does custom field service software need?
The baseline is encryption in transit and at rest, role-based access so a technician sees only their own jobs, remote wipe for lost phones, and audit logs on anything that touches money. Run payments through a processor like Stripe or Square so card data never touches your servers and the heaviest PCI burden stays with them. If your crews serve regulated sites such as healthcare or government facilities, say so in scoping, because access and documentation requirements shape the data model.
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.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
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.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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 Ethan.
Content Strategist · New-york · 6 posts on the site
Published · Last updated .
