Boundary & Product Sprint
Climate Product Strategy & Scoping
Many climate and sustainability projects stall even when the problem is real. The buyer may be unclear, the data messy, the AI overpromised, or the team caught between product, service, and open source.
Common warning signs
Problems to resolve before building
The pattern we see across startups, research, consortia, and companies
Reports, datasets, and expert knowledge exist, but the real work still lives in Excel, email, and PDFs.
Fluent answers are not enough. You need evidence quality, uncertainty handling, and human review before you trust the output.
The climate problem is real, but it is unclear who has the budget, the pain, and the mandate to pay for a first pilot.
Founders want a scalable product, while first customers pull them toward customization and consulting. That tension is normal, but dangerous if unmanaged.
Useful code does not automatically become infrastructure. Adoption needs users, governance, docs, funding, and trust.
Strong research and stakeholder ambition, weak ownership of tools, interfaces, and life after the funding period.
Three commercial stages
Choose the right level of commitment
Start with the smallest engagement that can answer the next decision
1. Diagnostic Sprint
2 to 3 weeks. Define the use case, audit the available data, assess feasibility, and prepare a pilot backlog and budget range.
2. Pilot or Prototype
6 to 10 weeks. Test one workflow with real data, measure results, identify adoption risks, and decide whether production is justified.
3. Production or Partner Role
3 to 12 months. Build and operate the system, deliver a consortium work package, or provide governance, support, training, and evaluation.
How the Boundary & Product Sprint works
Step 1: Scoping call
In 60 minutes we map what you are trying to achieve, who the user and buyer are, what already exists, and what is unclear.
Step 2: Boundary mapping
We clarify product vs service, open vs proprietary, collaboration vs competition, and advisory vs build vs venture path.
Step 3: Pilot hypothesis
We define the smallest pilot or funded next step that would prove value, along with what should not be built yet.
Step 4: Recommended commercial path
We recommend a paid sprint, build, funding application, consortium role, partnership, investment route, or a decision to stop.
Relevant experience
What we bring
Climate domain, software delivery experience in our team and network, and a clear collaboration boundary
We connect research, open-source tooling, and stakeholders across sustainability AI, climate risk, and adaptation.
Our team and network bring decades of software, AI, UX, and product delivery experience. This includes work with Score4More, AdaptNow, and Actwyser.
Before we go deeper, we define whether we should advise, build, partner on infrastructure, join a consortium, co-sell, support a venture, or stay at arm's length.
We do not recommend large builds before use case, users, data, and adoption path are clear. The first step is usually a sprint, pilot, work package, or benchmark.
Sprint outputs
What you get
Typical outputs from the Boundary & Product Sprint
Collaboration vs competition map
Where we and other partners fit, and where boundaries must stay explicit.
Product vs service split
What should scale as product, what stays service or custom work.
Open-source vs proprietary boundary
What should be shared infrastructure and what should stay closed.
Buyer and user definition
Who has the problem, who controls the budget, and what they would pay for.
First pilot hypothesis
The smallest test that proves traction or adoption.
Recommended next commercial step
A sprint, pilot, funding path, consortium role, or partnership, with a clear reason for the recommendation.
Proven work types
Four ways clients currently work with us
Each route is backed by delivered client work or a formal consortium role
Sustainability AI Productization
For rating agencies, ESG data providers, and sustainability consultancies with methodology, analysts, and data that need scalable AI-assisted workflows.
Adaptation Product Sprint
For funded adaptation projects, climate resilience platforms, and municipal or company workflows that need a focused product sprint.
Pitch, Product & Funding Sprint
For climate ventures that need sharper customer profiles, use cases, value logic, positioning, and a fundable technical scope.
Consortium Work-Package Partner
For consortia that need ownership of productization, user research, technical delivery, open source, and adoption.
From problem to outcome
Core case studies
Evidence from company projects, applied research collaboration, and funded product work
Score4More needed a better way to measure whether its AI pipeline selected information that was useful, not merely relevant. We helped set up an applied research collaboration with University of Zurich researchers, including Tobias Schimanski. Professional sustainability analysts contributed real questions and labels, resulting in the UsefulBench dataset and working paper.
Adaptation product work delivered in sprints: UX and product development, market and platform design, and go-to-market and pricing support.
Pitch, product, and funding work: positioning, customer profiles, use cases, value logic, funding support, and a credible technical delivery path.
Packages by audience
Not sure which package fits?
Start from your situation, then book a scoping call if you still need help choosing
Building too much, too early, for a buyer who is not yet clear. Start with Boundary & Product, Discovery, or Venture Studio.
Real data problems, unclear owner, workflow, or build-vs-buy path. Start with Discovery or Benchmark.
Work with companies and domain stakeholders on credible datasets, benchmarks, publications, prototypes, and open tools.
Too many prototypes disappear. Start with Open Infrastructure Adoption.
Need a productization, tech, or adoption work-package partner.
Climate ventures can hide product, AI, or buyer risk. Start with Boundary & Product or Venture Studio assessment.
Need to know whether sustainability AI is reliable enough for real decisions.
Frequently Asked Questions
What is the Boundary & Product Sprint?
A short engagement to clarify product vs service, open vs proprietary, buyer vs user, collaboration lane, and the first pilot before large build or funding commitments.
How is this priced?
Pricing depends on scope and is agreed after the scoping call. We do not publish fixed package prices; we define the smallest useful next step together.
Do we have to work with you after the sprint?
No. A valid outcome is a clear recommendation that you build in-house, buy a vendor tool, fund a consortium role elsewhere, or stop.
How does this relate to your other consulting work?
ESG consulting, climate risk assessment, data analytics, AI development, and open-source implementation remain capability pages. Packages are the entry points when the next step is still unclear.
Can you name projects you have worked on?
We have applied this approach in work with Score4More, AdaptNow, and Actwyser across sustainability AI, adaptation, product strategy, and delivery.
Not sure which package fits?
Start with a 60-minute scoping call. We will clarify the problem, the lane, and the smallest useful next step.
We usually reply within a few working days to schedule.
Book a 60-minute scoping call
Tell us what is unclear. We will suggest the right package or tell you if we are not the right fit.