About us
We build the part of a direct selling company that has to be right
Commission runs, genealogy and compliance reporting are the three systems a direct selling company cannot afford to get wrong. We have built them since 2016, for operators in the United States and South Africa.
Why this company exists
Direct selling has a software problem that is really a credibility problem. Vendor demos show a genealogy tree rotating on a screen and never once show a commission run. Plan rules get configured in a spreadsheet and reconciled by hand at period close. Migrations arrive with the tree intact and the sponsor history gone — which nobody notices until a matching bonus is disputed nine months later and the input no longer exists.
None of that is a technology limit. It is what happens when a platform is sold on how it looks instead of on what it can reproduce. So we took the opposite position: publish the mechanics. Every plan page on this site states the placement rule, the payout trigger and where that plan family goes wrong. Every comparison records only what a competitor documents publicly, with the date we checked it. The plan calculator runs the payout maths in your browser and tells you when a ratio is unfundable.
That is not transparency as a value statement. It is that an operator choosing a commission engine has to be able to judge the vendor before the sales call, because the cost of finding out afterwards is a year of disputes nobody can resolve.
What we actually build
Six things, on one data model. The list is short because these are the parts that decide whether a platform survives its second year.
Commission engines
Deterministic runs against a recorded rule version, so a closed period reproduces the amounts that were actually paid — after the plan changes, after a rank is renamed, two years later.
Genealogy at scale
Sponsor and placement stored as separate timestamped facts, every override written to an immutable log, and accurate drill-down at six figures of nodes rather than a paginated table.
Plan modelling before launch
The payout ratio your plan produces at realistic depth, tested against your gross margin, before anyone writes code. Most unfundable plans are discoverable in an afternoon and are instead discovered after launch.
Migrations off legacy platforms
Sponsor history, placement history and closed-period reproducibility carried through the move. Where the old system cannot produce them, we say so before the contract rather than after the cutover.
Storefront and payment integration
Shopify, WooCommerce, Magento and OpenCart keep the catalogue and the checkout. We take over order classification, volume, qualification, commission and payout.
Compliance reporting
Retail-versus-participant classification at the point of order, the ratio reported per period and per market, and buyback and clawback handling that reverses commission in the period it belonged to.
How an engagement runs
Five stages, and the order matters — the expensive mistakes all come from configuring an engine before the plan has been costed.
Plan review and payout modelling
You send the plan document, or a description if it is not written yet. We model the commission ratio it produces at realistic structure depth, against your product margin, and tell you what it costs to fund. This is the stage that occasionally ends with us recommending a different plan family.
Rule specification
Every mechanic written down as something the engine can execute: qualification thresholds, paid depth, compression behaviour, caps, carry-forward and flushing, clawback handling. Ambiguity here becomes a dispute later, so nothing stays in prose.
Sandbox and parallel run
Your rules configured in a sandbox and run against sample or your own historical volume. If you are migrating, the new engine runs in parallel with the old one and is reconciled to the cent before anything is cut over.
Data migration and cutover
Genealogy, sponsor and placement history, orders, balances and closed-period records moved with a reconciliation report on each. Cutover happens between commission periods, never inside one.
Operate and extend
Period-close support, rule changes versioned so old runs still reproduce, and new markets, plans or integrations added against the same data model rather than as a second system.
What we will not do
Every item below is checkable against this website, which is the only reason it is worth stating.
No invented social proof
The trust strip on our homepage is empty and stays empty until we hold an award, a membership or a press mention that is real and verifiable. Industry logos are third-party marks, and borrowing them is precisely the credibility failure this industry is known for.
No ratings we cannot audit
This site emits no aggregateRating and no review markup, because we hold no audited corpus of submitted reviews. Star ratings in search results are trivial to fabricate, which is exactly why we publish none.
No competitor claim we cannot cite
Comparison pages record what a vendor documents publicly, with the date checked. Where we found no public statement either way the cell reads “not documented” rather than “no”, because absence of documentation is not absence of capability.
No legal assurance and no income claims
We sell software. We do not operate a direct selling business, recruit distributors, or represent what anyone can earn. We will not tell you your compensation plan is lawful — that is your counsel's judgement, and a vendor who offers it is selling you a false comfort.
Company facts
The verifiable ones. Anything absent from this table is something we are not yet prepared to claim.
| Building direct selling software since | 2016 |
|---|---|
| Markets served | United States and South AfricaChosen rather than assumed. The USA brings FTC disclosure duties and state tax nexus; South Africa brings Consumer Protection Act s.43 and POPIA. Both are in the platform rather than bolted on per client. |
| Site languages | English, with Afrikaans structurally supported |
| Typical implementation | $4,900 – $49,000Prices shown are typical ranges for scoping purposes and are not a quote. Your figure depends on plan complexity, integrations, migration scope and market count. |
| Third-party trackers on this site | NoneNo analytics, no advertising pixels, no third-party fonts, no cookies set by this site. Open your browser's network tab and check. |
| General enquiries | hello@mlmsoftwarepro.com |
| Demos and pricing | sales@mlmsoftwarepro.com |
Frequently asked questions
Straight answers on plan mechanics, migration risk and compliance. If yours is not here, ask us directly.
Do you operate a direct selling company yourselves?
Do you work with pre-launch companies or only established ones?
Who owns the data and the code, and what happens if we stop working with you?
Why does a software vendor publish this much plan detail publicly?
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