FWB licensing community tools
Q&A with Raihan Anwar and Colby Holliday from Friends with Benefits
This points to FWB trying to turn community operations into software revenue. The pattern is clear in the interview, FWB first used tokens to control access to its own Discord, then built the same logic into tickets, newsletters, and live events, where a wallet acts like a membership card that software can check automatically. Licensing or spinning out those tools would let FWB sell infrastructure, not just memberships and culture.
-
The product roadmap started with internal pain points. FWB built custom Discord tooling first, then extended that same wallet check into ticketing and newsletters. That is the classic path from in house tool to standalone product, because the workflow is already proven on real users inside the community.
-
The live event example shows the concrete product. At FWB parties in Miami and Paris, entry was tied to a QR code linked to an ETH wallet, and access depended on holdings. In practice, that turns token ownership into an access control system that another community, venue, or creator brand could license instead of building from scratch.
-
This also fits a broader Web3 shift from pure status tokens toward utility. Related creator economy research highlights that stronger projects were moving from speculative membership ideas toward products with ongoing use. FWB was positioning its software layer, not just the token, as the durable asset that could travel to other communities.
If this model works, communities like FWB start to look less like clubs and more like software labs that incubate tools in house, then package the winners for outside customers. The next step is a market of wallet based identity and access products, where the strongest communities become the first distribution channel for the software they eventually sell.