Workflow software that turns commercial RF detections into case-ready emitter alerts for allied maritime surveillance programs.

1. Public investors just validated commercial RF SIGINT as a durable category, making it easier for defense buyers to standardize workflows on top of it instead of treating it as an experiment.
2. Near-profitability signals the underlying data providers can be long-lived vendors, which lowers platform risk for a startup building mission workflows above them.
3. Constellation expansion will increase coverage and detection volume, so customers need automation to turn more RF events into prioritized casework rather than more analyst toil.
4. A broader defense-tech listing wave suggests capital markets now believe government-facing space products can produce large outcomes, which improves the financing and exit story for a focused application layer.

Catalyst. HawkEye 360's IPO, first-day share surge, and planned constellation expansion show commercial RF SIGINT has crossed from niche capability into a growing data layer that now needs workflow software on top.

The product sits above commercial RF data providers and gives each program a mission-specific workspace for known emitters, anomalies, and analyst decisions. It automatically groups repeated detections into persistent entities, flags movement or behavior changes that matter to the program, and records why an alert was promoted or dismissed. Analysts can publish case-ready outputs for commanders, primes, or government customers without rebuilding the narrative each time from raw detections. Over time, the system becomes the source of truth for emitter histories, decision logic, and measurable program outcomes tied to commercial SIGINT.

What's different. HawkEye and peers own collection infrastructure; generic intel tools own broad dashboards. This company would own the mission-specific interpretation layer between them: persistent emitter libraries, analyst decision history, and case-ready outputs tuned to one surveillance program's thresholds and reporting chain. That workflow data compounds into defensibility because every confirmed emitter, dismissed alert, and published case improves the customer's operating model and is hard to recreate inside a spreadsheet stack.

Jobs to be done

flowchart LR
  Buyer[Maritime ISR program manager] --> Pain[Raw RF detections and manual emitter triage]
  Pain --> Product[Commercial SIGINT casework OS]
  Product --> Outcome[Faster validated coastal alerts]

Executive takeaways

• Commercial RF SIGINT demand is now visibly budgeted: HawkEye 360 reached the public markets with roughly $416M in proceeds, $117.6M of 2025 revenue, $302.6M of backlog, and a 61% U.S. government revenue mix, while also holding a renewed $98.8M Navy IPMDA contract [1][2].
• The product gap is no longer basic vessel visualization; it is turning RF, AIS, SAR and registry clues into analyst-trusted case files, decision logs and evidence packs that survive coalition and interagency handoffs [10][12][15][16].
• Competition is real but layered: upstream RF providers sell detections, broad mission platforms sell configurable operating environments, and adjacent SAR/AIS vendors sell more sensor inputs; none is purpose-built for emitter-casework workflow by default [3][5][6][8][9][26][27].
• Beachhead economics look plausible as an attach sale rather than a standalone platform rip-and-replace: six allied programs at about $700k ACV yields a year-3 SOM near $4.2M, with upside coming from expansion into border, sanctions, and EW workflows [2][14][25].

Market definition

The relevant market is mission software that operationalizes commercial RF and adjacent maritime surveillance feeds—RF geolocation, AIS, SAR, registry data and analyst rules—into auditable casework for coast guards, navies and ISR integrators, rather than selling raw detections or generic dashboards alone [3][10][13][14].

Customer and buyer

The day-to-day user is a lead analyst, mission-product manager or mission systems engineer inside an integrator, fusion centre or maritime security program that already consumes multiple data feeds. The economic buyer is the program manager or VP-level ISR owner who must prove faster detection-to-action cycles and coordinate evidence across agencies or partners [10][12][14][15].

Buying triggers

• A new or renewed coastal-surveillance program adds commercial RF data and suddenly exposes the manual work of adjudicating detections into a shared operating picture. [2][14]
• A spike in shadow-fleet, sanctions-evasion or IUU-fishing scrutiny raises the number of dark-vessel investigations and pushes programs to preserve stronger evidentiary chains. [22][23][24]
• Interagency or allied reporting obligations create pressure for measurable workflow outputs instead of ad hoc analyst notes and opaque scripts. [12][13][15]

