Aircraft Lease Management Software: Build or Buy at Your Clause Variation
Count your structurally distinct lease types before you count your tails.
On this page
Count your structurally distinct lease types before you count your tails. Under roughly ten aircraft whose leases came from one or two programmes and share a clause structure, with simple monthly reserves and no component level claims, buy AerData LEASE and put the money into technical records. Above about 25 aircraft on separately negotiated leases with different reserve bases, escalation clauses and claim caps, the reserve calculation has become contract logic and a spreadsheet is carrying it. A first release runs $100,000 to $200,000 over 14 to 20 weeks.
When is off the shelf genuinely the right call here?
Buy, and here is which one. If your fleet is under roughly ten aircraft, the leases came from one or two sale and leaseback programmes and share their clause structure, and reserves are simple monthly amounts without component level claims, AerData LEASE is the answer. It is purpose built for this industry and understands reserves, utilisation and technical asset structure in a way no general leasing tool does. It will hold that portfolio, and rebuilding it would be a poor use of capital.
Odessa is the right call when your business is primarily trading aircraft rather than managing them through a full lease term. It is a strong equipment leasing platform with real depth on contract accounting and portfolio administration, and for a trader the asset, the appraisal and the transaction matter more than the accrual engine. Buying adequate lease administration and spending your attention on the deal is the correct trade.
There is a third buy case that has nothing to do with fleet size. If you are growing and you expect your paper to standardise rather than diverge, buy now and revisit later. Plenty of lessors move from bespoke negotiation toward template structures as they scale, and building a per contract engine for clauses you are about to retire is money spent on your own past. There is no prize for building early.
The fourth is a documentation test. If nobody in your business can state, from memory, how many genuinely different reserve structures you administer, you are not ready to price a build. Someone senior has to read the actual documents first, and that exercise frequently ends with a lessor discovering they have three patterns rather than the nine they assumed.
When does a custom build actually pay off?
Build when clause variation is your commercial strategy. Lessors accumulate unusual clauses because that is what wins deals, and every packaged product models reserves through a configuration surface. Your unusual clause either fits that surface or it gets handled outside it. Over time the result is a licensed system holding the tidy leases and a set of spreadsheets holding the interesting ones.
That last pattern is the clearest signal in the category, and it is the one lessors notice last. Ask where the accrual for your most heavily negotiated lease is actually computed. If the answer is a workbook, the licensed system is no longer administering your portfolio, it is administering the easy part of it.
The second trigger is component granularity. A lease that lets a lessee claim against the reserve accrued for a specific engine serial rather than for the aircraft requires reserves held at serial level, with performance restoration and life limited parts separated, landing gear by position and the auxiliary power unit standalone. Aggregate balances at aircraft level are the most common modelling shortcut and the one that fails at claim time, because an engine swap means the hours accrued against the wrong asset.
The third is an event you have already had. A claim you could not evaluate against the clause without reading the lease from scratch. A true up negotiated rather than calculated because accruals were estimated during a reporting gap. A redelivery that cost money nobody forecast. Each of those, in this market, is usually larger than several years of any licence.
The fourth is concentration. If one person understands the workbook that calculates supplemental rent across a portfolio worth hundreds of millions, that is a board level exposure with a software fix, and it does not depend on fleet size at all.
How do they compare on the things that matter in this industry?
The reserve engine. Packaged products express reserves through a rate table. A lease defines an accrual basis, a rate, an escalation formula against a published index with a stated lag and base date, caps, floors and claim eligibility, and every one of those was negotiated. A per contract engine treats the lease as configuration expressed in code you control. That distinction is the whole product, and everything else is a view onto it.
Amendments. Rates change, leases get extended, clauses get renegotiated, and last year's accruals must remain reproducible exactly as computed. Effective dated contract terms with recalculation on demand is the right model. Editing a rate field in place is not, and it is what most spreadsheets and some configurations do.
Utilisation. Every route needs hours and cycles by aircraft and by component serial. The difference is what happens when the report arrives as a scanned page with the columns in a new order, which it will. Assume manual formats permanently, build ingestion that absorbs spreadsheets and documents, and raise an exception for a human. Getting fifty operators onto your template is a wish rather than a plan.
Return conditions. Both routes compute a redelivery position. Only a continuously computed one is commercially useful, because a monthly view of remaining green time, check status and records completeness gives you time to plan a shop visit or price an extension. Computed at redelivery, the same calculation only tells you what you owe.
What does total cost of ownership look like at your scale?
Put both sides on one page for three years.
On the buy side, take your platform licence and add the configuration and professional services you pay each time a new lease structure has to be accommodated. Then add the cost of what sits beside the platform, because in most lessors the interesting leases have migrated into spreadsheets and somebody maintains them. If both of those lines are growing every year, that is the signal rather than the licence itself.
Then price the failures. One true up dispute settled by negotiation rather than calculation. One redelivery where the return condition cost was not forecast. Put those against the build rather than against the renewal, because that is what a build is actually competing with.
On the build side, a first release runs $100,000 to $200,000 over 14 to 20 weeks in Digital Heroes delivery experience, covering the lease model with effective dated terms, the per contract reserve accrual engine at component serial level, escalation against published indices, utilisation ingestion with an exception queue, and rent and supplemental rent invoicing. A full platform adding claims with evidence and approval recorded against the governing clause, continuous return condition monitoring, security deposits and letters of credit with expiry alerts, accounting integration, technical records linkage and lender reporting runs $280,000 to $650,000 across 8 to 14 months.
Fleet size is a weak predictor here. Two lessors with the same number of aircraft can differ by a factor of two purely because one trades on standard paper and one negotiates every deal. What drives the number is distinct structures, component granularity, portfolio transfers and novations that must preserve accrual history, and multi entity structures with special purpose vehicles and multiple currencies.
Afterwards, budget 15 to 20 percent of build cost annually for an actively trading portfolio and less for one in run off. The two recurring lines are the utilisation exception queue, which is a role rather than an incident, and new lease modelling for the structurally new deals you sign each year.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. For most lessors sitting between the two bands, this is the right answer.
The clearest version is the utilisation ingestion layer on its own, at roughly $20,000 to $35,000. It sits beside AerData LEASE or Odessa, takes operator reports as documents and spreadsheets, matches them to aircraft and component serials, runs plausibility checks against the previous report and fleet averages, and pushes clean figures into whatever you already run. It changes nothing about your administration and it removes the reporting gaps that turn into estimated accruals, which is where true up disputes begin.
The second is the return condition monitor. Keep the incumbent for rent and reserves, and build a component that computes the redelivery position monthly against the actual lease conditions. It typically sits inside a $60,000 to $140,000 phase alongside security instruments, and it has the clearest commercial return in the category because it converts a cheque into a negotiation.
The third is narrower again. If the only thing living in a spreadsheet is the accrual for your handful of unusual leases, build a per contract engine for those alone and leave the tidy portfolio where it is. That is a smaller project than it sounds and it removes the concentration risk directly.
Leave technical records for a later phase in every case. It is a substantial project with its own budget, and folding it into a first release is the most reliable way to slip the schedule. A useful first release works from the utilisation report and the claim documentation alone.
Which should you choose, by operator size and stage?
Under ten aircraft on shared programme paper. Buy AerData LEASE. Simple monthly reserves and no component level claims is exactly what it handles, and your records are the better place for the money.
A trading business rather than a managing one. Buy Odessa or a comparable equipment leasing platform. The accrual engine is not where your margin comes from.
Ten to twenty five aircraft on two or three template structures. Stay bought and build one thing. Utilisation ingestion is almost always the right one, because reporting gaps are where estimated accruals and later disputes originate, and it is the cheapest component in the category.
Twelve aircraft on twelve negotiated leases. Build. Clause variation rather than fleet size is what makes this defensible, and component level claims with different escalation bases will not survive a configuration surface.
Above roughly 25 aircraft with six or more distinct structures. Build the platform and phase it. Accrual accuracy first, then claims, then return conditions and security instruments, then accounting and lender reporting on your covenant calendar rather than your delivery preference.
Whatever you choose, insist on a parallel run of about three months where both the system and the existing workbook produce accruals and every variance is explained. It is the line lessors most want to cut and the one we insist on, because the value of the system is that its balance is defensible against the lease, and the only way to show that is to account for each difference against the thing it replaces.
If you would rather someone argued with your brief than agreed with it, 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. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- 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) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
Frequently asked questions
What does it cost to switch off AerData LEASE?
The licence is the smallest part. The real cost is the parallel run: about three months where both the new engine and the incumbent produce accruals and every variance is explained, which sat at roughly $11,000 in a 34 aircraft worked example.
Historic accrual balances also have to come across and reconcile exactly, because your lenders have security over assets whose reserve history is the record. Budget that as reconciliation with a named owner on your side rather than as a data load.
What happens if our lease platform changes its pricing?
For most lessors the licence line is not where the money goes. It goes on the professional services charged each time a newly negotiated structure has to be accommodated inside the vendor rule surface, and those charges are usually booked as project spend rather than reaching the renewal discussion.
Pull two years of those invoices before comparing anything. If they are growing while your paper diverges, the exposure is structural rather than a pricing announcement away.
How long does an aircraft lease management build take?
Fourteen to twenty weeks to a first release covering the lease model, per contract accruals, utilisation ingestion and invoicing, then 8 to 14 months for the full platform. Add three months of parallel running before you retire the workbook.
The main schedule risk is lease discovery. Someone senior has to read the actual documents and turn negotiated clauses into a formal model, so pair a developer with your contracts manager for two weeks up front rather than discovering a misread clause after three months of accruals.
Is Odessa enough for a lessor with 20 aircraft?
It depends on what you do with them. Odessa has real depth on contract accounting and portfolio administration, and if you are primarily trading rather than managing through full lease terms it will carry the administration adequately.
Where it strains is the same place every packaged product does in a negotiated contract market. Reserves are expressed through a configuration surface, so a clause capping an engine claim at the balance accrued for that specific serial either fits or moves to a spreadsheet beside the system.
Can we build only the utilisation ingestion and keep everything else?
Yes, and it is the clearest single return in this category at roughly $20,000 to $35,000. It sits beside your existing platform, absorbs operator reports as documents and spreadsheets, matches them to aircraft and component serials, and runs plausibility checks before anything posts.
What it removes is the reporting gap. An operator under commercial stress stops reporting, accruals get estimated, and six months later the true up is a negotiation instead of a calculation. That sequence is what the exception queue exists to interrupt.
Why does tracking reserves per engine serial cost more?
Because it multiplies the objects that must accrue and reconcile. Airframe by check interval, each engine by serial with performance restoration and life limited parts separated, landing gear by position and the auxiliary power unit standalone is more modelling than a single aircraft balance.
It is also the only version that survives an engine swap. When a lease engine goes on wing, aircraft level reserves accrue against the wrong asset and the claim reconciliation later has to be rebuilt by hand from technical records.
Should technical records integration be in the first release?
No. Treat it as its own phase with its own budget after claims and return conditions are live. It is a substantial project rather than a line item, and folding it into a first release is the most reliable way to slip a schedule.
A useful first release works from the utilisation report and the claim documentation alone, which is how most lessors get accrual accuracy before taking on the records programme.
How do we tell a software problem from a paper problem?
Ask where your most heavily negotiated lease is actually accrued. If it is in a workbook beside the licensed system, that is structural and no configuration project will fix it, because the next deal will bring another clause the surface cannot hold.
If instead nobody can say how many distinct structures you administer, the problem is that the documents have not been read. Do that first. Lessors regularly find three patterns where they assumed nine, and the build they were about to fund gets smaller.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
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.
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.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
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.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
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.
How many developers does it take to build an ERP?
A typical Digital Heroes ERP pod is five to seven people: two or three backend engineers, one frontend engineer, a QA engineer, a project manager, and a part-time architect and designer. Bigger teams rarely go faster on ERP because the bottleneck is decisions about your business rules, not typing speed. What you need on your side is one empowered internal owner who can answer process questions within a day.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
What does it cost to maintain a custom ERP each year?
Budget 15 to 20 percent of the original build cost per year, so a $150,000 ERP needs roughly $22,000 to $30,000 annually for hosting, security patches, integration upkeep, and small improvements. Across Digital Heroes maintenance contracts, third-party APIs changing is the biggest recurring work item. That total still usually sits well under the license bill for a comparable NetSuite or Dynamics seat count.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 Theo.
UX Researcher · UK · London · 2 posts on the site
Published · Last updated .
