Tækniþróunarsjóður | Ísland.is

Captured cycle: This page is retained for historical guidance. Confirm whether the program has reopened before planning an application.

Tækniþróunarsjóður | Ísland.is

The Technology Development Fund (Tækniþróunarsjóður) is a broad Icelandic funding program run by Rannís, and it is best understood as a group of grant tracks rather than a single one-size-fits-all grant. Each category supports a different development stage and different applicants, including start-ups, established small and medium enterprises, universities, and public research institutions.

A common misunderstanding is to treat this as a single fixed program with a single max amount. In practice, it works as an ecosystem of tracks: seed-stage preparation support, early development support, growth support, market support, applied research support, and patent support. The official pages also state that most of these categories are competitive and that not all categories are open at all times.

To make a useful decision, you need to answer one question first: which stage best describes your project right now? If your project has a good prototype but no route to users, your track is different from one that already has paying customer pilots. If it is still only an idea, your track is different from one that already has measurable technical output.

At-a-glance (read this in under two minutes)

What the fund is trying to support

The fund’s intent is practical innovation: technologies or development work that can become something used in industry, services, or society. The category pages repeatedly describe outcomes like developing new products, improving processes, or introducing important upgrades rather than funding only abstract analysis.

The fund is therefore useful if you can describe:

• what problem exists today,
• what your project changes,
• how you will test or deliver this change,
• and who benefits.

In plain terms: if you can explain why your work matters and how it moves beyond a concept note, you are closer to being in scope. If your work is still only a scientific curiosity with no commercialization path, this may not be the right vehicle and will likely be a weaker fit than pure research funding routes.

What this fund offers in practice

The official category overview page provides the most operational summary and shows that support levels and conditions vary by grant type:

• Fræ/Þróunarfræ (Seed preparation): max around ISK 2 million, usually for concept-stage projects, typically 12 months, no mandatory co-funding requirement listed in the brief overview.
• Sproti: a development grant for early-stage company projects, up to about ISK 2 × 10 million, with usually no co-funding required.
• Vöxtur: intended for projects beyond very early idea stage, shown in one official overview as up to around ISK 2 × 25 million and typically subject to matching rules referenced in the full rules.
• Markaður: for marketing-related development support related to commercialization activities, with max around ISK 10 million and stronger co-funding expectations.
• Hagnýt Rannsóknarverkefni: up to around ISK 3 × 15 million over 1–3 years, with a matching expectation and explicit focus on applicable research outputs.
• Einkaleyfisstyrkur: for patent filing preparation support, with smaller maxima (hundreds of thousands of ISK) and stronger matching expectations in the details.

These amounts and percentages should be treated as indicative of the published range and category design, not as an automatic entitlement. The important part is not the absolute number; it is whether your project design fits the category and whether your proposal can be scored against the published category criteria.

If you compare this fund to a linear “bigger number = better chance” model, you will miss why applications fail. Review teams usually care more about clarity and feasibility than size alone. The category with the largest maximum is not automatically the best fit if your project has not reached that stage.

Who should apply, and who should apply elsewhere

Strong fit

A strong fit is usually any of the following:

• an Icelandic start-up with a clear technology or data-driven development need,
• an early-stage team with first prototypes and a defined use-case,
• a company that has passed idea stage and now needs support to advance through development,
• an SME with measurable R&D and commercialization milestones,
• a university or public lab with collaborative potential for applied development.

Weak fit (or wrong channel)

• exploratory science with no practical outcome pathway,
• projects seeking unrestricted operational spending with no technical milestones,
• teams unable to show what changes after grant support,
• teams hoping to use the fund as general budget support instead of a structured development plan,
• applications that do not match the selected category at all.

The program is not a poor fit just because your project is technical. The issue is whether the technical work is tied to measurable practical or commercialization outputs.

Eligibility and category fit checklist

You should build your own pre-check before application:

