How a 25-brand SaaS reseller eliminated the per-reseller revenue-share nightmare

The operator runs a SaaS company — the core product is a CRM + marketing automation platform — with a white-label reseller program. 25 agency partners resell the platform under their own brand to their own end-customer base. Each reseller has its own subdomain (reseller.platform.com), its own pricing (the reseller sets retail price, the platform takes a percentage), and its own revenue-share contract.

The contracts aren't uniform. Some resellers are on 70/30 (reseller keeps 70% of collected revenue, platform keeps 30%). Some are on 80/20. Some are on tiered schedules (70/30 on first $10k MRR, 75/25 above that). A few legacy resellers are on flat per-seat licensing. Combined platform MRR across all 25 resellers: $680k/mo, with roughly $450k of that flowing back to resellers in revenue-share payouts.

The reconciliation happened in Excel. The CFO and one staff accountant would pull monthly subscription revenue from Stripe (25 separate revenue streams, one per reseller subdomain), match it against each reseller's contract terms, net out chargebacks and refunds, calculate the payout amount, and push ACH to 25 reseller bank accounts on the 15th of each month.

Roughly 80 hours of labor per month on the reconciliation. And roughly 9 errors per month — miscalculated payouts, missed chargebacks, wrong tier applied. The errors didn't stay errors; resellers caught them on their end, filed disputes, and the CFO spent another 20+ hours per month re-calculating contested payouts.

Reseller churn was the downstream cost. When a reseller left the platform, the exit interview almost always cited "payout accuracy and timing" as a top-3 reason. Annual reseller churn was 28% — roughly 7 resellers per year leaving, each representing $20k–$50k/yr in lost revenue.

In Q2 2024 the platform lost 4 resellers in 6 weeks. Each of them, on exit, had filed disputes about payout accuracy in the trailing 3 months. The CFO had resolved all the disputes — mostly in the resellers' favor — but the damage was done. Each exit cost the platform $25k–$60k/yr in lost revenue, and the exits happened to include two of the top-10 resellers.

The operator did the math. At 28% annual reseller churn, with new resellers taking 6–9 months to reach profitability, the churn was eating the CAC on every new reseller acquired. The business was treading water.

The fractional CFO she'd hired six months prior had been through a similar situation at a prior company and recommended multiflow for reseller-payout orchestration. The operator booked a call.

The key implementation work was encoding each reseller's contract into the multiflow rule engine. Every contract became a computable set of deduction and payout rules.

Day 1–3: Contract inventory. All 25 reseller contracts re-read by the operator's counsel and the multiflow implementation engineer. Each contract's revenue-share terms, tier breakpoints, chargeback handling rules, refund handling rules, and payout timing encoded into JSON-structured rules. A handful of old contracts had been orally amended over the years without written updates — those got cleaned up with new addenda signed during the window.

Day 4–5: Parallel run. multiflow's calculation engine ran against the prior 90 days of actual platform data, producing what each reseller's payout would have been under the new system. Compared to what the CFO had actually paid out in the spreadsheet-based system. Delta: $4,340 total across 25 resellers × 3 months (roughly 0.35% — most of it was precision issues on percentage rounding). The operator signed off.

Day 6: Banking integration. The operator's business bank (Mercury) was wired into multiflow's ACH push. All 25 resellers' bank accounts verified via Plaid.

Day 7: Reseller portal rollout. Each reseller got login credentials to a per-reseller dashboard showing their subscription revenue, pending payouts, past payouts, chargebacks, refunds — all in real-time, not month-end. Previously they'd had no visibility until the monthly statement arrived.

Day 8: Test payouts. 25 × $1 test ACH pushes to verify each reseller's bank account was correctly routed. All 25 landed.

Day 9: Cadence change. Monthly payouts became weekly payouts. Each Monday, resellers got paid for the prior week's net revenue.

Day 10: First weekly cycle ran. 25 resellers paid their first Monday payout on day 10 of the cutover. The CFO watched the run in the dashboard — 11 minutes of processing time for what had previously been 2 full business days of spreadsheet work.

Reconciliation time moved from 80 hours/mo (CFO + 1 staff accountant) to 8 hours/mo (just the CFO doing spot-checks on the automated run). The staff accountant redeployed to FP&A work on reseller-profitability analysis — something the platform had never systematically done because the reconciliation workload had eaten all available finance capacity.

Payout calculation errors dropped from 9/mo to 0–1/mo. The rare errors that remained were almost always upstream data issues (a late-arriving chargeback reversal, a refund processed after the weekly cutoff) rather than calculation mistakes.

Reseller churn moved slowly but meaningfully. Over the first 12 months post-cutover annual churn dropped from 28% to 11% — a 60% reduction. The primary driver was the weekly payout cadence plus the real-time per-reseller dashboard. Resellers stopped having "is my payout right?" anxiety because they could see the numbers updating live, reconcile against their own records continuously, and raise small discrepancies the week they happened instead of waiting for the monthly statement.

Recovered annualized reseller LTV: roughly $112k/yr at steady state. That's the net of retained resellers who would have churned under the old system, against the new-reseller acquisition cost saved.

The operator's framing of multiflow's value for SaaS reseller programs: revenue-share payout is an entire category of back-office work that every SaaS reseller platform either builds from scratch or does in spreadsheets. The build-from-scratch path is a 6–12 month engineering project plus ongoing maintenance. The spreadsheet path is sustainable at 5 resellers, painful at 15, and business-limiting at 25+.

multiflow's marketplace-payout orchestration — the same infrastructure that powers the 30-brand gift marketplace case study elsewhere on this site — happens to match the reseller-revenue-share pattern exactly. The only difference is the accounting frame (marketplace sellers vs SaaS resellers) and the payment direction (platform → reseller in both cases, actually).

The quote at the top is the one the operator wanted in the hero. She added: "If I'd known this infrastructure existed I would have launched the reseller program three years earlier. The finance-back-office fear was the thing holding me back."