Revenue-Share Term Sheet

In plain English

You (the Creator) have an audience. A vetted Builder builds you a real, monetizable app and keeps it running. You share the revenue. WantBorn is on your side in that deal — we find and vet the builder, negotiate the split for you, put it in writing, and stay in the room afterwards. You keep your audience and your brand. The builder owns the code. Nobody pays up front. If the build stalls, we find you another builder. The clauses below just say that precisely.

1. Parties

• Creator: (name, entity, contact email) — audience / channels:
• Builder: (name, entity, contact email) — relevant prior work:
• WantBorn — the Creator's representative: we act as the Creator's representative/agent in structuring and stewarding this partnership. Our job is to protect the Creator's interests in a deal with a counterparty they didn't previously know — negotiate the terms, watch the downside, chase the Builder if things go wrong, and keep the settlement record honest. We're not the Builder, not your lawyer, and not a guarantor of either party's performance — we're the party in the room whose only job is the Creator's side.

2. The App / Scope

• Working title:
• What it is (one paragraph):
• Platforms: ☐ iOS  ☐ Android  ☐ Web  ☐ Other
• Core features (v1): 1. 2. 3.
• Out of scope (v1):

3. What “Launched” means

The rev-share and the success fee both turn on the app being launched. To avoid arguments later, "launched" means all of:

1. The app is publicly available to the Creator's audience on the agreed platform(s) — live, not a private/TestFlight build.
2. The app can take money — the monetization path works end-to-end and the revenue rail (§4) is configured and reporting.
3. The Builder has handed over the §6 items (working build + store listing + revenue-rail access).

Until all three are true, no success fee is due.

4. Revenue Share

• Net revenue = gross app revenue less platform/app-store fees, payment-processor fees, and the WantBorn fee (§9).
• Split of net revenue (seed — your agent negotiates this for you): Creator % (e.g. 50%) · Builder % (e.g. 50%). Must total 100%.
• Duration: (seed: 12–24 months from launch, renewable while the partnership is active)
• Reporting cadence: (e.g. monthly statement from the rail)
• Revenue rail (rails-agnostic): ☐ RevenueCat  ☐ App Store / Play direct  ☐ Stripe  ☐ Paddle  ☐ Other. Settlement happens on whichever rail the parties choose; WantBorn does not hold or disburse funds, and this sheet works the same over any rail.

5. IP & Ownership

• App code & IP: the Builder owns the source, design and underlying IP unless agreed otherwise here:
• Creator brand / name / likeness: licensed to the app for the term, for use in and promotion of the app only. The Creator retains all rights to their brand, name, likeness and audience relationship — never assigned.
• On termination: brand & likeness rights revert to the Creator immediately; shared assets handled here:

6. Responsibilities

• Creator: promote the app to their audience as agreed (), provide brand assets, give feedback, act in good faith.
• Builder: design, build, ship and maintain the app (bug fixes, OS-update compatibility, reasonable support) for the term; hand over build + store listing + revenue-rail access on launch; keep reporting accurate.
• WantBorn (your representative): structure and explain the deal, negotiate the split on the Creator's behalf, keep the milestone checkpoints and settlement record, and step in if the partnership goes sideways (§7, §8).

7. Launch & Milestones

• Target launch date:
• Milestone checkpoints (your representative checks in at each): 1. 2. 3.

8. Graceful exit & replacement builder

This is the clause that makes "we're on your side" real.

• If the Builder stalls or under-delivers (misses agreed milestones without a good-faith fix, goes unresponsive, or materially breaches), the Creator may raise it with WantBorn, who will work to re-broker the partnership with a replacement builder from the vetted bench so the Creator isn't left with a dead project. (For founding creators this is a guarantee; otherwise our best effort — and why your representative stays in the room.)
• Graceful exit: either party may terminate on days' written notice if the other materially breaches and fails to cure.
• Effect: rev-share on revenue already earned survives per §4; brand/likeness rights revert to the Creator per §5; the Creator keeps the right to have the project re-brokered.

9. WantBorn Fee

• Builder success fee (the representative's contingency fee): a one-time fee paid by the Builder on a launched match (§3): (seed: $500–$1,500 flat, or 8–15% of first-month net). Creators pay nothing — ever. The standard agent's contingency: paid by the abundant side, earned only on a real launch.
• Stewardship trail (optional, ongoing): if WantBorn keeps actively stewarding (settlement record-keeping, dispute handling, sourcing the next deal), a small ongoing platform share may apply: % (seed: 5–10%) — disclosed and agreed in writing, charged only while real stewardship continues, and waived to 0% for founding creators' first deal. Not active by default.

10. Confidentiality

Each party keeps the other's non-public information (brief details, audience data, code, financials) confidential and uses it only for this partnership.

11. Governing Law

Governed by the laws of (placeholder — set by the parties / their counsel), disputes resolved in .

12. Nature of Relationship

The Creator and Builder are independent parties; nothing here creates employment, a legal partnership, or a joint venture between them beyond what's expressly stated. WantBorn acts as the Creator's representative in structuring and stewarding the deal as described, and is not liable for the performance, conduct, or output of either party.

Signatures