Business Finland

IPR strategy inside a Business Finland R&D project

How intellectual property works inside a Business Finland R&D project — who owns the results, background versus foreground IP, subcontracting, and the mistakes to avoid.

Intellectual property is where R&D funding is quietly reassuring and quietly risky at the same time. Reassuring, because Business Finland funding is dilution-free and generally leaves the results in the company’s hands — you keep what you develop. Risky, because IP problems usually come from how you structured the project, not from the funder — and they surface later, when a partner, subcontractor, or acquirer starts asking who actually owns what.

This is strategic orientation, not legal advice. IP is contract- and situation-specific; get proper counsel for your case.

The good news: you keep your results

Unlike equity investment, Business Finland funding doesn’t take ownership of your company or, generally, of the IP you create. The results of a company R&D project normally stay with the company. That’s a real advantage of non-dilutive public funding — you fund the development and own the outcome.

But “you own it” is only clean if you built the project so that all the relevant IP actually flows to you. That’s the part companies get wrong.

Background vs foreground IP

The distinction that prevents most disputes:

Background IP is what you (or a partner, or a subcontractor) bring into the project — pre-existing know-how, code, models, data.
Foreground IP is what’s created during the project with the funding.

Problems arise when the two aren’t clearly separated. If your foreground results depend on someone else’s background IP that you don’t have proper rights to use, your ownership of the results is encumbered. Map, at the outset, what background IP the project relies on and confirm you have the rights to use it in the results.

Subcontracting is the main risk

The most common IP trap is subcontracting. When you pay an external party to develop part of the R&D, who owns what they create? By default — and depending on the contract — it may not automatically be you. If the subcontractor retains rights to work your product depends on, you have a problem that may not appear until a due-diligence process years later.

The rule: contract IP ownership explicitly, before the work starts. Any subcontracting agreement inside the project should state clearly that the foreground results transfer to your company (and handle any background IP the subcontractor uses). Don’t assume payment equals ownership.

Collaboration and partners

If the project involves partners or is part of a collaborative setup, IP ownership and usage rights among the parties need to be agreed up front. Joint development without a clear IP agreement is a recurring source of later conflict. Agree who owns what, and who can use what, while everyone is still aligned.

Why this matters beyond the project

IP clarity has value well past the R&D itself:

Fundraising and exit. Investors and acquirers scrutinise IP ownership. Encumbered or unclear IP — especially subcontractor-held rights — can reduce valuation or stall a deal.
Commercial freedom. You can only license, sell, or build on IP you actually and cleanly own.
Future funding. A clean IP position strengthens later applications and partnerships.

The practical checklist

Before and during the project:

Map background IP the project relies on and confirm your rights to use it.
Contract explicitly that foreground results from subcontractors transfer to you.
Agree IP ownership and usage rights with any partners up front.
Keep records of what was developed, by whom, and under what terms.

The takeaway

Business Finland funding lets you keep the IP you develop — but only if you build the project so the IP genuinely flows to you. The threats are almost always in the contracts, especially subcontracting, not in the funding. Handle IP as a design decision at the start, and you protect both the project’s results and the company’s future value.