Product Design · 2022–23 · Shipped
LinksDAO
Member perks, rebuilt as a storefront.
LinksDAO members held an NFT that unlocked partner perks, but the perks sat in a grid of logos where a site-wide discount, a tee-time concierge and a magazine all looked the same. As the only designer, on contract, I rebuilt Benefits as a storefront, with one card for discounts and points and one button that says how each is claimed. It shipped as designed in the Clubhouse, and LinksDAO later counted the points members earned here, as a small part, toward its token distribution.
- Role
- Design Lead (Contract)
- Year
- 2022–23
- Platform
- Web and mobile web
- Status
- Shipped



Reward Balance
2,325 PTS
Problem
Member perks sat in a static grid of partner logos. Every perk looked the same, and nothing said what you would get.
Approach
Benefits rebuilt as a storefront, with one card system for discounts and points, and one predictable way to claim each kind.
Result
LinksDAO later counted the points members built up here, as a small part, toward its token distribution.
01 · Problem
Every perk looked the same.
A site-wide discount, a tee-time concierge and a magazine subscription were indistinguishable.

LinksDAO members hold a membership NFT that unlocks perks from partners such as Callaway, TopGolf and Bridgestone. The Benefits page listed each partner as a logo, one line of text and a "View Benefit" link. From discovery, as I remember it (I no longer have the notes), members couldn’t explore by what they wanted, see what was new, or tell what types of benefit were on offer. Every part of the storefront answers one of those three. And each new partner meant a manual page edit. I was the only designer, on contract, working directly with the VP of Product and the Head of Design.
02 · Decision
A storefront, not a directory.
Benefits became a shop: a featured offer, categories, brands, products and curated picks.

How the landing page was structured changed in review. My first version read more like a list of items. The VP of Product and the Head of Design wanted more focus on a curated feed of products, so the home page gives its space to featured and curated products rather than listing everything.
- Chose
- A browsable shop with featured, categories, brands, products and curated picks
- Instead of
- A tidier partner grid with filters
- Because
- The grid's problem wasn't tidiness. Members couldn't explore it, see what was new or tell the types of benefit apart, and filters fix only the first. A shop has a place for each: categories to explore, a featured slot for what's new, and products and brands that say what the benefit is.
03 · Decision
Two kinds of benefit, one system.
One card with one tag slot: cream for a discount, green for points.

Some partners offer a discount and some offer points, and both use the same card. The same templates cover Shopify brands and affiliate products.
- Chose
- One card and one tag slot for discounts and points offers
- Instead of
- Separate Discounts and Rewards sections
- Because
- Members shouldn't have to learn which section a brand lives in. The tag tells the type at a glance.

- A discount, in cream. 15% Off, in the tag slot on the brand card.
- Points, in green. Same slot, same card: Earn 2x Points.
- The button says how to claim. Redeem Code for a code, Shop for a link out.
- Products use the same tag. The type reads before the name.
04 · Constraint
Links couldn't change its partners, so the button had to.
Each benefit has one primary button, and it says what happens next.

This one started from something that couldn't move. Each partner integrates its own way: some need a referral link, some a code pasted at their checkout, and some can be redeemed inside the Clubhouse. Links couldn't change any of that. Sending every benefit to the partner's site would have left the member to work out which kind they had. So the difference is carried by one thing, the label: link out, reveal a code, or redeem here.
05 · Design: Rewards
Points you can see, and spend.
The redeem modal shows the balance, the cost and the ending balance before the member commits.
A rewards page shows the balance, a history with pending and earned entries, and a referral link. Points redeem for Links Proshop gift cards and other rewards. The redeem modal says so plainly when there are not enough points.


- Balance and cost. What the member has, and what this takes.
- The ending balance. What is left, before they commit.
- One action. Redeem Now, named for what it does.
06 · Design: Onchain
Built for members who hold a wallet.
Each discount code is tied to the wallet of the member who claims it, and works once.
Membership is an NFT, in Leisure and Global tiers, and the profile shows the member's ENS name. A code bound to one wallet can't be passed around, and each member gets three by default. Points are recorded against the member, which is what later made them usable for the token distribution.
07 · Design: Final screens
What shipped.

08 · Result
The points counted toward the token distribution.
The redesign launched in the Clubhouse. I was contracted for the design only, and measuring it wasn't part of the contract, so I don't have usage numbers and won't quote any. As far as I know, everything shipped the way it was designed, though the rewards system may have been reworked behind the scenes afterwards.
If I'd been asked to measure it, I'd start with claims by type: whether Reveal code benefits were used as often as Redeem here ones, since that's where a member is asked to do the most.
Showing the ending balance before a member commits is a small version of what Checks Wiki later became: show the outcome before the step someone can't take back.
- Design outcome
- A static grid of partner logos became one benefits system: a storefront to browse, one card for discounts and points, one button that says how to claim, and a rewards page.
- Product outcome
- LinksDAO later counted the points members built up here, as a small part, toward its token distribution.






