# The Web3 product and brand checklist: what to fix before your raise or token launch

> What to fix in your product and brand before a raise, TGE or mainnet: 40 checks for wallet flows, failure states, contract addresses, token pages, whitepaper, deck and launch assets.

By Alterra Studio. Updated 2026-10-31. Canonical: https://alterra.studio/insights/web3-product-and-brand-checklist

Before a raise or a token launch, check your product and brand where crypto users and investors decide whether to trust you. That means the wallet connect and signing steps, what the product says when a transaction fails, proof that the contracts and team are real, a brand that doesn't look like every other token, a website and token page that explain the utility in seconds, and a whitepaper and deck that match the product. Launch assets go on the list too. Each of the 40 checks below comes with the reason behind it, tied where we can to what crypto users write.

## Why do Web3 products need their own checklist?

People arrive at a crypto product expecting to be let down. In a 2024 survey, Pew Research Center found that 63% of US adults have little or no confidence that current ways to invest in, trade or use cryptocurrencies are reliable and safe. In our own [crypto trust research](/research/crypto-trust-2026), we read 4,378 public comments about token rewards, wallets, staking and web3 games. Of the 978 passages about trusting or using a product, 282 (29%) said the offer looked like a scam or a cash grab.

The comments about wallets and staking are more practical. Common complaints there are failed or stuck transactions (80 of 384 passages), connecting, signing and approvals (70), and products that are too complex for a first-time user (70). Those are design problems, and a new holder meets them in the first five minutes. The comments come from Hacker News, Stack Exchange, Lemmy and Steam reviews, which lean more sceptical than crypto-native communities, so read the counts as what comes up most often rather than as a survey.

Investors can check the same things a user does. Opening the app, connecting a wallet and reading the token page takes ten minutes. If the deck shows one product and the app shows another, that gap turns into a question in the meeting.

> Figure: How many of these are true for your product today?: The screen before the wallet picker says what connecting unlocks; Every signature is explained in plain words before the wallet shows it; Every failed transaction says what failed and what to do next; Paused and ended pools or campaigns have their own states; One page lists every contract address, linked to the block explorer; The first screen says what the product does without the token; The token page reads on a phone and matches the whitepaper and deck; The deck shows the product as it ships. 0–3: Fix before you announce, Start with the wallet flows and the contract page. They are what users and investors try first.; 4–6: Close the gaps, Run all 40 checks in the guide. The misses are usually failure states and numbers that don't match across documents.; 7–8: Ready for a stranger, Run the full list with someone outside the team, on a phone, with a fresh wallet.. Rough guide. Eight of the 40 checks in this guide; the bands are our judgment, not measured thresholds.

## How should you run this checklist?

Give it to someone who hasn't seen the product. Have them use a phone and a fresh wallet with no funds, then one with a small balance on the wrong network. Tick only what they could do without help. Six to eight weeks before the raise or launch leaves time to fix what fails, and the timeline in our [startup launch checklist](/insights/startup-launch-checklist) works back from the date.

## Product: the flows a holder actually uses

- [ ] The screen before the wallet picker says what connecting unlocks. A lone "Connect wallet" button asks for trust and gives no reason, and in the rewards set, 23 of 208 passages said connecting a wallet or signing is the risky part.
- [ ] The wallet picker tells someone without a wallet how to get one, or lets them continue without one. In the wallets set, 70 of 384 passages said crypto is too complex for a first-time user.
- [ ] Every signature request is explained in your interface before the wallet shows it: what it is, what it costs and what it allows. Wallet pop-ups show what the contract asks for, which is rarely written for people, and signing and approvals came up in 70 wallet passages.
- [ ] A sign-in signature is labelled as a login message that costs nothing and moves no funds. Telling a login apart from a transaction is the question first-time users can't answer on their own.
- [ ] Token approvals ask for the amount the action needs, and the screen says so. Careful users check approval amounts, and an unlimited approval is the first thing they question.
- [ ] Every failed transaction says what failed, whether any funds moved and what to do next. Failed or stuck transactions are a common complaint in our wallets set: 80 of 384 passages, 53 of them from people it happened to.
- [ ] A slow transaction shows a pending state that says it's waiting on the network, with a link to it on the block explorer. During congestion, a transaction with no status looks like lost money.
- [ ] Empty and wrong states each have their own screen: no balance, no gas token, the wrong network, nothing staked yet. A screen that only shows zeros is where a first-time user gives up.
- [ ] Pools, campaigns and claims show whether they are active, paused or ended, and an ended one can't be joined. In the wallets set, 66 passages were about scams and paused withdrawals, and 17 about lock-ups and getting money out.
- [ ] The lock period, the reward rate and where rewards come from appear before someone stakes, and again in the confirm step. Where the rewards come from is the question in 25 wallet passages.

