Part of the guide: Network Marketing Lead Generation
Most small teams don’t have a CRM problem. They have a “nobody wrote it down” problem, and they go shopping for software hoping it will fix a habit.
I’ve been in this industry part-time since 2002. In that time I’ve watched a lot of good people buy a beautiful pipeline tool, spend a weekend building custom fields, invite five teammates, and then abandon it inside a month — because the system asked them for more than the business was producing. A CRM that takes ten minutes per contact will lose to a notebook every single time.
So here’s the version that survives contact with real life: a setup a team of two to ten people can stand up in an afternoon and still be using next year.
In this guide
- First, get honest about what a CRM is for
- Step 1: Write the stages before you touch software
- Step 2: Pick the fields — then delete half of them
- Step 3: One tool, one owner, one source of truth
- Step 4: Handle the ownership question before it becomes a fight
- Step 5: Build the compliance layer into the fields
- Step 6: The daily loop
- Step 7: The weekly review — three numbers only
- Your first 30 days
First, get honest about what a CRM is for
A CRM does exactly three jobs:
- It remembers who you talked to.
- It remembers what happened.
- It tells you who to talk to next, today.
That’s it. Forecasting dashboards, lead scoring, automation sequences — those are things you add after the three jobs are running. If you add them first, you get a beautiful database full of stale records and a team that quietly stopped opening it.
This is the same trap I wrote about in the complexity trap and the real customer: the system grows to satisfy the operator’s anxiety instead of the customer’s reality. Watch for it here. The moment your CRM setup takes longer to explain than to use, you’ve lost.
Step 1: Write the stages before you touch software
Open a blank page and write the actual path a person walks from stranger to customer or partner in your business. Not the path a sales book describes. Yours.
For most small teams it collapses to five stages:
- New — you have a name and a way to reach them.
- Contacted — you reached out; no real conversation yet.
- Conversation — they replied and you’re actually talking.
- Decision — they’ve seen the thing and are choosing.
- Customer / Partner / Not now
Five is a good ceiling. Every stage you add is a judgment call your team has to make correctly every time, and judgment calls are where data quality goes to die. If two people on your team would file the same contact differently, the stage is badly defined — merge it or rewrite it.
“Not now” matters more than people expect. It’s not a graveyard, it’s a queue. Most of the volume in a mature list lives there.
Step 2: Pick the fields — then delete half of them
Fields you actually need:
- Name
- Best contact method (and the handle itself)
- Source — how they came to you
- Owner — which teammate is responsible
- Stage
- Next action (a sentence)
- Next action date
- Notes (free text, append-only)
That’s eight. The last four are the engine; the first four are just filing.
Resist adding “temperature,” “score,” “personality type,” and “product interest” on day one. If you can’t point at a decision you’d make differently based on a field, the field is decoration. You can always add a field later — you can almost never get a team to backfill one.
One rule that saves a lot of pain: source is a fact, not a guess. “Instagram comment,” “referral from Maria,” “webinar replay.” Six months from now, source is the field that tells you where to spend your time, and it’s worthless if people freelance the values. Write the allowed list down.
Step 3: One tool, one owner, one source of truth
Pick the cheapest tool that does stages, a next-action date, and shared access. A free tier of a mainstream CRM is fine. A shared spreadsheet with those eight columns is genuinely fine for a team under five people — I’d rather see a spreadsheet used daily than a platform used never. If you want to know what I actually use and pay for, it’s on my recommended products page rather than buried in a post.
Then name one person as the system owner. Not the top producer — whoever is most annoyed by mess. Their job is small: enforce the stage definitions, kill duplicate records weekly, and be the only person allowed to add a field.
And commit to one place. The most common failure I see isn’t a bad tool, it’s four tools: contacts in the phone, notes in a messaging app, follow-ups in a paper planner, and a spreadsheet nobody’s opened since spring. Pick one. Move everything. Accept that the migration afternoon is boring.
Step 4: Handle the ownership question before it becomes a fight
On a team, one question will cause more damage than any software decision: who owns this contact?
Decide the rule in writing, now, while nobody’s emotional:
You have been paid late before
You have watched the number on the dashboard not match the number in your account. What is different now is simple: it settles on a public contract you can check yourself, not a dashboard I control.
Read the contract →Most participants earn little to nothing. No income is guaranteed. You can verify every payout on the public smart contract.
- Whoever entered the contact owns it.
- Ownership transfers only with a note in the record.
- Nobody contacts another person’s record without asking.
- A contact with no touch in X days returns to the shared pool (pick your X — 90 days is a reasonable default).
Write it in the same document as your stage definitions. Small teams almost never lose over strategy. They lose over two people messaging the same prospect in the same week.
Step 5: Build the compliance layer into the fields
This is the part most CRM tutorials skip, and it’s the part that costs money.
If you email people, the CAN-SPAM Act applies — it requires accurate header and subject-line information, an unsubscribe mechanism, and honoring opt-outs promptly. The FTC’s own compliance guide is worth twenty minutes of your time: CAN-SPAM Act: A Compliance Guide for Business. Note that the FTC states each separate violating email can carry a penalty — this is not a “we’re too small to matter” area.
If you or your team cold-call, the Telemarketing Sales Rule and the National Do Not Call Registry are in play. Start with the FTC’s guidance: Complying with the Telemarketing Sales Rule.
And if you’re in network marketing specifically, read the FTC’s business guidance concerning multi-level marketing, which covers income representations and what your team says in writing. Your CRM is where those written claims get stored and repeated.
Practically, this means three more things in your record:
- Consent — how and when they agreed to hear from you.
- Opt-out — a flag that removes them from everything, permanently, no exceptions.
- Do-not-call — separate from opt-out, if you dial.
Make opt-out a hard stop your team physically can’t override. That single design choice prevents most of the behavior that shows up on my MLM red flags list.
Step 6: The daily loop
The whole system reduces to one habit:
Open the CRM. Filter to “next action date is today or earlier.” Work the list. Before closing any record, set the next action and the next date.
A record without a next action is not a lead. It’s a memory.
Fifteen minutes, same time daily. If a teammate can’t do fifteen minutes, they can’t do the business — and that’s useful information to have early. If the fifteen minutes keeps sliding, the problem usually isn’t discipline; it’s that the workload was never sized for a real week, which is the burnout mechanic I unpack in how to avoid entrepreneur burnout.
Step 7: The weekly review — three numbers only
Once a week, as a team, look at:
- New contacts added (input)
- Conversations started (activity)
- Stage-to-stage movement (throughput)
Not revenue. Revenue is a lagging number and it makes people panic at the wrong moment. If contacts added is healthy and conversations started is flat, your outreach is broken. If conversations are healthy and nothing moves to Decision, your presentation is broken. The CRM’s real value is telling you which thing is broken instead of letting you guess.
This is also where you notice quality. A pipeline full of people who said yes to be polite looks identical to a real one on a dashboard — until nothing converts. Fixing that is an upstream problem, and it’s mostly about who you’re talking to in the first place; I covered that in recruiting professionals.
Your first 30 days
Week one: write stages and ownership rules, pick the tool, migrate contacts. Week two: everyone runs the daily loop, nobody adds features. Week three: first weekly review, fix the definitions people got wrong. Week four: now consider one automation — usually a follow-up reminder or a simple email template.
That order is the whole trick. Habit first, structure second, automation third. Reverse it and you’ll be shopping for a new CRM by autumn.
If you’re building the rest of your system around this and want the sequence I’d follow, start here.
Three posts a day. One email a day.
Everything I publish, in one short daily email. Real numbers, no hype, unsubscribe in one click.
Get paid 100%, on-chain, the second the sale clears
Most affiliates earn little, and that is disclosed up front. The difference here is not a promise about what you will make. It is that you can verify every payout yourself, on a public contract, in about twelve seconds.
See how the payout works →Most participants earn little to nothing. No income is guaranteed. You can verify every payout on the public smart contract.
Reading the ‘30-day sequence’ at the end made me think about how my bike shop’s repair queue evolved the exact same way — first just a whiteboard, then a rule about writing the customer’s name AND the bike’s actual problem instead of just ‘brakes,’ then eventually a proper board. Habit first, structure second, automation third is just… how anything that survives gets built, isn’t it? Not just CRMs.
Declan, what you’re circling is basically the shaping principle from behavioral psychology — reinforce the small correct behavior before layering complexity on top of it. The post’s ‘habit first, structure second, automation third’ sequence is that principle applied to team process rather than individual behavior, which is a less obvious application than the usual habit-book framing.
Philip, I’d add one more layer underneath the psychology of it: sequencing this way is also just honest. Building automation before the habit exists is building on a foundation you haven’t tested yet, and pretending otherwise because it looks more impressive to a new teammate is its own small dishonesty, even if nobody would call it that.
Five stages, eight fields, one owner — fine. Nobody asks what happens when the ‘system owner’ quits. Somebody always does.
The bit that stood out to me as the actual automation-ready part is Step 7 — three numbers, counted by hand, every week. I built a script that pulls those three counts straight from my sheet and posts them to the team chat every Monday morning before anyone’s awake enough to argue about them. It doesn’t replace the review conversation the post describes, it just removes the ten minutes of manually counting rows, so the fifteen-minute review is actually fifteen minutes of talking about what the numbers mean instead of producing them in real time in front of everyone.