Don’t just mass-spam cold DMs and wonder why nobody replies. Sales is personal. And the best outreach usually starts before you ever send the first message. 🧵

Never stop Perfecting you craft.

Indeed the "Best part is no Part"...

Community growth taught me something important: Acquisition is only the beginning. Someone joins. Then what? Do they understand the community? Do they find their people? Do they participate? Do they contribute? Do they eventually bring others? That's where the real work starts.

What's one Web3 growth tactic you think is becoming overused? I'll start: "Let's launch an ambassador program." An ambassador program can't compensate for weak positioning, poor product experience or a lack of genuine community value.

This is true... Let's love lead...

Five questions I'd ask before launching a growth campaign: Who? Problem? Promise? Proof? Distribution? If you can't answer those five clearly, I'd pause before scaling the campaign.

Sometimes a project doesn't need another influencer. It needs a clearer message. Sometimes it doesn't need another campaign. It needs better activation. Sometimes it doesn't need 20K more community members. It needs to understand why the current members aren't participating. The solution isn't always "more."

What ever happens, don't give up on your dreams.

I think about Web3 growth as: Positioning ↓ Narrative ↓ Distribution ↓ Activation ↓ Retention ↓ Referral Most teams want to jump directly to distribution. But distribution is downstream.

Your product description isn't your positioning. "We're building decentralized infrastructure." That's what you're building. It doesn't tell me: 1. Who needs it? 2. What problem does it solve? 3. Why should I care?

If someone landed on your project's website today and gave you 10 seconds: Would they understand: 1. What you do? 2. Who it's for? 3. Why it matters? That's a useful test for any Web3 or project.

This post is going to age like a warning label. When every spec, ticket, test, and report is generated by the same model, and the humans only exist to approve the output, two things disappear: 1. Actual understanding of the system 2. Any record that a specific human did anything that mattered That’s the part people keep skipping. AI can write the code. It cannot give you a soul, a contribution history, or a reason anyone should trust the work. The scarce thing was never lines of code.

Good positioning should make your marketing team's job easier. When the positioning is clear, you know: 1, what to say, 2, who to say it to, 3, where to say it, and what action you want people to take. Without that clarity, every campaign becomes a new guessing game.

What's the most confusing Web3 project positioning you've seen recently? Not necessarily a bad project. A project where you had to read 10 posts before you understood what they actually did.

A simple positioning formula: Audience + Problem + Promise + Proof For example: "We help [specific audience] solve [specific problem] so they can achieve [specific outcome], backed by [proof]." It doesn't have to sound clever. It has to be understood.

"Everyone in Web3" is not an ICP. "Crypto users" is not an ICP. "Developers" is not an ICP. The more specific you can be about who you're trying to help, the easier everything downstream becomes.

One thing I've learned working around Web3 growth: A bigger audience doesn't automatically mean better growth. You can have 100K followers and struggle to get meaningful product adoption. I'd rather have 5,000 people who clearly understand the value than 100,000 people who only know your logo.

Before asking: "How do we get more users?" Ask: Who exactly do we want? What problem do they have? What outcome do we create? Why should they believe us? Where do they already spend attention? That's the beginning of GTM.