The Roles We Take in a Consortium
We rarely take just one role. Most consortia need several of these together.
Business Perspective for Sustainable Outcomes
We bring a business perspective to the consortium from the start, working toward sustainable, long-term models for what the project produces, so the outcomes have a path to use and maintenance beyond the funding period, not just a final report.
Software Architecture Across Work Packages
We design the software architecture that connects different work packages on the data and interaction layer, so components built by different partners actually integrate into a coherent system rather than staying siloed.
Product and User Research
We bring product and user research into the project so the people who are meant to use what's built are genuinely at the center of it, which is what makes the difference between a prototype that gets adopted and one that doesn't.
Open Source Strategy
Where a consortium plans to release code or data openly, we help define the open source strategy: licensing, governance, and how the software architecture supports that choice rather than working against it.
Planning and Building Software
Beyond architecture and strategy, we do the concrete work: planning the technical roadmap and building the software itself as part of the consortium's delivery.
Training and Implementing AI/ML Applications
We train project partners and their teams on AI and machine learning methods relevant to the project, and implement the specific AI/ML applications the consortium's work packages call for.
Fundraising and Consortia
We help put a consortium together before a proposal is even written: finding complementary partners, shaping the work packages around who brings what, and supporting the fundraising process itself.
Horizon Europe Consortium Partnership
Horizon Europe is one of the best ways we know to collaborate at scale: it brings together researchers, universities, NGOs, public administrations, and businesses around a shared problem, with the funding and structure to actually build something rather than just publish about it. That combination of disciplines and perspectives is hard to assemble any other way.
We’ve built relationships with researchers, NGOs, and organizations across this landscape, and we’re growing our track record of participating in and supporting these kinds of collaborations. See our partners for who we already work with.
We partner in Horizon Europe (and other EU-funded) research consortia, typically taking on more than one role at once, depending on what a given consortium already has covered and what it’s missing.
What We Bring to a Large Consortium
- We build sustainable software. Not a research prototype that gets abandoned at the final review, but software built to keep running.
- We make sure it gets used. Through product and user research that puts adoption at the center of the design process, not bolted on afterward.
- We give it a long-term future. By building the business model and maintenance path in from day one, not just the deliverable that satisfies the grant agreement.
- We connect your work packages. Acting as the software architecture layer on the data and interaction layer, so what different partners build integrates instead of staying siloed.
- We bring cutting-edge technology. We screen, evaluate, and implement current AI/ML methods and open source tools relevant to the project.
Whether a project’s results survive past the funding period usually depends less on the technology alone than on whether business model, users, and architecture were designed together from the start. That is the combination we typically bring into a consortium: a long-term view of what gets built, with the technical work to make it hold together.
Roles in Detail
- Business perspective for sustainable long-term models. We work toward outcomes that have a realistic path to continued use, maintenance, or a business model after the project ends, not just a final deliverable report.
- Software architecture across work packages. We design how the data and interaction layers connect the pieces different partners are building, so the result integrates rather than staying fragmented.
- Product and user research. We keep the people who are meant to use the outcome at the center of the design process, since that’s what drives real adoption.
- Open source strategy. Where the consortium intends to release software or data openly, we help shape the licensing, governance, and architecture decisions that make that actually work.
- Planning and building software. We contribute directly to the technical roadmap and to writing the software itself.
- Training and implementing AI/ML applications. We train partner teams on relevant AI and machine learning methods, and implement the specific applications the project’s work packages need.
- Fundraising and consortia. We help put a consortium together before a proposal exists: finding complementary partners, shaping work packages around who brings what, and supporting the fundraising process.
How We Work With a Consortium
We’re happy to join a consortium at proposal stage, helping shape the work packages around the roles above, or join an already-funded project that’s realized it needs one or more of these capabilities. Get in touch early if you’re assembling a consortium and want to talk through where we’d genuinely add value, rather than filling a generic “technical partner” slot.
See our overview of Horizon Europe calls with a September 2026 deadline for specific topics where we think we’re a genuine fit.
We're happy to talk early, before a proposal is finalized, about where we'd genuinely add value.
Building a Horizon Europe Consortium?
Tell us about your call, your consortium so far, and which of these roles you're missing.