A note on method before the substance. What follows is a composite drawn from 90-day community programmes across several mid-sized DeFi protocols, not a single audited engagement. The protocol is not named because there is no single protocol to name, and the figures describe the range we see rather than one dashboard. Treat them as a planning baseline to argue with, not as evidence that a specific tactic caused a specific number.
The starting position
The pattern is consistent, and it is rarely about apathy. A protocol ships for two years, accrues a few thousand wallets, and holds a Discord where the last fifty messages are support tickets and price questions. The contributors are working. The community is reading rather than writing.
The diagnosis that matters: users who stayed have already decided the product is real, and nobody has given them a reason to do anything with that conviction beyond holding.
Days 1-30: become visible, then useful
The first month is not a campaign, it is presence. Someone from the team answers in hours rather than days, in public, with substance — including "I don't know, I'll find out" followed by the answer. Across the programmes this was the single most consistently effective change, and the least glamorous.
Structure comes next, because a busy server is not a navigable one: channels that map to what people actually want to do, pins that answer the questions asked most often, and a visible route from newcomer to contributor.
The tactics that landed flat in this phase: generic community calls with no topic, and a first announcement that was an announcement. Both attract the already-convinced and nobody else.
Days 31-60: give people something to make
Incentives alone reliably attract wallets and not people. What moved things was giving community members a small piece of real work with their name on it: a governance summary, a translated explainer, a walkthrough of a new feature, a bug report that gets fixed and credited.
Recognition did more than payment. A contributor listed in a release note produces more of the behaviour you want than a token allocation nobody can price. Token rewards ranked low as a driver on their own, and high when paired with visibility — which is also the cheapest thing you have.
Days 61-90: hand over the ceremony
The last phase is governance, and it is where programmes either consolidate or stall. Delegation tools, an open proposal process with a low floor for raising an idea, and a visible path from commenting to drafting to holding a role.
The compounding effect is the real finding: the first cohort of active members recruits the next one, because quality discussions and responsive maintainers are the thing that makes a server worth opening. Engagement that was paid for stops when payment stops.
What to measure, honestly
Pick a handful of numbers and watch them monthly: weekly active contributors rather than members, messages from non-team accounts, the share of proposals originating outside the core team, and retention of the first cohort of contributors after incentives end.
Numbers can be made to look like progress — activity counts every hello. The one that resists flattery is whether people who arrived for a reward are still there a quarter after it stopped.
Next: how treasury decisions are made once a community starts asking. Join our Discord.
References
Next, read 10 Governance Frameworks for Resilient DAOs. More in Governance & DAOs.