web3 growth & community strategist β’ content marketer β’ discord operations β’ research & educator all tweets are NFA. tg channel - https://teapawt.net/t.co/fpDIcxbWKf
π
Joined June 2025
- Tweets8.7K
- Following430
- Followers624
- Likes13.3K
Pinned Tweet
i've been around web3 for a while now, but i realized i've never really explained what actually do here.
so, let's fix that.
i work around web3 community and growth strategy, community management, discord operations, content marketing, research, and education.
but community is where most of my experience started.
when i first got into web3, i joined a few communities and became fascinated by how people interacted, learned, participated and actually felt like they belonged.
later, i joined a community that had regular classes, trivia nights, moderation opportunities, spaces and different ways for members to contribute.
that experience changed how i looked at communities.
i started noticing that a community isn't just a discord server with hundreds of people inside.
it's the structure behind it.
- how people enter.
- what they see.
- how safe the space is.
- how they participate.
- what makes them stay.
- how they're recognized and
- how the community connects back to the actual product.
that's also where i started noticing some of the things web3 projects get wrong.
- some communities depend too much on incentives to attract people.
- some have no proper onboarding.
- some discord servers are poorly structured, difficult to navigate or filled with unnecessary channels.
- some don't have proper security systems in place and
- sometimes, projects simply copy activities from another community without asking whether that activity actually makes sense for their own product.
i don't think every community needs the same playbook.
a DeFi project, an NFT project, an education platform and a consumer app can all need completely different community strategies.
that's the part i enjoy figuring out.
when i work with a community, i naturally look at things like:
β discord structure and accessibility
β onboarding and member experience
β community safety
β engagement and activities
β roles and recognition
β member behavior and retention
β how the community connects with the product
β growth opportunities
i've had the opportunity to work with projects like @NoventiaHq and @AlphanumeriaSol, where i've been involved in community management, discord operations, community structure, engagement and growth-related work.
i've also worked on research and content around different web3 projects, while continuing to learn more about the space.
i'm still learning.
i'm not going to pretend i'm an expert in every part of web3.
there are areas i'm still exploring, and there are things i want to get better at.
but i know what i'm good at:
- understanding communities
- organizing them
- creating ways for people to participate, and
- thinking about how community can contribute to the growth of a project.
so if you've mostly seen me on the timeline and wondered what i actually do:
now you know.
i'm facaw flinch aka @web3flincher
web3 community & growth strategist | community manager | discord operations | content marketing | research | educator.
Facaw Flinch βπ retweeted
Your AI agent can spend your money. Who stops it when it spends too much?
That question is exactly why @Baronoffweb3 and I have been building BILA: an autonomous payment and financial governance layer for AI agents.
Built for the @NEARProtocol hackathon. How it works.𧡠π
Facaw Flinch βπ retweeted
this is never meant to be a joke.
but try as much as you can to give people reasons to come to your brand always.
quote with your banner if you want π
π€ Paid partnership
Facaw Flinch βπ retweeted
this is never meant to be a joke.
but try as much as you can to give people reasons to come to your brand always.
quote with your banner if you want
this is never meant to be a joke.
but try as much as you can to give people reasons to come to your brand always.
quote with your banner if you want π
π€ Paid partnership
Facaw Flinch βπ retweeted
from a recent research of mine, I saw that the creator economy is projected to attract $37 billion in US ad spend in 2025, a 26% increase from 2024.
according to IAB's 2025 report, brands still rank these among their biggest needs:
-β’ 28% want better attribution.
-β’ 26% want consistent reporting.
-β’ 25% need better creator discovery and vetting.
-β’ 24% want stronger audience authentication and fraud prevention.
the money is flowing into creator marketing, but the infrastructure hasn't caught up.
brands are increasing their creator budgets, yet they still struggle to identify the right creators, prove campaign ROI and detect inauthentic engagement.
and man, that is a serious infrastructure gap, and it's exactly the kind of problem @launchpoint is trying to solve.
creators are tired of chasing brand deals, dealing with delayed payments and having their work undervalued.
creator marketing needs a better system.
@launchpoint is attempting to build that system through a platform that handles creator sourcing, campaign management, content verification, performance tracking and payouts.
launched in August 2024 as an NIL app for Ohio State athletes, the company has since evolved into a media distribution engine for high-growth companies.
it's focus is to make creator-led campaigns easier to launch, manage and measure at scale.
π§΅β―
Facaw Flinch βπ retweeted
As a community expert, there are alot of things you need to know before you can build a solid community.
But, the foundation of everything you need to know, the main thing you need to know before you can build any community is π§π΅π² π°πΌπΊπΊππ»πΆππ π΄πΏπΌπππ΅ πΉπΆπ³π² π°ππ°πΉπ².
They Include:
β
οΈ Acquisition.
β
οΈ Adoption.
β
οΈ Retention.
β
οΈ Advocacy.
β
οΈ Business Outcome.
If you can master this, there is no community you will have trouble building.
I spoke in detail on that in the video below π
Facaw Flinch βπ retweeted
not every web3 project needs a telegram community.
and not every project should be building on discord.
but somehow, the first thing many projects do after launching is create a telegram group.
why?
because that's what everyone else is doing?
i've seen projects launch a telegram, add a buy bot, and start chasing members before anyone can explain what the community is supposed to achieve.
this is where the problem starts.
before choosing a community platform, ask yourself:
what is the purpose of this community?
are you trying to:
- get feedback from users?
- educate people about your product?
- track contributions?
- build a group of people who actively use your product?
- create a space for discussions, support, and governance?
your answer should influence where and how you build.
telegram is great for quick conversations, announcements, and easy access. It can work well for communities that thrive on fast-moving discussions and market activity.
discord offers more structure.
you can organize discussions into channels, separate support from general conversations, create roles, recognize contributors, and build systems around participation.
if your project depends on people contributing, learning, building, or engaging over time, that structure matters.
but here's another thing people overlook:
not every project needs a community.
sometimes, what you need is a good product, a support channel, and a strong presence on x.
a community without a clear purpose becomes another empty group.
and an empty group doesn't become valuable just because you keep running zealy campaigns or giving away rewards.
stop asking:
"should we create a telegram or discord?"
start asking:
"what do we want people to achieve when they join us?"
because the platform is not the strategy.
the purpose is.
not every web3 project needs a telegram community.
and not every project should be building on discord.
but somehow, the first thing many projects do after launching is create a telegram group.
why?
because that's what everyone else is doing?
i've seen projects launch a telegram, add a buy bot, and start chasing members before anyone can explain what the community is supposed to achieve.
this is where the problem starts.
before choosing a community platform, ask yourself:
what is the purpose of this community?
are you trying to:
- get feedback from users?
- educate people about your product?
- track contributions?
- build a group of people who actively use your product?
- create a space for discussions, support, and governance?
your answer should influence where and how you build.
telegram is great for quick conversations, announcements, and easy access. It can work well for communities that thrive on fast-moving discussions and market activity.
discord offers more structure.
you can organize discussions into channels, separate support from general conversations, create roles, recognize contributors, and build systems around participation.
if your project depends on people contributing, learning, building, or engaging over time, that structure matters.
but here's another thing people overlook:
not every project needs a community.
sometimes, what you need is a good product, a support channel, and a strong presence on x.
a community without a clear purpose becomes another empty group.
and an empty group doesn't become valuable just because you keep running zealy campaigns or giving away rewards.
stop asking:
"should we create a telegram or discord?"
start asking:
"what do we want people to achieve when they join us?"
because the platform is not the strategy.
the purpose is.
not every web3 project needs a telegram community.
and not every project should be building on discord.
but somehow, the first thing many projects do after launching is create a telegram group.
why?
because that's what everyone else is doing?
i've seen projects launch a telegram, add a buy bot, and start chasing members before anyone can explain what the community is supposed to achieve.
this is where the problem starts.
before choosing a community platform, ask yourself:
what is the purpose of this community?
are you trying to:
- get feedback from users?
- educate people about your product?
- track contributions?
- build a group of people who actively use your product?
- create a space for discussions, support, and governance?
your answer should influence where and how you build.
telegram is great for quick conversations, announcements, and easy access. It can work well for communities that thrive on fast-moving discussions and market activity.
discord offers more structure.
you can organize discussions into channels, separate support from general conversations, create roles, recognize contributors, and build systems around participation.
if your project depends on people contributing, learning, building, or engaging over time, that structure matters.
but here's another thing people overlook:
not every project needs a community.
sometimes, what you need is a good product, a support channel, and a strong presence on x.
a community without a clear purpose becomes another empty group.
and an empty group doesn't become valuable just because you keep running zealy campaigns or giving away rewards.
stop asking:
"should we create a telegram or discord?"
start asking:
"what do we want people to achieve when they join us?"
because the platform is not the strategy.
the purpose is.
Facaw Flinch βπ retweeted
The first thing I do on a new project has nothing to do with marketing.
I audit it.
Any project I'm thinking about joining gets a full audit before I agree to anything. I go through it looking for everything that needs my attention, because I never want to be the person saying "I didn't know" a few weeks in.
Once the audit is done, the next question is the team.
If the project already has one, I join it and start working. If it doesn't, I bring in my own team, depending on what we agree in the terms, so we build it together from the start.
Then comes the budget. I draft the marketing budget myself and send it to the founder before anything is spent. I want to know if the structure I've built is something he can actually work with. If it isn't, we find that out in a conversation and not in a bill.
After that, we get to work, and everything lives in one place. The screenshots show what that looks like: one room for all the growth work with the approved audit pinned at the top, and the plan shared with the team so everyone agrees on the framework before the detail gets built.
That's the whole order. Audit, team, budget, then work.
If you're a founder hiring for growth, expect this from whoever you bring in. Someone who wants to see everything first and puts the money on paper before spending it is protecting your project as much as their own name.
If you're a growth lead, try it on your next project. Audit before you agree, settle the team terms before you start, and get the budget in front of the founder before a single dollar moves.
Do the slow part first, and the rest gets easier.
Facaw Flinch βπ retweeted
Hi guys,
I recently created a community called BlockMates, with one goal in mind; to bring Web3 enthusiasts together to connect, share knowledge, exchange opportunities, and grow alongside one another.
So here's what to expect:
- Alpha sharing across memecoins, trading platforms, crypto casinos, gaming projects, NFTs, and RWAs.
- Valuable insights, discussions, and educational resources.
- Grind calls as the community grows.
- GAs featuring cash prizes, Telegram Premium, and X blue checkmark.
My goal is to build a community where everyone has something to learn, share, and gain.
Become a BlockMate: t.me/Kanblockmates
Facaw Flinch βπ retweeted
good morning ct.
one new thing i learnt yesterday - be persistent not consistent.
Facaw Flinch βπ retweeted
value is when you refer someone to a job and he delivers
and then, the dev asked the person to do another job later on.
that's real value and those are the kind of people i need in my network.
