Add leaders' objection-handling section to /tools
Six common recruiting objections as native <details> accordions (CSP-safe, no inline JS), each with an honest 'the truth' mechanics note plus a copy-ready 'say this' reply. Keeps team leaders accurate (spillover fills the matrix but never qualifies; upgrades optional; verify on-chain) and never promises income. Standalone team-resources/objection-handling.md kept in sync. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,139 @@
|
||||
# RM Circle Team Build — Objection-Handling Script
|
||||
|
||||
A reusable playbook for the objection every builder eventually hears:
|
||||
|
||||
> **"What if the two I bring in can't get their own two? Then it just stops there."**
|
||||
|
||||
The power move is never a theory speech — it's showing the person **their own leg**
|
||||
(or a real one) where it already happened. Below: the honest mechanics so you never
|
||||
say anything a prospect can poke a hole in, a fill-in-the-blanks response, and a
|
||||
worked example.
|
||||
|
||||
---
|
||||
|
||||
## The accurate mechanics (so you stay 100% truthful)
|
||||
|
||||
- **Qualification = 2 *personal* referrals.** Only people who join with a position's
|
||||
**own** referral ID count toward its 2/2. Each member must get their **own** two.
|
||||
- **Spillover fills the matrix, it does NOT qualify anyone.** When leaders above bring
|
||||
in more than two, the extra people are placed *down* the leg by the contract — that
|
||||
adds team depth and **can earn** the upline pass-ups when those people upgrade
|
||||
(payouts travel up the **placement/matrix** line). But spillover does **not** count
|
||||
toward the 2/2 of whoever it lands under. Don't promise it does.
|
||||
- **Depth pays.** Once a position is qualified, it keeps earning as its leg deepens and
|
||||
members upgrade — you catch pass-ups matched to your level. So the job is to help the
|
||||
leg go *deep*, not just wide.
|
||||
- **The leader's lever (when a leg is stuck):** you can **seed a new position** (a new
|
||||
wallet) under an *unqualified* direct, using **that direct's** referral ID — which
|
||||
helps qualify them. (Example: position #52 was placed under #35 to help #35 qualify.)
|
||||
You can also simply route a brand-new recruit through that leg's link (no extra cost).
|
||||
This is only needed for **unqualified** legs — a leg whose people already got their 2
|
||||
needs coaching, not money.
|
||||
|
||||
**Bottom line you can say out loud:** *"Everyone needs their own 2 — that part is real.
|
||||
But nobody does it alone: the team helps push legs that stall, and once you're qualified
|
||||
you keep earning as your team grows deeper."*
|
||||
|
||||
---
|
||||
|
||||
## The response framework (fill in the blanks)
|
||||
|
||||
1. **Validate, don't argue.** "That's a fair question — let me show you something real."
|
||||
2. **Point to live proof.** Pull up a position where the two directs already got their own
|
||||
two. Best if it's *their own* leg: *"Look — [#___] and [#___], the two [name] brought
|
||||
in, BOTH already got their own 2 and are qualified and building."*
|
||||
3. **Name the method.** "It's not luck. Get your 2, then help those 2 get theirs. That's
|
||||
the whole game — depth is what pays."
|
||||
4. **Show the team has their back.** "When a leg stalls, we push it together — that's what
|
||||
a team build *is*. You're never carrying it solo."
|
||||
5. **Reframe their results.** Give them their own numbers: qualified? total earned? team
|
||||
size? one step from the next level? Most discouraged builders can't see their own win.
|
||||
6. **Close to action.** "Bring your 2, then pour into helping THEM — stop chasing cold
|
||||
people who'll never move. Want to hop on a call and I'll hand you the exact words?"
|
||||
|
||||
**Guardrails:** never guarantee income; stick to on-chain facts (earned/qualified/team
|
||||
size are verifiable); if a leg genuinely has zero activity and no spillover, say so
|
||||
honestly and offer to help build it — don't pretend it auto-fills.
|
||||
|
||||
---
|
||||
|
||||
## Objection library (also live on /tools → "Objection handling")
|
||||
|
||||
Each: **the truth** (so you stay accurate) + **say this** (a ready-to-send reply).
|
||||
|
||||
**1. "If my two can't get their own two, doesn't it just stop there?"**
|
||||
- *Truth:* Everyone needs their own 2 personal referrals to qualify. Spillover fills the
|
||||
matrix and can earn you, but never qualifies someone for them. Answer = the method +
|
||||
a live leg where the first two already got theirs.
|
||||
- *Say this:* Fair question — but that's not how it plays out, because nobody builds alone.
|
||||
Get your two, then help those two get theirs. Your sponsor is paid as your team grows,
|
||||
so helping you win is literally their job — and when a leg stalls, the team steps in. It
|
||||
only stops if everyone quits helping, and that's the one thing a team is built to prevent.
|
||||
|
||||
**2. "Isn't this just a pyramid scheme or a scam?"**
|
||||
- *Truth:* Pyramid/Ponzi = a company holds deposits and pays old joiners from new joiners,
|
||||
nothing verifiable. Here no company holds funds; the contract pays peer-to-peer in the
|
||||
same tx; code + every payout readable on-chain. Real effort, real crypto risk — say so.
|
||||
- *Say this:* You should ask that. No company holds the money here — a smart contract on
|
||||
Polygon pays person-to-person in the same transaction, and you can read the code and
|
||||
every payout yourself. No pot of money to freeze or run off with. It's a team build with
|
||||
real risk, but the opposite of a black box. Verify it: rmcircle.team/contract
|
||||
|
||||
**3. "What if I bring people in and they quit or do nothing?"**
|
||||
- *Truth:* Positions live on-chain and don't vanish; team builds around a quiet spot; you
|
||||
need a few real builders, not volume.
|
||||
- *Say this:* Some go quiet — normal. But positions live on the blockchain and the team
|
||||
keeps building around them. You don't need everyone active; you need two who want it.
|
||||
Go deep with those two and the leg grows even when others sit still.
|
||||
|
||||
**4. "What if I can't afford the upgrades?"**
|
||||
- *Truth:* Upgrades are optional and self-paced; team income can fund them; never pressure
|
||||
anyone to overspend.
|
||||
- *Say this:* You're never on a clock, and never use money you can't afford to lose. Start
|
||||
comfortable; as your team grows, the payments coming in fund your next step up. Move at
|
||||
your own pace.
|
||||
|
||||
**5. "I'm not a salesperson and I don't know anyone."**
|
||||
- *Truth:* It's sharing a link + a short video; the site explains it; two people, not 200.
|
||||
- *Say this:* There's nothing to sell — you share a 60-second video and your link, and the
|
||||
site explains it. You need two curious people, not a big network. I'll hand you the words.
|
||||
|
||||
**6. "How do I know it's safe and won't rug pull?"**
|
||||
- *Truth:* No pooled treasury (same-tx disbursement) so nothing to abscond with; but
|
||||
smart-contract risk and volatility are real — point to the contract review + Polygonscan.
|
||||
- *Say this:* No pot of money for anyone to run off with — the contract pays out in the
|
||||
same transaction someone pays in. But any contract carries risk, crypto is volatile, and
|
||||
only use what you can afford to lose. Trust the code, not me: rmcircle.team/contract
|
||||
|
||||
**Leader guardrails:** never guarantee income; lead with a real on-chain example over any
|
||||
claim; if a leg has no activity, say so honestly and offer to help build it.
|
||||
|
||||
---
|
||||
|
||||
## Worked example (the message sent to #28, "Aku")
|
||||
|
||||
> Morning Aku 🙏
|
||||
>
|
||||
> First, real talk: I love how you're thinking. Asking "how do we keep this expanding?"
|
||||
> is exactly what a leader does. Let me answer both parts honestly.
|
||||
>
|
||||
> **Your re-entry idea:** you're onto something real. Opening a new position under an
|
||||
> active member is 100% allowed, and I already do it for the team. A leader re-entering
|
||||
> under the group *is* a real growth engine — good instinct. One tweak: reaching the top
|
||||
> level isn't a fixed headcount; you climb by upgrading, and the team's own activity pays
|
||||
> for those upgrades. The more we build, the more the top can climb and re-enter, which
|
||||
> feeds everyone below. It compounds.
|
||||
>
|
||||
> **Now the big one — "what if my 2 can't get their 2, it stops there."** Let me kill it
|
||||
> with your OWN account: #35 and #36 — the two you brought in — BOTH already got their own
|
||||
> 2, both qualified, both building. The exact thing your prospects swear is impossible
|
||||
> already happened right under you. That's how #35 got there — when his leg needed a push,
|
||||
> the team helped seed his second spot. Nobody builds alone.
|
||||
>
|
||||
> And give yourself credit: you're qualified, you've earned over 2,200 POL on-chain, you've
|
||||
> got 7 on your team, and you're one step from the next level. You're not failing — you're
|
||||
> winning. The people saying "it can't be done"? You're the proof it can.
|
||||
>
|
||||
> Your play: stop chasing a hundred cold people. Bring your 2, then pour into helping THOSE
|
||||
> 2 win — depth is what pays you. Let's jump on a call and I'll hand you the exact words to
|
||||
> answer that objection so it never slows you down again. You've got this. 🔥
|
||||
Reference in New Issue
Block a user