Guide

Every Collaboration Is Now a Scenario: Inside Ordana's Unified Journey

July 24, 20268 min read

Short answer: Ordana merged the old "project collaboration" and "scenario collaboration" into one journey. The scenario is now the underlying primitive — even a 1-on-1 runs as a single-member scenario. The journey just takes one of two shapes, decided by how many members can be a revenue source, and every collaborator now applies before they can join. Same rails, cleaner mental model, better collaborators.

The old problem: two things that looked like one thing

We used to ship two separate concepts. A "project collaboration" was owner-led: you run the thing, you bring people in to help, revenue flows through you. A "scenario collaboration" was multi-party: several startups bundle into a joint offering and split what it earns. On paper the distinction was clean. In practice, new users couldn't tell them apart. Founders would start a project when they meant a scenario, or open a scenario for what was really a 1-on-1.

Scenarios had a second problem: joining one was too easy. A frictionless "join" button filled scenarios with members who hadn't verified their identity, hadn't set up payouts, and hadn't said what they'd actually contribute. Collaborations stalled before they started because nobody had committed to anything concrete. The concept was right; the onboarding was doing the opposite of qualifying people.

The fix: one journey, two shapes

So we collapsed the two into a single primitive. Everything is a scenario now. What changes isn't the entity — it's the governance, and that's set by one honest test question:

Can revenue originate from more than one member?

One revenue source → project shape. Only the owner sells; collaborators contribute to the owner's offering and earn a share of it. Governance is owner-led — the owner is the only one who invites and approves. This is a lever: grow now, pay from the upside.
Two or more revenue sources → full scenario. Multiple members can each be a revenue source, so they co-own the offering. Governance is vote-based — members co-edit the plan and vote to invite, remove, or close. This is a flywheel: turn your customers into each other's customers.

Notice the test is about revenue sources, not head count. Two people can run a one-revenue-source project (one sells, one builds). Two companies that each sell into the collaboration are a two-source scenario. Getting this right is the whole game, which is why Ordana's AI routes new collaborations by exactly this test — no bias toward scenarios, no "scenarios are always better." The right shape is whichever the revenue math says it is. If you want the deeper version of the multi-source case, our guide to scenario collaborations walks through the Haier ecosystems where this pattern is best documented.

Why the flywheel is more than a metaphor

In a single-source project, you're financing growth against future revenue — a clean, powerful lever. In a multi-source scenario, something structurally different happens: every sale carries a built-in upsell. When your customer buys from a partner in the scenario, you earn a share. When their customer buys from you, they earn a share. Your addressable base effectively multiplies by the number of members. That's why the two shapes aren't ranked — they solve different problems. A lever pulls harder on your engine; a flywheel spins everyone's together. Real-world scenario use cases show where each one earns its keep.

The new apply-first flow, end to end

Here's the biggest change a collaborator will feel. You no longer "join" — you apply. When someone is invited into a collaboration, clicking Apply starts a short, deliberate sequence:

Connect Stripe. KYC identity verification and payout setup happen first, so every applicant is a real, payable entity before anything else.
Upload proof of capabilities. Show what you can actually do — work, credentials, track record. This is what turns "interested" into "qualified."
State responsibilities and a minimum revenue-share %. You declare what you'll own and the smallest share you'd accept for it. No vague hand-shakes; a concrete contribution at a concrete price.
Get an auto-generated meeting agenda. Ordana drafts the agenda for the intro conversation so the first call is about substance, not logistics.
Owner approval. The owner reviews and approves. Membership is granted only at approval — never on the click. Applying is a request, not an entry.

Throughout, invitees see an AI-estimated earning potential for the role. Treat it as exactly what it says — an estimate, never a promise. On the Autopilot tier, Ordana can run an automatic credibility check and auto-approve applicants above a trust threshold, so high-signal collaborators move fast without the owner babysitting the queue.

What this means for a founder in practice

The apply step looks like friction, and it is — positive friction. Every person who reaches your approval screen is already identity-verified, payout-ready, and on record with a specific contribution and a specific price. You're not sifting tire-kickers; you're choosing between people who've each done the work to show up seriously. That's a higher-quality collaborator pool and a governance model that's obvious from day one: owner-led when you're the single engine, vote-based when the offering is genuinely shared. If your starting problem is finding those people at all, how to find a collaboration partner covers the matching side — same ICP and job-to-be-done, but a different value-chain slot.

And the plumbing you already know hasn't moved. The contract plus automatic revenue sharing still sets up in about 15 minutes, the platform fee is still a flat 5% off the top with collaborators' shares summing to the remaining 95%, and Stripe still auto-transfers each cut after Ordana aggregates it into an invoice. The unification changed the front door, not the accounting.

Lever or flywheel — pick by the revenue, not the vibe

The cleanest way to hold all of this: a single-source collaboration is a lever and a multi-source collaboration is a flywheel. A lever multiplies force on your own growth — you get the resource now and pay from the upside it creates. A flywheel compounds because each member's customers become a shared base, and every sale carries that built-in upsell. Neither wins in the abstract. You pick by answering the honest question about revenue sources, and Ordana routes you accordingly. For where this fits in a broader growth plan, see the best way to scale a bootstrapped startup, and if you're ready to run it, start a collaboration on Ordana and let the apply-first flow do the qualifying for you.

Related reading:

Find your collaborators on Ordana → Free to join — pay only when revenue flows.