TUBITAK TEYDEB Consultancy
Turn your technical idea into an evaluable, trackable R&D project.
We bring programme and call selection, technical project architecture, work packages, budget, and periodic implementation together under one project logic. We don't work to make the file look strong — we work to make the technical claim provable.
Technical Uncertainty
The project's R&D justification
Work Package Logic
Activity, output, and dependencies
Measurable Output
Success criteria and verification
Periodic Consistency
Realisation and reporting alignment
Scope of Consultancy
Technical and financial consistency, from programme selection to periodic reporting.
The service is structured according to the project's maturity and the current conditions of the relevant programme or call.
01
Programme and Call MatchingCompany scale, project type, collaboration model, technology field, and call conditions are assessed together.
02
Technical Problem and Innovation AnalysisThe current technical level, alternative solutions, innovation elements, and R&D uncertainties are clarified.
03
Work Packages and TimelineActivities are sequenced by technical dependency; output, owner, duration, and success criteria are defined.
04
Budget and Resource PlanPersonnel, materials, services, travel, and other costs are linked to technical activities.
05
Application and Evaluation PreparationPRODIS entry, supporting documents, referee interview, presentation, and technical explanation preparation are supported.
06
Periodic Reporting and RevisionRealised activity, cost, technical output, and plan changes are reported consistently with the project file.
Evaluation Lenses
We test the project file from four distinct evaluation angles.
A strong technical narrative alone is not enough — method, capacity, budget, and output must be in balance.
01
Technical — R&D qualificationIs the technical uncertainty, innovation element, method, and difference from existing solutions explained clearly?
02
Implementation — FeasibilityAre the team, infrastructure, work packages, timeline, and external resources sufficient to reach the targeted outcome?
03
Financial — Budget justificationIs every cost linked to a technical activity, proportionate, explainable, and consistent with the project duration?
04
Impact — Output and valueIs the technical gain, competitive difference, and commercialisation direction at project completion made concrete?
Project Architecture
A good TEYDEB project is not a product pitch — it's a logical account of the technical problem to be solved.
The evaluator wants to understand not how well the product will sell, but why the current technical level falls short, what uncertainties exist, and by which method the company will reduce them.
Toygun Consultancy translates the company's technical knowledge into project language without inflated claims — linking the data from the technical team to the literature, existing solutions, work packages, and verification criteria.
Core principle: Every activity must be linked to a technical question, every work package to a concrete output, and every output to a measurable success criterion.
Project backbone
Problem: Why is the current solution not sufficient?
Uncertainty: What is the technical question whose outcome isn't known in advance?
Method: Which experimental or engineering approach will reduce the uncertainty?
Output: What will be produced or verified at the end of the project?
Success Criterion: How will the outcome's success be measured?
Working Process
We turn knowledge from the technical team into a project system that holds up through application and implementation.
01
Preliminary AssessmentThe programme, project qualification, and readiness level are reviewed.
02
Technical ArchitectureThe problem, uncertainty, method, and innovation are structured.
03
Work Plan and BudgetActivity, output, duration, resources, and cost are matched.
04
Application and EvaluationThe file, system entry, and technical interview are carried out.
05
Implementation and ReportingRealisations and changes are managed on record.
Critical Mistakes
Build high consistency, not high claims.
Mistaking product features for R&D qualification
A new or improved product doesn't build a strong R&D case unless the technical uncertainty and systematic method are explained.
Turning work packages into a task list
Instead of disconnected tasks, packages should answer technical questions and produce concrete outputs.
Letting the application and periodic realisation drift apart
Failing to manage changes as the project progresses makes reports retroactive and hard to defend.
Frequently Asked Questions
Common questions about the TUBITAK TEYDEB process
What does a good TUBITAK TEYDEB project look like?
It should be a logical account of the technical problem to be solved, not a product pitch. The evaluator wants to see why the current technical level falls short and by which method that uncertainty will be reduced — not how marketable the product is.
What stages does your consultancy scope cover?
It covers programme and call matching, technical problem and innovation analysis, work packages and timeline, budget and resource plan, application and evaluation preparation, and the full periodic reporting and revision process.
What is your core principle when preparing a project application?
We link every activity to a technical question, every work package to a concrete output, and every output to a measurable success criterion — relating data from the technical team to the literature and verification criteria rather than producing inflated claims.
From which angles is the project file evaluated?
We test the file through four evaluation lenses. A strong technical narrative alone is not enough — method, capacity, budget, and output must be balanced.
TEYDEB Project Preliminary Assessment
Let's clarify your project's R&D qualification and the right programme direction together.
Share the technical problem, targeted output, current team, and project stage. Let's identify which project components need development before you apply.