Market Size & Where EFB Demand Is Coming From

The global commercial electronic flight bag market is valued at approximately $3.75 billion in 2025 and is projected to reach $9.60 billion by 2035, a compound annual growth rate of 9.9%, according to MarketsAndMarkets, Commercial Electronic Flight Bag Market. A separate estimate from SNS Insider (2025) puts the wider EFB market at $6.01 billion by 2032, growing at 7.2% a year - the range reflects different scoping of hardware versus software versus data-services revenue, but every major forecaster agrees demand is accelerating, not plateauing.

That same SNS Insider analysis found the portable segment (Class 1 and Class 2) held 73% of 2023 revenue, and North America held the largest regional share at 37%. That split matters for a business plan: it tells you where the addressable market actually sits today. A new entrant chasing Class 3 installed systems is competing for the smaller, slower-moving 27% of the market that requires an STC and years of certification runway. A new entrant building a Class 1/2 portable app or a document-management layer on top of existing hardware is chasing the 73% of the market that can go from pilot demo to signed contract in a single sales cycle.

Three forces are driving the growth curve. First, fleet operators are under real cost pressure to eliminate paper - a Boeing-cited estimate widely used across the industry puts the fuel and printing saving from removing a 35-pound paper flight bag at several thousand dollars per aircraft per year, which is the number most sales decks in this space open with. Second, regulators have converged on a workable approval framework (see the licensing section below), which has removed the "will this even be legal" objection that slowed adoption a decade ago. Third, the software layer has shifted from single-purpose chart viewers to integrated platforms - flight planning, weight and balance, document management, and journey logging in one app - which raises the average contract value per tail and creates switching costs once an operator is trained on a platform.

For a UK-based founder, the relevant comparison is that the UK Civil Aviation Authority processes EFB approvals against the same underlying ICAO-aligned framework as EASA, so a product built for UK CAT operators is largely portable into the wider European market once the CAA submission is complete. That's a materially different go-to-market story than most physical-product business plans, where UK and EU market entry require separate certification tracks.

Where the growth is actually concentrated

Aggregate market-size figures hide a more useful pattern for a business plan: growth is not evenly spread across the operator base. Regional and charter operators with 10-60 tails are the fastest-moving buying segment, because they carry the highest per-tail administrative burden relative to their size - a large airline already has an in-house avionics and compliance team, while a 20-tail charter operator is often running paper manuals held together by a single ops manager. That's the segment most new EFB entrants should build their first 12-18 months of go-to-market around, rather than chasing a flagship carrier logo on day one. Business aviation (private jet operators and fractional ownership programmes) is the second fastest-moving segment, driven less by cost pressure and more by the expectation that a modern private operator simply doesn't hand a client paper charts anymore.

Geographically, North America's 37% share reflects both an earlier regulatory framework (the FAA's AC 120-76 series dates back to 2003, giving US operators the longest runway to adopt) and a denser population of regional and charter operators than any other single market. Europe is the fastest-growing region on a percentage basis as EASA's Part-SPA framework matures and post-Brexit UK CAA rules stay closely aligned with it, while Asia-Pacific carriers are adopting EFBs later but at higher average fleet sizes per deal, which changes the sales-cycle economics for a vendor targeting that region.

Questions Founders Ask Before They Start

Before writing a full plan, most first-time EFB founders are trying to answer five questions. Getting these right upfront saves months of rework once you're in front of an operator or an investor.

What actually counts as a "commercial" EFB, versus a general-aviation app?

The distinction isn't the software - it's the operator. A commercial EFB is one deployed under Part 121, Part 135, or the EASA/UK equivalent (CAT - Commercial Air Transport) operating rules, which trigger a formal approval process (OpSpec A061, Part-SPA Subpart M, or SRG1849). The same tablet running the same app under Part 91 general aviation rules faces a much lighter compliance bar. Your business plan needs to state clearly which operator category you're targeting first, because it determines your certification cost and your sales cycle length.

Do I need to build hardware, or can I sell software on existing tablets?

Most successful new entrants in the last five years have built software on commercial off-the-shelf hardware (iPad, Getac, Panasonic Toughbook) rather than developing proprietary Class 3 installed hardware. It is dramatically cheaper to reach revenue, and it matches where 73% of the market's spend already sits.

How long before I can sign a paying commercial operator?

