Europe’s space financing market is producing companies that look less like conventional software startups and more like infrastructure operators. Two recent transactions make that distinction useful: ICEYE announced a €1 billion Series F, while Portugal’s Neuraspace secured €15.6 million through strategic private investment and public funding.

The amounts are radically different, but the operating question is the same: how does a capital-intensive supplier survive long procurement cycles while proving that its technology deserves a place inside mission-critical systems?

The disclosed facts provide only part of the answer. ICEYE’s financing demonstrates access to capital at exceptional scale; Neuraspace’s package combines strategic investment with support linked to Portugal’s Recovery and Resilience Plan. Neither funding total proves profitability, durable product-market fit or procurement success. What the transactions do reveal is how European dual-use suppliers can assemble capital, services and risk-management capabilities into a credible commercial model.

Capital must follow the customer’s operational timeline

Critical-infrastructure companies face a timing mismatch. They must finance hardware, technical talent, certifications and operational capacity before a government or regulated enterprise completes evaluation and procurement. Customers may also require demonstrations, integration work and evidence of reliability before committing to a larger programme.

ICEYE’s reported €1 billion Series F represents financing at a scale capable of supporting a broad operational footprint. Neuraspace’s €15.6 million financing uses a different architecture: strategic private backing alongside funding under Portugal’s Recovery and Resilience Plan. That blend is particularly relevant to earlier-stage infrastructure suppliers because different capital sources can serve different jobs.

Private equity can finance commercial expansion, recruitment and product development. Public programmes can support capabilities aligned with national or European priorities, provided expenditure and milestones satisfy programme rules. Strategic investors may contribute market access, technical context or credibility with prospective customers.

The operator’s lesson is not simply to collect as many funding sources as possible. It is to match each source to a defined workstream. Founders should document which capital funds reusable product capabilities, which supports programme-specific delivery and which provides the runway needed to endure procurement. Otherwise, restricted funding can be mistaken for flexible cash and one-off projects can obscure the economics of the core business.

Sell an operational outcome, not an impressive asset

Satellite infrastructure and space-domain awareness are technically sophisticated, but buyers do not purchase sophistication for its own sake. They purchase faster decisions, better visibility and lower operational risk.

ICEYE’s model is associated with synthetic-aperture radar satellite capabilities and the delivery of Earth-observation information. Neuraspace focuses on protecting satellites and strengthening space-domain awareness. In each case, commercial value depends on converting infrastructure and analysis into outcomes that customers can use repeatedly.

That changes the sales language. A supplier should move from describing sensors, models or orbital assets to specifying a decision workflow: what condition is detected, who receives the information, how quickly it arrives and what action becomes possible. For a regulated enterprise, the outcome might be continuity of service or a defensible risk decision. For a public customer, it might be situational awareness, sovereign capability or improved response coordination.

Operational resilience becomes measurable when it is expressed through service levels. Useful measures may include data availability, alert latency, coverage, false-alarm handling, recovery time and the percentage of relevant events delivered within an agreed window. The correct measures depend on the contract; they should not be asserted without evidence. The principle is to make resilience auditable rather than rhetorical.

What most people miss

The buyer is not only evaluating whether the technology works. It is evaluating whether the supplier will still operate during a crisis, whether data can be trusted, whether dependencies are controlled and whether the service can be integrated into existing command or compliance processes.

That means product design, financing and procurement readiness are connected. A company with excellent technology but insufficient runway creates continuity risk. A well-funded company without clear governance, service levels or escalation procedures also creates risk. In critical infrastructure, the company itself becomes part of the product.

Build recurring revenue around continued readiness

Capital-intensive companies need more than large project wins. Hardware sales and bespoke deployments can create revenue spikes, but they also create exposure to irregular budgets and delayed awards. A recurring service layer can make the business more resilient while aligning payment with ongoing customer value.

Potential structures include subscriptions for data access, monitoring contracts, capacity reservations, managed analytics and multiyear service agreements. A hybrid contract can combine implementation fees with recurring access and defined usage or response levels. The objective is not to force a software pricing model onto physical infrastructure. It is to identify which element of readiness must be maintained continuously and price that element accordingly.

Founders should separate recurring service revenue from integration, hardware and research income in internal reporting. They should also calculate the direct cost of fulfilling each service commitment. Revenue is not attractive merely because it repeats; it must cover infrastructure usage, data processing, customer support, compliance and operational redundancy.

Design the company for long procurement cycles

Government and regulated-enterprise sales rarely move in a straight line. Budget approval, security review, technical evaluation and contracting may involve different stakeholders. A supplier therefore needs stage-based evidence rather than a single persuasive pitch.

An effective sequence begins with a narrowly defined operational problem. A paid pilot should test an explicit decision or workflow, not serve as an indefinite demonstration. Its success criteria should be agreed before delivery, including the evidence required for a production contract. The supplier should also identify the budget owner, operational user, security authority and procurement route early.

Financing plans should assume delays. Management can model base, delayed and severe-delay scenarios for major awards, then define spending gates for hiring and infrastructure. Public grants and strategic capital can reduce pressure, but founders must avoid building permanent costs around temporary programme income.

ICEYE’s scale and Neuraspace’s blended financing illustrate different positions on this path, not a universal progression. Public support can validate strategic relevance, and a large private round can signal investor conviction. Neither replaces evidence that customers renew, expand usage or embed the service in operational processes.

Practical checklist for critical-infrastructure founders

• Map every capital source to a specific workstream, restriction and delivery milestone.
• Maintain procurement-delay scenarios and preserve runway beyond the optimistic contract date.
• Define the customer outcome in operational terms before presenting technical capabilities.
• Turn resilience into contractible measures such as availability, latency, coverage or recovery time.
• Identify the user, budget owner, security reviewer and procurement authority for each opportunity.
• Use paid pilots with predetermined success criteria and a documented route to production.
• Separate recurring services, implementation work, hardware and programme funding in management accounts.
• Calculate the full cost of meeting service levels, including redundancy, compliance and support.
• Build contingency plans for supplier failure, data interruption and surge demand.
• Treat financing as evidence of capacity to execute—not as proof of profitability or product-market fit.