Willingness to pay

Budgets already exist upstream: the Navy renewed a $98.8M IPMDA contract for RF data and analytics, NGA added a $2.5M analytics task order, and SeaVision shows agencies already pay for maritime-awareness tooling plus commercial data layers. The startup can therefore sell as a workflow attach against existing program spend, not as a brand-new budget category. [2][10][25]

Category dynamics

Growth signal 10.2%-13.6% CAGR in adjacent geospatial analytics markets

Validation signals

• HawkEye 360 reported 2025 revenue of $117.6M, backlog of $302.6M and completed a $416M IPO, showing real commercial and government demand for the underlying RF layer.
• The Navy renewed HawkEye 360 for a fourth IPMDA year under a $98.8M IDIQ, demonstrating sustained allied maritime RF budget lines.
• NGA extended HawkEye 360 and added a $2.5M analytics task order, suggesting buyers want more than raw detections.
• Quad regional pilots are already delivering commercial RF data to maritime agencies across Southeast Asia, the Indian Ocean and the Pacific.

Regulatory & technical constraints

• Products must fit national or allied maritime information-sharing-centre models and withstand scrutiny on data provenance and operational handoffs.
• Dark-vessel cases frequently involve AIS shutdowns, GNSS manipulation, flag hopping and identity obfuscation, so software must preserve evidentiary trails rather than rely on a single sensor.
• Operational usefulness depends on correlating RF with AIS, SAR, registry and rules-based analytics, increasing integration burden versus a single-feed product.

Upstream RF vendors such as HawkEye 360, Unseenlabs and Kleos monetize collection plus analytics; Palantir-class platforms monetize broad defense data operating environments; Spire and SAR vendors such as ICEYE monetize adjacent data layers. The defensible gap is a narrow workflow system for persistent emitter libraries, human adjudication, and case-ready evidence packs tuned to one maritime program’s thresholds and reporting chain [3][5][6][7][8][9][26][27].

Why incumbents do not win by default

• RF data vendors. They monetize collection, geolocation and some analytics, but customer pain persists when analysts still need to turn detections into reusable cases and audit-ready outputs.
• Mission platforms. Palantir-class platforms are powerful but broad; they do not come with maritime emitter taxonomies, adjudication flows or evidence-pack templates out of the box.
• Government visualization stacks. SeaVision proves agencies want fused AIS, SAR and RF with rules-based alerts, but it is still a situational-awareness layer rather than a program-specific case-management product.
• In-house integrator workflows. Regional MDA programs still rely heavily on training, trust and local fusion-centre capacity, which suggests a large amount of brittle analyst-driven workflow remains outside packaged software.

HawkEye 360's IPO, $117.6M of 2025 revenue, $302.6M backlog, 61% U.S. government revenue mix, and renewed $98.8M Navy IPMDA contract show that commercial RF SIGINT is now a real procurement layer rather than an experiment. The gap is downstream: allied maritime programs still turn RF, AIS, SAR, and registry clues into actionable cases through provider portals, spreadsheets, and analyst scripts that do not preserve a trusted evidentiary chain. The proposed company sells a buyer-side casework layer for maritime ISR integrators that already license RF detections and need persistent emitter libraries, human-reviewed anomaly workflows, and audit-ready evidence packs. The first customer is a 200-800 person integrator supporting one Indo-Pacific or European coastal-surveillance program, because that buyer already has the budget line, the program trigger, and the delivery burden when commercial RF feeds are added or renewed. The company should enter as an attach sale inside an existing contract vehicle, not as a rip-and-replace mission platform. Research supports a narrow but credible beachhead with an estimated $38.5M SAM and a year-3 SOM of about $4.2M if the company reaches six production programs at roughly $700k ACV. The deliberate sequencing is to prove a 30-50% reduction in analyst time-to-case for one reporting workflow, then expand into cross-program templates and adjacent sanctions, border, or EW investigations that reuse the same case-management core. The main unresolved gaps are downstream data-rights terms, how often buyers will approve persistent adjudication history in third-party software, and whether enclave deployment can stay standardized enough to preserve software margins.

Problem

