After a decade leading design in Web3, I’ve learned that it’s not about how many people you have — it’s about who you have.
We’re currently in the middle of securing a major partnership with one of the leading companies in Web3. I’ve been in situations like this countless times over the past decade.The client is big.The opportunity is significant.And then — as always — the question arises. “Wait, you’re just six people?”
There’s nothing unusual about this
We’re currently in the middle of securing a major partnership with one of the leading companies in Web3.
I’ve been in situations like this countless times over the past decade.
The client is big.
The opportunity is significant.
And then — as always — the question arises.
“Wait, you’re just six people?”
I’m used to it.
The assumption is instinctive: major clients require major teams.
But experience has taught me otherwise.
In fact, if you ask me, the real risk isn’t that we’re small —
the real risk is passing on us.
I don’t just design, I own
Officially, I’m the product designer on this team.
In reality, I operate more like a product owner.
And to be honest, that’s been true for most of my career.
I’ve spent the better part of the last decade designing and building in Web3 —
from leading design at one of the world’s top-three players to getting my hands dirty in early-stage startups and client work.
I’ve seen this space evolve, hype and crash, bull and bear.
If there’s one thing I know for sure, it’s this:
Good products are never about headcount.
They’re about people who give a damn.
In this team, titles don’t define us.
Ownership does.
If something is worth doing, we do it — whether it’s “in our lane” or not.
The strength is in the people
From the outside, we might just look like six people.
From the inside, we’re six people who could each stand in for an entire department.
I say that without exaggeration.
Our engineers?
They don’t just ship — they build with precision and scale in mind.
Product and design?
We’re aligned, decisive, and relentlessly focused on the user.
We don’t need layers of bureaucracy to deliver.
We don’t need a cast of dozens.
What we have is trust, clarity, and accountability.
That’s what delivers real products — consistently.
Small is not a limitation
I get it — clients always worry:
Is the team too small?
Can they handle the scope?
Will they understand what a major partner actually needs?
I’d argue that’s exactly what gives us the edge.
We’re small enough to stay agile,
small enough to move without friction,
small enough to focus on what matters —
the product and the people we’re building it for.
We’ve already proved this, again and again.
The headcount is irrelevant.
The quality of the team?
That’s everything.
The philosophy behind it all
Over the years, I’ve come to live by something Kazuo Inamori taught:
You benefit most when you help others first.
It’s not just something I read in a book —
it’s a mindset that’s shaped every product, every team, and every collaboration I’ve been part of.
Our founder shares this belief.
And frankly, that’s rare in Web3.
Before we ship anything, we always ask:
“Is this good for the user? For the client? For the ecosystem?”
If the answer isn’t a clear yes, we don’t ship.
Simple as that.
We’re not chasing pump-and-dump cycles.
We’re not here for vaporware.
We’re here to build things that make others better —
because when they win, we win.
What I really think
So, am I worried about this partnership?
Not in the slightest.
The six of us?
We’ve got the skill, the experience, and the discipline.
I’m not wondering if we can deliver —
I’m wondering if, by the end of it,
our partner will feel as lucky to have found us as we do working together.
And if history is any guide?
“I can’t believe six people did all this.”
It’s something I’ve heard more than once.