Skip to content
Regen Web3 Toolkit

Onboarding New Members to Your Local Node

Onboarding New Members to Your Local Node

Section titled “Onboarding New Members to Your Local Node”

Forty people RSVP’d to your launch event. Twelve showed up. Three came back. By month three, you’re running the whole thing yourself and wondering why you bothered. If you’ve ever stood in a half-empty room after a strong launch, you already know the real problem isn’t getting people in the door. It’s what happens in the days after.

Most local nodes don’t fail because the tech broke or the grant ran out. They fail because new people arrive, feel like strangers, and quietly drift away. The work of finding people is wasted if the work of keeping them never happens. This is the part nobody puts in the pitch deck, and it’s the part that decides whether your node grows or whether you end up doing everything alone.

A local node (a place-based chapter of a larger regenerative or ReFi, regenerative finance, network) lives or dies on this. Your job as a steward isn’t to onboard everyone yourself. It’s to build a system where the community onboards each other, so you don’t become the bottleneck you set out to replace.

Onboarding Is a Trellis, Not a Funnel

Section titled “Onboarding Is a Trellis, Not a Funnel”

Marketing teaches you to think in funnels: pour leads in the top, squeeze conversions out the bottom. That framing quietly poisons community work. A funnel treats people as throughput. A community is a garden, and what new members need isn’t pressure. It’s a trellis: a structure to climb that’s already there before they arrive.

The trellis is the difference between “we’ll figure out what to do with newcomers when they show up” and “we know exactly what the first 30 days feel like for someone who joins tomorrow.” You build it once. It works while you sleep. And it’s the only version of onboarding that doesn’t require you personally for every single new face, which is the only version that survives contact with your own limited time.

ReFi DAO’s Local Node program, which has incubated chapters across more than 20 countries, came to the same conclusion. Its node-maturity model (Seed, Sapling, Canopy) describes exactly this kind of growth. A Seed node is still building its core team; a Sapling has active engagement and real projects; a Canopy node is mature enough to “provide shelter and support” to others. New members are seedlings. Your onboarding system is what gives them something to grow up.

The First 90 Days Decide Everything

Section titled “The First 90 Days Decide Everything”

If you remember one thing, remember this window. Across volunteer and membership research, the pattern is consistent: people who don’t form a real connection early are much more likely to leave. One membership-sector analysis puts members who don’t engage in their first 90 days at 60 to 70% more likely to be gone by renewal time. Early dropout is almost never a motivation problem. People showed up motivated. It’s an onboarding problem.

The single highest-leverage move is also the oldest: a buddy, pairing each newcomer with one existing member whose only job is to make them feel known. The evidence is strong. Microsoft’s onboarding-buddy program found new hires with a buddy were 23% more satisfied with onboarding in their first week, rising to 36% more satisfied by 90 days, and organizations that run buddy systems report higher new-member retention. Treat the exact percentages as directional, not gospel (they come from corporate HR contexts), but the direction is solid and it’s free.

One concrete test from volunteer research: does a newcomer leave their first event knowing at least one other person’s name? If yes, they tend to come back. If no, they tend not to. That’s a bar you can actually design for.

🔧 For Practitioners: Make the buddy assignment a visible, low-status, rotating role, not a favor you beg for. A simple shared sheet (“this week’s welcomers: Ana, Marcus”) works better than a heroic volunteer coordinator, because it spreads the emotional labor and means the system survives any one person leaving.

Build the Trellis: A Repeatable First Week

Section titled “Build the Trellis: A Repeatable First Week”

Here’s a first-week structure you can copy. It’s deliberately boring and deliberately finite: boring so anyone can run it, finite so it ends and nobody lives in permanent “onboarding” limbo.

Day 1: A human says hello. Not the org. A named person. “Hi, I’m Ana, I’ll be your buddy this month, what brought you to us?” One question. Wait for the answer. This is the whole game.

Day 2-3: Context, lightly. Share the node’s story in two minutes, not twenty pages: why it exists, one thing it’s done, who’s involved. Link a single short page, not a 47-channel workspace. Then introduce them to one or two members who share their interest.