If you're building a Class 1/2 portable app, expect 9-15 months from first line of code to a signed pilot contract, including the operator's own approval paperwork. If you're pursuing a Class 3 installed system, add 12-24 months for STC work before you can bill a single tail.

What's the single biggest thing investors want to see?

A named pilot operator (even a letter of intent) and a clear regulatory approval roadmap. EFB investors have seen enough decks with an impressive TAM slide and no operator relationship to be skeptical of market-size claims alone.

Should I target airlines, charter operators, or business aviation first?

Most successful new entrants start with regional charter or business-aviation operators rather than flagship airlines. A 15-60 tail charter operator can make a purchasing decision in weeks, has a single decision-maker (often the accountable manager or chief pilot), and feels the administrative pain of paper manuals more acutely relative to its size than a major carrier with an established in-house avionics team. Airline procurement cycles, by contrast, commonly run 12-24 months and involve fleet-wide IT security review, which is the wrong first customer for a pre-revenue business.

How defensible is an EFB software business against the big incumbents?

ForeFlight, Jeppesen and Honeywell have scale, brand recognition and existing airline relationships, but they are also generalist platforms optimised for their largest accounts. New entrants typically win by going narrower and deeper - building for a specific operator type (charter, cargo, helicopter EMS) with workflows the generalist platforms treat as an afterthought, and by pricing and onboarding in a way that doesn't require a six-figure enterprise contract to get started.

What It Actually Costs to Build an EFB Business

Building a commercial electronic flight bag software or integration business typically requires $180,000 to $950,000 in the US, or £140,000 to £750,000 in the UK, to reach a signed pilot operator and a first renewal. The wide range reflects the difference between a lean Class 1/2 software MVP aimed at a single charter operator, and a fuller platform build aimed at Part 121 airline contracts with document management, dispatch integration, and multi-region data licensing from day one.

Cost Breakdown

• Core software development (flight planning, charts, weight & balance, app shell): $60,000–$320,000 (£47,000–£250,000)
• Aviation domain & certification consulting (AC 120-76E / AMC 20-25A compliance guidance): $25,000–$140,000 (£20,000–£110,000)
• Hardware for pilot trials (demo tablets, mounts, ruggedised units): $8,000–$45,000 (£6,000–£35,000)
• Data licensing (charts, NOTAMs, weather, terrain databases): $15,000–$120,000/yr (£12,000–£95,000/yr)
• Cloud infrastructure & data-isolation architecture: $10,000–$60,000 (£8,000–£47,000)
• Regulatory approval support (OpSpec A061 filing, CAA SRG1849, EASA Part-SPA submission): $12,000–$70,000 (£9,000–£55,000)
• Sales, pilot outreach & working capital (6-12 months): $50,000–$195,000 (£38,000–£158,000)

Two line items surprise most first-time founders. The first is data licensing - chart, NOTAM, and terrain data isn't optional, it's a recurring cost that scales with tail count from the day you sign your first customer, and it needs to be modelled as a cost of goods sold line, not a one-off setup fee. The second is regulatory approval support: even though the operator formally holds the approval (not the software vendor), operators expect their EFB vendor to walk them through the OpSpec/SRG1849 paperwork, and building that capability in-house or on retainer with an aviation compliance consultant is a real cost most software business plans omit entirely.

Class 1/2 portable versus Class 3 installed: a different cost profile entirely

The figures above assume a Class 1/2 portable software build, which is the route most first-time EFB founders should take. A Class 3 installed system is a fundamentally different, and far larger, undertaking: because the device becomes certified aircraft equipment, you're budgeting for an STC or design approval process that commonly runs $500,000-$2,000,000+ and 12-24 months before a single unit generates revenue, plus ongoing DO-178C software-assurance costs for every subsequent release. Unless you already have a Class 3 hardware background and a design organisation approval in place, most business plans should explicitly scope Class 3 as a Phase 2 expansion funded by Class 1/2 revenue, not a day-one build.

A useful rule of thumb for the plan's use-of-funds section: allocate roughly 45-55% of initial capital to software development and certification support, 15-20% to data licensing and infrastructure, and the remainder to sales, pilot operator relationship management, and a working-capital buffer of at least six months. Investors and lenders reviewing an EFB plan will look specifically at whether the working-capital buffer covers the gap between signing a pilot operator and that operator completing its own regulatory approval - a gap you don't control directly but must fund through.