For HubsAI's $HUBS launch, we mapped 32 states, 9 of them errors or empty states, before designing a single screen. The staking product came to 50 screens and states, from wallet connect to claiming rewards, and its notifications say plainly when something goes wrong, for example "Network Congestion: Transactions may take longer to confirm". The [HubsAI case study](/projects/hubsai) shows the connect flow step by step.

## Trust signals: can someone check that you're real?

- [ ] One page lists every contract address, chain by chain, each linked to a verified contract on the block explorer and copyable in one tap. The top theme in the rewards set was "looks like another token promo, presale or rug", at 95 of 208 passages, and a canonical list is how a holder tells you apart from a copy.
- [ ] The app, the website, the docs and the launch announcement all show the same addresses. One mismatched character is enough for a careful holder to wonder whether the site is fake.
- [ ] A page lists your official domains and social accounts and says what the team will never ask for, such as a seed phrase or a wallet connection through a direct message. Scams around a launch borrow your name, and this page gives people something to check against.
- [ ] Each audit links to the full report on the auditor's own site, with the auditor's name, the date, what was in scope and how the findings were resolved. A badge on its own doesn't say what was checked.
- [ ] The docs are current, and the app links to the right page at the moment someone has the question. Help that sits three clicks away from a confirm button rarely gets read.
- [ ] People can see who is behind the project: named founders with real profiles or, for a pseudonymous team, the backers, auditors and partners who know who they are. Across all three research sets, scam and cash-grab worries were the most common theme, at 282 of 978 passages.

## Brand: would anyone know it's you?

- [ ] Put your homepage next to five competitors' homepages with the logos covered, and check that you can still pick out your own. A look borrowed from the category tells a sceptic you're one more token in the feed, which is the doubt they arrived with.
- [ ] One ownable element runs through everything: a colour with a job, a typeface, an illustration style or a way of showing the product. Glowing coins and neon gradients on black are free for anyone to use, so they can't identify anyone.
- [ ] The app, the site, the deck and the social posts share the same colours, type and components. A holder who goes from a post to the site to the app should feel they never left.
- [ ] Colour has jobs: one colour for actions, one for failures, and red never used for decoration. When colour carries meaning in the product, people read status at a glance.
- [ ] The token name, ticker and product names are spelled and capitalised the same way everywhere. A ticker written three ways looks like three projects.

We were Everreach Labs' whole design team through 2024 and 2025, and one dark world ran across the quest hub, the $EVER claim portal, the tokenomics site, the whitepaper and every campaign, with mint and lime kept for anything a player could act on. On HubsAI, one teal marks every action and status, and a failure red appears only on failed transactions, errors and ended pools. A short timeline doesn't rule out a full system: [TICKIZ](/projects/tickiz), a ticketing platform, got its complete identity in four weeks.

## Token launch website checklist: is the utility clear, and does every claim state have a screen?

