Flycomm

**Product and the concrete problem it solves.** Flycomm addresses a deceptively basic infrastructure problem: organizations often cannot see how wireless networks actually perform where people, vehicles, sensors, and emergency teams use them. Operator coverage maps are predictions, while conventional drive testing is expensive, geographically sparse, and slow to repeat. A municipality may know that an area is nominally covered but not that a basement, road segment, industrial zone, border site, or emergency assembly point loses service under particular conditions. A mobile operator may know its own network but lack a consistent view of competitor performance, indoor behavior, or the practical effect of proposed new sites. Flycomm positions itself as a single environment for measuring, mapping, comparing, planning, and managing wireless connectivity. Its current website describes customers and markets across municipalities, transportation, security and defense, telecom and mobile network operators, tower companies, regulators, and IoT. The Startup Nation Finder profile identifies MuniC as a released product, while the company also presents a wider cloud platform and FlycommC2/SOC, indoor-intelligence, and churn-prevention modules. The problem is strategically important because communication failure is not only a customer-experience issue: it can interrupt emergency response, degrade connected vehicles and industrial sensors, and remove the communications layer on which public-safety and security operations depend.

**Core technology and how it works.** The technical proposition is a data and decision layer rather than a new radio standard. The Israel Innovation Authority describes Flycomm's system as cloud software with supporting hardware, using algorithms for fast, flexible network design and then applying big-data analysis and machine learning. The Israeli government's MWC 2025 company brochure gives a more operational description: Flycomm combines the accuracy of drive tests with simulation planning and the scale of crowdsourced measurements. In practice, the platform can ingest or collect observed signal and quality measurements, associate them with location and network conditions, compare operators or technologies, and turn the resulting geospatial data into coverage maps, infrastructure-gap analysis, planning scenarios, and monitoring views. The current company site says the system can map and verify coverage, compare operator performance, identify gaps in real time, and generate predictions across environments and technologies. The company also markets an Android measurement application in Israel that captures cellular and Wi-Fi signal data, speed, latency, serving and neighboring cells, bands, and operator identifiers; that public app description is consistent with a measurement flywheel, although the completeness, calibration, privacy controls, and representativeness of the resulting dataset require technical diligence. Public material does not disclose proprietary model architectures, training volumes, accuracy benchmarks by environment, or the exact hardware stack, so the defensible claim is an integrated measurement, geospatial-analytics, and planning workflow rather than an independently proven AI breakthrough.

**Market, customers, and go-to-market.** Flycomm has a multi-sided but coherent route to market. Mobile network operators and tower companies can use it for site planning, coverage assurance, network benchmarking, and deployment prioritization. System integrators can use its APIs and dashboards inside larger telecom or smart-city programs. Municipalities and regulators can obtain a more neutral view of operator performance and identify coverage gaps before committing public infrastructure. Public-safety agencies, transportation operators, and critical-infrastructure owners have a different buying motive: they need to know where communications fail, how coverage changes across routes and facilities, and what redundancy or additional infrastructure is needed before an incident. The company's current company page lists Amdocs and NTT DATA as ecosystem partners and Cellcom, m:tel, and IHS among its customer or ecosystem references; these are company-presented references, not independently audited contract disclosures. The official Israeli-language site also names Tel Aviv and Lod municipal technology references and presents MuniC as a city-facing platform, while the export ministry's MWC brochure lists mobile operators, tower companies, system integrators, IoT integrators, public safety, and resellers as target channels. This suggests a land-and-expand motion in which an initial measurement or planning deployment can grow into recurring monitoring, APIs, municipal transparency, emergency preparedness, or infrastructure optimization. The tradeoff is a complicated sales map: telecom procurement, municipal budgets, defense and public-safety buying, and tower-company operations all require different certifications, integrations, and reference cases.

**Traction, funding, and third-party validation.** Flycomm has more evidence of commercialization than a stealth-only startup, but its financial record is unusually incomplete. The Israel Innovation Authority entry for Flycomm Networks Ltd. lists a company registration number, a 2018 establishment date, 20 employees, an initial-revenues stage, and zero additional funding in that program record. Startup Nation Finder instead reports an August 2021 founding, an 11–50 employee range, undisclosed total funding, a pre-funding stage, and the released MuniC product. Flycomm's current company page says it was founded in Jerusalem in 2021 and reports 500% revenue growth over the preceding twelve months as of September 2026; that growth claim is company-reported and not supported by public revenue statements. The export.gov.il MWC 2024 and 2025 brochures provide independent government-channel corroboration that Flycomm was actively seeking investment and presenting a commercial AI/5G/connectivity platform to international telecom and public-safety audiences. The current website's named partner and customer references are useful go-to-market signals, and the Innovation Authority's initial-revenues classification is more substantive than a pure research-stage listing, but there is no public priced financing round, ARR, contract value, retention data, deployment count, or independent customer case study in the sources reviewed. The right diligence interpretation is an operating early-growth company with product and market access, not a venture-backed scale-up whose financing or revenue trajectory is already proven.