Day 4-5: A real invitation. A personal invite to the next gathering, with what to expect and an offer to answer questions first. “I’ll be there, find me” removes the activation energy of walking into a room of strangers.

Day 6-7: A genuine follow-up. After their first event: “How was it? Anything confusing?” That last question is your best research. The people who just joined can see every rough edge you’ve gone blind to.

That’s it. Resist the urge to add more. The classic mistake is drowning a newcomer in documentation, Discord channels, and a two-hour orientation video on day one. Pace the information. Curiosity is a renewable resource only if you don’t exhaust it in week one.

Use Web3 as a Welcome Mat, Not a Gate

Section titled “Use Web3 as a Welcome Mat, Not a Gate”

You know the tooling. The trap is using it to filter people instead of welcoming them. A token-gate (requiring someone to hold a specific token or NFT to enter a space) on day one tells a curious newcomer “prove you belong before we let you in.” That’s the central-overreach instinct in miniature, and it kills nodes.

Flip the tools to do the opposite:

  • POAP (Proof of Attendance Protocol, a free collectible NFT minted to people who show up to an event, issued on Gnosis Chain so both organizers and attendees pay nothing) makes a newcomer’s first moment a small gift, not a test. They came; they get a memento; they’re now visibly part of the story. Distribute it via a QR code at the event.
  • USSD and phone-first access, as Grassroots Economics does in Kenya, meets people where they already are. Anyone can join the Sarafu community currency by dialing *384*96# on Safaricom from any phone: no wallet, no seed phrase, no laptop. The blockchain is invisible. The barrier is gone. Will Ruddick’s team built their onboarding around community savings groups (chamas) so that joining is a social act, not a solo technical one.

The principle: technology should lower the first step, never raise it. If your onboarding requires a newcomer to understand your stack before they can say hello, your stack is the obstacle.

Protect Yourself From Burnout (This Is Onboarding Too)

Section titled “Protect Yourself From Burnout (This Is Onboarding Too)”

Here’s the part the playbooks skip. The person most at risk in your node’s first year is you. ReFi DAO’s own Local Node Incubator, a structured 15-week cohort that drew 100-plus participants and earned a Net Promoter Score of 9.4 out of 10 from stewards, exists precisely because doing this alone is unsustainable. Stewards from chapters like ReFi Medellín and ReFi Costa Rica, two of the network’s most mature nodes, didn’t scale by working harder; they scaled by building teams and partnerships.

Onboarding well is how you stop being the bottleneck:

  • Every newcomer is a potential future buddy. The integration goal isn’t “they attend.” It’s “they’re ready to welcome the next person.” A node where members onboard members is a node that doesn’t need you in the room.
  • Graduate people into roles, on purpose. Week 1: observe. Month 1: first contribution (help set up, share a skill). Month 3: a real role (facilitator, welcomer, working group). Each step is a handoff of work off your plate.
  • Let the network carry weight you don’t have to. This is where being part of a larger network earns its keep: shared onboarding guides, a sibling node to ask, a cohort of stewards who’ve hit the same wall. Lean on it. That’s not central overreach, that’s mutual aid. Overreach is when the center dictates how your community must run. Support is when it hands you a trellis and gets out of the way. Take the support; guard the autonomy.

If onboarding still depends entirely on your energy after six months, that’s the warning sign. Not a busy week, but a structural one. Fix the system, not your stamina.

Try This

Section titled “Try This”

Start here: Write the Day 1 message. One short, warm paragraph a buddy can send any newcomer tomorrow, ending in a single open question (“what brought you here?”). Save it where your team can find it. You now have the first plank of your trellis.

Go deeper: Set up a free POAP for your next event (poap.xyz) and assign two members as that month’s buddies, with the one job of learning each newcomer’s name and following up on day 6. Afterward, ask every newcomer one question: “what would have made this easier?” Write down the answers.

Stretch: Map your node against the Seed / Sapling / Canopy stages and design the full 90-day path that turns a first-time attendee into someone who welcomes the next newcomer. Build it so it runs without you in the room, then test that by stepping back from one onboarding cycle entirely and watching whether the trellis holds.

References

Section titled “References”