• Maritime surveillance programs that already buy commercial RF detections still spend scarce analyst time turning raw events into trusted emitter cases, prioritized alerts, and customer-ready outputs.
• Existing provider portals, common operating pictures, and in-house scripts do not preserve program-specific adjudication history or auditable evidence chains across coalition and interagency handoffs.

Solution

• Deliver an enclave-ready casework workspace that ingests RF plus AIS context, groups detections into persistent emitter records, routes anomalies for human review, and records why each alert was promoted or dismissed.
• Export evidence packs that combine RF, AIS, SAR, registry context, and analyst decisions for commanders, primes, and government customers without rebuilding the narrative from scratch each reporting cycle.

Why we win

• The company sits in the unowned layer between RF data vendors and broad mission platforms, so it can attach to existing programs without asking the buyer to replace upstream collection or the current common operating picture.
• Program-specific emitter libraries, false-positive outcomes, and audit logs compound into sticky buyer-owned workflow data that is hard for spreadsheets, services teams, or vendor portals to recreate.

Milestones

flowchart LR
  Wedge[Integrator-led maritime casework wedge] --> MVP[Emitter library and evidence-pack MVP]
  MVP --> Proof[Faster analyst-approved cases and reused reports]
  Proof --> Expansion[Multi-program workflow system of record]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 5 of the first 10 target integrators confirm that RF-to-case workflow pain is current, budgeted, and not solved by existing portals or scripts.
• At least 2 design partners approve persistent storage of analyst labels, adjudication history, and derived emitter records in an approved environment.
• At least 50% of paid pilots convert to production because customers reuse prior cases and evidence packs in live reporting.
• Two connector and deployment patterns cover more than 60% of qualified first-year opportunities without bespoke re-architecture.
• At least 2 production customers request one adjacent investigation workflow before first renewal.

Open diligence questions

• Which output gets paid for today: faster alert triage, reusable emitter library, audit trail, or customer-ready evidence pack?
• How often can an integrator buy this product inside an existing contract vehicle without waiting for a new ministry procurement line?
• What data-rights terms govern storage of detections, analyst labels, and derived histories in a third-party workflow layer?
• Can the product remain an overlay, or will buyers eventually require native workflow inside SeaVision-, Palantir-, or prime-owned environments?
• What minimum security posture is required to move from pilot to production across allied programs?

Model sanity

• Revenue engine. Base-case revenue comes from two Y1 pilots compounding into five active programs by Q4Y2 and six by Q2Y3 at roughly $60K of monthly revenue per active program.
• Must go right. The company has to standardize enclave deployment fast enough that pilot-to-production conversion stays at or above the BP's 50%+ target without turning the product into custom services.
• Model breaks if. If security review and procurement push the sales cycle toward eight months, the downside case sends cash below zero before the Y2 milestone is fully proved.
• Next-round proof. The next financing is justified once the company shows 4-5 production programs, two repeatable deployment patterns, and a credible path to six live programs without a large sales-team step-up.

Scenarios

Sensitivity

flowchart LR
  TargetAccounts --> PaidPilots
  PaidPilots --> ActivePrograms
  ActivePrograms --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: Base case still depends on only six total programs, so one slipped conversion or non-renewal removes roughly $720K of annual revenue. · Gross margin does not reach the 72% target until Y3 because enclave deployment and evidence-pack setup remain delivery-heavy through Y2. · Cash is modeled from EBITDA and does not include working-capital swings or unusual security-accreditation capex, so real runway could be somewhat shorter.

• Provider dependency. If one or two RF vendors control too much of the data supply, they could squeeze downstream workflow startups or launch similar tooling. Mitigation: Build multi-provider connectors early, own the analyst workflow and audit layer, and make customer value portable across data sources.
• Government adoption drag. Direct ministry sales can be slow, which can stall revenue even if users like the product. Mitigation: Start through integrators and primes that already hold program contracts and can buy workflow software against existing budgets.
• Analyst trust gap. RF analysts may reject automated grouping or alert scoring if the system feels like a black box. Mitigation: Ship human-in-the-loop review, transparent confidence explanations, and narrow initial deployments around one emitter class or coastline.