**Founders and team background.** Flycomm's current official About page names Moshe Lugasi as co-founder and CEO, Arie Lugasi as co-founder and CTO, and Eliran Oren as co-founder and COO. Moshe is described as a former Israeli Air Force officer and the founder of FlyTech, a drone-technology company that was acquired by ARDM. Arie is described as a telecommunications engineer with more than 35 years of experience at Motorola and Israel Aerospace Industries, with expertise in wireless technologies and RF systems architecture. Eliran is described as a FlyTech co-founder who now leads operations, partnerships, and customer delivery. This is a credible founder-market fit for a company sitting between wireless engineering, operational software, and security use cases: the team combines telecom and RF experience with Israeli aerospace, defense, and drone exposure, plus a prior company-building and acquisition history. There is, however, a material identity discrepancy to resolve. The Startup Nation Finder business profile lists Moshe Lugasi, Joseph Golan, and Arie Lugasi as the August 2021 founding team, while the current company site lists Eliran Oren and not Joseph Golan. That may reflect a founding-stage change, a historical profile error, or a role transition; it should not be silently harmonized. Public sources do not provide a verified engineering headcount breakdown, model-research leadership, security certifications, or program-management depth. Twenty employees is a useful scale signal from the Innovation Authority record, but supporting global telecom, municipal, and defense-adjacent deployments requires more than a strong founding group: diligence should verify RF measurement, data engineering, cloud security, customer success, and field-integration capacity.

**Competitive dynamics.** Flycomm competes across several layers. Rohde & Schwarz, Keysight, and Accuver provide mature drive-test, benchmarking, and radio-measurement tooling with deep operator relationships and extensive instrumentation. Infovista and Ranplan compete in network planning, optimization, and indoor or geospatial modeling. Ookla and CellMapper provide large-scale crowdsourced or consumer-facing network-performance datasets, while Amdocs and other telecom-software incumbents can bundle analytics and planning into broader operator transformation programs. Specialist network-monitoring and geospatial vendors may also compete for municipal and critical-infrastructure budgets. Flycomm's proposed edge is the combination of three capabilities in one workflow: measured drive-test-like evidence, scenario and simulation planning, and crowdsourced scale, exposed through a relatively accessible SaaS and API model. Its Israeli operating base and the team's RF, telecom, defense, and drone background may help it address operational environments that generic telecom analytics vendors do not prioritize. That edge is not yet a durable moat. Data quality, calibration, and customer integrations can be reproduced by well-funded incumbents; large operators may prefer existing suppliers; and crowdsourced data can be biased toward populated or digitally active areas. The decisive questions are whether Flycomm's local data improves decisions enough to overcome incumbent switching costs, whether it can prove accuracy in indoor, vehicle, rural, and emergency conditions, and whether the platform becomes embedded in planning and response workflows rather than remaining a consulting-enabled dashboard.

**Defense, security, and resilience relevance.** Flycomm's dual-use case is credible because the core capability serves both ordinary commercial network operations and communications continuity in public-safety, critical-infrastructure, and defense settings. A reliable map of cellular and wireless performance can support emergency-response planning, identify dead zones along evacuation or logistics routes, guide temporary-cell or private-network placement, and help infrastructure owners prioritize redundancy around hospitals, ports, utilities, transport corridors, and command facilities. Security and defense organizations can use network intelligence to understand coverage and availability across bases, borders, vehicle routes, and urban operating areas, although the public record does not establish a defense contract, military deployment, classified workload, anti-jam capability, or sovereign command-and-control accreditation. This distinction matters: Flycomm is not a tactical radio, SATCOM terminal, electronic-warfare sensor, or resilient mesh network. It helps decision-makers understand and optimize wireless infrastructure; it does not itself make a link survive jamming, denial, cyberattack, power loss, or physical destruction. Its strategic value is therefore enabling and infrastructural. The same platform can improve civilian network economics while supporting preparedness and continuity for allied public-safety and security organizations. Diligence should test data residency, privacy and consent for crowdsourced measurements, tenant isolation, API security, resilience of the cloud service, offline or degraded-mode operation, and whether its analytics can distinguish normal coverage variation from an incident requiring operational action.

**Growth stage, trajectory, and key diligence risks.** Flycomm is best classified as early-stage but commercially active. It has a released municipal product, a cloud platform, public references to telecom and systems-integration relationships, an Innovation Authority record indicating initial revenues, and a current claim of rapid revenue growth. It remains early because funding is undisclosed, public operating metrics are thin, founding-year records conflict, and there is no independently documented scale of deployments or recurring revenue. The upside trajectory is a vertical expansion from coverage planning into a wireless-intelligence system of record: operators could use it for network investment and benchmarking, cities for infrastructure transparency and emergency readiness, and security or defense organizations for mission-area connectivity assessment. The principal risks are (1) evidence risk, because the strongest performance and growth metrics are company-stated; (2) data risk, because measurement coverage, calibration, privacy, and crowdsourcing bias determine analytical value; (3) procurement risk, because telecom, municipal, and government sales cycles are slow and reference-heavy; (4) platform risk, because cloud availability, mapping providers, operator data access, and mobile telemetry permissions may affect service quality; (5) competitive risk from measurement, planning, and telecom-suite incumbents; (6) strategic overreach risk, because public-safety relevance does not equal defense readiness; and (7) team-scale risk, because a 20-person company may struggle to support varied international deployments. The next diligence milestones are audited revenue or retention evidence, named deployment scope, independent accuracy comparisons, a resolved founding-team record, security and privacy certifications, and proof that the platform improves communications continuity during real exercises or incidents.