Hardware & Data Suppliers You'll Need

Even a software-first EFB business depends on a small set of hardware and data suppliers to get from demo to deployed fleet. Naming these in your business plan - rather than writing "we will source appropriate hardware" - is what separates a plan an operator or investor trusts from one they skim past.

• Tablet hardware: Apple iPad Pro (most common Class 1/2 host), Getac and Panasonic Toughbook ruggedised tablets for harsher operating environments
• Mounting hardware: certified yoke and side-panel mounts from suppliers such as RAM Mounts and AmSafe Bridport for Class 2 installations
• Chart & navigation data: Jeppesen data services or Garmin's aviation database subscriptions, typically licensed as a per-tail annual fee
• Weather & NOTAM feeds: commercial aviation weather API providers integrated via standard ARINC 633/828 data formats
• Cloud infrastructure: AWS or Azure with aviation-grade data isolation architecture to meet operator IT security reviews
• Certification/compliance consulting: independent DER (Designated Engineering Representative) or aviation compliance consultants for AC 120-76E and Part-SPA submissions

Your plan should specify unit costs per tail for the recurring items (data licensing, cloud hosting) since these directly determine your gross margin - they aren't sunk startup costs, they're cost of goods sold that scales with every new operator you sign.

Two supplier decisions carry outsized weight in an operator's due diligence. First, your chart and NOTAM data provider needs global or regional coverage matching your target operator's route network - a domestic UK charter operator has very different data-coverage needs from a cargo operator flying transatlantic routes, and naming the wrong provider in your plan signals you haven't scoped the product against a real customer. Second, your cloud infrastructure decision needs to address how flight data is isolated from any connection to certified aircraft systems, since this is one of the first questions an operator's IT and safety teams will ask during a pilot evaluation - vague answers here routinely stall deals that were otherwise ready to close.

Pricing, Margins & Unit Economics

EFB pricing splits cleanly into two tiers. At the consumer and general-aviation end, subscriptions run roughly $200 to $3,000 per year - for example, ForeFlight's Pro Plus tier lists around $200/year, with its Business tier scaling from $3,000 up to $15,000+/year for enterprise dispatch and performance features. Commercial fleet contracts, the segment this business plan template targets, are priced differently: $40 to $150 per tail per month, plus a one-off integration and training fee per aircraft type.

A worked example makes the unit economics concrete. A 45-tail regional charter contract at $85/tail/month generates $45,900 in annual recurring subscription revenue from that single operator. Landing 12 similarly sized operators over three years builds toward roughly $550,000 in annual recurring revenue - before data-licensing pass-through costs, which typically run 12-20% of gross subscription revenue and should be modelled as a direct cost rather than absorbed into gross margin assumptions.

Gross margin on the software layer itself typically reaches 55-72% once a company clears roughly 40 tails under contract - below that threshold, fixed data-licensing minimums and cloud costs eat disproportionately into margin. Net margin in years 1-3 usually sits at 8-18%, after certification support costs, sales and pilot-relationship-management overhead, and ongoing compliance work. This is a slower ramp than a typical B2B SaaS business, and your financial model should say so explicitly rather than defaulting to generic 80% SaaS gross margin assumptions that won't survive investor diligence.

Beyond the core subscription, most EFB vendors add a second revenue line from integration and onboarding fees per aircraft type (typically $2,000-$8,000 per tail type, one-off), and a third from premium modules - dispatch integration, electronic journey logging, and document management add-ons that can lift average contract value by 20-40% once an operator is past the initial adoption phase.

Churn is the metric that matters most for a credible EFB financial model, and it behaves differently from typical B2B SaaS. Once an operator's pilots are trained on a platform and its manuals live inside your document-management module, switching costs are high - annual churn for an established EFB vendor with a properly onboarded fleet typically runs under 8%, well below the 15-20% common in generalist SaaS. The trade-off is a much longer and more expensive path to that first signed tail, so your financial model should show a realistic 9-15 month sales cycle for the first few contracts, compressing as case studies and referrals accumulate.

