DEV Community: Pruthvi prajapati

How to Automatically Split SaaS Revenue (Co-Founders, Affiliates & Business partnerships) Using Creem

Pruthvi prajapati — Wed, 25 Feb 2026 13:39:16 +0000

1. Why Revenue Splits Matter

You finish a deal. The money lands in the account - after that comes the stage no one mentions - open a spreadsheet, work out each share, start the transfers and check that no name was skipped. For most founders who run revenue share schemes, this is simply Tuesday.

Any expanding SaaS or product eventually faces the same complex challenge: cash will accumulate, and then you will need to determine who is going to receive what. No matter whether you are sharing the revenue with a co-founder, paying out affiliates on each referred sale, or paying contractors on a project-by-project basis, manual payouts are a formula for mistakes, missed deadlines, and broken trust.

The Problem with Manual Payouts

It’s slow and ends up being a waste of time when you have to calculate everything per transaction.
The mistakes by human beings cause over- or under-payments.
Late payments hurt relationships with partners and affiliates.
The more recipients you add, the messier it gets.

Common Founder & Affiliate Payout Headaches

Co-founders manually wired each other money after checking the bank
Affiliates chasing unpaid commissions via email
Contractors waiting weeks for revenue-share payments
Incorrect splits are discovered only at tax time
No visibility into what’s been paid vs. what’s pending

How Automatic Splits Solve This

Automatic revenue splits mean that the payment is tied to the occurrence of a transaction. As soon as the payment is received, the platform directs the payment to all the recipients according to the rules set, without human intervention, without Excel, without the slow wire transfer. The payment of all is on time, and all splits are provided with a clean audit trail.

2. What is Creem Revenue Splits?

Creem Revenue Splits automatically divides incoming payments between multiple recipients based on rules you define. When programmed, splits operate on autopilot. Every eligible transaction produces the distribution immediately, and you, the human, do not even lift a finger.

Core Concept

Think of a revenue split as a routing rule attached to your Creem store or product. When a payment arrives, Creem applies the split rule, calculates each recipient’s share, and routes the funds accordingly. Recipients receive their portion on the same payout schedule as you do.

💡 Note: Split payments incur a 2% fee. This fee is deducted from the transaction amount before any commission is distributed to recipients.

Percentage-Based

Each recipient gets a defined % of the transaction amount. Great for co-founders, affiliates, and revenue-share agreements where the split should scale with revenue.

Example: 50% to Founder A, 50% to Founder B

When Splits Are Triggered

On a successful one-time purchase
On each recurring subscription renewal
On upsell or plan upgrade payments
Not triggered on failed payments or free trials

3. Real-World Use Cases

👥 Co-Founder SaaS Split (50/50 Example)

Two co-founders launch a SaaS product. Rather than one founder collecting all revenue and manually wiring the other half to their partner each month, they configure a 50/50 split on Creem. Every subscription payment — new subscribers and renewals — is automatically split the moment it clears.

How it works in practice:

Customer pays $60 for any product
When someone purchases the product
Creem deducts 2% split fee ($1.2) from the transaction
With a transaction charge 3.9% + $0.40 per transaction, the remaining $56.06 is split
Both founders see the payout in their respective dashboards
- $28.03 to Founder A, $28.03 to Founder B
And Founder B can also see the amount in the payout section
On subscription renewal, the same split fires automatically
Any sales that occurred before the split was created will not be affected. As shown in the image below, there are two sales - one made before the split was added and one after - and only the latter is subject to the revenue split.

What happens with refunds or failed payments?

If a customer is refunded, the split is reversed proportionally each recipient’s account is debited their share of the refund. Failed payments (e.g., expired card) don’t trigger a split because no funds were collected. If a payment is retried and succeeds, the split fires at that point.

4. Setting Up Revenue Splits in the Dashboard

Before you can create a revenue split, your Creem store must be active, verified, and in good standing (no pending charges or high chargebacks). You also need at least one product in your store.

Prerequisites Checklist

Active and verified Creem store
Store in good standing (low chargebacks, no pending issues)
At least one product was created in your store
Recipients must have (or create) a verified Creem store

Step-by-Step: Creating Your First Split

Navigate to the Splits Hub in your Creem dashboard left sidebar
Click “New Split” on the splits overview page
Give your split a descriptive name (e.g., “Co-Founder 50/50” or “Affiliate Commission”)
Save the split — it becomes active immediately if StoreID is used,
You can also delete any split id from the dashboard

Adding Recipients

You can add recipients in two ways. If the recipient already has a Creem store, enter their StoreID (found in their dashboard under Settings). Alternatively, enter their email address — Creem will send them an invitation to create and verify a store so they can receive payouts.

⚠️ Important: Recipients must complete Creem’s onboarding and account verification before they can receive split payouts. Invite them early to avoid payout delays.

Viewing & Managing Splits