- [ ] The first screen says what the product does and for whom, in plain words, without needing the token to explain it. Nielsen Norman Group's analysis of page visits found that a page has to communicate its value proposition within 10 seconds to earn more of a visitor's time.
- [ ] The product is visible in the first screen: a real screen, a short loop or the film. In the rewards set, people said they act when a real product sits behind the token.
- [ ] Reward amounts and token prices come after the product. In the launch film we made with OMNI for Watt2Trade, half the running time is the product itself, and the reward amount never appears on screen.
- [ ] A token page explains what the token does inside the product before it shows supply, allocation, vesting with its cliffs and the unlock schedule. Lock periods, vesting and the source of rewards are what sceptics ask about first. The legal and region notice belongs on this page too. Your counsel writes the wording, and the page puts it where people read it before they connect or claim.
- [ ] Every tokenomics chart and table reads on a phone, adds up to 100% and matches the whitepaper and the deck. For Everreach, we worked the tokenomics site through at desktop, tablet and phone, with every chart state.
- [ ] Someone without a wallet can still understand the product and take a first step. In the games set, 112 of 386 passages said owning something on a chain adds nothing, so Everreach's claim portal has an "I don't have a wallet" path that keeps anyone from being blocked by crypto.

A claim page can end in more than one way. These four outcomes each need a screen of their own before launch. The wrong-network, no-gas and pending states are in our [wallet onboarding guide](/insights/how-to-design-wallet-onboarding).

- **Not eligible.** Say which rule applied and when the list was fixed. Jupiter's airdrop checker docs list Ineligible as a status and say the tool does not determine why a wallet is or isn't eligible, so the reason has to come from your own page. Arbitrum's docs give a model to quote: eligibility fixed at a snapshot on February 6, 2023, and a score under 3 listed as "Not eligible".
- **Already claimed.** Show the amount and a link to the claim transaction on the block explorer, and remove the claim button. Jupiter's docs describe a Claimed status with a View TX link to the transaction. Uniswap's open-source Merkle distributor has an error for a second claim, AlreadyClaimed. While the window is open, Arbitrum's distributor gives a wallet that has claimed and a wallet that was never listed the same answer, "nothing to claim", so the page has to check first and tell them apart.
- **Not open yet, or closed.** Show the date and time in the person's own time zone, and say what happens to anything unclaimed. Jupiter's docs list Claimable later, with the button disabled until the window opens, and Expired, after which the tokens cannot be recovered. Arbitrum's docs give both dates, March 23 and September 24, 2023, and its distributor refuses claims outside that window.
- **Rejected.** Say who said no. If the person taps Reject in their wallet, nothing is wrong. The Ethereum provider standard, EIP-1193, gives that its own code, 4001, "User Rejected Request", so say that nothing was sent and offer to try again. If the contract refuses the claim, as Uniswap's does for a proof that doesn't match its list (InvalidProof), give the reason and the next step.

## Whitepaper and docs: do they read like the product?

- [ ] The whitepaper opens with the problem and the product, and the economy comes after. In the games set, 31 passages ask where the game is, and Everreach's 46-page whitepaper spends its first 26 pages on the game before the economy starts on page 27.
- [ ] It's set in the same design system as the site and the app. A reader who lands on page 12 from a shared link should know it's yours without seeing the logo.
- [ ] It reads on a phone, as a web version or a PDF set at a size that works at phone width. Whitepaper links get shared in posts and group chats, where people open them on a phone.
- [ ] Every number matches the token page and the deck, and the cover carries a version number and a date. A reader who finds two different supply figures has to guess which one is right.
- [ ] The docs start with a quickstart and the contract list, then answer the questions support hears most. Each question answered there is one fewer ticket on launch day.

## Investor deck: does it match the product?

- [ ] Every product screen in the deck is the product as it ships, or is clearly labelled as a design in progress. An investor can open the app after the meeting and compare.
- [ ] The deck uses the same type, colour and product names as the site and the app. Our [Series A brand readiness guide](/insights/series-a-brand-readiness) covers why the website and deck should tell one story in one visual system.
- [ ] Token slides use the same supply, allocation and unlock numbers as the token page and the whitepaper. A number that differs between the deck and a public page becomes a diligence question.
- [ ] Each traction number has its source and date next to it: wallets, holders, volume or retention. An investor will ask where each one comes from.

## Launch assets: TGE, mainnet or a rewards campaign

