Affordable cloud OS for small airports replacing spreadsheets with real-time runway, gate, and turnaround management.

1. Blunav's 20-day Chennai pilot produced a government-verified 22% runway efficiency gain and was immediately adopted into daily operations, proving cloud airport OS technology is production-ready today—not a research project.
2. India's UDAN regional connectivity scheme is activating 50+ new airports simultaneously, creating a unique window where new airport directors are selecting their first digital platform with no incumbent vendor already entrenched.
3. A $1M institutional seed round led by Piper Serica signals that specialist capital is ready to back affordable airport-tech for emerging markets, confirming investor conviction in the category.
4. DGCA and equivalent regulators in Southeast Asia and Africa are tightening digital reporting mandates, forcing small airports to find affordable compliance solutions or risk operating certificate suspension.

Catalyst. India's UDAN scheme is activating dozens of previously dormant regional airports simultaneously, creating a cohort of new airport directors with mandated digital compliance requirements and no incumbent software vendor already entrenched.

A cloud-native Airport Operating System delivered as a monthly SaaS subscription that integrates runway scheduling, gate allocation, turnaround management, and DGCA compliance reporting on a single browser-based dashboard. The platform ingests real-time ATC feeds and ground handler inputs to flag runway occupancy overruns and auto-assign next tasks to crews. Airports go live in 2–4 weeks via a self-serve onboarding wizard rather than a 12-month enterprise implementation. Pricing scales by monthly departure volume, making the first deployment accessible to airports handling as few as 30 flights per day. As operational data accumulates, predictive analytics surface recurring delay patterns and recommend schedule adjustments, deepening switching costs organically.

What's different. Unlike SITA or Amadeus, which require $500K+ contracts and 12-month enterprise rollouts, this platform deploys in 2–4 weeks via cloud SaaS and prices per departure, making it the only economically viable option for airports handling 30–300 daily flights. The wedge—runway occupancy optimization—delivers a provable, measurable ROI within the first month, not after a multi-year implementation, reducing the sales cycle dramatically. Domain-expert founders with direct DRDO and airport IT systems credentials provide regulatory credibility that pure-software entrants cannot credibly replicate. Early airports become reference customers locked in by operational data depth and workflow integration rather than contractual penalties.

Jobs to be done

flowchart LR
  AirportDir[Airport Director] --> Pain[Manual Ops and Compliance Gap]
  Pain --> Platform[Cloud Airport OS]
  Platform --> Runway[Runway Occupancy Optimizer]
  Platform --> Gate[Gate and Turnaround Manager]
  Platform --> Compliance[Regulatory Audit Trail]
  Runway --> Efficiency[22% Efficiency Gain]
  Gate --> Efficiency
  Compliance --> Audit[DGCA Audit Pass]
  Efficiency --> Outcome[More Flights Lower Cost Regulatory Safety]
  Audit --> Outcome

Executive takeaways

• Blunav has a credible wedge because a live Chennai International Airport pilot reportedly cut runway occupancy time by 22% across 3,500+ flights and moved into daily operations, which is a stronger proof point than most seed-stage airport software claims.
• The competitive set is real but segmented: SITA and Amadeus are strong at large-hub integrated airport stacks, while AeroCloud and Veovo are closer analogs for cloud-native regional-airport software; none appear to dominate the India small-airport wedge by default.
• The near-term market is strategically interesting but economically narrower than generic multi-billion-dollar airport software reports imply; a bottom-up India wedge based on public airport counts supports low-single-digit millions of ARR before broader module expansion.
• The biggest non-product risk is procurement and data access, not market awareness: government airport buying cycles, AAI/ATC integrations, and compliance workflows will likely govern sales velocity more than product novelty.

Market definition

The relevant market is cloud-native airport operations software for small and mid-sized airports, especially modules covering airside event capture, collaborative turnaround coordination, gate and resource planning, and compliance-grade operational records. This is narrower than broad airport digitization or airport management system market definitions, which bundle major-hub systems, hardware, and passenger-processing products together.

Customer and buyer

The operational user is an airport operations manager or AOCC lead who needs a single live view of aircraft movements, stand and gate assignments, and turnaround milestones. The buyer is more likely the airport director, airport authority IT lead, or public procurement owner who must balance compliance, capex/opex constraints, and implementation risk. For India's smaller public airports, the real alternative is still fragmented manual coordination rather than best-in-class incumbent software.

Buying triggers

• New or newly expanded regional airports under UDAN create first-time software selection events where there is no entrenched incumbent and operational processes are still being formalized. [7][8][10]
• Airports facing delay pressure, tighter resource use, or runway-turnaround bottlenecks have a direct operational reason to trial A-CDM style tooling because public EUROCONTROL evidence links better milestone sharing to lower taxi and delay outcomes. [17][18][25]
• Public-sector audit, manual, and procurement requirements create a forcing function for software that can produce consistent operational records and standard workflows, even when the regulation does not prescribe a specific vendor stack. [13][23][24]

Willingness to pay

