Airline Operations Control Software: Build, Buy, or Wrap the Suite You Already Run
The threshold here is vendor spread rather than fleet size. If your crew system and your maintenance system come from the same vendor as your operations system, and controllers trust what the screen tells them, buy the renewal and stop reading.
On this page
The threshold here is vendor spread rather than fleet size. If your crew system and your maintenance system come from the same vendor as your operations system, and controllers trust what the screen tells them, buy the renewal and stop reading. If they come from three vendors, so constraints reach the duty manager by telephone, the arbitration and visualisation layer is yours to build, and a first release runs $130,000 to $275,000 over 16 to 24 weeks. Most carriers between roughly twenty and a hundred and fifty aircraft sit on the second side of that line, which is why the honest answer in this category is usually hybrid rather than either pure option.
When is off the shelf genuinely the right call here?
Start with the case where you should not spend anything. If you run under roughly twenty aircraft point to point with no bank structure at any station, a duty manager, a whiteboard and a telephone genuinely handle your operation. Software will not improve it enough to justify either the money or the distraction, and we would say so before quoting.
Above that, three products own the category. Lufthansa Systems NetLine and Ops, Sabre AirCentre and NAVBLUE N-Ops and Crew are substantial platforms containing real engineering, and their scenario coverage reflects years of work against operations you have not thought of yet. If one of them already owns your schedule, your crew and your operations together, and your controllers trust it, buy the renewal. Building alongside a suite that works creates a second source of truth, and in an operations control centre, abbreviated to OCC from here, a second source of truth is dangerous rather than merely wasteful. A controller acting on the wrong screen during a ground stop is a worse outcome than a controller acting slowly.
There is a third buy case that gets missed. If you are a young carrier still settling your commercial model, your bank structure and your crew agreements, buy now. Building an operations system around arrangements you have not committed to yet produces a model you will pay to change, and the packaged product will carry you through the years when the operation is still moving under you.
When does a custom build actually pay off?
The trigger is vendor spread. A carrier whose crew, maintenance and operations systems come from three different suppliers is already funding integration that never quite closes, and the practical result is that constraints reach the duty manager by telephone from the department that owns them. That is the condition a build addresses.
Two or more of the following usually means the arithmetic has flipped. Your controllers rebuild a disrupted day on paper because no screen shows aircraft rotations, crew legality, maintenance opportunities and slots together. Your recovery decisions cannot be reconstructed afterwards, so post disruption reviews run on memory and turn into arguments. Your delay attribution is filled in later by somebody reading a movement log, and the reactionary bucket is large and unexamined. Or you operate a bank structure at a hub where cascading failure is the dominant cost and nobody can see the cascade forming until it has already formed.
What we would push back on is the assumption that a build means an optimiser. In every OCC project we have delivered, the value was concentrated in the single picture and the decision audit trail. Automated recovery demonstrates well in a sales meeting and gets overridden in a real disruption, because a plan a duty manager cannot defend the next morning to a regulator, a union representative or a chief executive is a plan they will not sign. Build the picture, then the audit trail, then consider the optimiser.
How do they compare on the things that matter in this industry?
Compare on five practitioner grounds rather than on feature lists.
Constraint arbitration across vendors. The suites integrate to crew, maintenance and slot data properly when you buy their own components. When you do not, you fund and maintain that integration yourself. A custom layer treats arbitration as its entire job: maintenance opportunities become blocks on the same timeline, slot and curfew validation runs on every proposed movement, and crew legality is evaluated forward across the whole pairing rather than only the next sector.
Explanation. A recovery proposal expressed as a score gets ignored. One that states which flights are protected, which crews are affected and how, what happens to tomorrow's first wave and an estimated cost gets used. Packaged optimisers differ in how much reasoning they expose, and the ones that expose least are the ones controllers override most.
Audit trail. Recording the committed choice alongside the alternatives that were on the table is what turns a bad day into an improvement rather than a disagreement. It is cheap to build and it is rarely the reason anybody buys a suite.
Delay attribution. Capturing the primary cause at the moment of the decision, when the controller knows exactly why a departure was held, and computing the reactionary chain from the rotation graph, produces analysis that changes buffer and bank structure decisions. Attribution filled in afterwards produces a distribution that is directionally true and specifically useless.
Real time behaviour. A display lagging by two minutes gets abandoned, and a stale display is worse than a blank one because controllers act on it. Whatever you run has to show data age and degrade visibly rather than silently.
What does total cost of ownership look like at your scale?
A first release giving controllers one live timeline with crew legality, maintenance constraints and slot position evaluated in place, plus manual recovery with consequence preview and a decision audit trail, runs $130,000 to $275,000 and ships in 16 to 24 weeks in Digital Heroes delivery experience. A full platform adding ranked recovery proposals, passenger connection impact, network wide curfew and slot validation and post operation delay attribution runs $400,000 to $1,000,000 phased over 12 to 20 months.
The running costs are where operators get caught. Round the clock operational support is the largest line and the one most often omitted, because a system controllers lean on during disruption needs somebody reachable at three in the morning. Infrastructure for movement messaging plus crew and maintenance polling at control centre latency typically settles at $1,500 to $4,000 a month for a sixty aircraft carrier, more with multiple hubs. Support and enhancement runs 12 to 18 percent of build cost annually on top of that. Interface regression testing runs against every upstream vendor release, so with five upstream systems it is a recurring calendar item rather than an exception. And constraint definitions go stale: slot regimes change, curfew conditions change and crew agreements are renegotiated, so if nobody owns keeping them current the system becomes quietly wrong in a way controllers will notice before you do.
Set that against a renewal honestly. If the suite owns everything, the renewal wins. If it does not, you are comparing the build against the integration budget you already spend, not against the licence.
What does the hybrid look like, and when is it the honest answer?
For most carriers in this category the hybrid is the answer, and it is not a compromise. Keep the packaged system as the record for the fields it holds well, and build the arbitration, visualisation and audit layer around it.
The cheapest credible version is a read only integration layer plus the timeline, with no recovery actions at all, at $70,000 to $120,000 over ten to fourteen weeks. It proves two things no proposal document can: that you can obtain crew legality state, maintenance status and movement data at control centre latency, and that controllers will actually look at the screen. Both are the real risks in this category. Carriers who skip that step and discover in month four that their crew vendor will not expose legality state end up rebuilding the plan and paying for it twice.
Two boundaries are worth holding inside the hybrid. Do not reimplement crew flight and duty rules if your crew system already runs an engine you can query, because rewriting them is expensive, slow and a liability, and the vendor who owns those rules is the right place for them to live. And do not build a reaccommodation engine. What changes a cancellation decision is a small set of figures, being passengers at risk, connections lost, how many can be reaccommodated inside a defined window and how many face an overnight. That costs $40,000 to $80,000 including the reservation system integration, against several times more for a full engine your passenger service system already runs.
Which should you choose, by operator size and stage?
Under twenty aircraft, point to point, no bank structure. Buy nothing. Spend the money on a good duty manager and a better standby plan.
Twenty to sixty aircraft on a single vendor suite controllers trust. Renew. Put the budget into configuration and training, and revisit this only when you change crew or maintenance vendors.
Twenty to sixty aircraft with crew or maintenance from a different vendor. Take the read only layer at $70,000 to $120,000 first. It is the right size for the risk, and it either proves the case for a first release or tells you cheaply that your data access will not support one.
Sixty to a hundred and fifty aircraft with a bank structure at a hub. Build the first release at $130,000 to $275,000, sequenced picture first and audit trail second. Scope one hub. The bank logic that works at your largest hub is most of what the second hub needs, and building both at once doubles the discovery without doubling the learning.
Multi hub or multi air operator certificate operations. The full platform at $400,000 to $1,000,000 is defensible and it is still phased. Each hub carries its own bank structure and each certificate its own rules, and the recovery logic is not shared as cleanly as an organisation chart suggests.
Any carrier still settling its commercial model. Buy, and revisit the question once the operation has stopped moving under you.
If you would rather someone argued with your brief than agreed with it, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
Frequently asked questions
Should we replace NetLine or Sabre AirCentre with a custom system?
Almost certainly not. If either suite owns your schedule, crew and operations together and your controllers trust it, replacing it starts you from behind on scenario coverage that took the vendor years to accumulate, and a build alongside it creates a second source of truth that is genuinely dangerous in a control centre.
The case for building appears when the suite does not own everything. If your crew or maintenance system comes from another supplier, the build is an arbitration and visualisation layer over what you already run, and it competes with your integration budget rather than with the licence.
What does it actually cost to switch off our current operations suite?
The licence is the small part. The real switching cost is the interface estate: movement messaging, crew rosters with legality state, maintenance status, slot allocations and reservation data all terminate somewhere, and each connection has to be rebuilt and regression tested against a live operation that never pauses.
Add the controller retraining and a parallel period where both systems run during disruption, which is the only honest way to prove the new one. This is why we recommend wrapping rather than replacing for most carriers: you keep the interface estate you already paid for.
What happens if our vendor changes its pricing at renewal?
Your negotiating position is set by how much of the operation the vendor owns. A carrier whose schedule, crew, maintenance and operations all sit inside one suite has very little room, because the alternative is a multi year migration during which controllers work in two places.
The read only integration layer at $70,000 to $120,000 changes that position materially, because it establishes that you can obtain your own operational data at control centre latency. That is worth having before a renewal conversation rather than after one.
How long before controllers actually use a custom system every day?
Sixteen to 24 weeks to a first release, then a period of parallel use alongside the whiteboard. Treat the whiteboard disappearing as the real acceptance test rather than the go live date.
Adoption depends heavily on whether the developers spent time in the control centre before designing anything, because the details that govern uptake are behavioural: how many screens a controller already has, what gets shouted across the room, which phone rings most. Put a rough timeline in front of controllers by week eight, since the layout they want is never the layout designed first.
Can we build something smaller than a full first release?
Yes, and it is the sensible move whenever data access is uncertain. A read only integration layer plus the live timeline, with no recovery actions at all, runs $70,000 to $120,000 over ten to fourteen weeks.
It answers the two questions that decide the larger commitment: whether the upstream vendors will expose crew legality and maintenance state at usable latency, and whether controllers will work from the screen. Neither is answered by a proposal document, and both are expensive to discover in month four.
Do we need an automated recovery optimiser at all?
Not in the first release, and possibly not at all. Ranked recovery proposals with full explanations typically add $120,000 to $250,000, and they earn that only once controllers already trust the underlying picture.
The requirement that makes an optimiser usable is explanation rather than mathematics: which flights are protected, which crews are affected and how, what happens to tomorrow's first wave, and an estimated cost. A plan a duty manager cannot defend the next morning will be overridden however good the objective function is.
If we stay on the suite, can we still get our operational data out?
Ask now, in writing, and treat the answer as a procurement item rather than a technical one. Data portability in this category is commercial: what matters is whether crew legality state, maintenance opportunities and movement data can be published to a system you control, at what latency, and under what terms.
Carriers who establish that before scoping anything else avoid the most common failure in this category, which is discovering mid project that a closed crew system offers only a nightly file drop and cannot support a live legality view.
We fly twenty aircraft point to point. Is any of this worth it?
No, and we would say so rather than quote. Without a bank structure there is no cascade to see forming, the number of simultaneous decisions during a disruption stays inside what one experienced person can hold, and a whiteboard plus a telephone is proportionate.
The signal to revisit it is structural rather than numerical: you introduce a bank at a hub, you take on a second air operator certificate, or your crew and maintenance systems stop coming from the same vendor as your operations system. Any of those changes the answer.
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.
What should I prepare before contacting an agency about an internal tool?
Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.
What does an internal tool cost for a small business with 20 to 50 employees?
Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
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.
How long does it take to build an internal tool from scratch?
A working first version typically ships in 4 to 8 weeks, and larger multi-module tools run 10 to 16 weeks. Across Digital Heroes internal tool projects the schedule splits into roughly one week of process mapping, 3 to 6 weeks of build, and 1 to 2 weeks of testing with your actual staff. The most common delay is not development but waiting on the client for sample data and workflow decisions, so name one internal owner before kickoff.
How do I vet a development agency for an internal tools project?
Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.
How do we migrate years of spreadsheet or Airtable data into a new internal tool?
Migration is a standard part of the build, not a separate project: the agency writes import scripts that clean, deduplicate, and map your existing rows into the new database. On typical spreadsheet and Airtable histories, Digital Heroes budgets 3 to 10 extra days, most of it spent resolving inconsistencies like the same customer spelled four different ways. The safe sequence is a trial migration first, a review of flagged conflicts with your team, then final cutover over a weekend so nobody loses a working day.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Will a custom internal tool scale as our company grows?
Yes, provided it sits on a standard stack with a real database: PostgreSQL comfortably handles millions of records, and adding users costs hosting pennies rather than per-seat fees. The real scaling risks are organizational, not technical: new departments want features, processes change, and the tool needs a budget line to evolve. Set aside a small quarterly improvement budget instead of treating launch as the finish line, and the tool stays useful for a decade rather than getting rebuilt every two years.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools 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 internal tools 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 Tanvi.
QA Lead · Shopify · Delhi · 1 post on the site
Published · Last updated .
