Air Medical Transport Software: Build the Launch Decision Layer or Buy a Dispatch Product
The threshold is roughly six aircraft across more than one base. Below that, where a single communications specialist personally knows every crew and every aircraft, buy a purpose built dispatch product and fix the process around it, because your constraint is people rather than information.
On this page
The threshold is roughly six aircraft across more than one base. Below that, where a single communications specialist personally knows every crew and every aircraft, buy a purpose built dispatch product and fix the process around it, because your constraint is people rather than information. Above it, once nobody holds the whole state and duty clocks, maintenance status and weather sit on four screens under a three minute clock, build the launch decision layer beside the dispatch product you keep. That first release runs $90,000 to $180,000 over 14 to 18 weeks. Almost nobody should replace the dispatch product itself.
When is off the shelf genuinely the right call here?
Buy, and here is which one. Flight Vector is a purpose built air medical computer aided dispatch product and it handles the communications center workflow properly, which is more than can be said for the generic public safety systems some programmes have adapted. If you run one or two aircraft from a single base, that plus disciplined process is the right answer, and a build would be an expensive way to formalise knowledge that already fits in one head.
Keep ZOLL emsCharts, or whichever electronic patient care record you run, in every scenario. It does clinical documentation well, it carries the regulatory and clinical review expectations that come with that, and rebuilding it adds risk without adding capability. The same applies to Golden Hour on the documentation and revenue cycle side. Integrate, do not replace.
The second buy case has nothing to do with size. If a hospital system owns your programme and mandates its platform, your effort belongs in using that platform properly and fixing the process gaps around it. A parallel build your parent organisation will not fund or support is a worse position than an imperfect mandated system.
The third is honesty about the failure you are trying to fix. If your specialists make errors because the desk is understaffed at peak, that is a rostering and training problem. Software will not fix a two person desk covering seven bases on a Friday night, and buying a bespoke system to paper over it is the most expensive way to avoid a staffing conversation.
When does a custom build actually pay off?
Build when the accept decision depends on data nobody can see at the moment it is made. That is the structural fact of this industry: the accept is decided in minutes, its consequences are effectively irreversible, and it depends on information owned by three departments.
The clearest trigger is a mission accepted that could not legally be completed. If that has happened more than once for duty, maintenance or configuration reasons, the information problem is real and it is not going to resolve itself as the fleet grows. Duty state computed from a schedule rather than from events will be confidently wrong at exactly the wrong moment.
The second trigger is risk assessment timing. If your flight risk assessment is completed during preflight, it documents a decision already made rather than informing it, which inverts its purpose. Moving it in front of the accept is the single highest value change available in this category, and it depends on the system already knowing time of day, remaining duty, aircraft and landing zone history.
The third is turndown data. If your quality committee cannot answer how often you decline, at which bases, in which conditions, and whether the pattern shifted after a policy change, you are governing by anecdote. Turndowns logged as free text notes are unanalysable.
The fourth is an operational control center requirement. That raises the bar on what the person exercising operational control can actually see, and reconstructing live aircraft status, crew duty state and risk assessment from four systems afterwards is not the same thing as having it in one place at the time.
How do they compare on the things that matter in this industry?
Duty state. Dispatch products know where the aircraft is. Crew scheduling systems hold planned duty. Neither answers whether this crew can legally fly this mission right now, because that joins scheduling data, maintenance data and operational events in real time. A build makes duty a live computed value: duty starts when the crew signs on, flight time posts from the completed leg rather than a form the next morning, and rest is recorded when it begins.
Aircraft status. Maintenance tracking knows component times and inspection due points. Dispatch knows the aircraft is green. The damaging case is the middle one, an aircraft technically available with 1.4 flight hours before an inspection is due, committed to a two hour mission. Bringing hours to next limiting event onto the dispatch view is a small piece of engineering with a direct operational effect.
Availability. This is where the two routes differ most and it is invisible on a feature list. A communications center system that cannot fail needs redundancy, tested failover and a degraded mode with local state and reconciliation on recovery. In a worked example that engineering was $38,000 of a $170,000 first phase, close to a quarter, and it produces nothing a specialist can point at on a screen. It is also the line a generalist developer omits, which is why their quote looks cheaper.
Records. A packaged stack leaves flight times, crew, aircraft and patient linkage in four places, reconciled by a coordinator days later. Automatic close out with exceptions raised is the difference between a complete billing packet and one assembled from memory.
What does total cost of ownership look like at your scale?
The comparison is not your dispatch licence, because in the recommended shape you keep paying it. What you are comparing against is what the gap currently costs you, and most programmes have never priced it.
Count the aborted launches over twelve months, meaning every mission accepted and then not completed for duty, maintenance or configuration reasons. Price each at your own flight hour cost plus the transfer that went elsewhere. Then ask your revenue cycle team how many flights closed with an incomplete packet last year and what happened to them. Reimbursement here is contested and the completeness of the record carries financial weight, so confirm the interpretation with your compliance team, but incomplete records lose money under every reading.
On the build side, a first release covering a single launch decision view with live crew duty state, aircraft availability including next limiting event, base and configuration capability, and structured request and turndown logging runs $90,000 to $180,000 over 14 to 18 weeks in Digital Heroes delivery experience. A full platform adding risk assessment scored inside the accept flow with approval routing, crew scheduling, post flight reconciliation, billing handoff, maintenance integration and quality reporting runs $220,000 to $500,000 across 8 to 14 months.
A programme with eleven aircraft across seven bases running both rotor and fixed wing lands near $410,000 across both phases. Annual engineering runs about a sixth of build, roughly $68,000 on that platform, consumed by fleet changes, new bases, vendor interface changes and duty policy revisions, plus scheduled failover testing which is engineering time rather than an assumption. Add redundant hosting, weather data licences priced per seat or site, and annual refresher training given real shift turnover.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In air medical this is not a fallback, it is the recommended shape for essentially every programme large enough to be asking the question.
Keep Flight Vector or your existing computer aided dispatch for the communications workflow, the radio log and the call taking it already handles well. Keep the electronic patient care record for clinical documentation. Build the launch decision layer beside them: live duty state fed by sign on and posted flight time events, aircraft availability including hours to next limiting event and configuration status, base and capability matching, and structured request logging with dispositions. The launch decision is what is broken. The radio log usually is not, and replacing it buys you a migration rather than a safety improvement.
Inside that layer there is a further sequencing hybrid. Take crew duty first, because it removes the failure everyone in the programme can already describe from memory. Aircraft next limiting event is a close second and costs less. Weather integration can wait if your specialists already trust a source on a second screen, and the crew mobile application can wait provided sign on and rest events are being captured somehow from day one, even on a simple screen.
The condition is interface access. Ask your dispatch and maintenance vendors what they expose before designing around it, and settle the privacy review on clinical linkage early, because it runs at its own pace regardless of your schedule.
Which should you choose, by operator size and stage?
One or two aircraft, single base. Buy Flight Vector, keep your patient care record, and invest in process and staffing. Your specialist holds the whole picture and software cannot improve on that. Write down your base minimums anyway, because the exercise is cheap and it is the first thing any future build needs.
Three to six aircraft, two or three bases. Stay bought and start instrumenting. Log turndowns in a structured way even if it is a form, count aborted launches for a year, and capture crew sign on and rest as events rather than as a schedule. You are building the evidence that decides whether the next step is justified, and you are fixing duty accuracy for free.
Six to twelve aircraft, multiple bases. This is the crossover. Build the launch decision layer at $90,000 to $180,000 and go live at one base in parallel with existing practice before the rest follow. Programmes that cut over everywhere at once discover their duty event capture gaps during a real mission, which is the wrong time.
Twelve or more aircraft, rotor and fixed wing, or an operational control center requirement. Build the full platform, phased, and lead phase two with the risk assessment. A year of scored assessments shows which combinations of factors your programme routinely accepts, which is a conversation about culture nobody could previously have with evidence.
The financial case is utilisation, fewer aborted launches and cleaner documentation. The safety case is that the accident chain in this industry is individually acceptable factors accumulating inside a three minute decision, and software cannot make that decision but it can stop the person making it from guessing.
When you are ready to turn this into a specification, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. 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.
- 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) →
- 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) →
- Flexera's 2025 State of the Cloud Report (survey of 750+ technical and executive leaders) found that 84% of respondents believe managing cloud spend is the top cloud challenge for organizations today, with cloud budgets already exceeding limits by 17%. Source: Flexera (2025) →
- 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) →
Frequently asked questions
What does it cost to switch off Flight Vector?
In the shape we recommend, nothing, because you keep it. The decision layer sits beside the dispatch product and consumes from it rather than replacing the communications workflow, so there is no migration and no retraining on call taking.
If you did replace outright, the cost is not the software, it is the parallel operation. A communications center cannot run on an unproven system, so you would fund both plus a staffed overlap, and you would be spending that to rebuild the part that was already working.
What happens if our dispatch vendor changes pricing or its interface?
Pricing is the smaller risk, because in the hybrid shape the licence is a known line you can decide about. The interface is the larger one, and it is worth asking what is exposed and under what terms before you design around it.
The same applies to weather data. Those licences continue and are usually priced per seat or per site, and the terms constrain how you may display and retain the data, so switching providers later means reworking the interface rather than changing a setting.
How long before the first base is running on a custom decision layer?
Fourteen to eighteen weeks to first release, preceded by two to three weeks of discovery, in Digital Heroes delivery experience. Discovery is unusually valuable here because base specific minimums and local practice are rarely written down in one place, and the exercise typically surfaces at least one rule that two bases apply differently without either knowing.
Go live at one base in parallel with existing practice. Full platform delivery runs 8 to 14 months, with risk assessment leading phase two.
Is Flight Vector enough for a programme with ten aircraft?
It remains the right product for the communications center workflow and most operators that size should keep it. What no dispatch product can be on its own is the single authority on whether a specific crew can legally fly a specific mission right now, because that joins scheduling, maintenance and operational events owned by three departments.
At ten aircraft the answer is almost always the hybrid: keep Flight Vector, build the decision layer beside it, and integrate maintenance status into the same view.
Can we build only the duty clock and leave the rest?
Yes, and it is the correct first move. Duty state computed live from sign on events and posted flight times removes the failure every programme can already describe from memory, and it costs less than the aircraft and weather work around it.
Capture sign on and rest from day one even on a simple screen, because duty accuracy depends on those events existing rather than on the application being polished. The crew mobile application can follow in phase two.
Why is high availability such a large share of the cost?
Because it buys no visible feature. In a worked example, redundancy, tested failover, a degraded local mode and reconciliation on recovery accounted for $38,000 of a $170,000 first phase and produced nothing a specialist can point at on a screen.
It is also the line a generalist developer omits, which is why their quote looks cheaper. Ask any prospective firm what happens when the network fails at two in the morning. If they do not immediately discuss local state and reconciliation, they are pricing an ordinary business application.
Should the risk assessment move before the accept, and what does that cost?
Yes, and it is the highest value change in the whole build. Completed during preflight it documents a decision already made. Scored during the accept conversation, with the system populating time of day, remaining duty, aircraft and landing zone history, a threshold breach triggers the approval your operations specification requires while the decision is still open.
It sat at about $44,000 in a worked example and belongs in phase two, because it depends on the duty and aircraft data phase one establishes.
Does a hospital owned programme change the answer?
Usually yes, and towards buying. If your parent organisation mandates a platform, a parallel build it will not fund or support is a weaker position than an imperfect mandated system used properly.
What is still worth doing is the process work: structured turndown logging, event based duty capture and written base minimums. Those cost little, they improve safety governance immediately, and they are the same artefacts any future build would need if the mandate ever changes.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
What tech stack should a custom field service platform be built on?
The dependable 2026 stack is React Native or Flutter for the technician app, React for the dispatch console, Node.js or Python on the backend, and PostgreSQL with an offline sync layer on the device. Boring, widely used technology wins here because any competent team can maintain it five years from now. Be wary of an agency proposing a stack only they can staff; that is a lock-in strategy, not an engineering decision.
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.
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.
We're outgrowing Jobber. Should we move up to ServiceTitan or build our own?
Move to ServiceTitan if the problem is missing features on a standard residential trades workflow, because migrating between products is far cheaper than building. Build custom when the problem is fit: multi-day commercial jobs, subcontractor crews, or pricing rules that neither Jobber's Grow plan (about $199 per month billed annually, up to 15 users) nor ServiceTitan models cleanly. In Digital Heroes scoping calls, about half the teams asking this question turn out to need an integration or add-on rather than a new platform, so name the exact workflow gap before committing either way.
Will custom field service software scale if we grow from 10 technicians to 100?
Yes, when it is architected for growth from day one, and scale is where custom wins because cost per technician falls as you add crews instead of rising with every seat license. The real scaling work is operational: multi-branch dispatch, role permissions, and roll-up reporting, which usually arrives as a phase two costing 30 to 50 percent of the original build. State your three-year headcount plan in the first scoping call so the data model supports branch two before branch two exists.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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 Ben.
Senior SEO Strategist · New-york · 5 posts on the site
Published · Last updated .
