Aircraft Load Control and Weight and Balance Software: Build or Buy at Your Carrier Mix
The threshold is carriers and departure control systems, not departures. One carrier on one departure control system means buy, and that covers almost every airline.
On this page
The threshold is carriers and departure control systems, not departures. One carrier on one departure control system means buy, and that covers almost every airline. The build case belongs to ground handlers running centralised load control across several carriers and several departure control systems, where the multi tenant shape is the business itself. A first release runs $120,000 to $250,000 over 16 to 24 weeks with verification consuming a large share of it. This is the one aviation category where we routinely advise against building.
When is off the shelf genuinely the right call here?
Buy, and here is which one. If you are an airline operating one or two aircraft types under a single departure control system, Lufthansa Systems NetLine/Load, Smart4Aviation Smart LOAD or the load control within Amadeus Altea Departure Control will do this more reliably and far more cheaply than anything you commission. They are mature, they are used daily by carriers that depend on them, and they are correct on the arithmetic. The balance calculation is not where an airline differentiates.
The comparison is short and it usually ends the conversation. Take your annual licence and support figure, divide by your annual departures, and set it against a $250,000 first release plus 18 to 25 percent a year. Unless your departure count is very small or your licence is unusually large, the product wins by a margin no feature preference should override. We say this knowing it costs us the work, because putting a bespoke safety critical calculation into an operation that does not need one is a bad trade for the operator.
Buy as well if your pain is process rather than product. Controllers making errors under time pressure need better procedures, better staffing at peaks and a better structured handover from the gate, and none of those three is software. If your amendment tolerances and recomputation triggers are not written down clearly anywhere, that is the work, and it costs a fraction of a build. The same applies to dangerous goods acceptance, which is a separate discipline in cargo and already well covered.
When does a custom build actually pay off?
Build when your operation is multi tenant by nature. A handler providing centralised load control serves several airlines from one room. Each carrier brings its own departure control system, its own aircraft configurations, its own approved procedures, its own standard mass values, its own loadsheet format and its own message addressing. A controller may switch between three carriers in an hour, and each switch is a context change with different rules and, in most operations, a different terminal on the desk.
That desk arrangement is the risk. Several systems open at once is exactly the setup that produces a loadsheet issued against the wrong carrier's procedures, and no amount of individual product quality fixes it, because each product was built around a single airline's operation. Treating carrier as a first class dimension in one interface is a structural fix, and no vendor is going to build a problem of that shape for one customer.
The second trigger is coverage. If your carrier mix spans departure control systems that no single product consumes, you are not choosing between vendors, you are choosing between a build and a room that grows linearly with contracts. Handlers who have declined or lost business because onboarding a carrier on a fourth system was not viable already know the number.
The third is the record of a change. Last minute changes usually arrive by voice from a gate agent or a ramp lead, and the controller enters what they heard. The record afterwards is the entry rather than the original event. Capturing the change structurally at its source, with the index effect and the tolerance check computed automatically, leaves the decision human and takes the arithmetic out of the six minutes before the doors close.
The fourth is qualification evidence. If anyone with an account can produce a sheet for any type, and currency lives in a spreadsheet beside the system, an audit is a week of preparation rather than a query.
How do they compare on the things that matter in this industry?
The calculation. Both routes get it right, and any developer who treats that as the hard part has misread the category. The arithmetic is not difficult. What is difficult is that the output is a document the flight crew set the aircraft trim from, so nothing ships on the strength of unit tests and every component carries a verification burden that would be optional anywhere else.
The verification approach is the real comparison. A product arrives verified for its own model. A build has to recompute thousands of historical flights against the existing system and reconcile every difference, with sign off from your own specialists before a live sheet is issued. That is a named workstream at 12 to 20 percent of build cost, recurring on every change to a calculation path.
Carrier profiles. Configurations, standard mass values, amendment tolerances, loadsheet layout and message addressing belong to the carrier rather than to the system. Products model one carrier's world well. A handler needs all of them addressable from one interface, which is a data model decision rather than a configuration screen.
The ramp. Printed loading instructions with a signed copy returned is how much of the industry works, and it functions. What a device layer changes is timing: a container in the wrong position is known while the aircraft is still on stand rather than appearing on a sheet after departure. Gloves, sunlight, rain and a connection that drops behind an aircraft mean offline capability with reconciliation is mandatory, not an enhancement.
What does total cost of ownership look like at your scale?
If you are an airline, put your licence and support figure against a $120,000 to $250,000 first release plus 18 to 25 percent annually and stop there. That is the entire analysis.
If you are a handler, the alternative is not one licence. It is several, one per carrier's chosen system, plus the desks and the controllers you employ purely because a single person cannot safely serve three systems in one shift. Count those controllers, then count the contracts you have declined or lost because a fourth system was not viable.
On the build side, a first release covering the balance calculation for one aircraft type family under your approved procedures, loadsheet and loading instruction production, and structured last minute change handling runs $120,000 to $250,000 over 16 to 24 weeks. A full multi carrier platform adding several departure control integrations, dangerous goods segregation validation at load planning, ramp devices with offline confirmation, qualification enforcement and a complete audit trail runs $350,000 to $800,000 across 9 to 18 months.
The drivers are countable and they are all multiplicative rather than additive. Each departure control system is $30,000 to $55,000 and is the dominant factor for a handler. Each aircraft type family beyond the first is $25,000 to $60,000, since balance data, hold structure and index limits are type specific. Each carrier profile is $20,000 to $45,000. Message production and addressing is $25,000 to $50,000, because loadsheet transmission follows established industry formats that receiving partners test before they accept. Ramp hardware and offline behaviour is $40,000 to $70,000.
Afterwards, budget 18 to 25 percent of build for support, and note that support here is a round the clock obligation rather than office hours. Add $20,000 to $45,000 a year for regression verification, $15,000 to $35,000 a year for departure control version changes, and $40,000 to $90,000 for every new carrier you onboard. Price that onboarding into your handling contracts explicitly, because a low margin contract is worse than no contract once the engineering is counted.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In load control this is the honest answer far more often than a full build, and it is what we recommend to most handlers before they commission anything.
The clearest version is structured last minute change capture sitting in front of whichever product you already run. A gate agent's device reports the three passengers who did not board. The ramp reports the late bag with its hold position. The controller receives a structured change with its source and timestamp instead of a voice call, and enters it into the existing system with the tolerance question already answered. That addresses the highest risk moment in the process without touching the certified calculation at all.
The second is the qualification and audit layer. Bind type qualification and currency to the action rather than reporting on it monthly, and hold the evidence trail beside the product. For a handler this turns a carrier's annual contract review into a demonstration rather than a defence, and it needs no integration into the balance engine.
The third is the loading instruction device layer. Content stays with the incumbent, confirmation per position moves to a device, and deviations report back while the aircraft is on stand. Add it once the instruction content is settled.
What we would not do as a hybrid is split the balance calculation across two systems. One engine computes the sheet, and it is either the product or yours.
Which should you choose, by operator size and stage?
An airline on one or two types under one departure control system. Buy. NetLine/Load, Smart LOAD or the load control within Altea, and spend the difference on tooling, training and controller headcount.
An airline whose controllers make errors under pressure. Still buy, and fix the process. Write down the amendment tolerances, staff the peaks properly and structure the gate handover. Software will not repair an undocumented procedure.
A handler serving two carriers on one shared departure control system. Stay bought and build one thing. Structured last minute change capture is almost always the right one, because it addresses the highest risk moment without touching the calculation.
A handler serving several carriers across two or three departure control systems. This is the genuine build case. Model carrier as a first class dimension, integrate each departure control system once, and prove one carrier, one type family and one station completely before adding the second of anything.
A handler with a growing carrier mix and no viable single product. Build the platform and phase it, verification running alongside every component rather than at the end. Make the business case a capacity and risk argument rather than a licence saving, because a licence saving argument will not survive scrutiny.
The failure mode here is symmetrical and more serious than elsewhere. Building when you did not need to puts a bespoke safety critical calculation into an operation that had a good one. Staying bought when your controllers are switching between three terminals in a shift leaves the risk exactly where it is, and that risk is a sheet issued against the wrong carrier's rules.
If you would rather scope this before committing budget, 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.
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- Gallup reports global employee engagement fell to 20% in 2025 (its lowest since 2020, down from a 2022-2023 peak of 23%), and estimates low engagement costs the world economy an estimated $10 trillion in lost productivity, or 9% of global GDP. (Note: this figure appears in Gallup's evergreen State of the Global Workplace page, currently reflecting the 2026 edition reporting on 2025 data.). Source: Gallup (2025) →
Frequently asked questions
What does it cost to switch off NetLine/Load or Smart LOAD?
The licence is the smallest line. The real cost is the verification programme: recomputing a large historical sample of real flights against the existing system and reconciling every difference, with formal sign off from your own specialists. That is 12 to 20 percent of build cost and it cannot be compressed.
Nothing goes live on the strength of unit tests here, so plan live parallel running per carrier and per type family rather than a cutover date.
What happens if our load control vendor changes its pricing?
For an airline it changes very little, because the product still wins the comparison by a wide margin. Divide your revised licence and support figure by annual departures and set it against a $250,000 first release plus 18 to 25 percent a year before reacting.
For a handler the exposure is different. You are exposed to several vendors at once, one per carrier's chosen system, and a change at any of them lands on a contract you have already priced. That is an argument for owning the layer, not for reacting to one renewal.
How long does a load control build take?
Sixteen to twenty four weeks for a first release on one type family, and 9 to 18 months for a multi carrier platform. Verification runs alongside every component rather than at the end, which lengthens the calendar and is not negotiable.
The largest schedule risk is procedure capture. If your amendment tolerances and recomputation triggers are not written down clearly, that ambiguity becomes a design argument that consumes weeks at your expense.
Is Amadeus Altea enough if we already run it for departure control?
For an airline, generally yes. The load control within Altea is a serious product and if your departure control system is already Altea, using its load control removes an integration and a vendor relationship rather than adding one.
The limit is the same as every product in this category and it is structural rather than a feature gap. It is built around one airline's operation, so a handler serving several carriers across several departure control systems is asking it to be neutral about arrangements it was not designed for.
Can we build only the last minute change capture?
Yes, and for most handlers it is the right first move. A gate device reports the passengers who did not board and the ramp reports the late bag with its hold position, so the controller receives a structured change with source and timestamp rather than a voice call.
It sits in front of whatever product you run and does not touch the certified calculation. That matters, because the change decision stays human while the arithmetic and the tolerance check stop being human, which is the correct division of labour in a safety critical loop.
What does adding a second departure control system cost?
Between $30,000 and $55,000 for the integration itself, plus $15,000 to $35,000 a year across the estate for version changes, because those systems upgrade on their own schedule and you follow.
Add the carrier profile at $20,000 to $45,000 and any new aircraft type family at $25,000 to $60,000, each with its own verification pass. Onboarding a new carrier after go live typically lands at $40,000 to $90,000 in total, which belongs in your handling contract rather than in your overhead.
Should ramp devices be in the first release?
Not usually. Printed loading instructions with a signed copy returned is how much of the industry works, and the device layer at $40,000 to $70,000 is a genuine improvement rather than a safety prerequisite.
What devices change is timing. A container in the wrong position is known while the aircraft is still on stand rather than appearing on a sheet after departure. Add them once the instruction content is settled, and design for gloves, sunlight, rain and a connection that drops behind an aircraft.
How do we tell a software problem from a process problem?
Ask three controllers what triggers a recomputation rather than an amendment. If you get three answers, the constraint is your written procedure, and a build will encode the disagreement into something harder to change.
The signals that are genuinely structural look different: controllers switching between several terminals in one shift, a carrier you could not onboard because of a fourth departure control system, changes arriving by voice with no record of the original event, and currency evidence living in a spreadsheet beside a system that lets anyone issue a sheet.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
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.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
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 software system?
Digital Heroes builds custom 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 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 Eleanor.
VP Client Services · UK & EU · London · 1 post on the site
Published · Last updated .
