Most hub owners spend all their energy figuring out how to say yes—how to attract more members, remove friction from signing up, make joining as easy as possible. Almost nobody spends the same energy figuring out who they should say no to.
That imbalance eventually costs you. A hub that accepts everyone ends up serving no one particularly well, because the conversations, content, and culture inside it have to stay broad enough to accommodate people who don't actually share a common problem.
Growth and Fit Are Not the Same Goal
It's easy to treat every new member as a win. More members usually looks like more traction, more social proof, more momentum. But a member who joins without genuinely fitting your hub's purpose rarely becomes an active, contributing part of the community—they become a name on a list.
Worse, a member who doesn't fit can quietly change the tone of the space for everyone else. A question that's slightly off-topic gets asked, then another, then the conversation that used to be sharply focused on one problem starts drifting toward five loosely related ones. No single addition causes this. It's the cumulative effect of never saying no.
Growth without fit dilutes the exact thing that made your hub valuable in the first place.
What Boundaries Actually Protect
A boundary isn't about exclusion for its own sake. It protects two things at once: the relevance of what happens inside your hub, and the trust of the members already there.
When someone joins a tightly focused hub, they're making an implicit bet—that the people around them are dealing with a similar problem, at a similar stage, and that conversations will stay useful rather than scattered. Every member who joins without fitting that description quietly breaks that bet for everyone else, even if no one says so directly.
Being clear about who your hub is not for is what makes the promise to the people it is for actually mean something.
Write the Boundary Down, Not Just the Promise
Most hub owners can describe who their hub is for. Far fewer can describe, just as specifically, who it's not for. That second sentence is usually the missing piece.
Try filling in both of these, honestly and specifically:
"The person this hub is built for is someone who ________, currently facing ________."
"The person this hub is not built for is someone who ________, or who's really looking for ________."
The second sentence is almost always harder to write, because it means naming real people you might otherwise have welcomed in. That discomfort is usually a sign you're onto something true—boundaries that don't cost you anything to write rarely protect anything either.
A Boundary Only Works if the Promise Is Built on a Real Problem
Boundaries fall apart when the promise underneath them is too vague to test against. "A community for entrepreneurs" gives you nothing to say no to, because almost anyone could argue they fit. A boundary is only as sharp as the problem it's protecting.
That means the real work happens one level up, before you write a single boundary sentence: making sure what you're organizing your hub around is an actual recurring problem, not just a shared interest. Interests are broad enough that everyone qualifies. Problems are specific enough that most people don't.
Three checks help you tell the difference.
Does it keep resurfacing? A real problem doesn't show up once and disappear—it comes back across different people, different conversations, different weeks, because it's a genuinely recurring part of the situation your members are in. If you can only point to one person who's ever mentioned it, you likely haven't found a pattern yet.
Does ignoring it actually cost something? Some struggles are mildly annoying but ultimately harmless to leave unsolved. Others quietly cost people money, time, opportunities, or confidence the longer they go unaddressed. A problem worth building a hub around usually falls into the second category—there's something real at stake in solving it.
Does it need people, not just information? Plenty of problems have a clean, single answer sitting in a search result or a how-to article somewhere. Those don't need a community—they need a link. The problems worth building a hub around are the ones that genuinely benefit from other people's context, experience, and back-and-forth—where one answer rarely settles it for good.
A promise without a problem is just a description. A promise built around a real problem is a filter.
If what you're building around clears all three checks, the boundary becomes far easier to write—because you now know exactly what someone has to be experiencing to belong, and exactly what tells you they're chasing something else entirely.
Use a Small Amount of Friction on Purpose
You don't need a formal vetting process to introduce useful boundaries. Even a small amount of intentional friction at the joining stage does most of the work.
A short application—two or three questions instead of an instant sign-up button—filters naturally. It doesn't need to be exclusionary in tone. Questions like "What are you currently working on?" or "What brought you here?" cost a genuinely interested person thirty seconds, while someone who was never really the right fit tends to drop off before finishing.
This isn't about making joining hard. It's about making sure the people who do join actually meant to be there.
Say No Directly When It's Clearly Not a Fit
Occasionally someone applies, or asks to join, and it's obvious within the first exchange that they're looking for something your hub doesn't offer. The easiest path is to let them in anyway and hope it works out. It usually doesn't—for them or for the group.
A short, honest redirect serves everyone better: "It sounds like you're looking for [X], and that's not really what this community focuses on—but here's where you might find more of what you need." This costs you nothing, and it's far more respectful than a silent non-response or a member who joins, feels out of place within a week, and quietly disengages.
Revisit Your Boundary as the Hub Grows
The boundary that made sense at 50 members won't necessarily hold at 500. As your hub matures, the problem it solves may narrow, sharpen, or shift slightly based on what you've learned from the members already there.
Revisit both sentences—who it's for, and who it's not for—every few months. If you find yourself unable to write the second sentence with any real specificity anymore, that's usually a sign your hub has quietly drifted from having a clear boundary at all.
Put It Into Practice
Write the sentence: "This hub is not the right fit for people who ________ or who are looking for ________."
If it's hard to complete honestly, that's this week's real work—not writing another article, not adding another feature. Sharpening that one sentence will do more for your hub's focus than almost anything else you could spend the week on.
Key Takeaway
A hub that's for everyone ends up meaning very little to anyone. Knowing—and saying—who it's not for is what makes the promise to the people it is for worth keeping.
Read Next
If you haven't yet defined what your hub actually promises the people who do belong, The Promise That Keeps People Coming Back is worth reading first—boundaries only work once that promise is clear.
