yeshcube opens a call for Development Partners to join Allies
Allies is yeshcube’s collaboration system for connecting projects, scientific knowledge, technological capabilities and transfer settings. On 9 March 2026 the hub opened a call aimed at startups, applied research teams and social intervention models interested in joining as Development Partners.
The role brings in external projects looking for a framework to validate their hypotheses, document their progress and prepare their application in real settings. The call accepts initiatives at different stages, from concepts and prototypes to products already operating on the market.
Assessment will consider how the project fits yeshcube’s mission, its capacity to generate verifiable evidence and the possibility of establishing a collaboration with defined objectives, responsibilities and contributions.
The Development Partner role
Development Partners are external projects that join Allies to work on their research, validation, development or transfer within a shared framework.
The call is aimed at initiatives related to health, education, social inclusion, healthy aging, accessibility, wellbeing and other dimensions of human development.
Stage of maturity forms part of the analysis of each application. Projects may start from a hypothesis, hold a prototype, be preparing a pilot or run a solution already in operation.
Each proposal needs to identify the need it addresses, the population or setting it is aimed at, its current stage and the questions it needs to resolve. It also needs to set out which capabilities it can contribute to the ecosystem.
The Allies system
Allies brings together different collaboration roles associated with applied research and technology transfer.
Scientific Partners can contribute to methodological design, protocol review, independent assessment and interpretation of results.
Transfer Partners contribute capabilities in manufacturing, integration, implementation, distribution or deployment in real settings.
Backing Partners can take part through funding, business support and connection with investment networks aligned with validation processes.
Development Partners bring in projects that need to combine these capabilities to move from their current situation toward a more mature stage.
The involvement of each organization depends on the requirements of the initiative, the availability of partners and the agreements established for the project.
Ethical and scientific review
Selected projects can use the ERL scale to document the maturity of their evidence.
The framework distinguishes an initial hypothesis, a proof of concept, a controlled pilot, an initial transfer and the later stages of scaling and impact.
At the initial levels, work may center on formulating hypotheses, defining variables, preparing a prototype or designing a proof of concept. Later stages may include pilots, analysis of results, assessment in operational settings and preparation for transfer.
Ethical review examines the purpose of the project, the target population, potential risks, data handling and limits of use.
Scientific review examines the relationship between a project’s claims, the method applied and the available evidence. The aim is for every conclusion to correspond to the data obtained and to the actual stage of development.
Access to capabilities and alliances
Joining as a Development Partner connects a project with the capabilities available within Allies.
Those capabilities may include methodological support, scientific review, ethical advice, intellectual property, regulation, cybersecurity, technology architecture, product design, industrialisation, implementation and funding.
The specific combination is defined for each initiative. A project may need to prepare its first protocol, reach a validation setting, review its architecture or find a partner able to manufacture and distribute a solution that has already been assessed.
Access to resources and infrastructure depends on their relevance to the project, on availability and on the conditions agreed between the parties.
Agreements need to identify the contributions, the parties responsible, the timescales and the expected results of each collaboration.
Support for transfer
Transfer turns a solution with sufficient evidence into an application available to its intended recipients within a real setting.
Support may address the implementation model, technical requirements, documentation, training, maintenance, regulation and monitoring criteria.
Each project needs to determine which elements can be adapted during implementation and which need to be maintained to preserve the purpose and the conditions that were assessed.
Transfer may require the involvement of industrial partners, implementing organizations, public administrations, social organizations or distribution channels.
Allies makes it possible to identify these requirements and to facilitate connections where a project and the capabilities of the partners correspond.
Principles of collaboration
Relationships within Allies are structured on reciprocity, traceability and independence.
Reciprocity
Each party contributes knowledge, resources, technology, funding, access to participants or implementation capacity. Contributions and their counterparts need to be defined before work begins.
Traceability
Each collaboration establishes objectives, indicators, responsibilities and monitoring mechanisms. Decisions are documented and related to the information available at each stage.
Independence
Each organization keeps its autonomy, identity and decision-making capacity. Intellectual property, terms of exploitation and any exclusivity arrangement are governed expressly where applicable.
Joining process
Joining begins through the form available on the Allies page.
The Assessment Committee reviews the project’s alignment, its stage of development, its capacity to produce evidence and its potential contribution to the ecosystem.
Where a workable collaboration framework is identified, the parties define the scope, objectives, contributions, responsibilities and legal conditions.
Operational integration may begin through a bounded activity, a proof of concept, a validation protocol or a pilot.
Progress toward further stages depends on the results obtained and on the decisions agreed between the participating organizations.
Projects the call is aimed at
The call is open to technological, scientific and social projects with a defined application addressing human needs.
Profiles that may submit an application include:
- Startups developing technology products or services.
- Applied research teams with a solution in development.
- Organizations designing social intervention models.
- Projects that need to validate a hypothesis in real settings.
- Solutions preparing their transfer or scaling.
- Initiatives requiring scientific, industrial, legal or implementation capabilities.
An application needs to describe the project precisely, along with the problem addressed, the target population, the current stage, the collaboration required and the capabilities it can contribute.
Opening of the call
The call widens the entry of external projects into Allies as Development Partners.
Applications will be assessed individually to determine fit, the capabilities required and the possible framework for collaboration.
Submitting an application begins through the form available on the program page.
