Revenue splits: paying co-founders without spreadsheets
You shipped a product with a co-founder. You hired a contractor on a percentage. You launched an affiliate program. Now every month you open Stripe, export a CSV, do math in a spreadsheet, and fire off four bank transfers from your business account. Then someone messages you on a Sunday asking when their cut is landing.
This is the part of the SaaS stack nobody warns you about. The marketing pages all talk about subscriptions and tax compliance. Nobody talks about the fact that once you have one human being who isn't you taking a slice of revenue, you've signed up for a payroll problem nobody built a product for.
Revenue splits fix that. Every sale is divided automatically the moment money lands, and each person's share shows up in their own balance.
What revenue splits actually do
A revenue split is a rule for dividing sales revenue. In Creem, it applies to a whole store or a single product.
For example: "Allocate 60% to co-founder A and 40% to co-founder B." Affiliate commissions belong to Creem's separate affiliate program.
The mental shift: every sale has its shares calculated automatically, so you stop doing the partner math later.
Those shares credit recipient balances after deductions. Money reaches a bank account through withdrawal, separate from the split allocation.
If you've worked with Stripe Connect, the underlying concept is familiar: programmatic transfers between accounts.
The problem with rolling your own is the rest of the iceberg. A custom integration needs engineering and ongoing maintenance.
Who handles KYC, reporting and compliance depends on the Connect configuration. Refund reconciliation still needs a plan.
None of which is the work you wanted to be doing this quarter.
Who actually needs this (and who doesn't)
You need revenue splits if any of the following are true for your business:
- You have a co-founder. Even if equity is split 50/50 on cap table, monthly revenue distribution still has to happen somehow. Doing it by hand becomes the thing you both quietly resent.
- You run an affiliate or referral program. Affiliate payouts at scale are not a spreadsheet problem. They're a trust problem. Late payouts kill affiliate momentum faster than any other variable.
- You pay contractors or designers on revenue share. "I'll take 10% of what this brings in for the first year" is a fine deal until month three when you realize you have to track and pay it forever.
- You sell on behalf of someone else. White-labeled products, creator stores, marketplaces. The underlying creator needs their cut, automatically, every time their product sells.
- You run a partnership where another company drives the sale. Co-marketing deals, integration partners, reseller agreements. If the other side gets a slice, splits are the cleanest way to honor it.
You probably don't need this if you're a solo founder with no partners, no affiliates, and no contractors on revenue share. Wait until you do. The point of payments infrastructure is that it should appear the moment you need it, not before.
The math nobody shows you on doing this manually
Say your SaaS does $20k MRR with a co-founder and three affiliates. These assumptions put a price on distributing revenue by hand:
- Two to four hours a month on reconciliation, exports, calculations and bank transfers. Assume three hours at $150/hr: that's $450 a month, or $5,400 a year, in time you're not spending on the product.
- Wire fees: Costs vary by bank and destination. Assume $35 per international transfer: three monthly transfers cost $1,260 a year.
- At least one botched payout per quarter: Assume someone gets the wrong amount, sends a Slack message, and now you're doing forensic accounting on a Tuesday morning.
- One or two trust-killing late payouts a year: Assume you forget, travel, or a bank transfer fails. Your affiliate has to chase money they expected to receive. Affiliate momentum dies. The creator quietly stops promoting you.
Those assumptions total $6,660 a year, before time spent correcting errors. Late payments also erode the relationships growing your business.
On these assumptions, the break-even on automating distribution shows up almost immediately. Compare your actual time and transfer costs against split and withdrawal fees.
How Creem handles this
Creem ships revenue splits as a first-class feature, not a bolt-on. The pattern looks like this.
You add each recipient by email or store ID. Every recipient needs their own onboarded and verified Creem store before they can receive a share.
Recipients get paid by bank transfer, a supported e-wallet such as Alipay in China, or USDC on Polygon, depending on their country. The KYC happens once, up front, not at payout time.
You attach a split rule to your whole store or to a single product. "Sarah Chen, co-founder, 60%. Marc, co-founder, 40%." The rule travels with every sale it covers.
The split documentation allows 1 to 10 recipients per rule, with shares totaling no more than 100%.
When a customer pays, a 60/40 split applies to the amount remaining after Creem's documented deductions, including the additional flat 2% split fee, not to the gross sale amount, and not after two separately billed Stripe and Creem processing fees. The resulting credits are not deposits into recipients' bank accounts: recipients must request a withdrawal once their available balance reaches $50 or €50. Withdrawals are processed in the standard payout windows on the 1st and 15th of each month, as listed on the pricing page, rather than going out automatically without any action.
Refunds and lost chargebacks can reverse recipients' shares when the per-split Split refunds setting was on at the time of the sale. New splits default to on; existing splits remain off until you opt in. Changing the setting affects future sales only. Each recipient's reversal is limited to a proportional share of what they actually received. If you later win a disputed chargeback, Creem restores the clawed-back shares. Transaction fees, including the 2% split fee, are not returned. See the split-refund rules.
The dashboard shows you every payee, every split, every payout, every reconciliation event. The affiliate or co-founder logs into their own portal and sees their own balance and history. You stop being the customer service rep for your own business.
Three patterns this enables you actually couldn't run before
Co-founder splits that aren't equity. Equity is for the cap table. Revenue splits are for monthly cashflow. The two should be decoupled. With a split rule per product, you can say "this product line is 70/30, this other product line is 50/50" without restructuring the company.
Affiliate programs with automatic earnings allocation. Creem's separate affiliate program calculates commissions for you, so you stop doing the affiliate math after each sale.
Your affiliates can track their balance and request withdrawal for processing on the 1st and 15th, as listed on the pricing page.
Creator marketplaces that you, as a solo dev, can actually run. If you've ever wanted to build a Gumroad-style or Whop-style storefront where other people sell through your platform and you take a cut, the splits are the entire mechanic. Without automated splits you cannot run that business. With them you can ship one in a weekend.
Why Creem and not roll your own with Stripe Connect
You can build this on Stripe Connect. People do. The reasons not to:
- KYC and compliance for every payee becomes your problem. Connect makes you the platform for compliance purposes. You need legal coverage. You need an onboarding flow for payees. You need to maintain it.
- Tax forms at year-end. US affiliates over the 1099 threshold need a 1099-NEC. International payees need W-8BEN tracking. This is the stuff that breaks pipelines at 11pm on January 30th.
- Cross-border payout compliance. Different rules per destination country. Different reporting requirements. Different banks rejecting your transfer.
- You wanted to ship a product, not handle the seller's tax, invoices and disputes yourself. A merchant of record takes on that work.
Creem absorbs that work because Creem is the merchant of record. The 3.9% + 40¢ rate per successful transaction on the pricing page includes compliance, KYC, tax forms and cross-border routing.
On the standard plan, revenue splits add a 2% fee, taken before anyone's share is calculated. Withdrawals to a bank or USDC wallet carry their own transfer fee.
You bring the customer. Creem handles recipient verification, split allocation and payout processing.
When you should NOT use this
In the spirit of being honest: revenue splits are overkill if you are paying one contractor a flat monthly retainer. Just use a bank transfer or a payroll tool like Deel. Splits are for percentages tied to transaction volume, not flat fees.
They also don't replace your payroll system if you have W-2 employees. Splits handle 1099 / independent contractor / affiliate flows. Salaried employees still need payroll infra.
And if you're pre-revenue, this is a future problem, not a today problem. Don't optimize for the split flow before you have the first sale to split.
What to do this week
- List every human who currently gets a percentage of your revenue. Co-founders, contractors, affiliates, partners, anyone. Write down what they get and how you pay them today.
- Add up the time and fees you're spending on manual distribution. Even a rough number. You'll be surprised.
- Try Creem on one product or one affiliate first. Don't migrate the whole business in one shot. Pick the most painful manual payout and replace it. See how it feels.
FAQ
What is a revenue split in SaaS?
A revenue split automatically allocates each sale between recipients, so you don't have to export reports and calculate everyone's share by hand.
Every transaction is pre-allocated. Recipients receive balance credits first, then withdraw their available earnings.
How are revenue splits different from affiliate payouts?
Revenue splits share sales with co-founders, contractors or licensors. Affiliate commissions reward referrals.
Creem has separate split-payments and affiliate-program features within the same platform. You can support both without an affiliate-only tool.
Can I do revenue splits with Stripe?
Yes, you can build revenue splits with Stripe Connect.
When your platform handles pricing, Connect pricing adds $2 per monthly active account plus 0.25% + 25¢ per payout sent, in addition to standard processing fees.
When Stripe bills connected accounts directly, there are no additional Connect account or per-payout fees under that model. KYC, reporting and compliance duties depend on your configuration.
A custom integration still requires engineering and ongoing maintenance. Compare processing, account and payout charges alongside implementation costs, rather than treating the percentage payout charge as the total cost. Creem, by contrast, provides revenue splits alongside its merchant-of-record service.
How does Creem handle taxes on revenue splits?
Creem is the merchant of record on every transaction. Sales tax, VAT, and GST are collected and remitted before the split runs. The split happens on the net-of-tax amount, and Creem files the tax returns. Payees get their cut clean.
Can I split revenue between people in different countries?
Yes. Creem supports merchant onboarding and payouts across many countries, including stablecoin payout options where available. That does not mean every payout method is available in every country: check the pricing page for the supported list and the options available where you receive payouts.
How often do payouts happen?
Creem processes requested withdrawals on the 1st and 15th of each month. Bank arrival follows processing.
With at least $50 or €50 available, use Request Withdraw to enter the next processing window. New payments may have a 7–12-day risk hold before becoming payable.
Payees can track their accruing balance and per-transaction history in their portal. Withdrawals have separate transfer fees.
Do refunds claw back the split?
Only when Split refunds was on for that split at the time of the sale. New splits default to on; existing splits stay off until enabled. A refund or lost chargeback then reverses proportional shares of the revenue recipients actually received. Changing the setting does not change earlier sales, and fees are not returned. See the refund and chargeback rules.