- [ ] A launch film or clip shows the product in its first seconds, is cut for each channel and is finished a week before the date. The film we made with Watt2Trade's agency OMNI for its rewards launch helped drive 260,000+ wallet connections, as one part of a wider launch. Sizes for every channel are in our [launch video specs](/insights/launch-video-specs).
- [ ] The announcement post carries the official link and the contract address, and someone watches the replies for fake links from the first minute. A fake link in the top replies reaches the same people who saw your post.
- [ ] Quest, campaign and claim pages state their terms before anyone starts: what you get, the rules, the end date and who is eligible. In the games set, 20 passages call quests and dailies chores, and in the rewards set, 19 say rewards get farmed by bots and dumped. Everreach's quest pop-ups show the XP before you start and write the rules on the quest itself.
- [ ] Share images, a press kit and replies to the obvious questions, such as eligibility and which chain, are ready before launch day. The full asset list and its timing are in our [startup launch checklist](/insights/startup-launch-checklist).

## How does Alterra Studio help Web3 teams before a raise or launch?

Alterra Studio is a senior product and brand design team for Web3 teams from seed to Series B. We design the product flows on this list, from wallet connect and signing to staking, claims and their failure states, along with the brand, the token launch website, the whitepaper, the deck and the launch film, all in one system. For Everreach Labs we were the whole design team through 2024 and 2025, including the quest hub, the $EVER claim portal, the whitepaper and the Figma file the team worked from. For HubsAI we designed the landing page and a staking product of 50 screens and states. See our [product design service](/services/product-design), how we work with [Web3 teams](/industries/web3), or the [glossary](/glossary) for the terms used here. We price after a short call; see [how we price](/pricing).

## The short version

- Fix the wallet flows first: say what connecting unlocks, explain every signature in plain words, and design failed, pending, empty and ended states as carefully as success.
- Make trust checkable with one page of verified contract addresses, full audit reports, current docs and a clear answer to who is behind the project.
- Give the brand one ownable element and run one system across the app, site, deck, whitepaper and social.
- On the token launch website, show the product and what it does within seconds, put the token's terms and the legal and region notice on a page that reads on a phone, and give a claim page a screen for not eligible, already claimed, not open or closed, and rejected.
- Keep every number the same across the token page, whitepaper and deck, and have launch assets ready a week before the date.

## Sources

Checked October 30, 2026, except the five claim-state sources, which were checked October 31, 2026.

- Alterra Studio, [Why people don't trust crypto products: 978 comments, sorted](/research/crypto-trust-2026) (October 2026), with the aggregate counts as a CSV download.
- Pew Research Center, [On cryptocurrency, 63% of US adults not confident it's safe, reliable](https://www.pewresearch.org/short-reads/2024/10/24/majority-of-americans-arent-confident-in-the-safety-and-reliability-of-cryptocurrency/) (October 24, 2024).
- Nielsen Norman Group, [How Long Do Users Stay on Web Pages?](https://www.nngroup.com/articles/how-long-do-users-stay-on-web-pages/) (Jakob Nielsen, September 11, 2011).
- Jupiter, [Airdrop Checker](https://docs.jup.ag/user-docs/manage/portfolio/airdrop-checker) (page last modified October 6, 2026 per the site's sitemap, checked October 31, 2026), the Ineligible, Claimable later, Claimed and Expired statuses and what the checker does not explain.
- Arbitrum Foundation, [$ARB airdrop eligibility and distribution specifications](https://docs.arbitrum.foundation/airdrop-eligibility-distribution) (undated page, checked October 31, 2026), the snapshot date, the claim start and end dates and the eligibility table.
- Arbitrum Foundation, [TokenDistributor.sol](https://github.com/ArbitrumFoundation/governance/blob/ed01fe8adb1af82a99be180894fae153e34c52b7/src/TokenDistributor.sol) (source file last changed December 2, 2022, checked October 31, 2026), the claim start and end checks and the "nothing to claim" message.
- Uniswap, [MerkleDistributor.sol](https://github.com/Uniswap/merkle-distributor/blob/25a79e8ec8c22076a735b1a675b961c8184e7931/contracts/MerkleDistributor.sol) (source file last changed November 21, 2022, checked October 31, 2026), the AlreadyClaimed and InvalidProof errors.
- Ethereum Improvement Proposals, [EIP-1193: Ethereum Provider JavaScript API](https://eips.ethereum.org/EIPS/eip-1193) (checked October 31, 2026), provider error code 4001, User Rejected Request.
