Network Marketing Plan: The Two Things It Can Mean

This phrase covers two entirely different documents, and searches for it come from people looking for either one.

The company’s compensation plan governs how money is calculated: volume, components, ranks, payout rules. A distributor’s own working plan governs what they do on a Tuesday. They share almost nothing, and confusing them produces a familiar failure — a distributor who can recite the rank chart in detail and has no plan for the week.

Both are below. Take whichever one you came for.

Part one: the company plan document

The six sections it needs

Most published plans have three of these. Every dispute a company has comes from the other three.

1. Definitions. What volume is, and how many kinds you hold. Most working plans need at least two per product: commissionable volume, which decides how much commission an order generates, and qualifying volume, which decides whether it counts toward a rank or activity threshold. They differ deliberately — a starter kit often qualifies but pays little, a discounted bundle often pays but does not qualify. Holding one number for both means answering one of those questions wrongly.

2. The components. Each one, with what it pays on and at what rate. Named by what it is calculated from, so the vocabulary stays consistent across the document, the statement and the training material. See commission versus bonus versus incentive — the naming matters more than it sounds once reporting is involved.

3. Ranks. Exact thresholds, and how they are measured. “Team volume of 10,000” is incomplete: over what window, counted from which tree, compressed or not, measured at close or at any point in the period. Each of those choices produces a different rank chart from the same numbers.

4. Resolution order. When two components apply to the same volume, which resolves first. Almost never published, and it changes results rather than presentation. Covered in commission structure.

5. Caps, and cap overflow. Per component, per position, per period — and where the excess goes when a cap binds: discarded, carried forward, or into a pool. Undefined overflow is a payout decision the software makes by accident.

6. The edge cases. This is the section that is missing, and it is the cheapest one to write:

• A return processed after the commission on it was paid.
• A rank achieved, then lost the following period — is the bonus per achievement or per maintenance?
• A payout calculated but rejected by the bank. This is a payment state, not a commission adjustment; conflating them breaks reconciliation.
• Termination with a positive wallet balance, and what happens to open lines beneath.
• Volume from a product withdrawn mid-period.
• A distributor who moves market mid-period.

Six paragraphs. Every one of them will happen, and each is far cheaper to define now than after a specific person is affected, because by then whatever you decide looks like it was decided about them.

Versioning, which is not optional

Publish the plan however you like — PDF is fine. What matters is the discipline around it:

• each version carries a number and an effective date,
• superseded versions remain retrievable,
• the platform records which version each distributor accepted at enrolment,
• a commission run stores the rule set that produced it, rather than pointing at whatever the current configuration happens to be.

That last point is what lets you answer a question about March in April. Without it, any plan change makes every prior period unreproducible. A plan document with no version and no effective date is the cheapest compliance failure available, and it is discovered at the worst possible moment.

A presentation is not the plan

Companies build a plan presentation for recruitment and then let it drift from the governing document. Within a year the field is being taught rates that no longer apply.

The fix is procedural rather than technical: the presentation cites the plan version it was built from, and it gets reissued when the plan does. Anything in the presentation that does not appear in the plan document is not a rule, and anyone teaching it is creating an expectation you will be asked to honour.

Part two: your own working plan

If you are a distributor, this is the document that actually determines your outcome, and it is usually the one that does not exist.

Write activities, not income

The common failure is setting a monthly income figure and working backwards. It fails because income is an outcome you do not control, so a shortfall has no corresponding action — you can only feel bad about it.

Activity is an input you do control. A workable plan states:

• how many people you will speak to in a week, as a number,
• how you will follow up, and after how long,
• what you do with a customer who does not reorder — the highest-value activity in this business and the most neglected,
• how much of your own money is at risk, with a written limit,
• when you review, and against what.

The review is where the plan earns its value

Once a month, three honest numbers:

1. How many conversations did I actually have, against the number I planned?
2. What proportion became customers?
3. What did I spend, including product I bought for myself?

The third one is where most people stop being honest. Product bought to hit a qualification is a cost, not a sale, and counting it as inventory rather than expense is how a plan looks profitable for a year. If a rank required stock you did not need, that is data about the plan, not about your effort.

On planners and templates

Printed planners and downloadable templates are fine and none of them are necessary. A plan that fits on one page and gets reviewed monthly beats a system that gets abandoned in March. What matters is that the numbers are yours rather than a template’s defaults.

If you are evaluating an opportunity rather than working one, read is MLM profitable first — the published income disclosures are the most useful input to a personal plan, and they are the least read.

If you are building the plan the software has to run

The plan document and the platform configuration should be the same rules, expressed twice. When they diverge, the software wins — it is what actually pays people — and the document becomes fiction.

That is easier to maintain when plan rules are configuration rather than code, so a change is a dated configuration change rather than a development ticket and a quotation. The compensation plan software page covers what that requires, and compensation plans compared covers choosing the shape before you write any of it down.