1. Choose a category by stage, not by name.

   • If this is pre-feasibility and concept planning, seed support is usually more realistic.
   • If your team already has early development and prototype structure, Sproti is often a better match.
   • If you need to scale an existing project and prove market traction, Vöxtur may be more realistic.
   • If you need structured support for commercialization and go-to-market activities, Markaður may be relevant.
   • If you are in universities or public research with direct practical objectives, check applied research details.

2. Check applicant-type boundaries.

   • Some tracks explicitly target companies under a number of years.
   • Some tracks allow broad co-applicants (universities, institutions, large companies), others are narrower.

3. Check language and documentation requirements early.

   • Some pages are in Icelandic and important instructions about language apply.
   • Title and summary language requirements differ by channel and call.

4. Check finance expectations by category.

   • Not all categories require matching funds.
   • Some require high co-funding levels while some do not.
   • Marketing and patent-related support have separate structures and should be read from their official pages.

5. Check call rhythm.

   • Some tracks are open year-round; others run as call-based windows.
   • The important dates in one recent round were shown with deadline 16 February 2026 at 15:00 for several categories.

How to decide whether it is worth your time

Before writing your first draft, do a 20-minute fit test:

• Can I describe my project’s concrete result in one paragraph?
• Can I show evidence of customer need, even if only via interviews?
• Can I show a realistic development timeline with milestones and dependencies?
• Can I state where the money is spent, by month and by output?
• Can I explain my own co-funding or internal capacity realistically?

If you score 3 or fewer “yes,” you are not necessarily rejected, but you will spend time rewriting a weak plan. In that case, a better path may be to prepare a pilot memo first and return after one short user validation cycle.

What to prepare before you apply

A well-built application is a planning document as much as a funding request. Build it in this order:

1) Define a narrow problem and one measurable outcome

Do not write a broad policy-level story. Write one problem and one project output. For example:

• “We will reduce false alarms in industrial sensors by X% by Q4,” or
• “We will release a working software beta used by Y pilot sites in pilot testing.”

Reviewers often reject over-wide proposals because they cannot evaluate whether milestones are too many, too vague, or too broad.

2) Build a staged work plan linked to grant disbursement

Even if not yet explicitly confirmed in detail on your track page, project funding typically follows completed stages. A realistic plan should include phase 1, phase 2, phase 3 and a set of completion criteria for each.

For each phase specify:

• deliverable,
• target date,
• responsible person,
• expected cost,
• decision points.

3) Build a credible budget

Use a bottom-up budget:

• personnel by role,
• contract costs,
• infrastructure,
• specialist services,
• reporting and administration overhead.

Avoid top-line totals without logic. Reviewers can immediately tell if the spending plan is disconnected from execution. Keep costs explicit and avoid stacking all labor into one line with no task mapping.

4) Prepare co-funding evidence (if needed)

If your track requires matching, start this before drafting narrative sections. A co-funding plan without concrete evidence looks weak. Evidence can be:

• internal board or owner decisions,
• existing grant approvals,
• signed letters of intent,
• committed service contributions documented in writing.

Application process

Step A: confirm call status and category page

Because category deadlines and active windows vary, your first action is opening the current category page and reading requirements exactly as published now. Do this before writing a full statement.

Step B: gather official forms and instructions

Rannís and the fund pages include application instructions and rules. The English program page notes that some forms are not available in English, and some elements may need Icelandic title/summary elements in submission. This is not a minor detail; mismatched language formatting can delay a submission unnecessarily.

Step C: draft technical + commercial sections as one package

Keep these linked:

• what technology you build,
• why someone buys or adopts it,
• how you verify this with early testing,
• what success looks like.

Step D: draft budget and matching table

State the total project cost, requested grant amount, and matching amount side by side. If your category does not require matching, state this explicitly and justify that structure.

Step E: internal check and language pass

Ask at least one person outside your team to read the full package. The most common failure mode is “clearly correct internally” but incomprehensible to external reviewers.

Step F: submit early

For date-sensitive calls, the captured-cycle instructions asked applicants to submit before final-day technical stress. Use a buffer window for portal issues and attachment upload problems.

Timeline model you can use now

