• Deep-Tech Ventures Program

    Application Form -Cohort 2
  • Before You Start
    What to Prepare

    Set aside roughly 30–40 minutes. You can save and resume your application, but we recommend completing it in one sitting — so please have your information and documents ready before you begin.

    You’ll be asked about
    ✓Your technology, category, and TRL
    ✓The problem, your solution, and competitive advantage
    ✓IP status and proof of concept
    ✓Team members’ details — name, email, mobile, and position in the venture
    ✓Market opportunity and any early traction
    ✓Commercialization plan and budget
    Have ready to upload
    ✓Pitch deck (PDF)
    ✓Proof-of-Concept report or supporting evidence
    ✓CVs of core team members — include each member’s LinkedIn profile URL with a clear username
    ✓Patent / IP documentation (if applicable)
    ✓Letters of intent or pilot agreements (if any)
    ✓Any other supporting documents
    After submission: shortlisted teams will be asked to share a short 3-minute video of the team and the project.

  • Program Eligibility
    Before You Begin

    The Deep-Tech Ventures Program is designed for founders, researchers, innovators, and early-stage deep-tech startups seeking to transform validated technologies into commercially deployable products and scalable ventures.

    To be eligible, applicants must:

    ✓Have demonstrated a Proof of Concept (PoC) and achieved a Technology Readiness Level (TRL) of 3 or higher.
    ✓Be developing deep-tech or hard-tech innovation based on scientific research, engineering innovation, proprietary technology, or defensible intellectual property.
    ✓Be able to commit to the program duration if selected.
    Application deadline 31 July 2026
  • To continue please confirm:

  • Main Applicant Information

  • Do you have an affiliation with KFUPM?
  • Position

  • Technology Information

    Startup/ project details
  • Which category best describes your technology?
  • Current Technology Readiness Level (TRL) **

  • ** Associate your technology with Technology Readiness Level(TRL) for more info read the section below

    • What is Technology Readiness Level (TRL)? 
    • .dvp Deep-Tech Ventures Program TRL REFERENCE GUIDE
      Overview

      What Technology Readiness Levels measure

       

      Technology Readiness Levels (TRL) are a nine-point scale for grading the maturity of a technology, from the first observation of basic scientific principles through to a system proven in real operations. Each level carries a defined exit criterion that must be evidenced before a technology advances to the next. The scale runs in parallel for hardware and software, with a distinct description of what readiness looks like in each.

      Discovery → Development → Deployment  ·  lower TRL = earlier-stage, higher risk  ·  higher TRL = closer to market
      1
      2
      3
      4
      5
      6
      7
      8
      9
      DiscoveryTRL 1-2
      Discovery / DevelopmentTRL 3
      DevelopmentTRL 4-7
      DeploymentTRL 8-9
      For each level below, Hardware and Software describe what readiness looks like for each type of technology, and Exit criteria is the evidence needed before moving to the next level. Find the level that best matches your technology today.
      DiscoveryTRL 1-2
      1Basic principles observed and reported
      Hardware
      Scientific knowledge generated underpinning hardware technology concepts / applications.
      Software
      Scientific knowledge generated underpinning basic properties of software architecture and mathematical formulation.
      Exit criteria
      Peer-reviewed publication of research underlying the proposed concept / application.
      2Technology concept and / or application formulated
      Hardware
      Invention begins. Practical application is identified but is speculative; no experimental proof or detailed analysis is available to support the conjecture.
      Software
      Practical application is identified but speculative; no experimental proof or detailed analysis available. Basic properties of algorithms, representations and concepts defined; basic principles coded; experiments performed with synthetic data.
      Exit criteria
      Documented description of the application / concept that addresses feasibility and benefit, or patents.
      Discovery / DevelopmentTRL 3
      3Analytical and experimental critical function and / or characteristic proof of concept
      Hardware
      Analytical studies place the technology in an appropriate context, and laboratory demonstrations, modeling and simulation validate analytical predictions.
      Software
      Development of limited functionality to validate critical properties and predictions using non-integrated software components.
      Exit criteria
      Documented analytical / experimental results validating predictions of key parameters.
      DevelopmentTRL 4-7
      4Component validation in a laboratory environment
      Hardware
      A low-fidelity system / component is built and operated to demonstrate basic functionality and critical test environments; associated performance predictions are defined relative to the final operating environment.
      Software
      Key, functionally critical software components are integrated and functionally validated to establish interoperability and begin architecture development. Relevant environments defined and performance in this environment predicted.
      Exit criteria
      Feasibility documented; test performance demonstrating agreement with analytical predictions. Documented definition of the relevant environment.
      5Component validation in a relevant environment
      Hardware
      A medium-fidelity system / component is built and operated to demonstrate overall performance in a simulated operational environment with realistic support elements, demonstrating overall performance in critical areas. Performance predictions are made for subsequent development phases.
      Software
      End-to-end software elements implemented and interfaced with existing systems / simulations conforming to target environment. End-to-end software system tested in relevant environment, meeting predicted performance. Operational environment performance predicted; prototype implementations developed.
      Exit criteria
      Feasibility documented; test performance demonstrating agreement with analytical predictions. Documented definition of scaling requirements.
      6Sub-system model or prototype demonstration in an operational environment
      Hardware
      A system / component prototype that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate operations under critical environmental conditions.
      Software
      Prototype implementations of the software demonstrated on full-scale realistic problems. Partially integrated with existing hardware / software systems; limited documentation available. Engineering feasibility fully demonstrated.
      Exit criteria
      Model or prototype documented; test performance demonstrating agreement with analytical predictions.
      7System prototype demonstration in an operational environment
      Hardware
      An engineering unit that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate performance in the actual operational environment and platform.
      Software
      Prototype software exists with all key functionality available for demonstration and test. Well-integrated with operational hardware / software systems demonstrating operational feasibility; most software bugs removed; limited documentation available.
      Exit criteria
      MVP documented; test performance demonstrating agreement with analytical predictions.
      DeploymentTRL 8-9
      8Actual system completed and qualified through test and demonstration
      Hardware
      The final product in its final configuration is successfully demonstrated through test and analysis for its intended operational environment and platform.
      Software
      All software thoroughly debugged and fully integrated with all operational hardware and software systems. All user, training and maintenance documentation completed. All functionality successfully demonstrated in simulated operational scenarios; Verification and Validation (V&V) completed.
      Exit criteria
      Product validation documented; test and performance verifying analytical predictions.
      9Actual system proven through successful operations
      Hardware
      The final product is successfully operated in an actual environment.
      Software
      All software thoroughly debugged and fully integrated with all operational hardware / software systems. All documentation completed. System has been successfully operated in the operational environment.
      Exit criteria
      Mass production documented and operational results.
      Source: Adapted from the Baseload Applied Grant (BAG) Guidelines, Table 7 - Technology Readiness Level (TRL) definitions.
    •  
    • 0/300
    • 0/300
    • 0/300
    • Does your venture have any of the following?
    • ! Important

      Applicants must own, or have the legal right to commercialize, the core intellectual property underlying the proposed venture. Any third-party or institution-owned IP must be disclosed and clearly separated from the IP that the team owns or intends to own and commercialize.

    • Browse Files
      Drag and drop files here
      Choose a file
      Cancelof
    • 0/300
    • Browse Files
      Drag and drop files here
      Choose a file
      Cancelof

  • Team Composition

    Include information of the team members who will be part of the startup (including the main applicant). This section will be used to assess the Team's strengths and weaknesses. Key factors of assessment will include Team composition, Technical Experience Alignment with proposed project, Entrepreneurial Experience, Emotional Intelligence.
  • Does your team have:
  • Browse Files
    Drag and drop files here
    Choose a file
    Cancelof
  • 0/300
  • 0/300

  • Market Opportunity

  • 0/300
  • Have you engaged with potential customers?
  • Have you received any of the following?
  • Browse Files
    Drag and drop files here
    Choose a file
    Cancelof

  • Commercialization Readiness

  • 0/150
  • 0/300
  • 0/300

  • Supporting Documents Upload

  • Browse Files
    Drag and drop files here
    Choose a file
    Cancelof
  • Browse Files
    Drag and drop files here
    Choose a file
    Cancelof
  • i Please note

    If your team is shortlisted, you will be required to share a short 3-minute video of the team and the project.

  • Program Terms & Conditions

  • Program Agreement
    Terms & Conditions

    By submitting this application, I confirm that:

    ✓The information provided is accurate and complete.
    ✓I understand the stated program funding amount is an investment combining both monetary and in-kind services, provided in exchange for equity in the venture. If selected, DTV Ventures will require applicants to sign a founder collaboration agreement to define the scope of support and equity-claim terms.
    ✓Participants must actively engage in all required sessions, workshops, reviews, and deliverables throughout the program period (a total of 14 weeks).
    ✓All financial resources must be used strictly for approved business and technical development purposes.
    ✓Any IP developed during the program will be subject to the relevant DTVC / KFUPM IP policies.
    ✓Participants must maintain confidentiality regarding proprietary materials, strategies, and information shared during the program. Breach of confidentiality will lead to immediate dismissal from the program and may result in legal action.
    ✓DTV Ventures reserves the right to remove any participant or team that fails to meet program requirements, violates any of the stated terms, or exhibits unethical behavior.
    ✓Participants consent to the use of their name, project title, photos, and video materials for marketing and promotional purposes by KFUPM, DTV Ventures, and affiliated entities.

  • Code of Conduct

  • Participant Commitment
    Code of Conduct

    All participants are expected to uphold the highest standards of professionalism and integrity during their time in the program, in compliance with KFUPM and DTVC policies. Violations of the code of conduct may result in disciplinary action, including termination from the program.

    The code of conduct includes, but is not limited to:

    ✓Treating all mentors, peers, organizers, and partners with respect. Discrimination, harassment, or abusive behavior will not be tolerated under any circumstances.
    ✓Committing to honesty in all communications and dealings, including accurate reporting of project progress and financial usage.
    ✓Working in a positive and respectful manner. Participants must not share any private or sensitive information without permission and should help create a trusted environment for everyone.
    ✓Adhering to all DTVC policies, applicable laws, and any additional program-specific guidelines provided during the course of the program.
  • Should be Empty: