
| I Build For Web3 teams: Positioning, GTM, Growth and Community | Content Marketing | CMO @twin3_ai | Follow me for Tips and useful growth frameworks |
Check my Highlights
Joined September 2024
- Tweets7.2K
- Following1.1K
- Followers4.2K
- Likes9.8K
Pinned Tweet
Most Web3 projects donβt blow up because of hype.
They blow up when they finally get clear, consistent, and community-driven.
Thatβs where I come in.
I help Web3 startups unlock real growth, the kind that brings users, not just followers.
Hereβs what I do:
β Rewrite your messaging so people finally get it
β Build sprint-based growth roadmaps (not random posts)
β Turn your active users into micro-ambassadors
β Run marketing campaigns that feel organic, not forced
β Use memes, threads, AMAs, KOLs, and bounty systems intentionally
β Help you partner with aligned DAOs & alpha groups
β Bring narrative, not noise
No paid ads. No influencer spam. Just real playbooks.
I build in public. I teach as I do.
And I love helping founders bring their mission to life through smart marketing.
If youβre a Web3 builder who wants:
β’ Community-led growth
β’ Positioning that clicks
β’ Campaigns that work
β My DMs are open π¦
@web3eaglealpha
Letβs scale your vision.
I think these has to be the largest freeze in the history of hacks...
But why didn't this kinda freeze happen during the bybit hack?
Community managers, what is one thing that helped your server become more active without relying on giveaways?
You don't build an active community by opening more channels.
Give people a reason to return, a reason to participate and a clear idea of what the community is for.
the idea of just saying what you actually think is gonna happen (oil stays high, rates come down slower than people expect, whatever) and then having something build a real portfolio around that, show you how it would've done, and then actually run it is kinda different from the usual "here's a signal" stuff.
what gets me is you can just tag @fxyzai under any random post and it builds it right there. so instead of just arguing in the replies you can turn the take into positions and see if it even holds up. also the part where it keeps watching news and updates based on your feedback feels like it could either be really useful or completely chaotic depending on how much you mess with it.
gonna try a couple of my own takes on it later and see what it comes up with. the "starts with practice money and can't withdraw" thing is at least a reasonable way to do it instead of just letting people dump real money in on day one.
check the comments so you understand the underlying technology @fxyzai is building.
Every market order on Pacifica pays the full taker fee. No exceptions. Most traders just treat that as the cost of wanting to be filled now.
@fxyzai built a way around it.
@fxyzai is an AI-native trading workspace for onchain markets. Describe a rule and it builds the thing you need from it β a running executor, a dashboard, a guardrail. No code.
Type "make a chase limit executor" into the prompt bar and it's live in seconds. There are ready-made templates too: chase limit, TWAP, iceberg, DCA, funding arb.
The fee problem is straightforward. Want filled immediately? Market order. Market order means taker fee, every time. You could re-peg a limit order by hand as price moves, but in practice nobody does that consistently.
Their fix is a chase limit executor. It posts post-only, so every fill counts as a maker, then tracks the best bid or ask tick by tick until it fills.
You still set the risk yourself. Offset controls how far from the touch it sits. Follow mode is either Maintain, which tracks price in both directions, or Trail, which moves one way only and holds through pullbacks so they still get filled.
Peg to lets you sit on your own side of the book or one tick inside the opposite quote, still post-only. Max chase distance acts as a kill switch if price runs away from your entry. Poll interval sets how often it re-checks the book.
None of this needs real money to test. There's a paper trading mode with its own starting balance, so you can run the executor before switching it live.
In the demo, it opens a BTC position on Pacifica by chasing the best bid, then closes the same position using the identical logic. Maker rate going in, maker rate coming out.
The fee difference is the whole pitch: 0.32 per fill on a market order versus 0.12 per fill through the chase executor. That's 62% less paid in fees, and it applies to every trade run this way, not a one-time saving.
f(.)xyz isn't built around one exchange either. It runs as a single terminal across Hyperliquid, Lighter, Backpack, and Pacifica, you build the strategy once, run it wherever liquidity is best.
Top 3 bots to fork and use on fxyz
There are already some interesting bots you can fork, customize, and put to work on @fxyzai .
Here are 3 I think you should check out π
Web3 Growth Notes β Day 3
One thing I think Web3 projects need to pay more attention to is how they choose creators for their marketing campaigns.
I've seen people focus so much on follower counts that they forget to ask the most important question.
Can this creator actually help us reach the people who might use our product?
Think about it.
A creator has 100k followers and promotes your project. The post gets thousands of likes, plenty of impressions, and people talking in the comments.
But after the campaign, how many people actually visit your platform? How many try the product? How many become regular users?
Now imagine another creator with just 2k followers who understands your product and has an audience that trusts their recommendations.
That creator might bring fewer impressions but attract people who are genuinely interested in what you're building.
Do you see the difference?
I'm not saying creators with big audiences are not valuable. They can be very useful, especially when your goal is awareness and visibility.
But a big audience doesn't automatically mean a good campaign.
This is why I believe projects need to look beyond follower counts when choosing creators.
β’ Look at their audience.
β’ Look at the kind of conversations they generate.
β’ Look at whether their content reaches the people you're trying to attract.
And if your goal is to bring in users, make sure you're tracking results beyond likes and impressions.
Because at the end of the day, you need to know what the campaign actually did for your project.
Sometimes, the creator with the biggest audience isn't the one you need.
The question is, are you choosing creators because of their numbers, or because they can help you achieve your goals?
Web3 Growth Notes β Day 2
Not every Web3 project needs to spend more money on marketing.
Sometimes, the problem is that you're marketing on the wrong channel.
I've seen people act like if you're building in Web3, you must be active on X, grow a Discord, post on Telegram, run campaigns, and do everything at once.
But do you really need all of that at the same time?
Let's say you're building a product for developers.
You can spend weeks posting general content on X, hoping developers will notice you.
Or you can identify where those developers already spend their time, the kind of content they pay attention to, and what would make them interested in trying your product.
Which one makes more sense?
This is where I think some teams get it wrong.
They copy what worked for another project without asking if it can work for theirs.
One project might grow through X because its audience loves discussions and educational content.
Another might get better results from developer communities, technical documentation, partnerships, or direct outreach.
It doesn't mean one project has a better marketing team than the other.
Their audiences and products are different.
The channel that works for one project might not work for yours.
Before you start spreading your team across every platform, ask yourself:
β Who exactly are we trying to reach?
β Where do these people already spend their time?
β What kind of content or activity would get their attention?
β How will we know if this channel is actually bringing results?
You don't have to be everywhere to grow.
Find the channels that make sense for your product, test them, pay attention to the results, and put more effort into what works.
Of course, you won't always get it right on the first try. That's why you test instead of just assuming.
Marketing isn't about being everywhere.
It's about getting in front of the right people with the right message.
A Discord with 10k members and no conversations is not the flex some projects think it is.
Member count is easy to show.
A community that actually cares is a different thing.
tbh, I think this is one thing a lot of Web3 projects still get wrong.
Having 100k followers is good, but if those followers aren't bringing people who actually use your product, what exactly are you paying for?
Sometimes, a smaller creator with the right audience can bring better results than a big account.
It's not always about how many people see your project. It's about reaching the right people.
Stop choosing creators based on numbers alone. Look at the results too.
unpopular opinion: 100k followers mean nothing if you can't bring real users to a project.
a creator with 2k engaged followers who converts users is more valuable than one with 100k followers who only brings likes and impressions.
read that again.
we've become so obsessed with follower counts that projects sometimes choose creators based on numbers instead of results.
will web3 ever get better?
Can you explain your project in one sentence without using the words innovative, revolutionary or next-gen?
Web3 Growth Notes β Day 2
Not every Web3 project needs to spend more money on marketing.
Sometimes, the problem is that you're marketing on the wrong channel.
I've seen people act like if you're building in Web3, you must be active on X, grow a Discord, post on Telegram, run campaigns, and do everything at once.
But do you really need all of that at the same time?
Let's say you're building a product for developers.
You can spend weeks posting general content on X, hoping developers will notice you.
Or you can identify where those developers already spend their time, the kind of content they pay attention to, and what would make them interested in trying your product.
Which one makes more sense?
This is where I think some teams get it wrong.
They copy what worked for another project without asking if it can work for theirs.
One project might grow through X because its audience loves discussions and educational content.
Another might get better results from developer communities, technical documentation, partnerships, or direct outreach.
It doesn't mean one project has a better marketing team than the other.
Their audiences and products are different.
The channel that works for one project might not work for yours.
Before you start spreading your team across every platform, ask yourself:
β Who exactly are we trying to reach?
β Where do these people already spend their time?
β What kind of content or activity would get their attention?
β How will we know if this channel is actually bringing results?
You don't have to be everywhere to grow.
Find the channels that make sense for your product, test them, pay attention to the results, and put more effort into what works.
Of course, you won't always get it right on the first try. That's why you test instead of just assuming.
Marketing isn't about being everywhere.
It's about getting in front of the right people with the right message.
Web3 Growth Notes β Day 1
a lot of projects want growth, but not everyone understands what growth actually requires.
A founder launches a project, starts posting on X, opens a Discord server, announces partnerships, maybe runs a campaign, and expects things to move.
But after some time, the numbers are not looking good.
The X account isn't getting the attention they expected. The Discord has members, but only a few people are actually talking. The content is going out, but it's not bringing the right people to the project.
Then the question becomes, "What are we doing wrong?"
Sometimes, the problem isn't that the team isn't working hard enough.
The problem is that the activities are not connected to a clear growth strategy.
Let me explain what I mean.
1. You need to understand your positioning first.
Before you start pushing content everywhere, can people actually understand what your project does, who it's for, and why they should care?
If someone visits your X profile today, will they understand what you're building in a few seconds?
If they read your last five posts, will they understand the value of your project?
If the answer is no, bringing more people to your page might not solve the problem.
You could be getting attention without giving people a good reason to stay.
2. Your marketing activities need to work together.
Content, community, partnerships, and growth campaigns shouldn't feel like four different departments doing their own thing.
For example, let's say you're launching a new Web3 product.
Your content should help people understand the problem you're solving.
Your partnerships should help you reach relevant audiences and build credibility.
Your community should give interested people a place to learn, ask questions, contribute, and stay connected.
Your growth strategy should help you understand which activities are actually moving people closer to using your product.
Do you see how these things connect?
It's not just about doing more. It's about making sure each activity has a purpose.
3. Stop measuring growth by numbers alone.
Having 10,000 followers looks good.
Having 5,000 Discord members looks good too.
But what happens when those people don't care about your product, don't participate in your community, and never become users?
This is where some projects get it wrong.
They celebrate the numbers without asking what those numbers are doing for the project.
I'm not saying followers and community members don't matter. They do.
But you need to look beyond the numbers.
Are the right people discovering your project?
Are they engaging with your content?
Are they asking questions, trying the product, contributing to the community, or telling others about it?
Those are the kinds of questions worth asking.
Because attention is useful, but attention alone isn't the same as growth.
So, where should a Web3 team start?
Before spending more money on marketing or adding more activities to the calendar, take a step back and ask yourself three questions:
β Can people clearly understand what we're building and why it matters?
β Are our marketing activities reaching the people we're actually trying to attract?
β Can we tell which activities are contributing to meaningful progress?
Be honest with your answers.
You might discover that you don't need another campaign yet. You might need clearer positioning, better content, a more intentional community strategy, or a better way to measure what's working.
And that's okay.
The goal isn't to look busy. The goal is to make progress.
I'll be sharing more practical lessons on positioning, GTM, growth, content marketing, and community building throughout this series.
If you're building in Web3, I hope these notes help you think through your growth strategy a little differently.
Let's build.
Not every project needs a louder announcement.
Sometimes it needs a clearer message.
More visibility won't fix positioning people don't understand.
If people need 5 minutes to understand what your project does, your positioning probably needs work.
Clarity makes it easier for people to care, remember how you and explain you to someone else and that makes it much easier.
A Web3 project can have a good product and still struggle to get users.
Sometimes the problem is not the product.
It's positioning, distribution and how well people understand why they should care.
I won't call these insights @imlocha I would call these a full course approach to getting started with creators...
Thanks for giving these wonderful insights for free.
Web3 Growth Notes β Day 1
a lot of projects want growth, but not everyone understands what growth actually requires.
A founder launches a project, starts posting on X, opens a Discord server, announces partnerships, maybe runs a campaign, and expects things to move.
But after some time, the numbers are not looking good.
The X account isn't getting the attention they expected. The Discord has members, but only a few people are actually talking. The content is going out, but it's not bringing the right people to the project.
Then the question becomes, "What are we doing wrong?"
Sometimes, the problem isn't that the team isn't working hard enough.
The problem is that the activities are not connected to a clear growth strategy.
Let me explain what I mean.
1. You need to understand your positioning first.
Before you start pushing content everywhere, can people actually understand what your project does, who it's for, and why they should care?
If someone visits your X profile today, will they understand what you're building in a few seconds?
If they read your last five posts, will they understand the value of your project?
If the answer is no, bringing more people to your page might not solve the problem.
You could be getting attention without giving people a good reason to stay.
2. Your marketing activities need to work together.
Content, community, partnerships, and growth campaigns shouldn't feel like four different departments doing their own thing.
For example, let's say you're launching a new Web3 product.
Your content should help people understand the problem you're solving.
Your partnerships should help you reach relevant audiences and build credibility.
Your community should give interested people a place to learn, ask questions, contribute, and stay connected.
Your growth strategy should help you understand which activities are actually moving people closer to using your product.
Do you see how these things connect?
It's not just about doing more. It's about making sure each activity has a purpose.
3. Stop measuring growth by numbers alone.
Having 10,000 followers looks good.
Having 5,000 Discord members looks good too.
But what happens when those people don't care about your product, don't participate in your community, and never become users?
This is where some projects get it wrong.
They celebrate the numbers without asking what those numbers are doing for the project.
I'm not saying followers and community members don't matter. They do.
But you need to look beyond the numbers.
Are the right people discovering your project?
Are they engaging with your content?
Are they asking questions, trying the product, contributing to the community, or telling others about it?
Those are the kinds of questions worth asking.
Because attention is useful, but attention alone isn't the same as growth.
So, where should a Web3 team start?
Before spending more money on marketing or adding more activities to the calendar, take a step back and ask yourself three questions:
β Can people clearly understand what we're building and why it matters?
β Are our marketing activities reaching the people we're actually trying to attract?
β Can we tell which activities are contributing to meaningful progress?
Be honest with your answers.
You might discover that you don't need another campaign yet. You might need clearer positioning, better content, a more intentional community strategy, or a better way to measure what's working.
And that's okay.
The goal isn't to look busy. The goal is to make progress.
I'll be sharing more practical lessons on positioning, GTM, growth, content marketing, and community building throughout this series.
If you're building in Web3, I hope these notes help you think through your growth strategy a little differently.
Let's build.













