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 work packages on the data and interaction layer, so components built by different partners integrate into a coherent system.
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
Many climate consortia are strong on research and stakeholder ambition, but weaker on productization, technical integration, user workflows, and post-project adoption. What matters is a clear role in work packages, tasks, deliverables, person-months, and budget.
Horizon Europe brings researchers, universities, NGOs, public administrations, and businesses together around a shared problem, with funding and a structure for delivery.
We’ve built relationships with researchers, NGOs, and organizations in this field. See our partners for current collaborations. Our team and network also bring long software and product delivery experience.
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 apply current technology carefully. We screen, evaluate, and implement AI/ML methods and open-source tools relevant to the project, with explicit limits and evaluation criteria.
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.
Roles in Detail
- Business perspective for sustainable long-term models. Outcomes with a realistic path to continued use or a business model after the project ends.
- Software architecture across work packages. How data and interaction layers connect what different partners build.
- Product and user research. Keep intended users at the center of design.
- Open source strategy. Licensing, governance, and adoption for open releases.
- Planning and building software. Technical roadmap and implementation.
- Training and implementing AI/ML applications. Methods training and project-specific applications.
- Fundraising and consortia. Putting a consortium together before a proposal exists: partners, work packages, and fundraising support.
If the overall collaboration lane is still unclear (advisor, builder, competitor boundary), start with the Boundary & Product Sprint.
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.
Common delivery gaps
Delivery gaps to address
The product question that funding language often skips
Research and dissemination are covered; interfaces, user workflows, and adoption are not.
Deliverables satisfy the grant agreement but have no path to maintenance or use afterward.
Partners build components that never integrate on the data or interaction layer.
Code is promised as open; licensing, community, and long-term stewardship are unclear.
Scoping outputs
What you get from a work-package scoping conversation
Typical outputs when we join as productization / technical / adoption partner
Work-package role definition
What we own vs what stays with research partners.
Task descriptions
Concrete tasks aligned to call language and delivery.
Deliverables and milestones
What ships, when, and how adoption is measured.
Effort and budget assumptions
Person-months and budget logic for a proposal or amendment, agreed after scoping rather than published as fixed prices.
Architecture and implementation plan
How components connect and stay maintainable.
Adoption and sustainability plan
Life after the funding period.
We are happy to talk early, before a proposal is finalized, about where we would genuinely add value.
Book a 60-minute work-package scoping call
Tell us about your call, your consortium so far, and which productization, technical, or adoption role you are missing.