Yassine Bentaieb
Work

Subber

Launch & Community Platform for Web3 · 2022–2025

I co-founded Subber and designed it end to end: one place where web3 communities got discovered, launched campaigns and rewarded their holders.

It grew to 20k+ daily users and 10k+ communities across 30+ chains, and raised a seed round.

Role
Co-founder: Product, Design, Ops
Site
subber.xyz

Making community value visible

In web3 nobody could tell which communities were real. Every community got a public profile showing its size, activity and holder perks, ranked side by side.

Trending communities, filtered by chain. Boosts and seven-day momentum set the order.

Launch once, reach thousands of servers

Brands built an airdrop, raffle or presale, gated it by tasks, tokens or Discord roles, and posted it to every community they picked in one click.

Subber sits between the projects launching campaigns and the communities receiving them.
Choosing an audience. Reach updates as communities are picked.
The holder's side: three tasks, then claim.
The same campaign, posted into Discord.

One profile across every chain

Holders linked wallets across 30+ chains and saw every drop they qualified for in one feed, and exactly why they had access.

The holder dashboard. "Why you have access" turns gating into a short to-do list.

Building a community to learn from one

Subberoos, our in-house PFP collection, gave holders a shared identity and let us test every tool on ourselves first.

The Subberoos community page. Art direction, collection and product were all made in-house.

A system built for other people's brands

Every community brought its own art, name and chain, and campaigns also had to work inside Discord. The product had to stay consistent around content it couldn't control, on surfaces it didn't fully own.

So the system came down to three rules: the interface stays quiet, every color has one job, and every state a holder can reach gets designed.

The entry widget set the standard

The most important piece was the entry widget. It sits where a holder decides whether to take part, so it answers three questions first: am I eligible, what do I need to do, and what do I get.

Getting it right set the standard for every gated reward. The same eligibility check, task list and claim button carry a giveaway, a presale, an airdrop or a raffle, so a new campaign type only needs new values.

Four campaigns, one widget. Each eligibility state says what happens next, and the presale shows the check running.
Neutral chrome lets community art be the loudest thing on the page, and color only carries meaning. Hover a role to see where it's used, or try the worst case.
The task gate is where holders get stuck, so its states are part of the component. A failure always says what's missing. Try Verify. Rebuilt from the shipped screens; the spec is written for this page.
One campaign, three layouts. Type, reward, chain and call to action are defined once, so a new campaign type doesn't mean redesigning every surface.

What I'd change

  • Split brand from danger Coral meant both Subber and a failed task. I'd give failure its own color, as the rebuild above does
  • Name roles in code first Tokens like status.danger and action.claim make these rules enforceable, not just conventions
  • Write rules agents can read States and usage in the repo, so an AI prototype starts from the real system

Outcome

Subber grew to 20k+ daily users and 10k+ communities across 30+ chains, and raised a seed round.