A simple three-year build-up for the plan's revenue table: Year 1, one anchor operator at 15-20 tails generating roughly $15,000-$20,000 in annual recurring revenue while certification support and product development dominate spending; Year 2, three to five operators and 60-100 tails, crossing into positive gross margin territory; Year 3, eight to twelve operators and 200+ tails, where the business reaches the roughly 40-tail threshold needed for healthy unit economics several times over and net margin moves into the 8-18% range referenced above.

Funding Routes for an Aviation Software Startup

Funding an EFB business is a hybrid problem: it has the capital-intensity of an aviation business and the growth profile of a software company, and most lenders and investors are only comfortable with one half of that story.

In the US, SBA-backed lending is a realistic route for the hardware, working-capital, and certification-support portions of your build - SBA loans typically require 10-20% down, a materially lower bar than conventional aviation equipment financing, though lenders will still weight the strength of your business plan, your team's aviation domain experience, and your personal financial position heavily for a pre-revenue applicant. SBA loans are not designed to fund pure software development risk, which is why most EFB founders pair a smaller SBA or bank facility for equipment and working capital with equity or angel capital for the software build itself.

In the UK, the Start Up Loans scheme offers up to £25,000 per founder (up to £100,000 for a team of four) at 6% fixed interest with free mentoring, which is a useful bridge for the founder-capital portion of the build alongside private angel or seed investment. Because EFB sits at the intersection of aviation and SaaS, angel investors with aviation operating experience - ex-airline dispatchers, former avionics engineers, charter operators - are typically a faster and more informed source of early capital than generalist SaaS investors, who often lack the context to evaluate your certification roadmap.

Whichever funding route you pursue, lenders and investors evaluating an EFB business will expect to see the certification pathway costed and timed alongside the financial model - not as a footnote, but as a dependency that gates your first revenue milestone. Our bespoke business plan service builds both in the same document.

Grant and R&D-tax-credit routes are worth scoping alongside equity and debt. In the UK, the software development and data-integration work behind an EFB platform frequently qualifies for HMRC's R&D tax relief scheme, which can return 10-27% of qualifying development spend as cash or a reduction in corporation tax - a meaningful offset against the $60,000-$320,000 core development budget referenced earlier. In the US, aviation-adjacent technology ventures should check eligibility for SBIR/STTR grants where the product has a genuine safety or efficiency angle, though EFB software applications tend to qualify less often than hardware or sensor-based aviation technology.

Whichever mix of funding you use, avoid the common structuring mistake of raising a single tranche sized to "get to profitability." Because your first few contracts are gated by an operator's own regulatory approval timeline - a variable you influence but don't control - most successful EFB raises are staged: an initial round to fund product build and the first pilot operator's approval process, followed by a second round once that first operator is live and paying, priced off a proven (not projected) churn and expansion rate.

FAA, EASA, CAA & Transport Canada Approval

Unlike most business-plan template categories on this site, the regulatory section for an EFB business isn't a checklist you complete once - it's an ongoing dependency your sales cycle runs through, because your customer (the airline or charter operator) is the one who must hold the approval, not you. Your plan should demonstrate you understand that distinction and can support the operator through it.

United States

• Commercial (Part 121/135) operators need OpSpec/MSpec/LOA A061 under FAA Advisory Circular AC 120-76E before operational EFB use
• Physical EFBs are classified Class 1 (portable, no aircraft connection), Class 2 (portable, mounted, can connect to aircraft power/data), or Class 3 (installed equipment, requires STC/design approval)
• Class 2/3 mounting and electrical installation falls under 14 CFR Part 43 maintenance rules
• General aviation (Part 91) operators have a lighter path historically referenced under AC 91-78
• OpSpec A061 issuance typically takes 8-16 weeks once documentation is complete; a Class 3 STC can take 12-24 months

United Kingdom

• CAT operators need approval under CAT.GEN.MPA.141, administered by the UK Civil Aviation Authority
• Operators complete the EFB compliance checklist (SRG1849) plus an EFB Policy and Procedures Manual and a risk assessment
• NCC operators don't need formal CAA approval but must comply with NCC.GEN.131; NCO operators comply with NCO.GEN.125
• Approval plus the Operational Evaluation Test typically takes 3-6 months

European Union & Canada

• EASA: Part-SPA Subpart M and AMC 20-25A govern portable versus installed EFB hosts across EU operators; Type B software applications require operator approval before deployment
• Canada: Transport Canada Advisory Circular AC 700-020 governs certification, airworthiness and operational approval of portable and installed EFBs, with EFB data connections requiring TCCA Aircraft Certification approval for isolation from aircraft systems

