The War‑Windfall Separation Framework

A governance and capital allocation model for dual‑use technology startups

1. Problem Statement: Dual‑Use Inevitability

Modern infrastructure technologies are intrinsically dual‑use. A satellite imaging system designed to monitor crop health can locate a tank column. An industrial IoT network built for predictive maintenance can relay coordinates for a precision strike. A cloud platform optimised for logistics can serve both a humanitarian convoy and a military resupply operation.

Examples are not hypothetical:

Satellite SAR (Synthetic Aperture Radar) systems, such as ICEYE‑type platforms, provide all‑weather, day‑night ground imaging. Civilian applications include flood mapping and disaster response. Military applications include target detection and damage assessment. The same sensor, the same data stream, the same company.
Telecom and cloud infrastructure underpins civilian communication and military command networks. The distinction is not in the hardware but in the user and the purpose.
Industrial automation and sensing systems designed for factory optimisation can be repurposed for logistics tracking in conflict zones.

The key insight: conflict usage is structurally unavoidable, not exceptional. A startup that builds a generally useful sensing or communication technology cannot guarantee that it will never be used in a war. The only way to avoid dual‑use exposure is to build something with no military relevance – which, for many deep‑tech sectors, is impossible.

2. Ethical Tension

The inevitability of dual‑use technology creates a direct ethical problem: companies may benefit financially from active conflicts.

A civilian SAR satellite operator sees increased demand for high‑resolution imagery when a war breaks out. Governments and defence primes become customers. Revenue rises.
An IoT platform that never intended to support military logistics finds itself contracted to track assets in a conflict zone. Valuation increases.
Even without direct defence contracts, the overall market appetite for sensing, resilience, and communication technology surges during geopolitical crises. Equity valuations rise across the sector.

This is not a question of intent. A company may have designed its systems exclusively for civilian disaster response. But when a war begins, that same capability becomes strategically valuable. The result is a war windfall: incremental profit attributable to active conflict‑driven demand rather than baseline civilian demand.

The ethical tension lies not in the technology itself, but in the capital benefit. Can a startup that wants to do good accept money that flows from destruction? And if it does, what structural rules should govern that acceptance?

3. Proposed Structural Solution

We propose a three‑layer system that separates civil operation from defence exposure, and then separates capital benefit from both.

Layer A — Civil Entity (Entity A)

Operates strictly civilian missions: environmental monitoring, infrastructure inspection, disaster response, agricultural sensing, etc.
No defence contracting. No military customers. No export to sanctioned entities.
Operates under civil regulatory frameworks (e.g. commercial remote sensing licences, data privacy laws, export controls applied only to baseline restrictions).
Entity A may be founder‑owned, venture‑backed, or publicly traded – but its revenue must come exclusively from non‑defence, non‑intelligence sources.

Layer B — Defence/Security Entity (Entity B)

Contains any dual‑use or defence‑adjacent capabilities that cannot be cleanly removed from the technology stack.
Operates under state‑supervised export control regimes, including compliance with arms trafficking regulations, end‑user controls, and sanctions.
May be sold or transferred to approved defence primes (e.g. Airbus, Thales, BAE Systems, Lockheed Martin, or comparable sovereign contractors) under regulatory supervision.
Entity B is structurally separate from Entity A: different legal entity, different cap table, different governance.

Layer C — Exit Mechanisms

If structural separation between civil and defence capabilities is not feasible (e.g., the core IP is inseparable, or the company cannot be cleanly split), then the entire combined company is sold to an approved buyer under regulatory supervision.
The sale proceeds are then redistributed according to the war‑windfall reduction mechanism described below.

4. Financial Firewall Principle

A critical rule must be enforced: defence‑ or security‑derived revenue must not subsidise or accelerate civilian product development.

No cross‑subsidisation between Entity A and Entity B. Civil R&D is funded from civil revenue. Defence R&D is funded from defence revenue (or from the buyer, after divestment).
No shared R&D funding loops. A contract to improve SAR resolution for defence purposes cannot also fund civil algorithm development unless the civil benefit is separately purchased and accounted for at arm’s length.
No retained royalties from defence‑linked assets after divestment. Once Entity B is sold, the original founders and investors of the civil entity have no ongoing financial interest in defence revenues.

