People arrive. Nothing happens.
You may call it low engagement.
The actual problem could begin much earlier: no meaningful first action.
Web3 growth diagnostics + strategy
Your numbers can be right and your diagnosis can still be wrong.
Engagement dropped.
Retention weakened.
The community went quiet.
Growth stalled.
Those are symptoms.
02Growth finds the mechanism underneath them... then identifies what should change first.
Start a DiagnosisFor early and growth-stage Web3 teams
Diagnosis before prescription. Evidence before strategy.
Visible signals
Diagnostic reading — example
Awaiting evidence
Engagement
Retention
Members quiet
What's actually happening?
Activation?Retention?Trust?Positioning?Founder dependency?
Recognition / failure states
Your dashboard reports outcomes. It rarely explains them.
People participate once. Then disappear.
More acquisition may temporarily hide it.
Activation happened. Retention didn't.
Everything moves when the founder moves.
Announcements perform. Quiet periods don't.
The room is borrowing the founder's pulse.
Three similar dashboards. Three completely different problems.
Start with the diagnosisA harder truth
More growth can make a broken growth system worse.
Weak activation
More reach creates more people who arrive and leave.
Weak retention
Acquisition hides churn instead of fixing it.
Unclear positioning
Distribution amplifies confusion.
Founder dependency
More members can increase spectators without increasing network strength.
We don't start by asking how to make you louder. We start by asking what happens after people arrive.
Diagnostic map
We investigate the system. Not one metric.
Market
Positioning
Attention
Activation
Retention
Community
Trust
Conversion
Failures cross layers. Sequence is not causal proof.
Growth problems rarely live where they appear.
A retention problem can begin during acquisition. A community problem can begin in positioning. A conversion problem can begin before the user ever reaches the product.
We trace the failure backwards until the evidence stops contradicting the explanation.
Our internal diagnostic system examines behavioural evidence, public surfaces, user pathways, community structure, positioning, incentives and conversion mechanics before recommending intervention.
The P.A.T.R.I.O.T. diagnostic system
Seven dimensions. One diagnostic system.
The surface is visible. The diagnostic depth is not.
Positioning
Does the project own a distinct, defensible space in the market mind?
Activation
Do new members have a clear first action that converts them to participants?
Trust Architecture
How deep does belief in the project itself reach — past Level 1?
Retention Loop
Is there a mechanism pulling members back between announcement events?
Identity Coherence
Can the founder's public voice sustain community belief under pressure?
Onboarding Friction
How many steps and how much confusion stand between interest and participation?
Trust Signals
What external proof exists that this project is real and progressing?
Interactive diagnosis
What are you seeing?
Selected signal
Engagement ↓
Most obvious conclusion
“We need better content.”
What 02Growth would investigate first
- Did attention fall?
- Did participation fall?
- Did existing contributors leave?
- Did the composition of the audience change?
Same symptom. Different mechanisms.Diagnose mine
02Growth diagnosis
Before you buy execution, know what deserves fixing.
A focused investigation into the growth system behind your project. Delivered in 7 days.
Every engagement is scoped as a focused 30-day investigation. Not a retainer. Not a vague monthly. A specific 30-day window with named outputs, named owners and named acceptance conditions. Half upfront on day one. Half at day 30, when you can see exactly what was built.
30
day engagement
50/50
payment split
No 90-day retainer required to understand what is wrong.
01
The constraint
The highest-leverage problem currently restricting growth.
Positioning + Identity Layer
02
The evidence
What we observed and why it supports the diagnosis.
Trust Signals Layer
03
The mechanism
What's causing the visible symptom... and why.
Trust Architecture + Retention Layer
04
The priorities
Three changes tied directly to the diagnosed constraint.
Activation + Onboarding Layer
05
The readout
A 30-minute strategic walkthrough with your team.
All Seven Dimensions
06
The quiet test
A 14-day validation period designed to show whether the mechanism actually changes.
Retention Loop Layer
Process
The process is simple. The thinking isn't.
Signal
You give us the project, context and current concern.
Investigation
We examine public surfaces, product journey, community behaviour, positioning and available evidence.
Diagnosis
We test competing explanations until the strongest mechanism remains.
Readout
You receive the diagnosis, evidence and intervention priorities.
Decision
Execute internally, engage 02Growth, or take the system elsewhere.
You do not have to hire us to implement what we find.
Model difference
We don't begin with a service menu.
Traditional growth model
Problem appears
Sell corresponding service
Content / KOLs / Community
Paid growth / Campaigns
02Growth
What changed?
Why?
What mechanism explains it?
What is the constraint?
What should change first?
Only then decide what execution is necessary.
The recommendation earns the service. The service never determines the diagnosis.
Our strongest client relationships begin with a referral. Every engagement is designed to earn one.
Proof
Evidence, not adjectives.
Case records are published only when the evidence can support the claim.
Record 01 — Growth & distributionVerified
Web3 Community Growth
Growth Strategy & X Positioning
End-to-end growth strategy for an early-stage TON ecosystem project. Repositioned the founder's X narrative, built a structured referral activation sequence, and engineered the community's first independent content contributors within 30 days.
Independent post rate increased from 4% to 31% within 28 days
New member first-action rate lifted from 0 to 22% within 48 hours of joining
Community active during 3 consecutive founder-silent periods for the first time
Delivered by Hamzat — Core Strategist, 02Growth
Download full case recordRecord 02 — Community architectureVerified
DeFi Protocol Community
Trust Architecture & Retention Engineering
Diagnosed a trust bleed at Level 2 of a 1,400-member Telegram community that had stalled despite growing follower count. Rebuilt the activation sequence and introduced the first recurring community ritual that operated without founder prompting.
Quiet-period engagement sustained at 18% average — up from near-zero
Level 2 community members began recruiting independently by day 21
Founder dependency index reduced from critical to stable in 30 days
Delivered by Hamzat — Core Strategist, 02Growth
Download full case recordRecord 03 — Positioning & narrativeVerified
Web3 SocialFi Project
Narrative Positioning & X Growth
Identified a positioning blur problem for a SocialFi project whose X language was interchangeable with eight direct competitors. Rebuilt the founder's narrative spine and content architecture so the project occupied a distinct, ownable position within 45 days.
X follower growth rate 3.4x in 45 days from repositioned content
Community members began using 02Growth vocabulary to describe the project independently
Inbound founder DMs started arriving from content alone by week 5
Delivered by Hamzat — Core Strategist, 02Growth
Download full case recordDiagnostic language
We give the problem a better name.
Founder Dependency
Momentum that exists only while the founder supplies it.
Activation Gap
The distance between arriving and taking a meaningful first action.
Trust Bleed
Belief lost through small, repeated contradictions.
Retention Failure
Participation without a reason to return.
Participation Debt
The growing cost of an audience trained only to watch.
When founders start using better language to describe the problem, they start making better decisions about it.
Fit / not fit
We work with three projects at a time. Right now we have one slot open.
Good fit
- +Existing product or project
- +Some users, attention or community already exists
- +A real growth problem
- +A team that can provide evidence
- +Willingness to change assumptions
Not a fit
- ×Fake engagement
- ×Follower farming
- ×Pump-and-dump objectives
- ×Guaranteed token-price expectations
- ×No substantive product or project
- ×A team unwilling to expose evidence
If you only need noise, we are probably the wrong team. If you need clarity, start here.
Public intelligence
See how we think before you hire us.
Intelligence note 01
Why engagement decline isn't a diagnosis
Unlocks when the live post is verified
Intelligence note 02
The founder-dependency test
Unlocks when the live post is verified
Intelligence note 03
Why acquisition can hide a retention failure
Unlocks when the live post is verified
Begin with the evidence
You already know what changed. Let's find out why.
If the dashboard looks healthier than the behaviour — or the project feels harder to grow than the numbers suggest — we'll start with the evidence.
Diagnostic intake
Start with what you're seeing.
Don't diagnose it for us. Give us the evidence and the consequence.
Step 1 of 6