Liquidity: The Community Problem That Isn’t About How Many Members You Have

A marketplace only works when both sides show up at the same time. Enough buyers and enough sellers, in the same place, right now. A community built around questions and answers is a marketplace like that, whether anyone designed it to be one or not, and it fails the exact same way a two-sided marketplace fails: not from too few people total, but from too many of one kind and not enough of the other.

Call it a liquidity problem, because it borrows the right word from finance. Liquidity there means an asset can actually be bought or sold at a fair price, right now, without anyone waiting around for a match. A community with a liquidity problem has plenty of people who want something, an answer, a reaction, a reply, and not enough people supplying it fast enough for the wanting to feel worth showing up for.

This is not the cold-start problem

Community bootstrapping is about getting anyone to show up at all: an empty room, nobody posting first. Liquidity assumes you’re past that. You have members. Some of them are even active. The room isn’t empty. It’s just lopsided, and lopsided is a quieter kind of dying, because the activity feed still looks alive from the outside.

Here’s what it looks like from inside a real community. A Q&A space fills with questions faster than anyone answers them. Every new arrival adds to the demand side. Almost nobody arrives already equipped, or willing, to sit on the supply side. Six months in, there’s a long tail of unanswered posts sitting under the fold, and every one of them is a small, specific proof to the person who wrote it that this place doesn’t actually work.

Metcalfe’s Law quietly assumes symmetric connections

Metcalfe’s Law says a network’s value grows with the number of possible connections between members. It’s a clean idea and it’s mostly right, but it assumes anyone can reach anyone for anything. A two-sided community breaks that assumption on purpose. A beginner asking a question isn’t looking for a connection to another beginner. They’re looking for a connection to someone who already knows the answer, and if that specific kind of connection is thin, total headcount barely matters.

The instinct, when this happens, is to grow harder. More marketing, more signups, more top-of-funnel. It doesn’t fix a lopsided ratio. It makes the ratio worse, because almost everyone joining a community arrives on the demand side by default. Nobody signs up already primed to spend their first hour answering strangers. The supply side has to be built on purpose, or it never resolves itself just by adding more people to the demand side.

Why the supply side stays thin even when it exists

The Ringelmann Effect explains part of why the supply side stays thin even once you do have knowledgeable members sitting inside the community. A question posted to a room of five feels addressed to someone specific. The same question posted to a room of five thousand feels like someone else’s job, and the person capable of answering it correctly in thirty seconds scrolls past, because answering doesn’t feel like theirs to do. Supply doesn’t just need to exist. It needs to feel individually summoned.

There’s a real fix for this, and it isn’t waiting. Seed the thin side yourself, visibly, before the ratio has any chance to correct on its own. The founder, or an early expert member, personally answers the first fifty or hundred questions, fast, in public, with their name on it. It’s slow and it doesn’t scale, and that’s the point early on. It sets the floor for response time before anyone new arrives to calibrate against, and it gives the first genuine volunteer answerers a working example of what a good answer here looks like, instead of a blank template and a guess.

What actually closes the loop

Jetonomy, a standalone forum, Q&A, and ideas plugin that also plugs into BuddyNext, builds a version of this directly into its Q&A space type. Questions can be marked with an accepted answer, which does two things at once. It closes the loop for the person who asked, so a question doesn’t sit there looking permanently unresolved, and it turns every accepted answer into a small, visible credential for whoever wrote it. That’s the supply side getting a reason to show up again that isn’t altruism alone.

Jetonomy’s trust levels do something similar for the timing problem specifically. Newer members start at a lower trust tier and earn promotion through real participation, which means the people most likely to already be answering, the ones with enough history in the room to have earned a higher tier, are also the people whose answers carry a visible signal of having been reliable here before. A brand-new account posting a confident answer and a trust-level-four member posting the same answer read differently to the person who asked, even if the words are identical, and that’s not a bug. It’s the same mechanism that makes a doctor’s answer feel different from a stranger’s, compressed into a plugin setting.

Most of your demand doesn’t need a live answer

Not every question needs a live person answering in real time. Someone searching a community’s archive for something that’s already been asked twice before doesn’t need supply. They need a well-organized archive that search can actually surface. This is where liquidity and raw headcount split apart again: an archive with a few hundred deeply-answered questions can serve thousands of future searchers with zero live supply required, as long as the search works and the content is structured to be found.

The liquidity problem is really about the smaller slice of questions that are novel, specific, or time-sensitive enough that the archive can’t cover them yet. Those still need a live answerer, and that’s the slice worth solving on purpose. Everything else takes care of itself once search and organization stop being an afterthought.

Where this shows up fastest: course communities

A course community is the cleanest place to watch a liquidity problem form, because the syllabus manufactures matched demand automatically. Every student on lesson four generates a question at roughly the same pace. If the instructor is the only supply, the ratio holds fine for the first cohort and collapses on the second, because the number of students doubled and the number of instructors didn’t.

The fix most course communities eventually land on isn’t hiring more instructors. It’s converting a small number of ahead-of-schedule students from the first cohort into the second cohort’s early supply, seeded exactly the way described above, before their own questions have even stopped.

The check that actually tells you which problem you have

Check the ratio before you check the headcount. Count how many posts in your Q&A or discussion space have zero replies after 48 hours, and compare that to how many new questions arrived in the same window. If the unanswered pile is growing faster than the answered pile, you don’t have a growth problem yet.

You have a liquidity problem, and it’s solvable in a way a growth problem usually isn’t: by finding the forty people who already have the answers and giving them a reason to show up, before you go looking for four thousand more people who only have the questions.