You can use this practical structure whether your category is open year-round or has a fixed date:

Weeks 1–2:

• confirm call status,
• choose category,
• lock key outputs and team responsibilities.

Weeks 3–4:

• draft project and market sections,
• estimate milestones and resource needs.

Weeks 5–6:

• build full budget,
• prepare letters/commitment evidence,
• check language and attachment rules.

Week before deadline:

• final technical plausibility review,
• complete final checks for section completeness,
• submit and verify confirmation.

For projects in competitive, non-open windows, subtract time for any missing attachments early.

Common mistakes that reduce competitiveness

1) Wrong category selected

The biggest practical issue is mismatch. If your project is concept-stage but filed under growth, or if your company is too early for a high-stage category, the review will focus on mismatch, not technical ambition.

2) Overstated maturity

If your timeline claims completion of advanced prototypes in months while the project complexity suggests longer cycles, reviewers will often mark the plan as unrealistic.

3) Unclear milestone logic

A milestone list is only useful if each milestone has measurable outcomes. “Increase innovation” is not measurable. “Reduce setup time by 30% for pilot process X by date Y” is measurable.

4) Budget disconnected from milestones

Do not submit a budget with no causal link to deliverables. Your budget should explain why each major cost is required and how it supports completion.

5) Weak co-funding position when required

If the category requires a matching contribution, a weak or vague plan reduces credibility heavily. Put co-funding evidence in clear sections.

6) Ignoring language requirements

The English landing summaries are helpful, but application mechanics can still be Icelandic-first. Follow official field instructions precisely.

7) Treating fund support as pre-sales funding

This fund is not a substitute for regular operating cash. It supports defined development work tied to measurable outputs.

How applications are judged (what usually matters)

Across these categories, common judging priorities are practical and repeatable:

1. Clarity of technical challenge: Is the problem real and well described?
2. Feasibility: Is the proposed method coherent with team capability?
3. Commercial sense: Does the team know where adoption happens?
4. Budget realism: Does spending align with outputs?
5. Execution readiness: Are risks identified and managed?
6. Fit with category and rules: Is this application in the right track?

Even a technically interesting idea is less competitive if it is poorly structured. Conversely, a moderate idea can score higher if it is deeply grounded and clearly executable.

FAQ for first-time applicants

Can non-Icelandic teams apply directly?

The fund is designed for the Icelandic innovation system, with primary applicants tied to Icelandic entities in the relevant category pages. If you are not based locally, this usually requires a strong local applicant route.

Does this fund support all technologies?

The pages present category-wide support for innovation and development, not one narrow topic. It is broad, but each track and call can emphasize specific priorities. Read current requirements before assuming any topic is automatically accepted.

Is this only for companies?

No. Public research and universities appear in the program structure, especially for applied research-style tracks.

Are application forms available in English?

Not always. The official summary for the fund notes that some application forms are not available in English and that title/summary can have Icelandic language requirements. Check the live form instructions before writing your final text.

Is there a support call now?

Some categories are open all year, while others have specific deadlines. A recent published call included categories with a February 2026 15:00 deadline. Always use current pages because round timing changes.

What about patent support?

There is a patent-focused grant category with lower maxima than development categories. If your principal need is patent filing strategy and preparation, this can be relevant, but it has its own rules and matching constraints.

What to do next, right now

1. Open the official Rannís fund landing page and copy the current category URLs for your chosen track.
2. Download the official rules for that category.
3. Build a one-page problem-to-deliverable summary.
4. Choose milestones and assign each to budget lines.
5. Confirm what can be in Icelandic versus English in your selected submission flow.
6. Contact the fund email only after these steps, with one focused question per request.

This sequence significantly reduces the odds of a weak submission and avoids the two most common errors: category mismatch and budget mismatch.

Official links and references

• Tækniþróunarsjóður – Rannís (Icelandic)
• Grant-category overview
• Category rules
• Seed support (Fræ/Þróunarfræ)
• Sproti
• Vöxtur
• Markaður
• Hagnýt rannsóknarverkefni
• Contact: [email protected]