Public price lists are rare in this category, which itself suggests enterprise-style selling. Still, AeroCloud's public materials emphasize materially lower upfront IT costs and no user license caps versus on-premise systems, while Blunav's own positioning stresses affordability for airports that still use manual workflows. That points to a willingness-to-pay range anchored more by avoided staffing, delay, and capacity losses than by a classic per-seat SaaS benchmark. [1][2][32][33]

Category dynamics

Growth signal 6.1%-7.6% CAGR across public airport software / airport digitization market definitions

Validation signals

• Chennai pilot evidence gives Blunav a measurable runway-efficiency claim rather than a generic digitization pitch.
• Chennai reportedly integrated Blunav into daily operations after the pilot, improving referenceability.
• AAI reports a large enough regional-airport cohort under UDAN to support focused beachhead selling.
• Cloud-native peers already market airport software on lower-infrastructure and modular deployment economics.

Regulatory & technical constraints

• DGCA documentation and aerodrome manual requirements create a need for defensible procedures and records.
• Public-airport buying requires formal procurement and contracting discipline that can slow software adoption.
• Full A-CDM-style value depends on shared milestone data across airport, airline, handler, and ATC stakeholders.
• Real operational optimization often requires integration with AODB or equivalent live data sources.

SITA and Amadeus represent the legacy enterprise reference set, with deep AODB, CDM, and airline integration capabilities that matter at large airports but can imply heavy implementation and sales motions. AeroCloud and Veovo show that cloud-native airport operations software is viable in the market, including resource management and operational databases for smaller or more agile airports. ADB SAFEGATE is strongest where apron, gate, docking, and operational sensor data are central. The gap Blunav is exploiting is not that airport ops software does not exist; it is that there is still limited evidence of an India-specific, low-friction, small-airport-first offer with a hard runway-efficiency proof point and a public-sector reference.

Why incumbents do not win by default

• Legacy airport suites. Legacy suites do not win by default because their strength is breadth and integration depth, while the small-airport buyer often starts with a narrow operational pain and a low tolerance for long implementation cycles.
• Cloud-native global challengers. Cloud-native vendors prove the demand for lighter-weight airport software, but their public materials are still oriented toward broad airport operating platforms rather than a sharply localized India airside wedge.
• Apron and airside infrastructure vendors. Airside specialists can own data-rich parts of the operation, but their public offer tends to skew toward larger infrastructure or sensor-led deployments that may be too heavy for smaller airports unless paired with a simpler software-first motion.
• In-house dashboards and manual workflows. Internal tools and spreadsheets persist because procurement is slow and buyers can patch together operations manually, but those substitutes usually lack shared milestone logic, scalable auditability, and optimization across stakeholders.

Blunav is building a cloud-native Airport Operating System priced as a monthly SaaS subscription, targeting the 95+ UDAN regional airports in India that operate on radio, paper logs, and spreadsheets because legacy aviation software (SITA, Amadeus) requires $500K+ contracts and 12-month implementations. The company's 20-day government pilot at Chennai International Airport reduced runway occupancy time by 22% — from 59 to 46 seconds per aircraft — and was immediately adopted into daily operations, providing a government reference that de-risks buyer decisions at other public airports. The buying trigger is a DGCA compliance audit or a runway near-miss incident forcing an airport director to demonstrate digital monitoring within 90 days; the initial contract is a paid pilot or MoU rather than a full enterprise deal, bypassing slow public procurement. A $1M seed round led by Piper Serica (May 2026) funds 12–24 months of product expansion and sales into the UDAN cohort. The India beachhead supports a bottom-up SOM of ~$0.6M ARR at 20 airports in year three; the longer path runs through Southeast Asia and Africa as module depth grows. The primary execution risk is public procurement velocity, not product-market fit.

Problem

• Small and mid-sized airports globally operate on radio, Excel, and WhatsApp because enterprise aviation software (SITA, Amadeus, IBS) requires contracts exceeding $500K annually and 12-month implementation cycles — structurally unviable for airports handling 30–300 daily flights.
• India is activating 50+ new UDAN regional airports simultaneously; each new director must choose a first digital platform with no incumbent entrenched, but DGCA compliance mandates are tightening and digital audit trails are expected.
• Runway occupancy at manual airports runs 20–30% above achievable rates; turnaround delays cascade into gate conflicts and missed slot windows, while regulators are increasingly demanding timestamped operational records that paper logs cannot produce.

Solution

• Cloud-native Airport OS delivered as a monthly SaaS subscription: integrates runway scheduling, gate allocation, turnaround management, and DGCA compliance reporting on a single browser-based dashboard with real-time ATC feed ingestion.
• Airports go live in 2–4 weeks via a self-serve onboarding wizard; no on-site implementation team required; pricing scales by monthly departure volume starting at ~$1,500/month for airports with 30 flights/day.
• Predictive analytics surface recurring delay patterns as operational data accumulates, deepening switching costs organically while expanding the value delivered per seat.

Why we win

