Compensation plan
Hybrid MLM Software
A hybrid plan runs two trees against the same people: a placement tree that pays on pairing and a sponsorship tree that pays on levels. Most hybrid disputes are not about rates — they are about which tree a bonus was calculated on.
What you get
Outcomes operators report after moving onto the platform.
Two trees, both authoritative
Placement and sponsorship are stored separately and in full. A bonus is never calculated against a tree it was not defined on.
Statements say which rule paid
Every line names its tree, its rule and its period. That single detail is what makes a hybrid supportable at scale.
Caps that hold across components
Per-component caps plus an optional total ceiling, so pairing and level payouts cannot combine into a ratio no one budgeted.
Plan structure
The placement shape this plan produces, drawn from its real width and depth rules.
Positions are placed in a width-capped tree for pairing, while a separate sponsorship tree records who enrolled whom. A distributor's two trees rarely look alike, and both are authoritative for different bonuses.
How the plan actually pays
A hybrid is not a third plan family. It is a binary and a unilevel running side by side against the same distributors, and the reason it needs saying that plainly is that the two trees genuinely differ.
The placement tree is width-capped, usually two wide. It decides pairing, carry-forward and cycles. Spillover means the people below you here may have been enrolled by someone else entirely.
The sponsorship tree has unlimited width and records who enrolled whom. It decides level commissions, matching bonuses and usually rank qualification.
A distributor with four personal enrolments has four frontline positions in the sponsorship tree and two in the placement tree. Both statements are true. Every bonus definition in the engine names which tree it is calculated on, because that is the question support will be asked.
The run order matters
Components are calculated in a fixed, versioned sequence:
- Volume aggregation — personal, group and leg volume for the period.
- Cycles on the placement tree, with carry-forward updated and caps applied.
- Level commissions on the sponsorship tree, after compression.
- Matching bonus, which depends on step 2’s output, so it cannot run earlier.
- Pools, which depend on total company volume and every prior step.
- Total cap, applied last, with the configured overflow behaviour.
Reordering steps 2 and 4 changes what people earn. Which is why the order is a versioned plan setting rather than an implementation detail — a recalculation of a period from last year runs against that period’s rules and reproduces its numbers exactly.
Configuration decisions to make before launch
- Which tree carries rank qualification. Group volume on the sponsorship tree is the common answer, with a per-leg cap and a placement-leg sponsorship requirement.
- Cycle rules, unchanged from a pure binary: pairing basis, carry-forward expiry, flush behaviour, cycle cap per rank.
- Level depth and rate shape on the sponsorship tree, gated by rank.
- Matching bonus base and rate. A percentage of frontline cycle earnings is standard; a percentage of their total earnings is much more expensive.
- Total cap and overflow destination, applied after all components.
- Statement layout. Every line labelled with its tree and rule, because a hybrid statement that only shows totals is unsupportable.
Modelling it before you commit
Model the components together. Run the cycle assumptions and the level table through the plan calculator separately to understand each, then add them and apply your total cap — the combined ratio is the only number that matters to your margin. If the total only works because the cap binds, say so in the plan document, because the cap is then doing the work distributors will attribute to the rates.
Commission mechanics
How money moves through this plan, rule by rule.
| Trees maintained | Two: a placement tree (usually binary) for cycle commissions, and a sponsorship tree (unilevel) for level commissionsBoth are stored in full. Neither is derived from the other. |
|---|---|
| Cycle commission | Paid on matched volume in the placement tree, with the same pairing, carry-forward and cap rules as a pure binary |
| Level commission | Paid on the sponsorship tree by level, so personal sponsoring is rewarded independently of placement |
| Matching bonus | A percentage of a personally sponsored distributor's cycle earnings, paid on the sponsorship tree — the usual glue between the two |
| Rank qualification | Typically group volume on the sponsorship tree plus a personal-sponsorship count in each placement leg |
| Statement reconciliation | One statement per distributor per period, with every line labelled by the tree and rule that produced it |
| Cap interaction | Caps apply per component and optionally to the total, so a global ceiling is enforceable across both trees |
| Run order | Deterministic and versioned: volume aggregation, then cycles, then levels, then matching, then pools |
At a glance
| Best suited to | Companies that want binary recruiting momentum without abandoning the reward for personal sponsoring |
|---|---|
| Typical payout ratio | 40% to 50% of sales volume — the highest of the plan families, because two components stack |
| Main design risk | Stacked components. Each looks affordable alone, and the total is what breaks the margin |
| Most common shape | Binary pairing plus five to seven unilevel levels plus a 10% to 20% matching bonus on frontline cycle earnings |
| Run frequency | Cycles weekly, levels and matching monthly, with the run order fixed and versioned |
Questions operators ask before they switch
Straight answers on plan mechanics, migration risk and compliance. If yours is not here, ask us directly.
Why keep two trees instead of deriving one from the other?
What makes a hybrid more expensive than its parts?
How do you cap a hybrid safely?
Can we start as a binary and add unilevel levels later?
Ready to Transform Your Direct Selling Business?
Send us your plan rules and we will run a live commission cycle against them, on your numbers, before you commit to anything.
- Configured in a sandbox before the call, usually within two business days
- No slide deck and no card — you watch your own plan pay out
- Your plan document stays confidential and is deleted on request
Prefer email? Write to us at sales@mlmsoftwarepro.com