How to choose MLM software: a buyer checklist for US companies

How to read this checklist

This guide is written for founders and operators in the United States evaluating MLM software, whether you are launching a new company or replacing a platform that no longer fits. It is organized as a working checklist: score every vendor against each section, and weight the sections that match your situation. Vendors that dislike these questions are telling you something.

We build custom MLM software, and this checklist is the same one we would hand you before signing with anyone, including us. The goal is that whoever you choose, you choose with open eyes.

Compensation plan support

The single most common failure in MLM software projects is a plan mismatch discovered after signing. Before you evaluate anything else, write your plan down in one page: structure (binary, unilevel, matrix, hybrid), every bonus type with its formula, rank requirements, caps, carryover rules, and how returns and chargebacks affect previously paid commissions.

• Does the platform calculate every bonus type in your plan natively, or does anything require custom code, and who pays for that code?
• Ask for a sample commission statement from a real customer running your plan type. Not a demo data statement: a real one.
• If your plan is hybrid, ask how volume is attributed once and reused across bonus types. Double attribution bugs are expensive.
• Ask what happens when an order is refunded after a run closes. The answer should be a clawback in the next run, with an audit trail.

Ecommerce and integrations

If you sell physical product, the storefront and the compensation engine must agree on volume, tax and inventory. If you already run Shopify or WooCommerce, ask exactly how the integration attributes distributor sales to the tree, and how it handles guest checkout by a customer referred through a replicated link.

• Native integration versus middleware: which is it, and what breaks when the cart platform changes its API?
• Sales tax: does the platform compute nexus based US sales tax itself, integrate a service, or leave it to you?
• Payment processing: which processors are supported, and who owns the merchant account?
• Autoship: can distributors manage their own subscription changes without a support ticket?

Commission engine transparency

When a distributor disputes a commission, support needs to see the math. Black box engines turn every dispute into an engineering ticket.

• Can you open any single payout and see the volume, rank and bonus lines that produced it?
• Are commission runs reproducible: locked periods, identical results on re-run?
• Can you run a shadow commission run against next period's plan changes before activating them?
• Is there a sandbox where you can enter test orders and watch payouts calculate?

Hosting, security and data ownership

MLM databases hold Social Security numbers, tax IDs and bank details for your entire field. Treat the vendor's answers here as pass or fail.

• Where is data hosted, and is it encrypted at rest and in transit?
• Who holds encryption keys, and what is the breach notification process?
• Is SSO or at least enforced 2FA available for corporate users?
• Can you export the full database (distributors, orders, commissions) in a usable format at any time, without a professional services engagement?
• Is there a documented RPO and RTO for backups and disaster recovery?

Mobile apps

Distributors live on phones. A responsive website is table stakes; an app with push notifications, rank progress and one tap sharing is a growth tool.

• Is the app native, React Native or Flutter, or a web wrapper?
• Whose app store accounts publish it, and what is the update cadence?
• Does the app show the same commission data as the web back office in real time?

Migration risk

If you are replacing an existing platform, migration is the riskiest part of the project. Ask for the migration plan in writing before signing.

• Who owns the export from your current vendor, and is it complete (genealogy placement, not just sponsorship)?
• How is historical commission data handled: migrated for statements, summarized, or dropped?
• Is there a parallel run period where both systems calculate commissions and you compare results?
• What is the rollback plan if the parallel run disagrees?

Our migration guide covers the process end to end, including the placement versus sponsorship trap that breaks most binary migrations.

Pricing models and what they hide

MLM software pricing generally falls into three models.

Model	Typical range	Watch out for
Licensed SaaS	1,000 to 10,000 dollars setup plus 500 to 5,000 dollars monthly	Per distributor fees that scale with your success, and custom plan work billed hourly
Custom build	12,000 to 120,000 dollars plus ongoing maintenance	Scope creep on plan edge cases; unclear ownership of source code
Revenue share	Low upfront, percentage of sales	Long term cost exceeding a build, and exit clauses that lock you in

Ask every vendor: what costs extra? Plan changes, additional bonus types, app store releases, support tickets, and data export are the usual suspects. Our pricing page publishes the ranges we see across the market.

Red flags

• A demo that only shows happy path data, with no errors, no disputes, no refunds.
• No written commission calculation documentation, only a demo.
• "We can build that" for every request, with no estimate or timeline attached.
• Source code ownership that stays with the vendor even after full payment.
• References only from companies you cannot verify, or testimonials without named companies.
• Pressure to sign within days, framed as a discount deadline.

Questions to ask references

Ask for three references running your plan type for at least a year. Ask them: what broke in the first six months, how long support takes to respond during a commission run, what they would negotiate differently, and whether payouts have ever been wrong and how it was handled. Honest answers to the last question matter more than the answer itself.

The five questions that end a vendor call early

Scorecards are patient; your calendar is not. These five questions, asked verbatim in the first call, filter faster than any checklist because weak vendors answer around them.

1. "Show me a commission statement from a customer running my plan, with one line opened to its volume and rank detail." No statement, no second call.
2. "What did your last commission day incident look like, and how long to resolution?" A vendor with no incident story is either new or not telling you things.
3. "Price me a data export and a plan change today." Verbal answers do not count; ask for the email.
4. "Who exactly, by name and role, delivers my implementation?" Teams that cannot name the engineer name the account manager instead.
5. "What did you tell the last prospect you declined?" A vendor that has never declined anyone has never evaluated anyone.

None of these are hostile; they are the questions your future self, mid outage or mid migration, will wish had been asked. Good vendors enjoy them.

Scoring the shortlist

Score each vendor from 1 to 5 on: plan fit, engine transparency, ecommerce fit, security, mobile, migration plan, total cost over three years, and reference quality. Weight plan fit and engine transparency highest; they are the two you cannot fix later without a replatform. Then bring the top two into a paid pilot or a shadow commission run if the vendor offers one. The pilot is where marketing claims meet actual arithmetic.

If it would help to talk through your shortlist with a builder rather than a seller, contact us; we will tell you honestly when a licensed platform fits you better than a custom build.