Web3 hero lines a stranger can repeat: ten rewrites and the rule behind each

The hero of a landing page has one job: a stranger reads it once and can tell someone else what the product does and for whom. Most web3 heroes fail this test not because the writing is bad but because it is written for people who already know. Below are ten hero patterns that appear again and again on project pages, what a sceptical first visitor actually concludes from each, and a plainer line that does the job. The "before" lines are composites of patterns seen on public project pages, not quotes from any client. The "after" lines are illustrative; your own numbers and nouns go in the slots.

The test to apply before you read the list

Cover the logo and the chain name. Read the hero aloud to someone who does not work in crypto. Ask them to say, in one sentence, what it does and who it is for. If they cannot, the hero is not finished. Write the sentence they should have said. That sentence, or something very close to it, is your hero.

Ten patterns and their rewrites

• Before: "Unlocking the next generation of DeFi." What the visitor concludes: nothing; every third project says this. After: "Borrow USDC against staked SOL without unstaking. Devnet live, mainnet 14 Nov." Rule: name the action, the asset and the date.
• Before: "The liquidity layer for everything." What the visitor concludes: this is infrastructure for other builders, and it is not clear which. After: "One deposit, routed to the three deepest Solana pools for your pair. For market makers running under $2M." Rule: if it is for builders or professionals, say which ones and at what size.
• Before: "Built different." What the visitor concludes: the team could not decide what to say. After: "Perpetuals with settlement on-chain every block, not once a day." Rule: replace attitude with the one mechanical difference a competitor cannot claim.
• Before: "Own your data." What the visitor concludes: a slogan with no product behind it. After: "Your trading history, exportable to a file you hold, readable by any wallet. Nothing stored on our servers." Rule: turn the value into a thing the visitor can picture doing.
• Before: "Join 50,000+ users." (on a page launched last month) What the visitor concludes: the number is followers or airdrop farmers, and the rest of the page is probably inflated too. After: "312 wallets have run the devnet demo since 1 Sep. Changelog below, updated weekly." Rule: publish the small true number with its date; it is worth more than a large unverifiable one.
• Before: "Audited. Secure. Trustless." What the visitor concludes: three adjectives, no link, so probably no audit. After: "Audited by [firm], report dated [date], two medium findings fixed (link)." Rule: every trust word needs a linked artefact or it counts against you.
• Before: "Revolutionising payments for the unbanked." What the visitor concludes: the team has not met the user. After: "Send USDC to a phone number in Nigeria; recipient cashes out at any of 1,200 agent locations. Fee under 1%." Rule: name the corridor, the counterpart and the fee.
• Before: "Powered by Solana. Lightning fast. Near-zero fees." What the visitor concludes: the pitch is the chain's, not yours. After: "Order confirmation in under a second, so your market order fills at the price you saw." Rule: translate the chain property into a consequence for this product's user.
• Before: "Coming soon. Join the waitlist." What the visitor concludes: nothing exists yet. After: "Devnet demo open now, no wallet needed to read. Mainnet on 14 Nov for the first 500 wallets that complete the demo." Rule: replace the waitlist with the thing you can already show, and give the date and the cap.
• Before: "A community-owned protocol for the future of X." What the visitor concludes: there will be a token, and the page is really about that. After: "No token. Fees go to the treasury and are published monthly. Governance by the wallets that use it." Rule: if there is no token, say so in the hero's second line; if there is, say what it does in one clause.

Three habits behind every rewrite

• Nouns a stranger can check. Assets, dates, counts, names, links. Adjectives are free, so they are worth nothing.
• One reader. Write for the single person most likely to pay or deposit first. Everyone else can read the docs.
• One action. The hero button does one thing. "Join Discord" next to "Launch app" next to "Read docs" is three exits.

What the hero cannot fix

A clear hero exposes a weak page rather than rescuing it. If the hero now says exactly what you do and the page still does not convert, the problem is further down: the proof section makes claims the visitor cannot verify, the how-it-works is written from the protocol's seat instead of the user's, or the page never says who it is not for. Those are harder to see from inside the team, because you already believe the page.

When a written teardown is worth paying for

Fix the hero yourself; you do not need help for that. A teardown earns its price when the hero passes the one-line test and the page still does not convert, or when you cannot tell which of two or three positionings a stranger would understand. The teardown is a written document: what a sceptical first-time visitor concludes at each scroll depth, what to write instead and in what order, and how the page reads against the alternatives that visitor is comparing you with. It is delivered by email within 24 hours of a matched USDC payment on Solana. Nothing is sent before payment, and nothing is charged before you accept the quote.