I got a full-time, 9–5 offer recently and turned it down to focus on Uny (@UnyLive).
The role was in another state, Monday to Friday. I even proposed showing up twice a week, but that didn't work out.
I've weighed my options, and I genuinely believe I made the right decision.
But man, when there's no cashflow coming in from anywhere, and you remember how broke you are, you can't help but revisit that decision sometimes. 😭😂
Anyway, back to business.
Locked in. 🫡
Founders/builders focus on features, but users care more about the experience.
Nobody buys a product just because of what it can do. They buy it for what it can do for them, how it makes them feel, or how it changes their lives.
You're not just selling features. You're selling the experience that comes with them.
I’ve got a list of 70+ Web3 founders I want to engage with on X.
So I started visiting their profiles, one by one.
I expected to find interesting stories about what they’re building.
Instead, I kept finding product updates, technical jargon, and feature announcements.
These are people building interesting things, yet their content makes you work too hard to care.
I think founders get so deep into building that they forget what it’s like to be on the outside.
They know the problems, the failed attempts, the hard decisions.
But when they post, all that disappears.
All we’re left with is an announcement.
It’s like walking into a cinema and being handed the script without knowing what the movie is about.
Your audience doesn’t need another list of features; trust me on that because I am one of your audiences as well.
They need to know what was broken, who had the problem, and why you decided to fix it.
That’s the story behind your product.
You don’t have to dumb down the tech. Just give people a reason to care before asking them to understand it.
For the love of God, hire a competent content person/Head of Content.
And no, this isn’t an ad for you to hire me. Hire someone else if you have to. 😂
Just get someone who can find the interesting bits in what you’re building and turn them into content people actually want to read.
Your timeline is teaching people what to expect from you.
Make it worth their time.
Your product might be why people stay.
Your story gives them a reason to pay attention.
➠ We've forgotten why we started creating content.
Recently, @HeyYoGB called out something in my approach to content that got me thinking.
It wasn't that I lacked ideas or expertise to share. It was that I wasn't doing enough to demonstrate what I could actually do with them.
It reminded me of a conversation I had with @jon_es2, about something I think many of us have overlooked:
We've blurred the line between creating content and demonstrating our expertise.
There are people in Web3 who are excellent at what they do, yet struggle to find opportunities to put their skills to work.
Of course, market conditions, limited opportunities, positioning, and connections all play a role.
But I wonder if we also need to rethink how we use content.
Are we creating content to become known, or using it to show people what we're capable of?
There's nothing wrong with building an audience. But not everyone wants to become a content creator.
Some of us simply want to get hired, land clients, or help companies solve problems and grow their businesses.
Shouldn't our approach to content reflect that?
Imagine you're a growth marketer. Instead of sharing another post about growth strategies, you could identify an early-stage company with an interesting product, examine its growth opportunities, and demonstrate how you'd approach one of them.
As a designer, you could show how you'd improve a product's user experience.
As a developer, you could build something that demonstrates your technical ability.
As a product marketer, you could analyse a product's positioning and show how you'd communicate its value more effectively.
You're not just telling people what you know. You're giving them a reason to believe you can do the work.
Your content becomes more than a way to attract attention. It becomes evidence of your thinking, capabilities, and the problems you can solve.
But there's another part to this.
Demonstrating your expertise is only half the equation. You also need to create a path for that expertise to generate opportunities.
Who needs what you do? What problems are they trying to solve? Are the right people seeing your work, and are you building relationships with them?
You can be exceptionally good at what you do and still struggle to find opportunities if the people who need your expertise never see it or understand its value.
Simply posting more won't necessarily fix that.
You need to be intentional about the problems you demonstrate your ability to solve, the companies you want to reach, and how you connect your expertise to their needs.
This doesn't mean auditing every company's business for free. It means being deliberate about demonstrating your capabilities and turning that demonstration into meaningful conversations and opportunities.
You don't necessarily need a massive audience. You need the right people to understand the value you can bring.
That's something I'm beginning to think about more deliberately myself.
Instead of constantly asking:
What should I post today?
Perhaps we should ask:
What can I demonstrate that shows the kind of problems I can solve?
And then:
Who needs to see it?
I'm still figuring out what this looks like in practice, but I think it's a better starting point for those of us who want our expertise to create opportunities.
Maybe we don't need to create more content. Maybe we need to make our content count for something beyond attention.
Because creating content and demonstrating expertise aren't necessarily the same thing.
And if our goal is to turn our skills into opportunities, perhaps it's time we started treating them differently.
@kenn_ronin and @Designer_Elo are two of my favourites doing this as well.
A great journey and a solid demonstration of expertise.
There's something powerful about documenting your work and letting people see what you can actually do.
Respect, Pulkit. 🫡
xitter.cf/Pulkit_Kudiwal/status/…
Temitayo retweeted
If you are coming to NYC for token2049 and need help curating an event I am a dm away
Books give you time, age and wisdom you haven’t lived yet.
They let you learn from experiences you haven't had, understand things you haven't encountered, and access minds you might never meet.
A book is a time machine.
i’m temitayo, 23.
a startup founder, systems thinker and professional figure-it-out-as-i-go dude from nigeria.
just fcking around and finding out.
Things building Uny has taught me at 23.
If someone asked me, “What has building Uny taught you at 23?”
I think the first thing I'd say is that an idea can sound really good in your head and still be completely unproven.
I’ve had people hear the Uny idea and go, “yeah, I’d use that.”
It feels good.
But then you go outside and actually talk to students, organisers, agents, vendors...
You start noticing all the little things you completely missed while sitting with the idea.
I remember manually helping students find accommodation before Uny was even live.
That experience changed something for me.
I realised you don't always need the finished product to test whether there's something worth building.
Sometimes you just need to get your hands dirty and solve the problem yourself.
I’ve also learned that validation feels very different when there’s something real on the line.
Someone actually paying you.
Someone coming back because they need help again.
Someone changing what they normally do because you've made something easier.
Those moments hit differently from someone saying, “this is a cool idea.”
And I've had to learn not to dress up the story either.
There’s a lot of pressure as a founder to make it look like everything is moving.
Big numbers. Big projections. Big announcements.
But if something hasn't happened, it hasn't happened.
I'd rather have a small piece of real evidence than a beautiful story I can't defend.
I think I'm also learning that building a startup is basically a long conversation with reality.
You have an idea.
Reality pushes back.
You adjust.
You try again.
Reality pushes back somewhere else.
And slowly, the thing you're building starts looking less like what you imagined and more like what people actually need.
At 23, I don't think I know enough to have all the answers.
But I know I'm much less interested in proving that I'm right now.
I just want to find out what's true.
And keep building from there.
I was still up working late into the night when @jon_es2 ' message notification popped up.
I read it and froze.
Still speechless.
A week ago, he was talking about getting back to the grind.
We speak about tomorrow as if it belongs to us. 😞💔
RIP @Le_vite1 🤍🕊️
Reminds me of this piece I wrote:
xitter.cf/c8__el/status/20012416…



















