Open Infrastructure Adoption Sprint
Open Climate Infrastructure That Gets Adopted
Open-source climate tools often have strong technical value but weak adoption. They need onboarding, governance, integrations, trust, and a reason to become part of daily work.
Common barriers
What prevents adoption
Tools, datasets, models, and communities
A public repository exists, but onboarding, documentation, and a clear path for users do not.
Unclear who maintains the project, how decisions are made, or what happens when a maintainer leaves.
The tool works alone; it does not fit into institutional workflows, data lakes, or reporting stacks.
Open source is treated as free night work. There is no paid support, foundation path, or service layer.
Organizations want a tool deployed, but have not decided governance, ownership, or long-term maintenance.
How the Adoption Sprint works
Step 1: Map users and barriers
Who should use the tool, why they do not today, and what 'adopted' would mean.
Step 2: Governance and maintenance
Decision rights, contribution paths, security updates, and who pays for continuity.
Step 3: Integration and onboarding
Docs, training, APIs, and institutional fit.
Step 4: Funding and support logic
We define what stays free, what is shared, and what can be supported through paid services or grants. Implementation can follow.
Relevant experience
What we bring
Adoption planning and practical implementation
We define user and contributor paths, maintenance models, and the institutional requirements for trust.
Setup, customization, training, and integration for climate risk, ESG, and related open tools on infrastructure you control.
We work with and around open climate tooling (including the Climate Risk Intel Tool Hub) and can help you choose and deploy what fits.
Our team and network bring long software architecture and product experience, applied to open and climate contexts including work connected to Score4More, AdaptNow, and Actwyser where relevant.
Sprint outputs
What you get
Typical outputs from the Open Infrastructure Adoption Sprint
Adoption map
Target users, barriers, and success criteria.
User and contributor path
How people find, trust, and contribute to the tool.
Governance and maintenance model
Roles, processes, and continuity plan.
Integration roadmap
How the tool connects to real workflows and systems.
Funding and support logic
Sustainable models around the commons.
Partner and ecosystem map
Who else needs to be involved for adoption.
Frequently Asked Questions
Is this only strategy, or do you also implement?
Both. The sprint clarifies adoption and governance. When implementation is the right next step, we can set up, customize, train, and integrate open tools on your infrastructure.
How is this priced?
Scope and price are agreed after a 60-minute scoping call. We do not publish fixed package prices or fixed delivery weeks without understanding your stack and constraints.
Do you only work on tools you built?
No. We help with third-party open climate and sustainability tools as well as projects in our ecosystem, such as Climate Risk Intel and related open datasets.
Who is this for?
Open-source climate projects, data platforms, funders, NGOs, public-sector infrastructure projects, research communities, and organizations deploying open tools internally.
How does this relate to applied research collaboration?
Applied research collaboration starts from a shared research question that may lead to a dataset, publication, benchmark, or first tool. This package starts from existing open assets that need adoption and sustainability. See also the Boundary & Product Sprint if the lane is unclear.
Make open climate tools adoptable
Book a 60-minute scoping call to define adoption, governance, or implementation as the next step.
We usually reply within a few working days to schedule.
Book a 60-minute scoping call
Tell us about the tool, dataset, or community. We will help clarify adoption barriers and a concrete collaboration path.