Business Finland
What Business Finland evaluators actually look for in an R&D funding application
The six criteria evaluators weigh (novelty, scalability, team, budget, impact, international dimension). Signals they trust vs discount. Revise-and-resubmit failure modes. Real approvals EUR 70k–957k (2021–2026).
Short answer: Business Finland evaluators weigh six things, in roughly this order: genuine R&D novelty (not routine development), scalability of the resulting business, team’s ability to execute the plan, budget realism, the impact narrative (renewal, jobs, exports, spillover), and the international / spillover dimension. Everything else in the application — layout, tone, appendices — is decoration around those six. Applications get rejected or sent back for revision when one of the six is weak, not when the writing is imperfect.
Business Finland publishes its own criteria page and every consultancy in Finland cites it. The problem is that the public page is written for legal and political defensibility, not for a founder trying to shape a real application. It tells you the labels the evaluators use. It does not tell you what evaluators actually mark down, what they under-weight, and what makes a project plan get flagged for a second review.
Across four approved grants we have personally shaped for Finnish companies — EUR 1.57M in Business Finland approvals between 2021 and 2026, ranging from a EUR 70k first grant to a EUR 957k multi-year programme — the pattern is consistent. Below is the operator’s version of what evaluators are actually looking for, section by section, with the failure modes that quietly kill otherwise-decent applications.
The six criteria evaluators actually weigh
Not every instrument scores these identically — Sprint, R&D grant, Young Innovative Company, and growth funding have their own tilts — but the underlying six show up in every review.
- Genuine R&D novelty. Is there a real technical, methodological, or productization uncertainty at the heart of this project, or is this a build with a well-understood outcome?
- Scalability. If the R&D works, is there a credibly large business at the end of it — or a large improvement to an existing one?
- Team execution risk. Can this team, at this stage, actually deliver this plan?
- Budget realism. Do the numbers line up with the work described, or is the budget either padded or unserious?
- Impact narrative. Does the project meaningfully increase Finland’s renewal capacity — new jobs, new exports, new capabilities, spillover to the ecosystem?
- International / spillover dimension. Does the resulting business travel outside Finland, and does the R&D benefit reach beyond the applicant?
The rest of the application document — cover pages, org charts, GANTT diagrams — is scaffolding. Evaluators score the six.
1. Genuine R&D novelty
This is the single filter that decides whether the application belongs at Business Finland at all. Business Finland is a public R&D funder, so its whole mandate is to de-risk work the private market will not fund alone. “R&D” here is not a mood; it is a specific claim that there is a defined uncertainty — technical, methodological, or productization — that the project intends to resolve.
Evaluators do not want vague ambition. They want a sentence that reads something like “we do not yet know whether X can be achieved with Y approach at Z reliability, and this project is how we find out.” If the founder cannot say that in one sentence, the application is already in trouble.
What makes this section fail:
- Describing an ambitious deployment of a well-understood technique as if the ambition itself were the R&D.
- Framing “adopt AI in our operations” or “build an internal copilot” as R&D — that’s procurement or productivity work.
- Uncertainty stated at the market level (“we don’t know if customers will pay”) rather than at the technical/productization level.
- Buzzword-heavy novelty (“generative AI-powered platform”) without a specific technical unknown attached.
- No reference to prior art. Evaluators mark down applicants who write as if the field started yesterday.
2. Scalability
Once novelty is credible, the second question is size. Not “how big is this year’s revenue,” but if the R&D succeeds, how large is the business or the productivity effect that follows? Business Finland’s mandate is renewal of the Finnish economy — small-outcome projects, even if technically clean, do not compete well.
Scalability is scored on two axes: market size (addressable customer base, geography, willingness to pay) and defensibility (does the R&D create something a follower cannot trivially copy). Both need to be argued, not asserted.
What makes this section fail:
- Unquantified market size — “the global AI market is EUR 200 billion” is treated as noise, not evidence.
- Only Finnish TAM, when the instrument implies international growth.
- No defensibility argument. If the project ends and any competitor can replicate the result in six weeks, scalability is weak.
- Confusing “big vision” for scalability. Ambition without a mechanism is not fundable.
- Scaling claim that contradicts the team plan (a two-person team claiming they will serve a EUR 10B market alone).
3. Team execution risk
Business Finland evaluators read the team section the way an investor reads it: can this team ship this plan? The rest of the plan is only as strong as the people who will execute it. This is the section where senior evaluators most often have quiet objections that never surface in the written feedback.
Two things carry weight: domain-specific R&D experience (has this team done work like this before, or credibly worked alongside people who have) and evidence of shipping under uncertainty (prior projects delivered, prior grants managed cleanly, prior products taken to market).
What makes this section fail:
- CV dump with no mapping to the work packages. Evaluators want to know who does what, not who exists.
- Overweight founder biographies, underweight technical hires. If the R&D is ML-heavy and the team has no senior ML person, the project reads as unstaffed.
- Named subcontractors with no explanation of what they cover or why.
- Missing accountability. It should be obvious who owns each work package.
- Team plans that assume hires that have not happened yet, without a hiring plan or a plan-B.
4. Budget realism
Budgets are read forensically. Evaluators know within a narrow band what senior R&D personnel cost per hour in Finland, what a work package of a given shape typically consumes, and what a defensible split between salaries and subcontracting looks like. Padding is visible. So is under-scoping.
The evaluator is asking two questions in parallel: does the budget match the plan and does the split of costs match the instrument’s rules (personnel share, subcontracting cap, indirect costs, VAT treatment). If either answer is no, the file is either revised down or returned.
What makes this section fail:
- Round numbers everywhere. “EUR 500,000 for personnel” without a personnel plan reads as fiction.
- Subcontracting share out of line with the instrument’s cap.
- Missing co-funding plan. Evaluators need to see how the company’s share is covered, in cash or in loan.
- Personnel costs that assume senior hours from people who are not senior, or hours that would require the CEO to be full-time on delivery while also running the company.
- Budget that grew to match a target number rather than the work.
5. Impact narrative
Business Finland is a policy instrument. It reports upward to ministries that report to voters. Every approved project needs a story about why Finland is better off if this happens — measured in jobs, exports, tax base, and capability build-up. This section is where many technically strong applications lose points because founders treat it as boilerplate.
Impact is not a mood; it is a small set of measurable claims. Direct headcount growth over the project horizon. Export share. Follow-on private investment attracted. New IP or capability that stays in Finland. Ecosystem spillover — will other Finnish companies benefit from this work?
What makes this section fail:
- Vague “creates jobs” claims without numbers or a timeline.
- No export dimension when the instrument is growth-oriented.
- Impact that only accrues to the applicant, with nothing that spills to the broader Finnish ecosystem.
- Claiming impacts that the plan cannot produce — 50 hires from a EUR 200k project is not credible.
- Ignoring sustainability, safety, or societal dimensions on projects where they naturally apply.
6. International / spillover dimension
For growth-adjacent instruments especially, evaluators explicitly weigh the international angle. Purely domestic projects are legitimate for some instruments, but even there, spillover to research partners, universities, or downstream Finnish companies improves the score.
The evaluators are asking: does the resulting business or knowledge leave Finland in a value-generating way? Exports, foreign customers, international collaborators, and publications or open-source outputs that raise Finland’s visibility all count.
What makes this section fail:
- No named international market, target customer segment, or first-mover geography.
- “Global launch” claims with no localization, no regulatory work, no partner plan.
- International collaborators who appear only in the org chart and never in the work packages.
- Zero spillover — no research partner, no ecosystem link, no open output, no plan to share what is learned.
Signals evaluators trust vs signals they discount
Not every strong-sounding sentence lands equally with an evaluator. The pattern below repeats across four approved files.
| Category | Signals evaluators trust | Signals evaluators discount |
|---|---|---|
| Novelty | Named technical uncertainty; reference to prior art; a testable hypothesis | Generic AI / GenAI buzz; “revolutionary” claims; buzzword stacking |
| Market | Segmented TAM with sources; named target customers; letters of intent | “USD 200B global market” numbers; unsegmented TAM; no named customer |
| Team | Domain-specific track record; prior R&D delivery; named work-package owners | CV dumps; founder-only biography; unassigned work |
| Budget | Personnel plan with named seniority; subcontracting scoped to the instrument’s cap; declared co-funding source | Round numbers; padded subcontracting; missing co-funding plan |
| Impact | Specific hire count, export target, follow-on capital estimates, spillover paths | “Will create many jobs”; broad statements without numbers |
| International | Named markets, localization plan, active foreign collaborators | Vague “global expansion”; passive international claims |
| Credibility | Prior Business Finland or Horizon Europe delivery; named collaborators; internal R&D history | Reliance on the consultant’s reputation instead of the applicant’s |
The trust column shares one property: every entry is a claim the evaluator can verify, either from the file itself or from public data. The discount column shares the opposite — claims that cannot be falsified, because they were not really claims.
How ambition should scale with company stage
One of the quiet failure modes is a company applying for a euro number that does not match the shape of the project or the maturity of the team. The reverse also happens — a company that could credibly execute a programme-scale project applies for a starter grant and wastes the opportunity.
The right sequence is stage → project shape → work packages → instrument → budget. Starting from a target number and working backward is exactly the pattern evaluators recognise and mark down.
The progression across four grants we have shaped illustrates this graduation:
- EUR 70,000 (2021) — a small Finnish company with one honest R&D uncertainty. Single work package, tight scope, no international claim yet. The application asked for what the work actually required. Approved as-is.
- EUR 957,000 (2024) — a mid-market industrial company with real internal R&D history, a multi-year applied-AI programme, and defensible data assets. Three-plus work packages, senior hires named, credible spillover to Finnish suppliers. The scale was justified by the shape, not by the ambition.
- EUR 187,000 (2025) — a SaaS scale-up with one clean productization uncertainty and a six-month arc. Deliberately narrow. Could have been padded to EUR 300k; would have been marked down for it.
- EUR 357,000 (2026) — a company graduating from an internal AI capability to a productized platform with a first international work package. Two fundable shapes stitched into a coherent programme, sized honestly for the team’s capacity.
None of these companies would have gotten another’s number. Evaluators do not reward ambition; they reward the match between the plan, the team, and the ask.
Common reasons an application gets “revise and resubmit”
Business Finland rarely rejects outright on a first read. More often, the file comes back with a request to revise and resubmit, which is a strong signal — the project shape is fundable but something specific is blocking approval. The recurring reasons:
- R&D uncertainty not clearly stated. Evaluators cannot name the specific unknown the project resolves.
- Work packages that are actually procurement. One or more WPs read as buying, not researching.
- Budget mismatch with plan. Numbers do not track the work, or the personnel plan is inconsistent with the budget.
- Missing or vague co-funding plan. Evaluators need to see the company’s own share is secured.
- Team gap. A critical senior role — usually the technical lead — is unnamed or under-experienced.
- Impact section that reads as boilerplate. No numbers, no timeline, no verifiable claim.
- International dimension weak on a growth-oriented instrument. No named market, no localization plan.
- Overlap with a previous project. Reviewer suspects the work was already funded or already done.
- Ambiguity about who owns the IP at the end of the project, especially where subcontractors carry heavy hours.
- Sustainability / ethics / safety ignored on a project where they naturally apply.
Each of these is fixable in a revision without changing the underlying project. That is the point of the revise-and-resubmit signal — the evaluators are telling you which one of the six criteria they cannot currently score high enough.
FAQ
Does the reviewer talk to the applicant during Business Finland evaluation? Sometimes. Business Finland evaluators may schedule a call or request written clarifications, especially on larger applications or when a specific criterion is unclear. Evaluation is document-first, but applicants should be prepared to defend the file live if asked.
How long does Business Finland R&D application evaluation typically take? For most R&D grant instruments, expect roughly two to three months from submission to decision, sometimes longer for larger multi-work-package files. Sprint funding decisions are faster. Publicly stated turnaround is a floor, not a promise.
Does branding or the visual polish of the application document matter to Business Finland evaluators? Marginally. Clean structure and clear headings help evaluators find what they need, but graphic design does not move scores. Time spent on aesthetics past legibility is time not spent on the six criteria that actually score.
Do Business Finland evaluators weight founder background heavily? Yes, as part of team execution risk. A strong founder does not rescue a weak plan, and a weak founder is rarely fatal if the technical lead is credible. What matters is whether the specific people named in the file can deliver the specific work packages.
Can a Business Finland funding decision be appealed? Yes, formally. In practice, a stronger move is usually to take the written feedback, revise honestly against the criticism, and resubmit. This converts to a higher approval rate than pushing a formal appeal against a decided file.
Is there a published scoring rubric for Business Finland R&D applications? Business Finland describes evaluation criteria publicly but does not publish per-criterion weights or numeric rubrics. Six operational criteria — novelty, scalability, team, budget, impact, and international dimension — are the working shape of what evaluators discuss internally.
Does having an existing product help or hurt a Business Finland R&D application? Neutral on average. It is positive if the existing product credibly demonstrates the team’s ability to ship, and negative if the new R&D reads as further build-out of an existing product with no new uncertainty. Evaluators draw a line between extension and research.
Do Business Finland evaluators prefer specific AI use cases such as LLMs or computer vision? No. The technology mix is neutral. What matters is that a real uncertainty sits inside whichever technology is chosen. A computer-vision project with a clean methodological unknown scores identically to an LLM project with the same shape.
The one-sentence version
Business Finland evaluators are looking for a genuine R&D uncertainty, a business large enough to matter if the R&D succeeds, a team that can actually ship the plan, a budget that tracks the work, and a credible impact story that reaches beyond the applicant — and they will send an otherwise-decent application back to be revised as many times as it takes to see all six clearly.
Related: What kinds of AI projects does Business Finland actually fund? · Business Finland R&D grant vs R&D loan — which one, when, and why the mix matters · Are Business Finland grant consultants worth the fee? · Can a foreign-founded company registered in Finland get Business Finland funding?