The firewall ensures that a startup does not become a backdoor mechanism for channelling war‑zone money into civil innovation. If civil technology is valuable, it should stand on its own commercial merits.

5. War‑Windfall Reduction Mechanism

The core of the framework is the war‑windfall reduction mechanism. It applies when conflict‑driven demand materially increases revenue for either entity.

Definition: War windfall = incremental profit attributable to active conflict‑driven demand rather than baseline civilian demand. Baseline is measured by revenue projections from civilian markets, excluding known military customers or conflict‑zone contracts.

Mechanism:

Identify the war‑windfall portion of revenue. This requires transparent accounting and third‑party audit (or state supervision) during periods of active conflict.
Separate that incremental profit from the company’s retained earnings. It is not distributed as dividends, not reinvested in defence R&D, not used for founder or employee bonuses.
Allocate the war‑windfall amount to approved external recipients, such as:
- Charitable foundations focused on humanitarian aid or post‑conflict reconstruction.
- Humanitarian initiatives (e.g. Red Cross, UNHCR, medical relief).
- Non‑military startup investment (e.g. venture funds that explicitly exclude defence, intelligence, and military‑adjacent sectors).

Explicit exclusion: No war‑windfall funds may be reinvested into defence, intelligence, or military‑adjacent sectors. The money exits the defence economy entirely.

This mechanism does not prevent a company from operating in dual‑use markets. It does not ban defence contracts. It simply ensures that the financial benefit of conflict does not accrue to private or corporate enrichment. The war windfall is structurally neutralised.

6. Exit Philosophy

Sometimes separation is not cleanly achievable. The core IP may be indivisible. The team may be the same. The technology may be so deeply dual‑use that any attempt to split the company creates two non‑viable halves.

In such cases, the fallback rule applies: the entire company is sold under regulated conditions, and the proceeds are redistributed according to the war‑windfall reduction principle.

Clean exit option: Founders and early investors may exit with a fair valuation based on civilian‑only revenue projections, not conflict‑inflated multiples. The war‑windfall portion of the sale price is identified and allocated as above.
Avoidance of permanent dual‑use entanglement: A company that cannot separate its civil and defence activities should not remain under private control. It is transferred to a regulated defence prime, where it belongs. The original team may move on, restart, or build something new – without a perpetual moral liability.

This exit philosophy recognises that some technologies are inherently too entangled for private governance. The state (through approved buyers) takes over, and the private financial gain from that transfer is limited to the civilian‑derived value.

7. Key Conceptual Insight

The framework is not about avoiding dual‑use technology. That is impossible for many deep‑tech startups. The insight is to separate technological participation from conflict‑derived financial enrichment.

Technology use is inevitable and, to a large extent, uncontrollable. Once a system exists, you cannot guarantee who uses it or for what purpose. Attempts to impose use‑based restrictions (e.g. “we will not sell to militaries”) are often unenforceable and, in practice, merely shift the problem to intermediaries.
Capital benefit, however, is controllable. A company can choose how to account for its revenue, how to structure its entities, and where to allocate its profits. The war‑windfall reduction mechanism does not prevent a satellite from imaging a war zone. It prevents the company from pocketing the incremental profit as if it were ordinary civilian revenue.

Thus, the framework accepts dual‑use reality while governing capital flows. It is a structural solution, not a moralistic one.

8. Conclusion

The proposed model for dual‑use technology startups rests on four pillars:

Acceptance of dual‑use technological reality. Conflict usage is structurally unavoidable.
Separation of civil and defence pathways into distinct legal entities, with a financial firewall between them.
Neutralisation of war windfalls through identification, separation, and allocation to humanitarian or non‑military purposes.
Exit mechanisms when separation is not feasible, transferring the entire company to regulated defence primes and redistricting private gain to civilian‑derived value only.

This framework does not moralise. It does not ask founders to renounce defence contracts or to pretend that dual‑use technology can be clean. It simply asks: if your company benefits from a war, what structural rules will you put in place to ensure that benefit does not become private enrichment from destruction?

The answer is a governance architecture that separates participation from profit. And that architecture can be designed, implemented, and audited – without sanctimony, without denial, and without leaving the problem to someone else.

This blog post is part of a series on governance models for frontier technology startups. The author is a founder working on dual‑use sensing systems. The framework described is under active development and is not legal advice.