All active splits appear on the Splits overview page
Click any split to see transaction history and recipient details
Add or remove recipients at any time
Modify percentages — changes apply to future transactions only
Recipients can see their commission payments in their own Activity tab

5. Payout Timing & Recipient Requirements

Understanding when recipients get paid — and what they need to do before they can receive funds — is critical to setting expectations with partners and avoiding support headaches.

When Recipients Receive Funds

Recipients are paid on the same schedule as the merchant. Creem processes payouts on a regular cadence (typically weekly or bi-weekly, depending on your region and account standing). This means your affiliates, co-founders, and contractors don’t wait any longer than you do.

How Recipients Can Receive Funds

Bank transfer (standard ACH or international wire)
E-wallet payments
Stablecoin (USDC) payouts — useful for cross-border payments

Recipient Onboarding Requirements

Recipients must create and verify their own Creem store
KYC (Know Your Customer) verification is required before funds are released
Recipients must connect a valid payout method (bank account, e-wallet, or crypto address)
You can invite recipients by StoreID or email — they’ll receive onboarding instructions

⚠️ What happens if a recipient isn’t verified? Payouts will be held until the recipient completes verification. No funds are lost — they’re queued and released once KYC is complete. This is why it’s important to invite recipients before you start processing payments.

6. Managing Refunds, Disputes & Adjustments

How Refunds Affect Splits

When a customer is refunded, the split is reversed proportionally. Each recipient’s share is debited from their balance to cover their portion of the refund. This happens automatically — you don’t need to manually recover funds from recipients.

Chargeback Handling

Chargebacks are disputes initiated by the customer’s bank. If a chargeback is filed on a transaction that was split, the dispute amount is deducted proportionally from all recipient balances. Creem handles the mechanics automatically, but you should notify your key recipients if a significant chargeback occurs.

Best Practices for Financial Reconciliation

Use Creem’s split transaction history as your source of truth — every split is logged with timestamps and amounts
Export split reports monthly for your accountant or finance team
Ensure recipients understand that refunds and chargebacks will reduce their balance
Document split agreements in a written contract outside of Creem — the platform enforces the numbers, but the legal agreement is yours
Set up webhook logging so you have an independent audit trail

7. Advanced Revenue Split Patterns

Tiered Affiliate Commissions

Standard splits apply a single percentage to all transactions. For tiered commissions (e.g., 10% for the first $1,000 in sales, then 15% above that), implement the tier logic in your backend and dynamically assign different split rules depending on where the affiliate stands in their tier.

Multiple Recipients (3+ Splits)

You can add multiple recipients to a single split. For example, a three-founder startup might configure 40% to Founder A, 35% to Founder B, and 25% to Founder C. Creem distributes to all recipients simultaneously on every qualifying transaction. Make sure your percentages sum correctly — leaving a remainder means the difference stays in your store account.

Subscription Revenue Splits

Revenue splits fire on every successful renewal, not just the initial purchase. This makes them ideal for SaaS co-founder arrangements. Both founders receive their share every month without any recurring manual action. If a subscription is paused, upgraded, or cancelled, splits only fire on actual successful payment events.

Conditional Splits

Need different splits for different products? Associate each split with specific products in your store. A platform might have a 90/10 split for premium sellers and an 85/15 split for standard sellers. Create separate split rules for each tier and attach them to the relevant products.

8. Best Practices for SaaS & Platform

Keep percentages clean and easy to understand — avoid oddly specific numbers like 33.33% that can create rounding issues
Document split agreements in writing outside of Creem — a signed agreement protects both parties
Invite recipients before you go live — unverified recipients cause payout delays
Monitor the Splits dashboard weekly — catch payout failures early before recipients notice
Brief recipients on the 2% fee upfront — surprises damage trust
Test splits in a staging/sandbox environment before going live

9. Conclusion

Revenue splits are one of those features that seem simple on the surface but can dramatically change how you operate. Instead of devoting hours each month to manual payout calculations, wire transfers, and spreadsheet audits, you configure the rules once and let Creem handle distribution indefinitely.

For co-founders, it eliminates money conversations that can strain working relationships. For affiliate programs, it means affiliates get paid instantly, which is one of the best ways to keep them motivated and actively promoting your product. For contractors and agencies, it removes the friction of invoicing cycles and creates a clean revenue-share arrangement that scales as the business grows.

When to Use Revenue Splits

Any time two or more parties share in the revenue of a product or service
Affiliate programs where manual commission tracking creates overhead
Contractor or agency arrangements with a percentage-based revenue share
Platforms that need to route funds to sellers automatically
Investment agreements requiring automated revenue distribution

You currently divide revenue with a co-founder, an affiliate, or a contractor by hand. One misplaced decimal triggers an uncomfortable talk. Configure the split once inside Creem, and that talk never starts.

🚀 How to Use FlyonUI Block with AI Tools?

Pruthvi prajapati — Wed, 30 Jul 2025 12:16:10 +0000

