From Token Gating to Product Studio
Q&A with Raihan Anwar and Colby Holliday from Friends with Benefits
This shows FWB was trying to turn community operations into a product factory, not just run a Discord. The team started by building its own bots to check wallet ownership and manage access inside Discord, then moved into ticketing and newsletters where the same wallet check could unlock an event, a feed, or a piece of software. In practice, that makes the product team look less like an internal tools group and more like a small agency building reusable crypto membership software from live community needs.
-
The workflow was concrete. A user linked a wallet, a bot checked token holdings, Discord roles changed, and that same wallet could later be used to admit someone to a party by QR code. FWB was productizing one repeated action, prove ownership once, then use it across chat, media, and events.
-
This is why in house building mattered. FWB said everything had been built internally, and was already thinking about buying DAO assets or Discord tooling from others. That is the behavior of a studio assembling a stack of community software, not just a membership club adding perks.
-
The closest market analogy was the early token gated Discord ecosystem around tools like Collab.Land. The difference is that FWB was not only using token verification for access control, it was extending that logic into real world ticketing and media products that could later be licensed or spun out.
The next step for this model is a broader on-chain identity layer, where one wallet becomes the login for community, content, commerce, and events. If that stack works, communities like FWB stop acting like social clubs with a token and start acting like incubators for new software businesses built from their own member workflows.