• Chennai International Airport government pilot is a hard proof point: 22% runway efficiency gain across 3,500+ flights, measured by automated timestamps, now embedded in daily operations — a credential no new entrant can fabricate.
• Per-departure SaaS pricing is structurally impossible for SITA or Amadeus to match given their cost bases; incumbents cannot profitably target airports under 5M annual passengers.
• UDAN activation is creating a cohort of first-time airport directors with no entrenched vendor, open to a 2–4 week deployment that solves an urgent compliance deadline.
• Founding team with DRDO, UN aviation, and airport IT systems backgrounds carries the regulatory credibility required to clear government procurement gatekeepers.
• Operational data accumulation and DGCA audit trail depth create switching costs even before the feature set expands; airports that store 12+ months of timestamped events are unlikely to restart with a new vendor.

Milestones

flowchart LR
  Wedge[Runway efficiency wedge] --> Pilot[30-day paid pilot]
  Pilot --> ROI[Measurable ROI in 30 days]
  ROI --> Production[Production subscription]
  Production --> Data[Airport operational data graph]
  Data --> Stickiness[Switching cost deepens]
  Production --> Reference[Published case study]
  Reference --> NextAirport[Next UDAN airport]
  NextAirport --> Pilot
  Production --> Modules[Module expansion per airport]
  Modules --> ACV[Higher ACV]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 10 UDAN airport directors will convert a warm outreach into a paid pilot conversation within 12 months, validating that DGCA pressure is a real buying trigger and not just an assumed one.
• Pilot-to-production conversion rate reaches 50%+ after 5 completed pilots, confirming that the runway occupancy ROI story survives the transition from trial conditions to ongoing operations.
• Chennai contract renews at or above its original value within 12 months of daily-ops adoption, proving that the efficiency gain is durable and not a pilot-period artifact.
• Self-serve onboarding consistently achieves go-live in under 30 days without on-site engineering support, sustaining the structural cost advantage over enterprise competitors.
• ATC or operational data integrations can be implemented at new airports within 60 days using a semi-automated or observer-mode approach, avoiding single-point dependency on AAI API approvals.

Open diligence questions

• What are the exact commercial terms, annual contract value, and renewal date of the Chennai International Airport deployment today?
• How many UDAN airport directors have been contacted since seed close, and what is the current pipeline of qualified pilots or signed MoUs?
• At which integration depth (manual milestone capture vs. full ATC feed) is the 22% runway efficiency gain reproducible, and how does ROI degrade with less integration?
• Do AAI-operated regional airports procure software as SaaS opex, project capex, or bundled systems-integration contracts, and has any non-Chennai airport issued a formal tender or RFP for airport operations software?
• What is the realistic pilot-to-contract timeline at a typical UDAN airport given government procurement rules, and does the seed runway cover at least three full procurement cycles?
• How has the founding team mapped the DGCA aerodrome manual certification pathway for software that captures and exports compliance records?

Model sanity

• Revenue engine. Base-case revenue is driven mainly by growing from 5 to 20 to 30 paying airports while blended ACV steps up from pilot pricing toward the research-modeled $30K annual level.
• Must go right. The model needs Chennai to keep compressing sales cycles so a two-to-three seller motion can land 20 airports by Month 24 without adding a heavier field team.
• Model breaks if. If procurement stretches toward the downside case and exit ARPU stalls near $2.2K per month, cash goes negative before the company reaches the Month 24 proof point.
• Next-round proof. The next financing is justified when Blunav shows 20 production airports, ~$600K ARR, and evidence that module expansion can lift ACV above the narrow India-only wedge.

Scenarios

Sensitivity

flowchart LR
  Outreach[Reference-led outreach] --> Pilots[30-day paid pilots]
  Pilots --> Conversions[Production airports]
  Conversions --> Revenue[Subscription revenue]
  Revenue --> GrossProfit[72% gross profit]
  GrossProfit --> Opex[Headcount + travel + compliance]
  Opex --> Cash[Ending cash]

Flags: The India-only wedge is economically narrow, so revenue per FTE stays well below normal SaaS efficiency until ACV expands or international markets open. · BP Month 33 calls for average ACV of at least $38K, but Month 36 also calls for 30+ airports and ~$900K ARR; the base case therefore keeps portfolio ACV near $30K and treats upsell ACV lift as partial, not universal. · Seed cash barely lasts through Y3 in the base case, so any delay in AAI integration access or pilot conversion would force an earlier round.

• Government Procurement Delay. Airport authorities are government entities with slow procurement timelines that can stall even technically superior products for 12–24 months. Mitigation: Use the Chennai reference to secure a memorandum of understanding or paid pilot agreement rather than a full contract as the initial commitment, allowing faster deployment while formal procurement proceeds.
• Incumbent Downmarket Expansion. SITA or Amadeus could launch a stripped-down cloud tier targeting small airports, leveraging existing airline relationships and IATA certifications to crowd out newcomers. Mitigation: Lock in the first 20 UDAN airports with multi-year subscriptions and deep operational data integration before incumbents notice the segment; per-departure pricing is structurally impossible for incumbents to match given their cost bases.
• ATC Data Access Dependency. Real-time value depends on integrating ATC feeds controlled by the Airports Authority of India, which may restrict or delay API access to third-party software vendors. Mitigation: Begin with a sensor-plus-observer model using ground-based MLAT and ADS-B receivers that the airport itself owns, reducing dependency on AAI API approval while the formal integration is negotiated in parallel.