Because EASA's Part-SPA framework and the UK CAA's post-Brexit rules remain closely aligned, a product built to satisfy a CAA SRG1849 submission carries most of the documentation needed for a subsequent EASA Part-SPA filing - a genuine advantage for a UK-based founder planning to expand into continental European operators in year two or three.

Insurance and liability

Regulatory approval is necessary but not sufficient - most commercial operators will also require their EFB vendor to carry technology errors-and-omissions (E&O) and professional indemnity cover before signing a contract, given that flight planning and weight-and-balance calculations feed directly into flight-safety decisions. Typical cover levels requested by regional operators run $1-5 million, rising toward $10 million+ for larger fleet or airline contracts. Your business plan's risk section should name a target insurance level and an estimated annual premium (commonly $8,000-$35,000 depending on cover level and claims history) rather than leaving this as an unstated assumption.

Data protection is the second compliance layer that sits alongside aviation approval. An EFB platform processes operational data, crew personal data, and in some configurations passenger manifests, which brings UK GDPR and EU GDPR obligations into scope for any UK or European operator contract, and equivalent state or federal privacy rules for US operators depending on the data handled. Building a data-processing agreement template and a clear data-residency answer before your first sales conversation avoids a compliance objection derailing a deal late in the sales cycle.

EFB Terms Every Business Plan Should Use Correctly

Investors and operators will notice quickly if these terms are used loosely. Get them right in your plan.

• EFB (Electronic Flight Bag): an electronic device or system that replaces paper charts, manuals, and performance calculations traditionally carried in a pilot's flight bag
• Class 1/2/3: the FAA's hardware classification - Class 1 is fully portable with no aircraft connection, Class 2 is portable but mounted with a data/power connection, Class 3 is installed certified equipment
• Type A/B/C software application: EASA's functional classification of EFB software by risk - Type A is low-risk (e.g. checklists), Type B affects situational awareness and needs operator approval, Type C requires full airworthiness certification
• OpSpec/MSpec/LOA A061: the specific FAA operations specification paragraph that authorises a commercial operator to use an EFB
• STC (Supplemental Type Certificate): the FAA/EASA approval required to install a Class 3 EFB as certified aircraft equipment
• SRG1849: the UK CAA's EFB compliance self-assessment checklist that CAT, NCC and NCO operators complete as part of approval
• Journey log / electronic technical log: the digital record-keeping module many EFB platforms bundle alongside charts and performance tools
• ARINC 633/828: industry data-format standards commonly referenced for how EFB software exchanges weather, NOTAM and performance data
• DO-178C: the software-assurance standard applied to safety-critical avionics software; Class 3 installed EFB applications are typically assessed against it, while Class 1/2 portable apps usually are not, which is one reason portable products reach market faster
• Weight and balance calculation: a core EFB function that determines an aircraft's centre of gravity and confirms it's within safe operating limits before dispatch - one of the first modules operators evaluate in a pilot trial

Getting this vocabulary right matters beyond investor credibility - it's also what an operator's chief pilot or head of flight operations will use to test whether you understand their world in the first five minutes of a sales call.

Sample Business Plan Preview

Here's an extract from the kind of commercial electronic flight bag business plan our team writes - so you can see exactly what you'll get:

What's in the Template

Every Avvale business plan template includes these sections, pre-structured for your industry:

• Executive Summary - Your business at a glance, written to hook investors in 60 seconds
• Company Overview - Legal structure, ownership, location, and founding story
• Industry Analysis - Market size, growth trends, and regulatory landscape
• Customer Analysis - Target operator segments, buying triggers, and decision-maker mapping
• Competitor Analysis - Vendor landscape mapping and your differentiation strategy
• Marketing Plan - Channels, messaging, and operator acquisition strategy
• Operations Plan - Development roadmap, certification milestones, and support structure
• Management Team - Founder bios, advisory board, and key hires planned

The optional Financial Forecast add-on (included in our $300/£250 and $1,000/£800 packages) provides a 5-year Excel model with income statement, cash flow, balance sheet, break-even analysis, and per-tail unit economics built for EFB-style recurring revenue - not a generic SaaS template that ignores data licensing and certification costs.

Frequently Asked Questions