The room you already pay for is a vetted guest pool
You joined the mastermind or the private Slack for your own reasons, and the membership fee already did work you never see. It screened everyone in the room. That vetting is exactly what makes a fellow member a strong guest, and exactly why treating the roster as a prospect list gets you removed.
This is a different move from scouting strangers by their public work on GitHub and Substack, where you have no standing and no shared room. Here you are already inside, with trust you paid for and a reputation to protect. It is closest to working the network you already have, with one added rule: the network has house rules, and breaking them costs your seat.
Read the room's rules before you read the roster
Every paid community publishes a norm on self-promotion, in a pinned post, a code of conduct, or a channel named for it. Find that norm before you approach anyone. A group with a #self-promo channel is telling you where asks belong. A group with none is telling you asks go in private, sparingly.
The norm is not decoration. A community that runs a jobs channel and a wins channel but has nowhere to post a plug is a community that expects you to ask one person at a time, quietly, and never at the whole room. Reading that correctly is the difference between a welcome question and a warning from a moderator.
Climb the permission ladder in order
Standing in a community is earned in a sequence, and the sequence is the etiquette. Skip a rung and the ask lands as extraction. Climb them in order and the same ask lands as a peer offering something useful. Four rungs, from the day you join to the day you take a conversation off-platform.
- Observe and contribute first. For your first weeks, give more than you take: answer questions, share what actually worked, show up in the threads. Members who recognize your name from real help will open a DM. Members who first hear from you inside a booking request will not.
- Identify the high-signal members. The person who writes the long, useful answer, runs the side channel, or gets tagged when a hard question lands is showing you their guest instinct in real time. You are not guessing at authority from the outside. You are watching it work in a room you share.
- Make the soft ask before the direct one. Float the show where the norm allows it, a self-promo channel or a relevant thread, and let interested members raise a hand. Then follow with a specific DM to the one or two you actually want, referencing what they said in the room, not their title.
- Take it off-platform only after a yes. Move to email or a call once someone has agreed in principle. The community got you the introduction and the trust. Do not run the whole booking in its channels, and do not export the member list anywhere the community did not intend.
The soft ask and the direct ask do different jobs
The soft ask is public and opt-in: you name the show where self-promotion is allowed and let members volunteer. The direct ask is private and specific: one DM to one person you most want. Lead with the soft ask. It surfaces willing guests and spares you from cold-DMing a room that owes you nothing.
| The move | Do | Don't |
|---|---|---|
| Your first weeks | Contribute in public until members know your name from help, not requests | Join and post a guest call the same week |
| Choosing who to ask | Pick the members whose contributions you have actually read | Scrape the roster and message everyone with a title that fits |
| Making the ask | Use the self-promo channel first, then a specific DM to one or two people | Mass-DM the membership with a copied invite |
| Using the list | Keep the people who say yes as warm contacts you nurture | Export or reuse the member directory outside the community |
The people who say yes are worth more than one episode. A fellow member who guested well is a warm contact, a likely referral, and a future collaborator. Keep them in your guest pipeline in Pod Green Room with the context of where you met them. The relationship the community started keeps going after the recording.
Match the ask to the kind of community it is
A paid mastermind of twelve founders and a Discord of two thousand hobbyists are not the same room, and the same ask does not fit both. Trust is high and personal in the small one, thin and channel-mediated in the large one. Read the type, then set how direct you can be.
| Community type | What membership signals | The norm that governs the ask |
|---|---|---|
| Paid mastermind | A small group that paid to be around peers at their level; high trust, low volume | A peer-to-peer DM is welcome. Reference something they said in the room. A broadcast "who wants to come on my show" reads as taking from the group |
| Alumni Slack | A shared formative program, loose but real affinity years later | One post in the right channel, opportunities or introductions, then a DM that leads with the shared cohort. Never a cold sweep of the whole roster |
| Members Discord | Shared interest, hundreds or thousands of members, weak individual trust | Earn visibility first, then use the designated self-promo or collab channel. DMing members who have never engaged with you reads as spam at this scale |
| Live cohort course | You are going through the material together right now, in the trenches | The warmest room of all, once you have actually worked alongside someone. Ask in the group or a natural DM after real rapport, not on day one |
Move it off-platform only after the yes
The community earns you the introduction, not the whole transaction. Once a member agrees in principle, move the scheduling, the brief, and the prep to email or a call. Running the entire booking inside the group's channels clutters a shared space and signals you see it as your funnel.
Once the conversation leaves the community, the community's structure stops carrying it for you. That is where bookings from any warm room tend to stall. Queue the follow-ups in Pod Green Room against each member who said yes, and the second and third notes actually go out instead of dying in a Slack thread you scroll past.
The pool is shared, and it does not refill fast
One extractive campaign can get you muted, removed, or quietly warned about by the members who run the place. A single community is a small, finite pool of trust. Spend it like you plan to be in the room next year. Members remember the person who arrived, asked, and left.
The discipline here is the same one that keeps a target-account invitation from reading as a sales pitch: the ask has to stand on its own merit, not on what you quietly want from the room. If the only reason to book someone is that you both pay the same membership, that is not a reason a guest can feel good about.