ESA vs. EU procurement: the IP-ownership rule every founder gets wrong

Two public buyers, two different rulebooks

The European Commission, EUSPA, ESA, and national space agencies are, per EU Space Academy's Selling to Europe course, the main public buyers a European space company deals with — and they operate mainly through public procurement tenders and research grants. It's tempting to treat "public-sector procurement" as one rulebook. The course, taught by BHO Legal's Dr. Ingo and Dr. Philip, is explicit that it isn't.

ESA is an independent intergovernmental organization, and it runs its own procurement rules and provisions, separate from EU law. The EU — meaning contracts issued by the European Commission or EUSPA — operates instead under the EU Financial Regulation, which the course describes as similar, in places almost identical, to national public-procurement law, but with its own particular rules in practice. National member-state procurement law is a third, related-but-distinct layer again. First-time bidders consistently underestimate how much these three regimes diverge in the details — worth confirming which one governs before you assume anything carries over from a previous bid.

The IP-ownership rule founders get backwards

Here's the single highest-value fact in the course, and per its own lawyers, one that even experienced space-industry SMEs get wrong: in an ESA contract, the contractor remains the owner of the IP it generates while carrying out the project. In an EU contract — European Commission or EUSPA — the IP generated during the project is owned by the customer, not the contractor. Assume the opposite of whichever one you're used to, and you'll misjudge what you actually walk away with.

To use this rule you need two definitions the course leans on:

• Background IP — intellectual property you already owned or had rights to before the project started, and that you bring into it: existing patents, pre-existing code, prior know-how.
• Foreground IP — intellectual property newly generated while carrying out the funded project itself.

The ESA-vs-EU ownership split above applies specifically to foreground IP. Background IP stays yours going in — but the course adds an important caution: don't over-declare what you flag as background IP. Only flag what your project genuinely needs. Whatever you list as background IP becomes subject to license-rights obligations toward ESA, the Commission, or EUSPA, so over-flagging needlessly hands over rights you didn't need to encumber.

One more warning worth carrying into any cap-table or due-diligence conversation: a lot of early-stage space companies' core technology starts life as a license from the university or research organization they spun out of. The course's advice is blunt — get independent legal review of that license agreement at the point you sign it, even if the university insists it will handle everything. These are foundational contracts, and problems such as royalty terms or scope limits tend to surface years later, once they're expensive to renegotiate.

Simplified for comparison — always confirm the exact IP and data clauses in the specific contract or grant agreement you're signing. See our companion piece on IP, data protection, and company form for the data-protection side.

How long a European space tender actually takes

Budget your runway around this: per the course, tender procedures "can take half a year, nine months" for a fairly ordinary case, and its lawyers say they've seen large tender procedures run "up to two years" from launch to contract. That entire window sits before any contract revenue lands — you're expected to pre-finance product development, market entry, and the tender-preparation work itself, proposals, compliance paperwork, reference-building, out of your own capital.

Practically, that means a tender submitted this quarter is a fundraising-and-runway question, not a near-term revenue one. If your financial model assumes a six-week sales cycle because that's normal in commercial software, re-anchor it — ESA and EU tender timelines run on a different clock, and the course's own experience puts large-tender timelines at up to two years.

The document set to keep permanently ready

One piece of the course's advice pays for itself the first time you use it: keep a standard tender document set current at all times, rather than assembling it from scratch under deadline pressure. Per the course, the standard set includes:

1. An extract of your company register
2. Documentation of your legal entity form
3. Financial identification forms
4. Europass CVs for all key people on the project
5. A list of project references

The logic is simple: the more of this is prepared and kept up to date, the less effort each individual tender procedure costs you, freeing your time for the part that actually differentiates your bid — the project content itself — rather than chasing down a register extract the week a deadline closes.

What this means for your next bid

1. Before signing, check who owns foreground IP under that specific instrument — don't assume ESA's rule carries over to an EU contract, or vice versa.
2. Only declare background IP your project genuinely needs; over-flagging pulls it into licensing obligations you didn't need to accept.
3. If your core technology is licensed from a university or research organization, get independent legal review of that license before you sign — not after royalties become an issue.
4. Build your tender document folder — register extract, legal form, financial ID forms, Europass CVs, references — before you need it, and keep it current.
5. Budget runway assuming six months to two years before contract award on large tenders, and treat your company form as part of your tender-readiness; see our companion piece on IP, data protection, and company form for why a bare-minimum entity can get you excluded before evaluators even reach your technical proposal.

FAQ

Sources