Most people in Web3 don’t evaluate projects.
They vibe, then complain later.
Here’s how i actually break down a Web3 project in 5 steps before I take it seriously 👇
➠ The “Why does this even exist?” test
If I can’t explain the project in one sentence without using buzzwords… others may run but I pitch to fix it.
Yeah, we get paid fixing that.
Real projects solve something. Everything else is decoration.
➠ The people behind it.
I don’t care how clean the website looks.
Who are the founders? What have they built before?
In Web3, anonymous is fine, but incompetent is not.
➠ The token logic (not hype).
What is the token actually doing?
Not “governance” just for vibes. Not “utility” with no usage.
If the token disappeared today, would the product still make sense?
If yes… that’s a red flag.
➠ The community quality.
Not size. Quality.
Are people asking smart questions?
Or is it just “wen airdrop” and “gm fam”?
A noisy crowd ≠ a strong community.
➠ The momentum vs substance balance
Some projects have hype but no depth.
Others have depth but no attention.
The winners usually have just enough hype… and something real underneath.
That’s it.
No fancy metrics. No overthinking.
Just clarity.