How to start a community when you have no members

Promise a specific kind of help

“A community for entrepreneurs” leaves a newcomer guessing. “A weekly review group for solo consultants improving their first offer” explains who belongs, what happens, and why they might return. Choose a shared situation, a useful recurring activity, and a simple participation rule.

Before building many channels, write a welcome page with the purpose, schedule, code of conduct, privacy expectations, and contact for help. Explain whether the space is free, paid, public, or private.

Offer value even when only one person arrives

The first member should be able to use a resource, ask a question, receive a thoughtful response, or attend a scheduled working session. That value can initially come from you. A community that needs fifty active people before anyone benefits is difficult to start.

Prepare a small set of useful founder-authored material: a start-here post, a completed example, a resource list, an introduction prompt, a real question, and the date of the first event. Label all examples and founder posts honestly.

Invite the first person personally

Find someone already trying to make the progress the community supports. Explain the limited founding format: “I’m starting a small weekly offer-review group. I’ll host the first sessions and help each person leave with one improvement. Would that be useful?” Tell them when it happens and what participation requires.

Do not sell “access to an active network” when there is no network yet. Offer the real founding experience: attention, help, and influence on the format. If the first invite is declined, ask what would make the activity useful rather than pushing membership.

Build a founding circle around a ritual

1. Invite a few compatible people individually, at a pace you can welcome well.
2. Host a scheduled session or weekly thread with one clear task and a small finished output.
3. Respond to early contributions so a member does not post into silence. Ask permission before introducing members to each other.
4. End each activity with the next date and a reason to return.
5. Invite feedback privately as well as publicly; newcomers may hesitate to criticise an empty room.

A ritual might be Monday goal-setting, Friday feedback, or a monthly problem-solving session. Choose a cadence you can sustain instead of promising daily events you cannot deliver.

Seed usefulness without faking activity

You may curate public resources with attribution, publish your own answers, and create clearly labelled example discussions. Do not create fake member accounts, fabricated success stories, or bots pretending to be human participants. If an AI helper is present, identify it and explain its limitations.

Keep the structure small. Three purposeful areas—start here, ask for help, and this week’s activity—can work better than twenty empty channels. Add categories when actual participation creates a need.

Measure exchanges and return, not just joins

Track invited people, accepted invitations, first contributions, posts receiving a useful response, and return participation at the agreed cadence. Ask members what they accomplished. Ten registrations with no replies is a different outcome from three members who help each other finish a task.

If people join but do not contribute, reduce the difficulty of the first ask. If they contribute but do not return, examine whether the activity recurs often enough to matter. If the founder must initiate everything indefinitely, consider whether a workshop or service would serve the need better. Invite growth after the small experience is worth repeating.