Guide
How to build a community, starting with a dinner of eight
Most advice about community starts with a platform and a growth plan. Real ones start with a table, a handful of people and a reason to meet again. This guide walks the path from the first dinner to a paid membership, in the order it usually happens.
Start smaller than feels respectable
The instinct is to launch big: a name, a logo, a landing page, a hundred people in a chat. Resist it. A community is a group of people who feel responsible to each other, and that feeling cannot be announced into existence. It forms when the same people sit across from each other more than once.
So the first unit is a dinner of eight. One table, one conversation, one host. Ten or eleven invitations will usually land you eight at the table.
Decide who it is for before you invite anyone
Write one sentence: this is for ___ who want ___. Founders who want honest peers. New parents who want adults to talk to. People who moved to a city and know nobody. The sentence is not for your website. It is for you, so that when you are choosing between two potential guests, you have a way to decide.
The narrower it is, the faster it works. Narrow groups feel like belonging. Broad groups feel like an event.
The first dinner
Who to invite
Ask people you already know and trust, and ask each of them to bring someone you have not met. Friends vouch for friends, which makes the room safe, and you still end up with new faces. Avoid filling the table with people who all know each other. Half the point is introductions.
Where
A restaurant with a private table, or a home. Pick somewhere quiet enough to hear. Loud rooms break eight people into three conversations and nobody leaves having met everyone.
How to run it
- Greet each person at the door and introduce them to someone, with one useful fact. "This is Mai, she just moved back from Berlin and is thinking about starting a ceramics studio."
- Seat people deliberately. Separate partners and friends.
- Offer one question to the whole table at the start. Not an icebreaker game, a real question: what is something you are working on that you are unsure about?
- Eat with everyone. A host who hovers makes the guests nervous.
- End on time. People remember the night better when it ends while it is still good.
The day after
Message every guest personally. Thank them, mention something they said, and name one person at the table they should stay in touch with. This single habit does more for retention than any tool.
Make the second one easy to say yes to
At the end of the first dinner, say the date of the next one. Not "we should do this again". An actual date, ideally within five weeks. Communities die in the gap between a great first night and a vague promise.
Keep it recurring and predictable. The first Thursday of every month beats a different day each time. Predictability lets people plan their lives around you, and that is what belonging looks like in practice.
Find your regulars
By the third or fourth gathering you will see a pattern. Some guests come every time, bring friends and write to you afterwards. These are your regulars. They are not the loudest people. They are the ones who feel at home.
Spend time with them. Ask what they like, what they would change, who else should be there. Give one or two of them a small job, such as welcoming new people or choosing the next venue. Ownership turns attendees into a community faster than any programming.
Hold a standard
Every community has a culture, and it is set by what the host tolerates. If someone dominates the table, pitches their business to strangers or makes others uncomfortable, say something privately and early. Letting it slide costs you your best members, quietly, one at a time.
Verification helps with the other half. When you know every guest is who they say they are, you can say yes to people you do not know yet, and they can trust the table. This is one of the reasons IRL checks the ID of every member.
Grow by invitation, not advertising
Past the first few dinners, the best source of new members is current members. Ask each regular to bring one person each quarter. Keep the group small enough that you can still know everyone by name. When it outgrows one table, start a second table rather than a bigger one.
Public events are fine for discovery, but treat them as a doorway. The community is what happens at the smaller gatherings after that.
Bring in a second place to talk
Once people have met, a group chat or shared space helps them stay in touch between events. Keep it modest. Introductions, plans, small favours. If it turns into noise, people mute it, so post less and make each message useful.
When to charge, and how
Charge too early and you filter out the people you are trying to attract. Charge too late and you burn out hosting for free. The usual signal is that people come back without being chased, and you can say in one sentence what a member gets.
Three stages most communities pass through
- Cover the cost. Ask guests to pay for the meal. Nobody objects to paying for dinner, and it reduces no-shows.
- Pay the host. Add a small hosting fee to events. It makes the work sustainable and signals the thing has value.
- Membership. Offer a monthly or annual fee for something concrete: priority seats, member-only dinners, introductions curated by you, a directory. Keep it to what you can reliably deliver.
Whatever you charge, describe it in plain words, tell existing members first, and keep a free way in for people you really want in the room.
Mistakes that quietly end communities
- Growing the list before the table works.
- Changing the format every month.
- Making the host the only connector, so the group depends on one person.
- Skipping the follow-up message.
- Letting a vague audience creep in, so nobody is sure who it is for.
Where a tool helps
You do not need software for dinner one. When you are hosting every month, you want one place to publish events, see who came, remember who is new, and invite verified people. That is what the organiser desk on IRL is for, and you can import existing events from Luma by pasting a calendar link. If you already run a community and want to move it, book a call.
Questions people ask
How long does it take to build a community?
Expect six to twelve months of steady, boring consistency before it feels alive. The first eight people are fast. The next fifty take a season, because trust grows at the speed of repeated meetings, not announcements.
How many people should the first event have?
Eight. It is small enough for one conversation and large enough that one no-show does not sink the night. Invite ten or eleven to land on eight.
Should I start online or in person?
In person if you can. A group chat is useful once people have met. Before that it is a room full of strangers who have no reason to speak.
When can I charge for membership?
When people already come back without being chased, and when you can say in one sentence what a member gets that a non-member does not. That is usually after four to six gatherings, not before.
What if nobody replies to my invitations?
Invite fewer people, more personally. A message written to one person by name beats a post to a hundred. Ask ten people you already know, and ask each to bring one person.
Do I need an app or platform?
Not for the first dinner. A message thread and a place to keep names is enough. Tools matter once you are hosting regularly and tracking who came, who was new and who to invite next.
Running a community?
Talk to us about moving yours onto IRL. Bring the members you already have.
Book a call