Back

Guide

Scenario Collaborations: How Bundled Partnerships Create Revenue No Solo Project Can

April 16, 20269 min read

A single project serves one need. A bundled offering — where multiple complementary projects combine into one package — serves the full need. The difference matters because customers increasingly buy integrated solutions, not individual tools.

This is the logic behind scenario collaborations: multiple projects combine their capabilities, go to market together through a shared offering, and split the revenue automatically.

The concept isn't theoretical. Haier has been running this model across thousands of micro-enterprises for over a decade. The results show why bundled partnerships consistently outperform solo execution — and what infrastructure is required to make them work.

What a Scenario Collaboration Actually Is

A scenario collaboration is a structured partnership between two or more complementary projects that:

  1. Bundle their capabilities into a single offering — one product, one launch page, one value proposition that addresses the customer's full problem
  2. Go to market together — jointly selling the combined offering rather than cross-referring separate products
  3. Share the revenue automatically — each partner earns a pre-agreed percentage of the revenue the bundled offering generates

The key word is bundled. This isn't a referral partnership or an integration. It's a combined offering where the whole is more valuable than the sum of the parts — and each partner shares directly in that value.

Evidence: What Happens When Companies Bundle Instead of Solo

Haier's ecosystem model offers some of the best-documented examples. Three cases are worth studying for the pattern they share.

Wensli Silk: 30% Revenue Increase in One Month

Wensli Silk, a well-known Hangzhou textile manufacturer, had a problem: customers complained that their silk garments were too fragile for conventional cleaning. Wensli made silk, not washing machines. They couldn't solve this alone.

Through Haier's Internet of Clothing ecosystem, Wensli partnered with Haier's washing machine team and a detergent producer. Together they developed AirWash — a cleaning method using minimal water and a specialized vaporized detergent. AirWash machines were placed directly in Wensli's stores.

The result: a 30% increase in Wensli's revenue in the first month. Customers who previously avoided buying silk because of cleaning concerns now purchased confidently. The bundled offering — silk garments plus in-store AirWash cleaning — solved a problem that neither partner could address independently.

A detergent micro-enterprise spun out of this collaboration as well, creating an entirely new business line from what started as a partnership.

Xiaoyi: From Industrial Tags to 4x Market Valuation

Xiaoyi manufactured clothing tags — the small labels inside garments with washing instructions. It was a factory-only, B2B business. Then the Internet of Clothing ecosystem created an opportunity: smart washing machines that could read RFID tags and automatically select the correct wash cycle.

Xiaoyi joined the ecosystem. Their tags went from passive labels to active technology components. The market shifted from exclusively industrial to household use.

The result: Xiaoyi's market valuation rose from RMB 100 million to 400 million. A 4x increase, driven not by a new product but by joining a bundled offering where their existing product served a new function.

Yeehoo: 50% Premium on Infant Clothing

Yeehoo, a high-end retailer of infant clothing, partnered with Haier to place AirWash machines in their stores. The combination of Yeehoo's patented organic infant clothing and Haier's specialized cleaning technology created a premium offering.

As Yeehoo store manager Zhang Meling explained: "We have developed a patented product and technology for making infant cotton clothes with green and organic materials, suitable for sensitive baby skin, and Haier's AirWash is perfect for cleaning these garments."

These specialized products commanded a 50% premium price. The premium existed because the bundled offering — garment plus care solution — addressed the full customer need. Neither product alone justified the premium.

The Pattern: Why Bundled Offerings Create More Revenue

Three things consistently happen when complementary projects bundle instead of selling separately:

  • The addressable market expands. Wensli reached customers who wouldn't buy silk without a cleaning solution. Xiaoyi reached an entire consumer market they'd never served. Each partner accessed customers they couldn't reach alone.
  • The offering commands higher prices. Yeehoo's bundled garment-plus-care service justified a 50% premium. Integrated solutions are worth more than the sum of their parts because they eliminate the customer's coordination burden.
  • New revenue streams emerge. AirWash cleaning generated per-use revenue. Rocking horses in vaccination stations generated per-ride revenue shared between partners. The bundled offering creates opportunities none of the partners would have seen independently.

As Li Yang, Haier's Internet of Clothing platform owner, observed: "Previously, 80% of our business was our core product. Now that core business is only 20% of our revenue, and 80% is new business."

The core product became the entry point. The bundled ecosystem generated the majority of revenue.

What Makes Scenario Collaborations Work (and Fail)

