ShopRevenue / Partnerships

REVENUE · PARTNERSHIPS

Build together.
Measure what works.

A structured pathway for technical partners, suppliers, educators, communities and project teams to move from a shared problem to a bounded pilot and a documented next step.

Explore partnership lanesSee Lab workReview licensing

Partnerships are explored case by case. This page is not a grant, investment offer, certification, franchise or guarantee of commercial results. Each party remains responsible for its own legal, technical, safety, financial and regulatory decisions.

THE PARTNERSHIP MODEL

A good partner makes the system stronger.

We look for relationships that add capability, evidence, access or implementation capacity—not just logos. The work should leave behind a clearer result than it started with.

Sustainable Oasis infrastructure and partnership pathway

What a responsible partnership must answer.

  • 01Shared problem — what real need are we solving?
  • 02Contribution — what does each party bring?
  • 03Scope — what is inside the pilot and what is not?
  • 04Evidence — what will be measured, and who owns the record?
  • 05Responsibility — who handles safety, compliance, service and decisions?
  • 06Next step — what happens if the result is useful—or not?

A partnership is a working relationship, not an endorsement. Shared branding never replaces evidence, legal review or local responsibility.

PARTNERSHIP PATHWAY

From shared problem to repeatable proof.

Question → Baseline → Prototype → Measure → Document. Then decide whether to expand, revise, pause or stop.

01 · AlignName the problem and desired outcome.
02 · BaselineRecord starting conditions and constraints.
03 · PilotRun a bounded, time-limited test.
04 · MeasureCollect evidence, costs and limits.
05 · ReviewShare findings and decide honestly.
06 · ScaleExpand only when the record supports it.

Partnership boundary: A pilot can produce evidence and learning; it cannot promise performance, certification or market success in advance.

PARTNERSHIP LANES

Bring the capability the next Oasis needs.

These lanes describe the kinds of collaboration we can scope. They are invitations to a conversation, not automatic approvals or purchasing commitments.

Technical energy partner working on resilient power systems
PARTNERSHIP LANE

Technical and product partners

Bring components, engineering, service or field expertise for energy, water, food, shelter and automation systems.

Discuss technical partnership
Sustainable Oasis pilot kit and demonstration site
PARTNERSHIP LANE

Pilot and demonstration sites

Host a bounded field trial where conditions, installation choices, costs and results can be documented.

Discuss a pilot site
Sustainable Oasis living lab and education partnership
PARTNERSHIP LANE

Community and education partners

Connect schools, communities, makers and educators to practical experiments, workshops and shared learning.

Discuss education partnership
Sustainable Oasis workshop and implementation team
PARTNERSHIP LANE

Suppliers and implementation teams

Coordinate procurement, installation, repair and local service without hiding who is responsible for the work.

Discuss implementation
Sustainable Oasis energy measurement and research
PARTNERSHIP LANE

Research and measurement partners

Design stronger baselines, tests, data collection and reporting for prototypes that need credible evidence.

Discuss research partnership
Sustainable Oasis resilience and strategic partner pathway
PARTNERSHIP LANE

Strategic ecosystem partners

Connect financing, logistics, land, distribution or institutional capacity to a documented Sustainable Oasis pathway.

Discuss ecosystem partnership

We do not publish partner logos, performance claims or case studies until permission, scope and evidence are documented.

PARTNERSHIP STANDARD

Value is shared. Accountability is named.

We prefer small, testable commitments that protect both sides and create useful evidence.

01 · Shared value

Clear reason both parties benefit

The contribution and expected value for each party are stated before work begins.

02 · Bounded scope

Deliverables and exclusions visible

The pilot, timeline, milestones, dependencies and exclusions are written down.

03 · Evidence plan

Metrics and owner named

Baseline, method, measures, data access and the evidence owner are agreed.

04 · Safety & compliance

Local duties respected

Permits, code, professional duties, accessibility and responsible service remain visible.

05 · Transparent economics

Costs and conflicts disclosed

Costs, in-kind support, revenue expectations and conflicts are disclosed honestly.

06 · Review & exit

Pause, revise or stop cleanly

The parties can review evidence, correct course, publish, pause or stop without pretending success.

PartnerWho is contributing?
ContributionWhat capability is added?
Pilot scopeWhat is in and out?
Timeline & milestonesWhen will work happen?
Evidence ownerWho keeps the record?
Safety & complianceWho reviews deployment?
Economics & conflictsWhat is disclosed?
Review & next stepHow is the decision made?

COMMERCIAL BOUNDARIES

A partnership is not proof.

Collaboration can create access, learning and evidence; it does not automatically create endorsement or performance claims.

PARTNERSHIP

Working relationship

Parties cooperate under a defined scope; no implied endorsement is created by collaboration alone.

RECOMMENDED

Research-selected

A product or approach may fit a use case; it is not necessarily tested in our lab.

LAB TESTED

Measured in bounded conditions

A product or system was evaluated under documented Sustainable Oasis conditions and limits.

OASIS PROVEN

Operating in a documented pathway

The asset has moved beyond a concept into a documented kit, system or infrastructure route; local review still applies.

PROPOSE A PARTNERSHIP

Have a capability we should test together?

Send the organization, capability, proposed contribution, location, timeline and desired outcome. We will review fit, scope, evidence and responsibilities before a next conversation.

  • 01Describe partner and capability.
  • 02Define the pilot or collaboration you have in mind.
  • 03Include location, timeline, safety constraints and success measures.

This form starts a conversation only. It is not a contract, purchasing commitment, grant or guarantee of acceptance.

FROM PARTNERSHIP TO OASIS

Build the next useful proof together.

Move from a shared problem to a bounded pilot, a documented result and—when it earns that right—a repeatable kit, system or infrastructure pathway.

See Lab workExplore kitsReview licensing

PROVE → EARN → FUND → ACQUIRE → BUILD → REPLICATE — for generations.