What we do

Turn shared challenges into testable work.

Our intended model brings together focused digital products, thoughtful partnerships and evidence-led learning. The scope is still being established.

Four intended capability areas

Build, enable, connect and improve.

These pathways are CMS-managed proposals rather than a fixed service catalogue. Scope, team, timing and delivery commitments would be agreed before work begins.

proposed

Build impact products

  • Purpose-led product teams
  • Sustainability initiatives
  • Potential delivery partners

Explore practical digital products around clearly defined environmental or social problems.

The proposed work can combine discovery, interface design, technical prototyping and proportionate testing. Technology is selected only when it offers useful value, with product maturity and limitations stated clearly.

Scope, boundaries and expected outputs

Problem addressed

A promising idea may need a focused, testable product response before anyone can responsibly commit to scale.

What may be provided

  • Problem framing and product discovery
  • Accessible experience and service design
  • Prototype engineering and responsible testing

What is not included

  • A guaranteed launch, adoption level or impact outcome
  • Technology chosen solely because it is fashionable
  • Unreviewed handling of sensitive or production data

Intended process

Understand the need, agree the risk and learning questions, build the smallest useful response, then test and decide what follows.

Expected outputs

  • A defined problem and intended user group
  • A concept or working prototype at an agreed maturity
  • A decision record covering evidence, risk and next steps

Availability and model

Proposed only. Team capacity, eligibility, timing, fees and any subsidised component must be agreed before an engagement is offered.

Evidence: No completed engagement evidence is published for this proposed area.

Discuss this pathway

proposed

Enable eco-conscious enterprises

  • Eco-conscious makers
  • Small sellers
  • Early-stage responsible enterprises

Explore suitable technology, design, learning and digital-operation support for makers and small sellers.

The intended pathway starts with how an enterprise actually works and what capacity it has. Any support should fit that reality, respect the maker's agency and avoid implying environmental certification.

Scope, boundaries and expected outputs

Problem addressed

Small enterprises may face fragmented tools, limited digital capacity and difficult routes to customers without needing an oversized platform.

What may be provided

  • Digital-operation and user-journey review
  • Appropriate design or technology support
  • Learning and market-access experiments where approved

What is not included

  • Automatic grants, free services or guaranteed sales
  • Independent certification of a seller or product
  • Claims that handmade goods are automatically better for the environment

Intended process

Understand the business and its constraints, identify a priority gap, agree a proportionate support plan, then review practical usefulness.

Expected outputs

  • A prioritised operational or growth need
  • An agreed tool, workflow or capability response
  • Documented learning and handover information

Availability and model

Proposed only. Selection, capacity, commercial or subsidised terms, and environmental-claims standards are not yet published.

Evidence: No completed engagement evidence is published for this proposed area.

Discuss this pathway

proposed

Develop partnerships and ecosystems

  • Civil-society and community organisations
  • Companies and institutions
  • Funders and public bodies

Bring relevant organisations and communities together around a specific, shared challenge.

The intended role is to help clarify the need, participating roles, decision rights, safeguards and delivery path. No organisation is represented as a partner until the relationship is approved and documented.

Scope, boundaries and expected outputs

Problem addressed

Useful initiatives can stall when people, resources, responsibilities and evidence requirements remain disconnected.

What may be provided

  • Collaborative discovery and programme framing
  • Role, governance and delivery-path design
  • Shared learning and reporting structures

What is not included

  • A partnership created by submitting an enquiry
  • Unapproved affiliation, endorsement or logo use
  • Funding or delivery commitments before written agreement

Intended process

Frame the shared need, conduct appropriate due diligence, co-design roles and safeguards, then agree delivery and review points in writing.

Expected outputs

  • A shared problem and participant map
  • Clear roles, safeguards and decision points
  • A proposed delivery and learning framework

Availability and model

Proposed only. Every collaboration requires capacity review, due diligence and separate written terms; no active partner list is published.

Evidence: No completed engagement evidence is published for this proposed area.

Discuss this pathway

proposed

Measure and strengthen impact

  • Programme and product teams
  • Mission-led organisations
  • Potential evidence partners

Define practical indicators, collect proportionate evidence, disclose limitations and learn from results.

The intended approach separates activities, outputs, outcomes and long-term ambitions. Any method must fit the decision being made, protect participants and avoid turning an estimate or product signal into an environmental or social result.

Scope, boundaries and expected outputs

Problem addressed

Broad impact language can hide weak definitions, missing baselines and evidence that cannot support the conclusion being claimed.

What may be provided

  • Theory-of-change and indicator framing
  • Evidence, boundary and limitation design
  • Learning reviews and responsible reporting support

What is not included

  • Audit, certification or regulatory assurance unless separately qualified
  • Invented baselines, outcome totals or causal claims
  • Official SDG, 3ZERO, EPR or government endorsement

Intended process

Define the decision and change pathway, specify evidence and owners, collect only appropriate data, then review findings and limitations together.

Expected outputs

  • A documented theory of change or measurement question
  • Indicators with definitions, periods, scope, sources and owners
  • A learning record that distinguishes findings from uncertainty

Availability and model

Proposed only. Suitable expertise, independence, scope and commercial terms must be agreed; this is not presented as an assurance service.

Evidence: No completed engagement evidence is published for this proposed area.

Discuss this pathway

A practical cycle

Small enough to learn. Clear enough to question.

This is the intended development rhythm. A project may stop at any stage if the need, safety case or value is not strong enough.

  1. Listen

    Understand the context, constraints and people affected before settling on a solution.

  2. Frame

    Agree the problem, intended outcome, risks and what would count as useful evidence.

  3. Prototype

    Create the smallest responsible version that can answer an important question.

  4. Test

    Observe real use, seek criticism and check accessibility, privacy and unintended effects.

  5. Decide

    Improve, pause, retire or scale based on evidence—not momentum alone.

Decision guardrails

What every piece of work should make clear.

  • The needWhose problem is being addressed, and how do we know it matters?
  • The roleWhat can a digital product or partnership reasonably contribute?
  • The powerWho can decide, participate, challenge and leave?
  • The riskWhat could go wrong, and who may carry that cost?
  • The evidenceWhat will be measured, by whom, and with what limitations?
  • The endHow can the work be changed, handed over or retired responsibly?

Questions, answered

Frequently asked questions

Plain answers about where things stand and how to take part.

What kind of work is being considered?

The current direction includes venture development, collaborative programmes and focused product experiments. Each is described as proposed until scope, team, timing and delivery commitments have been agreed.

How will environmental or social impact be reported?

Claims should be specific, dated and connected to a documented source or method. Until evidence is approved, the website describes aims and approach without publishing impact totals, certifications or outcome promises.

Work with us

A useful collaboration starts with a clear question.

Share the challenge, who it affects and what a good next step might look like.