You found out by accident. Somebody posted a photo of two coffee cups on a table in a city you have never been to, tagged another member, and captioned it something like "finally meeting after two years of talking every day."
You felt genuinely happy. And then, about four seconds later, you felt something else. A small, unattractive twinge that went: two years of talking every day? In my community? And I did not know?
Let us talk about that twinge, because every founder gets it, almost nobody admits it, and how you respond to it will shape whether your community becomes a real place or stays a broadcast with comments.
The pang is normal and it is not a good guide
Here is what the pang is actually made of. A bit of exclusion, which is human. A bit of professional anxiety, which sounds like: if they have each other, do they still need me. And a bit of surveillance instinct, which sounds like: what are they saying in there.
All three are understandable and all three will give you terrible advice.
Because the thing you just discovered, two members who became genuinely important to each other inside a space you built, is the single best outcome available in this entire line of work. It is the thing you cannot manufacture, cannot buy, and cannot fake. If it is happening, you did something right that most people never manage.
The correct response to the pang is not to act on it. It is to notice it, name it privately, and then go and be delighted in public.
Why side friendships are the actual product
Think about what makes a community sticky in a way that no content library ever achieves.
If members only have a relationship with you, then you are a service. Your value is your output. When your output dips, or somebody more interesting appears, or their interest shifts, they leave, and nothing holds them.
If members have relationships with each other, then leaving costs something. Not in a manipulative sense. In the ordinary human sense that people do not casually walk away from friends. The membership stops being a subscription to your work and becomes the place where their people are.
There is a version of your community where every conversation goes through you. It is called being a bottleneck, and it has a hard ceiling: your available hours. There is another version where members answer each other, encourage each other, meet up, collaborate, hire each other, and occasionally get married, and that version scales in a way you cannot personally provide.
The group chat you are not in is evidence of the second version. Frame it that way and the twinge loses most of its power.
What happens if you fight it
Some founders, usually without quite realising, try to keep everything in the room. They ask people to keep conversations in the main space. They express mild disappointment when a side channel forms. They join every subgroup. They set up structures so that all paths lead back to them.
Two things happen. The side conversations continue, because you cannot stop adults from becoming friends. And they move somewhere you will never see, held by people who now feel slightly furtive about a completely normal human thing.
You have not prevented anything. You have just made yourself the last to know, and taught your members that closeness is faintly against the rules.
The splinter fear, examined honestly
There is a real version of this worry and it deserves a straight answer.
Yes, occasionally a group of members forms a chat, realises they mostly value each other, and leaves together. It happens. It has happened to people I admire.
But look at what caused it, because it is almost never the friendship. It is one of these: the community was quiet and the side chat was livelier, the price stopped matching what people got, the founder had become absent, or somebody was actively organising an exit because they wanted to run their own thing.
The first three are your responsibility and are fixable. The fourth is rare and mostly self limiting, because running a community is much harder than complaining about one, and the person leading the walkout usually discovers that within four months.
The defence against a splinter is not control. It is being worth staying for. A vibrant main room, a fair price, and a present host beats any policy you could write.
When a side group is a symptom
That said, pay attention to the pattern rather than the instance.
One group chat between three friends is lovely. Six separate side chats that have quietly become where all the real conversation happens is a signal about your main space. It usually means one of two things: the main room feels too public and performative for the actual questions people have, or it is too busy and fast to hold anything.
If you notice that pattern, do not police the side chats. Improve the room. Make a smaller, quieter space inside the community with a clear purpose. Slow down the busiest channel. Ask a few people, privately and without any edge to it, what they say elsewhere that they would not say here. The answers are usually specific and fixable.
How to encourage this on purpose
You can accelerate member to member connection deliberately, and it is some of the most satisfying work there is.
Introduce people. Explicitly, by name, with a reason. "You two should talk, you are both wrestling with the same pricing problem from opposite directions." Do this once a week and you will change the texture of your community within a quarter. It costs ninety seconds.
Answer less. Genuinely. When a question comes in that three of your members could answer, wait a day. Your instinct to be first and most useful is the single biggest suppressor of peer conversation in most small communities. Sit on your hands and let somebody else be the helpful one.
Make small groups possible. A quarterly pairing, a four person thread on a shared problem, an optional regional channel. Small containers produce friendships. Large rooms produce audiences.
Celebrate connection when you see it. When two members collaborate, say so warmly and publicly. You are showing everybody else that this is what the place is for.
Support meetups without owning them. If members in a city want to get together, be enthusiastic, offer a channel for coordinating, and do not turn it into an official event with your branding on it. Also be honest with yourself: a member organised gathering is not something you can vouch for or supervise, and you should not imply that you can.
The boundaries that matter
Being encouraging does not mean being careless. A few firm lines.
Never hand out a member's contact details to another member. Not their email, not their phone number, not their address, not even to somebody lovely with a good reason. Pass the request along instead and let the member decide. This sounds small and it is enormous, because the whole thing rests on people trusting that joining did not put their details into circulation.
Never build a directory that publishes anything a member did not deliberately choose to publish, field by field. Opt in, always, with the ability to remove themselves in one step.
Never read, monitor, or ask about the contents of private messages between members. If a platform lets you see them, do not look. If somebody reports a problem, handle the report on the basis of what they bring you.
Do warn people, once, warmly, in your welcome material: a private community is a trusted space, and that is exactly why the occasional bad actor tries to use one. Tell members that nobody should ever ask them to move a payment off platform, that you will never message them asking for money or credentials, and that they should tell you if anyone does. This single paragraph prevents a specific and very common harm, and it costs you nothing.
And if a member's behaviour in private messages is making somebody uncomfortable, treat that with the same seriousness as anything in public. Private does not mean unaccountable.
The loneliness underneath, which is worth naming
Here is the part I actually wanted to get to.
Building a community where everyone becomes friends with each other can be a strange kind of lonely. You are the host, which means you are in every room and fully in none of them. You know a great deal about a great many people and most of them know your public version. Members become close to each other in a way they mostly cannot become close to you, because you are the person who might one day have to send them a difficult email.
That is real, and pretending otherwise is how founders end up leaning on their members for friendship in ways that get complicated fast.
So go and get your own group chat. Two or three people doing similar work, somewhere private, where you are a peer and not the host. It fixes almost all of this. Most of the founder loneliness I see is not caused by community work being isolating. It is caused by not having anywhere to be a person who needs help rather than a person who provides it.
And then look at that photo of the two coffee cups again, and let yourself enjoy it properly. You made a room, and two strangers walked into it, and now they fly to see each other. That is not a threat to your business. That is the best thing on your entire balance sheet, and it does not fit in a dashboard anywhere.
Do this this week
Find two members who should know each other and introduce them by name, with the reason spelled out.
Pick one question you would normally answer immediately and wait twenty four hours. See who steps in.
Check your welcome material for the one paragraph about never moving payments off platform and never sharing credentials. If it is not there, add it.
Check that nothing in your community publishes a member's details without them having chosen it, field by field.
And find your own group chat. Message two people at a similar stage today and start it. You have spent a long time building somewhere for other people to belong, and you are allowed to have one too.