Welcome to this in-depth tutorial on how to build a modern, AI-assisted landing page for a BBQ restaurant using FlyonUI, Copy Prompt, and Context7 MCP — all inside a Next.js project.

⚡ Whether you're a developer looking to speed up UI creation or someone curious about integrating AI tools into your dev workflow, this guide will walk you through every step.

👨‍🏫 Introduction
🧱 What Are FlyonUI Blocks?
- 🔍 Block Categories at a Glance
- 🌮 Why Use FlyonUI Blocks?
⚙️ Starting with Different Framework and Technologies
✅ Steps:
- 1. Copy–Paste FlyonUI Blocks
- 2. Using Copy Prompt
🧠 Let’s build the BBQ Restaurant Landing Page with the Copy Prompt Feature
🛠️ How It Works
- 1. 🔥 Hero Section
- 2. 🏆 About Us Section
- 3. 🍔 Menu Section
- 4. 🛎️ Services Section
- 5. 🎊 Testimonials
- 6. 📞 Contact Us
- 7. 🖥️ Footer
How to Customise FlyonUI Blocks
- 🍀 1. Direct Code Changes
- 📌 Example: Adjusting Icon (Avatar) Size
- 🍀 2. Customizing Components with Context7 MCP
- 🔍 What is Context7 MCP?
- ⚙️ Setup Context7 MCP
- 📦 Example Use Case
✅ Conclusion
📺 Watch the Full Video

🧑‍💻 Introduction

Hey everyone! In this blog, we’ll walk you through how we built a fully responsive landing page for a BBQ restaurant using FlyonUI Blocks and some powerful AI tools.

We'll be using:

FlyonUI Blocks
The Copy Prompt feature
And the Context7 MCP server

All inside a Next.js setup — it’s super fast, clean, and easy to extend.

🧾 What Are FlyonUI Blocks?

FlyonUI Blocks are a curated collection of 500+ ready-to-use layout sections built with Tailwind CSS, covering everything from marketing headers to dashboards, ecommerce pages, data tables, and more. Each block is customizable, responsive, accessible, and supports themes and RTL layouts.

FlyonUI is an open-source Tailwind Component library offering:

80+ standalone components, like buttons, cards, modals, alerts, switchers, accordions, and advanced selects
Blocks built on top of components—500+ free and premium layout sections to compose pages quickly

🔍 Block Categories at a Glance

FlyonUI Blocks fall into five main categories:

Category	Description
Marketing UI	Hero sections, CTAs, feature highlights, testimonials
Dashboard & App UI	Layouts, widgets, modals, sidebars, charts, forms
eCommerce UI	Product cards, filters, reviews, cart, checkout flows
Data Table UI	Interactive tables, stats, filters, pagination
Bento Grid UI	Responsive grids and layout systems

Each section includes both free and pro options and is theme-ready with RTL support.

🎨 Why Use FlyonUI Blocks?

⚡ Jet‑Fast UI Composition

You can assemble entire pages by mixing and matching the Tailwind blocks—no repetitive boilerplate, just copy-paste or import.

🧩 Clean, Maintainable Code

Blocks use semantic class names built on Tailwind utilities for readable, modifiable markup that avoids class clutter.

🌈 Unlimited Theming

Support for multiple design themes (Light, Dark, Luxury, Corporate, etc.) without rewriting classes, plus full dark mode and RTL compatibility.

💡 Fully Customizable Interactivity

Includes headless JS plugins for accessible interactive components (dropdowns, accordions, overlays)—no additional frameworks needed.

🛠 Cross‑Framework Support

Works seamlessly in plain HTML or within React, Vue, Svelte, and other Tailwind-compatible environments.

⚙️ Starting with Different Frameworks and Technologies

FlyonUI provides framework integration guides for multiple frameworks. Most contain manual setup instructions and starter kits. We’ll be using the Next.js starter kit for this tutorial.

NextJs starterkit github

✅ Steps:

Clone the FlyonUI Next.js starter project
Install dependencies:
```
npm install
```
Run the development server:
```
npm run dev
```

💡 New to FlyonUI? Watch the Getting Started with FlyonUI | Beginner’s Guide ⚡️.

How to Use FlyonUI Blocks

There are multiple ways to use FlyonUI Blocks:

1. Copy-Paste FlyonUI Blocks

You can use the Copy button in the code section to grab the HTML. However, if the block contains CSS or JS, you must copy and integrate those separately into your project.

2. Using Copy Prompt

This feature lets you copy a complete code block (HTML, CSS, JS) using a structured prompt — ideal for feeding into AI tools.

🧠 Let’s build the BBQ Restaurant Landing Page with the Copy Prompt Feature

The Copy Prompt feature is a game-changer. It helps you instantly copy a structured prompt to feed into your favorite AI tool.

🛠 How It Works

Visit 👉 FlyonUI’s Tailwind CSS Blocks.

Use the pre-built prompts to generate your website sections using AI tools like VS Code, Cursor, or Windsurf.