Part of the guide: Network Marketing Lead Generation
A solo CRM problem and a team CRM problem are not the same problem, and almost every “best CRM” article on the internet answers the first one while you’re living in the second.
Solo, the question is simple: will I remember to follow up on Tuesday? Once you have a team, the question changes shape entirely. Now it’s: do I know which of my twelve active builders actually talked to anyone this week, or am I taking their word for it on a Zoom? Are my leaders and I working the same prospect without knowing it? When someone quits, does their contact list walk out the door with them? I’ve been in this industry part-time since 2002, over twenty years of watching teams grow and shrink, and I’ll tell you plainly: the tool matters less than the structure you put inside it. But at team scale, a bad structure gets expensive fast.
Let me show you what that structure looks like, with real examples you can copy.
In this guide
- What actually breaks when you go from one person to a team
- Example 1: A shared pipeline with stages that mean something
- Example 2: Tags that let you run a team, not just a list
- Example 3: The leader’s weekly view
- Example 4: A follow-up cadence you can automate without becoming a robot
- Which tools fit which team size
- The compliance layer nobody sets up until it’s too late
- The honest limit of any of this
What actually breaks when you go from one person to a team
Four things, and they break in this order.
Visibility dies. You genuinely cannot tell activity from busyness anymore. A leader “on fire” and a leader avoiding the phone look identical on a group call. Both are enthusiastic.
Duplication starts. Two reps message the same prospect from the same team in the same week. The prospect notices. It reads as a machine, not a person.
Data leaks. Reps keep contacts in their own phone. Someone leaves, and six warm relationships leave with them, along with any hope of a clean handoff.
Compliance goes unmanaged. One rep writes an income claim into a follow-up template, and now that template is running on autopilot to a few hundred people with your name on the top of the org.
A CRM doesn’t magically fix these. A CRM is just the place where you decide how they get handled once, instead of re-deciding badly twelve times.
Example 1: A shared pipeline with stages that mean something
Most teams set up a pipeline with stages like “Interested,” “Very interested,” “Super interested.” Those are feelings, not facts, and they can’t be verified.
Build stages around events that either happened or didn’t:
- Added — name is in the system with a source (event, referral, DM, ad).
- Reached out — first message or call actually sent, dated.
- Conversation had — two-way exchange, not a monologue.
- Exposed — they saw the tool, the video, the call, the sample.
- Follow-up scheduled — a specific date exists.
- Decision — yes, no, or “not now, revisit [date].”
- Onboarding — first 30 days, separate pipeline.
Notice that every stage has a binary test. There’s no arguing about whether stage 4 happened. That’s the point. When a leader tells me the team is “working hard,” I don’t argue — I look at how many names moved from 2 to 3 this week. Movement between those two stages is the whole business. Everything before is list-building; everything after is momentum.
Example 2: Tags that let you run a team, not just a list
Contact tags are where team CRMs earn their money. A workable minimum set:
source:—event,referral,ad,dm,warmowner:— which rep holds the relationshiptype:—customer,builder-curious,pro(see my case for why you should recruit professionals rather than whoever answers first)status:—active,dormant,do-not-contactrevisit:— a date, not a vibe
The owner: tag alone kills the duplication problem. The do-not-contact tag is not optional — it’s the thing that keeps a “no” from getting messaged again by a new rep in eight months, which is how teams build reputations they can’t shake.
And here’s the tag most teams never create: customer-only. If you can’t pull a clean list of people who buy your product with no interest whatsoever in the business, you may not have a real customer base. That’s a structural issue I’ve written about in the complexity trap and the real customer question, and no CRM will hide it from you — which is exactly why you want it visible.
Example 3: The leader’s weekly view
Here’s the report I’d want on a Monday morning, and every decent CRM can build it:
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.
| Metric | What it tells you |
|---|---|
| New contacts added, by rep | Is the top of the funnel alive? |
| Stage 2 → 3 movement | Real conversations, not just sends |
| Follow-ups overdue | Where money is currently leaking |
| Contacts with no next action | Names quietly rotting in the database |
| Customers reordering vs lapsed | Whether the product actually holds people |
That last row is the one most teams never track, and it’s the most honest number in the business. Recruiting can be inflated by excitement. Reorders can’t.
Example 4: A follow-up cadence you can automate without becoming a robot
The mistake is automating the relationship. Automate the reminder instead.
- Day 0: personal message, manual, from the owner.
- Day 2: automated task fires — “call [name].” The call is human; only the nudge is automatic.
- Day 5: if no response, one value-first message. Not a pitch. Something useful.
- Day 12: last touch. “Should I close your file or check back in the spring?”
- No answer: move to
revisit:with a date six months out. Not deleted. Not pestered.
Every step there is a human sending a human message. The software’s only job is making sure the day doesn’t slip. That’s a genuinely different design philosophy from the “set up 47 automations” approach, and it holds up better with prospects who can smell a sequence from a mile away.
Which tools fit which team size
I’m deliberately brief here, because tool choice is the least important decision on this page.
- 2–5 people: a shared Google Sheet with the columns above, plus everyone using their own free HubSpot or Zoho seat. Prove the discipline before you buy anything.
- 5–25 people: a proper CRM with shared pipelines and per-owner records — Pipedrive, Zoho, or Freshsales all do this well and cheaply. Network-marketing-native options like Penny speak your language out of the box.
- 25+ with real volume: an all-in-one like GoHighLevel starts to earn its cost, because you’re now managing email, SMS, pipelines, and onboarding in one place. Below that scale it’s usually an expensive way to feel productive.
Verify current pricing on the vendors’ own pages before you commit; it moves constantly. If you want my broader take on the software I actually think is worth paying for, it’s on my recommended products page.
The compliance layer nobody sets up until it’s too late
This is the part that only becomes real at team scale, and it’s worth getting right.
When your CRM sends commercial email on behalf of a team, the CAN-SPAM rules apply — accurate headers, a real physical address, a working unsubscribe honored within ten business days. The FTC’s CAN-SPAM compliance guide lays it out in plain language. Build the suppression list into the CRM itself so an unsubscribe in one rep’s account is respected across the whole team.
If your team calls or texts cold lists, the Telemarketing Sales Rule and Do Not Call obligations are in play; the FTC’s telemarketing compliance guidance is the primary source, not whatever a leader said on a training call.
And on the messaging inside your templates: the FTC’s business guidance concerning multi-level marketing is explicit that companies and participants shouldn’t make misleading income representations. Your CRM is the single best place to control this, because templates are reviewable and one-off DMs aren’t. Lock the templates. Review them quarterly.
If reading that guidance makes you uneasy about your own opportunity rather than just your copy, that’s worth sitting with — I’ve listed the red flags I watch for separately, and the reasons I stepped back from network marketing seriously are largely structural, not emotional.
The honest limit of any of this
A CRM makes a working team more efficient. It makes a broken team visibly broken faster, which is useful but rarely welcome. It will not create belief, it will not fix a product nobody reorders, and it will not make a compensation plan pay what it doesn’t pay.
What it will do is remove the excuse. Once every contact has an owner, a stage, and a next action with a date, the only remaining variable is whether people do the work. That clarity is uncomfortable, and it’s exactly what most teams are unconsciously avoiding when they spend three weeks choosing software.
Set up the pipeline in the first example this week. Add the tags from the second. Run the Monday report from the third for four weeks and don’t flinch at what it shows you.
If you want the ground-level version of how I think about building this whole thing — where the leverage actually is and what I’d skip entirely — 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.
The tag list in Example 2 is exactly the kind of thing I’d spend three weekends ‘setting up properly’ before I contacted a single person. I don’t have a CRM problem. I have a starting problem with a CRM-shaped disguise.
Davey. A CRM won’t fix over-preparing. It just gives you a cleaner place to hide from the phone call. Same avoidance, better spreadsheet.
Davey, the reason the binary-stage design in Example 1 might actually help your specific failure mode: it removes the judgment call. ‘Reached out — dated’ either happened or it didn’t, so there’s nothing left to perfect before you’re allowed to log it. Over-preparation has less to attach itself to on a yes/no field than it does on a feelings-based stage like ‘very interested.’
Twenty-two years of corporate life and I sat through more ‘weekly view’ dashboards than I can count, and this one is better than nearly all of them, for one reason: every metric in that table is falsifiable. My old employer had a metric called engagement, which meant whatever the slide needed it to mean that quarter, and nobody below director level was ever allowed to ask how it was actually calculated. Stage 2 to 3 movement can’t be gamed the same way — either the conversation happened and got logged, or it didn’t. I spent two decades managing people against numbers that mostly existed to justify decisions already made elsewhere. This is the first version of ‘track your team’ I’ve read that would have told my old boss something true.
Graham, we called this exact idea something else back in ’94 — index cards in a shoebox. Same rule: an event either happened or it didn’t. The software’s changed four times since then. The rule hasn’t moved an inch.
The 5-25 person tier recommends Pipedrive, Zoho or Freshsales ‘cheaply’ with no price given, and the 25+ tier says GoHighLevel ‘starts to earn its cost’ with no cost stated either. Two tiers, zero numbers. What’s the actual monthly spend at each size, roughly?
The whole cadence in Example 4 assumes a comfort with direct messaging that I don’t have and don’t want to build. I’ve never DM’d a stranger in my life and my audience still grows. Nothing here accounts for someone built by writing rather than by reaching out first.
Sorry if this is a silly question, but if building an audience through writing works without ever messaging anyone first the way Anneke describes, does the customer-only tag from Example 2 still apply the same way, or is that whole tracking system really built assuming you’re the one reaching out every single time?
Anneke, same conclusion, different reason. Twelve-hour night shifts don’t leave room for a Day 0 personal message, a Day 2 call, and a Day 5 follow-up. The cadence isn’t wrong. It’s built for someone with more hours in a day than I currently have.