R&D projects involve uncertainty and high costs. Public funding shares this risk and makes it easier for innovative projects to come to life. However, the scope, criteria and schedule of funding programs may change over time; this article provides a general framework, and the current call text must always be checked before applying.
- Develop the idea within a scientific framework.
- Make the goals measurable and the budget consistent.
- Base every application on the current call text.
Why do funding programs matter?
R&D activities are work whose outcome isn't guaranteed. Funding covers costs such as personnel, equipment and services, giving the company the courage to try innovative ideas. At the same time, preparing for funding forces the project to mature scientifically and managerially.
R&D funding is a mechanism that helps companies finance risky, long-term technology investments. Developing an innovative product or process requires time, expert staff, equipment and testing costs; funding eases part of this burden and makes it easier for companies to take on bold projects. But funding shouldn't be a goal in itself: first the project's commercial and technical value should be considered, then the appropriate funding mechanism.
In Türkiye, there are programs from different institutions such as TÜBİTAK, KOSGEB, the Ministry of Industry and Technology, development agencies and EU programs. Each has a different target group, application procedure and evaluation criteria. For the current list of programs, see our projects and funding programs page.
1. Develop the idea scientifically
Applications written without a problem definition, literature review and comparison with existing solutions remain weak. As well as "what will we do?", the question "why hasn't anyone solved this yet, and how will we solve it?" must be answered. The project's technically innovative side must be stated clearly.
The first step in turning an idea into an R&D project is defining the problem correctly. What technical uncertainty will be resolved? What's lacking in existing solutions? Where does the innovation lie? Literature and competitor analysis show whether the idea is truly original. An academic perspective adds great value at this stage, because reviewers look not only at whether the product is good but also at whether the development process is scientifically defensible.
2. Feasibility and goals
Technical feasibility, timeline, team competence and budget are the backbone of the project file. Goals should be measurable: for example, "reducing processing time to a specific level" instead of "faster".
A feasibility study sets out technical feasibility, market potential, cost and revenue estimates and risks. Goals should be measurable: for example, "reducing the error rate below a specific level" or "shortening processing time". Vague goals cause problems both in application evaluation and during execution.
3. Preparing the project proposal
Work packages, timeline, risk analysis, team introduction and budget must be consistent with each other. Following the call's format and page/character limits is necessary for a proper evaluation.
The project proposal should consistently describe the objective, method, work packages, risk analysis, team, budget and outputs. The most common mistakes are work packages and budget that don't match, an unclear innovative element and unrealistic timelines. The file is expected to follow the call format exactly, be written in short, clear language and back every claim with evidence.
4. Execution and reporting
In approved projects, periodic technical and financial reporting is critical. Documenting expenditures, justifying deviations and delivering outputs on time affect project success.
In an approved project, the real work starts then. Work packages must be carried out on schedule, expense documents kept in order and periodic reports submitted on time. Spotting the risk of deviation early and notifying the institution is the best way to solve problems before they grow.
How can you get support?
With its academic staff, DGH Ar-Ge provides technical support in idea development, proposal preparation and execution. Evaluation and approval are at the discretion of the relevant institution; no guarantee is given.
At DGH Ar-Ge we offer idea development, eligibility analysis, application file preparation and execution support. The approval decision lies with the institution and cannot be guaranteed; we focus on making the file strong, consistent and aligned with the call. You can start with a free initial consultation.
Quick pre-application checklist
Before applying, you should be able to answer these questions: What is the project's innovative element and how will I prove it? Where is the technical risk and how will I manage it? Is my team competent enough, and how will I fill missing expertise? Is my budget aligned with the work packages? What measurable output will I have at the end of the project? If you don't have clear answers, it's better to postpone the application and spend time on preparation.
Common mistakes
The most common mistakes are presenting routine software development as R&D, leaving the innovative element vague, inflating the budget, keeping an unrealistic timeline and leaving the application until the last day. Also, applying to different programs for the same cost may run into the double-funding ban, so checking the rules should be part of the application strategy.
How to choose the right program
Company size, project type, duration, budget and targeted output are evaluated together. If you're an SME having your first R&D experience, start-up-focused programs stand out; for more comprehensive, industry-oriented projects, industrial R&D programs; and for specific technology areas, call-based programs. For investment-heavy projects, KOSGEB's technology investment program, and for projects involving university collaboration, programs such as SAN-TEZ can be considered. When choosing, look not only at the funding amount but also at the application workload, reporting obligations and schedule.
It may be possible to benefit from different parts of different programs for the same project, but the double-funding rules must be observed. Eligibility analysis is the most valuable step in the application strategy.
R&D center and technopark advantages
In addition to project-based funding, there are legislation-based advantages for companies that build a formal R&D structure, such as the R&D and design center certificate and operating in technology development zones. These offer certain tax and social security incentives and opportunities for university collaboration. Conditions depend on the number and qualifications of staff, premises and type of activity, and may change over time. For details, see our R&D center certificate and Technopark pages.
University–industry collaboration
When academic knowledge and industrial needs come together, projects with both scientific depth and market reality emerge. In the collaboration, intellectual property, publication rights, confidentiality and use of outputs should be put in writing from the start. Choosing the right academic partner is decisive for the project's success; working with relevant expertise also has a positive effect in the referee evaluation.
Practical tips for preparing the application file
Before you start writing the file, review the call text, evaluation criteria and application form headings line by line. Note what information each heading expects from the reviewer and structure your file around these headings. Use short, clear and measurable sentences in the technical description: "reducing processing time to a specific level" instead of "improving performance". Add the basis (literature, preliminary experiment, market data) next to every claim.
Design work packages with interconnected outputs; each package should have a start, end, owner and validation criterion. Match the budget to the work packages and check that cost items meet the call conditions. Finally, read the file as an outsider would: is the innovative element clear on the first page? Are there inconsistencies, repetition or ambiguity? This independent reading noticeably improves the quality of the file.
Record-keeping and documentation during execution
The most common problem after approval is that documents are kept in disorder even though the work is done well. Keep staff work records, purchase documents, invoices and payment receipts, test and experiment records and meeting notes in an orderly folder structure from the start of the project. At periodic reporting time you need to match technical outputs with financial documents; when this matching is set up from the start, report preparation takes hours, not days.
Talk to our experts
Have a project on this topic? The first consultation is free: get in touch or 0534 065 87 78 call this number.