Revenue Sharing
Configure a waterfall once. Revenue flows in, splits calculate instantly, and every party gets paid via Stripe Connect — automatically.
HYVV's revenue sharing engine is a deterministic waterfall that handles every calculation, every payout, and every edge case — so you never have to think about it again after setup.
How Revenue Sharing Works
Revenue arrives (Stripe webhook or manual entry)
↓
Waterfall engine calculates each party's share
↓
Reserve threshold check (defer if cash is low)
↓
Stripe Connect transfers fire automatically
↓
Audit log appended with SHA-256 hash
↓
Recipients see the payment in their portal as soon as the split runs
Creating a Revenue Share Agreement
Use the New Agreement Wizard (7 steps):
Step 1 — Deal Basics
Define the parties: who is this with, what is their role (operator, advisor, licensor, investor-like participant).
Step 2 — Legal Wrapper
Choose the agreement structure. HYVV recommends the right type based on your answers:
| Type | When to use |
|---|---|
| Services + Rev Share | Operator doing ongoing work |
| License / Royalty | IP, content, brand, software |
| Revenue Participation | Capital-like contractual right to revenue |
| Profit Participation | Profit-linked incentive |
| JV / Ownership Path | Requires attorney review |
Step 3 — Economics
Define the revenue formula:
Payout = (Revenue Base − Exclusions) × Share %
- Revenue base — gross, net, product-specific, or custom
- Exclusions — taxes, processing fees, refunds
- Share % — 0.01% to 99.99%
- Payout simulation — enter estimated monthly revenue, see projected payout instantly
Step 4 — Timeline & Caps
- Agreement start date and sharing start trigger
- End condition: fixed date, dollar cap, payout multiple, or perpetual until buyout
- Buyout option: company call right with formula (3× trailing 12M, NPV, fixed)
- Change of control: mandatory payoff on acquisition
Step 5 — Deliverables
Define what the counterparty must deliver to earn the payout:
- Milestones (drag-to-reorder)
- KPI thresholds
- Enforcement: payment suspension, step-down on missed KPI, cure period
Step 6 — Safeguards
- Minimum cash reserve before payouts fire
- Deferred payout handling (carry forward, cumulative with interest, or forgiven)
- Annual payout cap
- Manager approval gate before each remittance
Step 7 — Review & Sign
Live agreement preview with all terms filled in. Send for e-signature directly.
Payout Triggers
| Trigger | How it works |
|---|---|
| Real-time | Calculates on every dollar of revenue |
| Daily | Sweeps accumulated revenue once per day |
| Weekly | Sweeps every 7 days |
| Monthly | Sweeps at end of each calendar month |
| Threshold | Fires when accumulated revenue reaches a set amount |
Payment Waterfall
When multiple agreements exist, HYVV pays them in priority order.
Drag agreements up or down in the Waterfall view to set priority. When available cash is limited:
- Higher-priority recipients are paid first
- Lower-priority recipients are deferred
- Deferred amounts carry forward to the next period (configurable)
Earn Links
An Earn Link is a shareable URL that lets anyone claim a revenue share stake.
https://app.hyvv.io/earn/acme-corp-xK8m2
The claim flow (3 steps):
- Recipient opens the link, reviews the terms (share %, cap, duration)
- Signs the agreement electronically
- Connects their Stripe account for automatic payouts
From that point, the claimant is in the waterfall. No manual work required.
Configuration options:
- Share percentage
- Dollar cap (auto-stops when hit)
- Duration (months or date)
- Maximum number of claimants
- Expiration date
- Email domain restriction
Recipient Portal
Every recipient has a private view showing:
- Total earned to date and remaining cap
- Period-by-period earnings ledger (revenue base → share → payout → status)
- Next payout date and amount
- Milestone status
- Agreement terms and signed documents
Audit Trail
Every revenue event, calculation, transfer, and deferral is logged with:
- Timestamp
- Revenue base used
- Share percentage applied
- Amount calculated
- Stripe transfer ID (if sent)
- SHA-256 hash chaining each record to the previous one
The ledger is append-only — nothing can be edited or deleted.