Eesee icon

Eesee

Launchpad, tiers and staking for a Web3 marketplace

Book a call
Eesee: Launchpad, tiers and staking for a Web3 marketplace
  • 45+screens and states designed and built
  • 70+components in the shared library
  • 12 weeksfrom kickoff to the first sale

About the project

Eesee is a gamified Web3 marketplace: NFTs, tokens and real-world assets are sold through on-chain raffles, where buyers pay for tickets instead of the full price. Its launchpad runs token sales for the same community, from IDOs to IROs (initial raffle offerings), with tiers for people who stake the ESE token and an AI agent that helps them research upcoming projects.

We designed and built the launchpad web app with eesee's team: project discovery, sale pages, tiers, staking, LaunchDrop and the claim portal.

The challenge

A token sale moves fast and forgives little. A round can sell out in minutes, every project sets its own rules, and one missed step (KYC, a stake, the right network) means no allocation.

Eesee was moving its launchpad from first-come, first-served sales to a stake-to-participate model, where the ESE you stake decides your tier and your allocation. People needed to see where they stood, what the next tier would give them and what to do before a round opened, without reading the docs.

Our role

A product designer and two front-end engineers from Nemy worked with eesee's in-house design and blockchain teams for twelve weeks. We designed the launchpad's flows and screens, built the front end in Next.js and TypeScript on top of eesee's contracts and APIs, and handed over a component library their team could extend.

What we designed and built

  • Home: the AI agent, the tier system and the ESE token up front, live totals for funds raised, projects launched, ESE staked and KYC users, then upcoming IDOs with filters
  • Sale pages: the round timeline from guaranteed allocation to the first-come round to claim, with price, total raise and tickets sold, and the next step pinned
  • Tiers: what each tier unlocks, how much ESE it takes and how far you are from the next one
  • Staking: pools by lock period with APY, the unlock date and the withdrawal rules shown before you commit
  • LaunchDrop and the claim portal: rewards and purchased tokens in one list, with what you can claim today
  • Always in view: wallet connection, KYC status, and live gas and ESE prices in the footer of every page

The web3 UX we solved

  • Networks: every sale names its chain, and the buy button asks the wallet to switch networks instead of failing on the wrong one
  • Gas: the current gas price is always on screen, and every transaction shows its fee before the wallet opens
  • Signing: before a wallet prompt appears, one line explains what is about to be signed (approve, stake, buy or claim) and why some actions take two signatures
  • Timing: countdowns in local time and clear round states (upcoming, live, sold out, claim), so nobody misses a round by misreading UTC
  • Trust: the audit, the terms and support are linked from every page, and no screen asks for a signature it doesn't explain

What we handed over

Eesee's team took over a typed Next.js codebase, a component library documented in Storybook, and Figma files that match the code one to one. Contract calls, round states and error messages live in one place, so a new kind of sale needs new copy and a config entry rather than a new page.

What we did
Launchpad design & front-end development
Category
Crypto · Launchpad
Platform
Web app
Timeline
12 weeks
Team
Product designer, 2 front-end engineers
Stack
Next.js, TypeScript, wagmi, viem, WalletConnect

Building something like Eesee?

Tell us about it on a 15-minute call.

Book a callSee our work

More work

All work
Ask your AI about us