Not every partnership becomes a scenario collaboration. The ones that work share specific characteristics:

Complementary, Not Overlapping

Every successful example involves partners who bring different capabilities. Wensli brought silk manufacturing and retail presence. Haier brought washing technology. The detergent partner brought chemistry. None of them competed with each other. Each was essential.

When partners overlap in capability, the collaboration becomes competitive. When they complement, it becomes multiplicative.

A Shared Customer Problem

The bundled offering must address a single customer problem that no partner can solve alone. "I want silk clothing I can actually clean at home." "I want my child vaccinated without spending three hours in a waiting room." The problem defines the bundle.

If partners can't articulate the customer problem their combined offering solves, the collaboration is a marketing exercise, not a scenario collaboration.

Revenue Sharing, Not Revenue Referral

The critical infrastructure difference: every partner earns from the combined offering's revenue, not from referral fees. When Haier's ecosystem sells an integrated vaccination station renovation, every partner — carpenters, software developers, equipment manufacturers — earns a share of the total contract value.

Revenue sharing aligns incentives in a way referral fees cannot. A referral partner earns a one-time fee and moves on. A revenue-sharing partner has ongoing financial stake in the offering's success. That stake drives sustained engagement, quality, and urgency.

Coordination Infrastructure

Multi-party revenue sharing is easy to describe and hard to execute. It requires:

  • Contracts that specify each partner's contribution and revenue percentage
  • A shared go-to-market presence — a single page or offering the customer sees, not three separate pitches
  • Automated revenue tracking and distribution — so partners get paid accurately without manual reconciliation
  • Transparent reporting — every partner sees the same revenue data

Haier built this infrastructure internally (their "Workbench" platform). For projects outside corporate ecosystems, this infrastructure is the primary barrier. The collaboration model makes sense. The coordination logistics kill it.

How Scenario Collaborations Work on Ordana

Ordana's scenario collaboration feature is built specifically around this bundled partnership model. The mechanics:

  1. Partner discovery. Ordana's AI matches complementary projects — identifying where capabilities align and where bundled offerings could address unserved customer problems.
  2. Shared launch page. Each scenario collaboration gets a public page where the bundled offering is presented as a single product. One URL, one value proposition, one call to action. Customers see the combined offering, not three separate pitches.
  3. Auto-generated contracts. Revenue percentages, contribution expectations, and duration are defined upfront. Every partner signs the same contract. Changes require consensus — no unilateral edits.
  4. Automated revenue splitting. When revenue flows through the shared offering, Stripe automatically distributes each partner's share. No invoicing between partners. No manual reconciliation. Each partner sees real-time revenue data.

The model mirrors what Haier built internally — but accessible to any project, without requiring an 80,000-person corporate ecosystem.

When a Scenario Collaboration Makes Sense

Not every partnership needs to be a scenario collaboration. The model fits when:

  • Your product is one part of a customer's full problem. A design tool is useful alone, but design + development + deployment is a complete solution. A bundled offering can charge for the full solution.
  • You're entering a market where credibility requires breadth. Enterprise customers want complete solutions. Three specialized startups bundling into one offering can compete with larger companies that offer everything in-house — often with better quality per component.
  • You have complementary distribution. One partner has the audience, another has the product, a third has the implementation capacity. Bundling lets each partner access the others' distribution.
  • You want to test a market without building everything yourself. Instead of spending 12 months building adjacent features, partner with someone who already has them. If the market responds, the collaboration validates the direction.

The common thread: the combined offering creates value that none of the individual parts can capture independently.

The 80/20 Shift

Li Yang's observation — that his core product went from 80% of revenue to 20%, with ecosystem-generated business filling the other 80% — is the most striking data point in any of these cases.

It suggests that for many projects, the biggest revenue opportunity isn't improving the core product. It's bundling that product with complementary partners to address a larger customer problem. The core product becomes the entry point. The bundled offering becomes the business.

That shift doesn't require Haier's scale. It requires coordination infrastructure and the right partners. Both are solvable.

The Haier examples in this article are drawn from research by Bill Fischer, published in the Business Ecosystem Alliance. Additional Haier case studies: Peking Duck ($600K in 6 months) and Smart Vaccine (52,000 stations transformed).

Ordana's scenario collaborations give any project the same coordination infrastructure that Haier built for its 80,000-person ecosystem — partner matching, shared launch pages, auto-generated contracts, and Stripe-powered revenue splitting.

Related reading:

Learn more about Ordana →