What a Web3 Product Consultant Actually Does
Consulting · 2023-01-15 · 6 min read
When I tell people I'm a Web3 product consultant they usually ask one of two things. "What does that actually mean?" Or "Isn't that just a fancy title for giving advice?"
Fair questions. The consulting world is full of vague titles and vaguer deliverables. So let me break down what this work actually looks like.
What the Job Actually Is
A Web3 product consultant helps crypto and Web3 teams build products that people use. Not products that people trade. Not products that people speculate on. Products that solve real problems and retain real users.
The work falls into a few buckets:
Product Strategy
This is the big-picture stuff. What should you build? For whom? Why would they care? How do you know?
Most Web3 teams have strong technical intuition but weak product intuition. They know what's technically possible. But they haven't validated whether anyone actually wants it. Product strategy bridges that gap.
In practice this means:
- Running user research to validate (or invalidate) assumptions
- Defining product-market fit criteria and measuring progress
- Prioritising features based on user impact, not technical interest
- Designing experiments to test hypotheses quickly
Product Audits
This is a deep-dive into your existing product. Where are users dropping off? Why? What's the onboarding experience like? How's retention? Is your token design helping or hurting?
A good audit gives you a prioritised list of fixes. Not 100 things to change. The 5-10 changes that will have the biggest impact.
Growth Frameworks
How do you get from 100 users to 1,000? From 1,000 to 10,000? Product-led growth, referral mechanics, community-led growth, content strategy. Building the systems that make growth sustainable instead of relying on one-off campaigns.
Team Coaching
Sometimes the biggest value is helping your team think about product differently. Teaching frameworks. Reviewing work. Asking the right questions. This is less glamorous than "product strategy" but often more impactful.
A Week in the Life
Here's what a typical week looks like when I'm working with a client on a full-service engagement:
Monday: Review last week's metrics. What moved? What didn't? Update the hypothesis tracker. Prep for team sync.
Tuesday: Team sync call. Review progress on current experiments. Discuss blockers. Prioritise the week's work. This is usually the most important meeting of the week.
Wednesday: Deep work. User interview analysis, onboarding flow redesign, token mechanics modelling or writing up audit findings. The actual thinking and designing.
Thursday: Async feedback on team work. Review designs, specs or prototypes. Answer questions via Slack or Telegram.
Friday: One-on-one with founder. Strategic discussion about bigger picture items. What's working, what's not, what to try next.
It's not glamorous. There are no big reveals or dramatic presentations. Just consistent, focused work on making the product better.
When to Hire a Consultant
Not every team needs a consultant. Here's when it makes sense:
You Have a Product but Can't Find PMF
You've built something. People are using it (kind of). But retention is poor, growth is stagnant and you're not sure what to change. A consultant brings fresh eyes and cross-project pattern recognition. They've seen what works and what doesn't across many products.
You're Moving from Web2 to Web3
You have product experience in Web2 but you're new to crypto. A consultant helps you avoid the Web3-specific pitfalls: token-first thinking, ignoring wallet UX, confusing speculation with engagement. These mistakes can cost you 6-12 months.
You Need Strategic Clarity
Your team has a lot of ideas but no clear direction. You're building features but not sure they're the right ones. A consultant helps you prioritise based on user data and product principles, not gut feeling.
Your Team Is Too Close to the Product
After months of building, you lose perspective. Everything seems important. You can't see the obvious problems because you're too deep in the details. An outside perspective cuts through that.
When to Build In-House Instead
Consultants aren't always the answer. Here's when you should hire a product person instead:
- You need full-time execution: Consultants work part-time. If you need someone shipping product decisions 40+ hours a week, hire a PM
- You're very early stage: Pre-idea or pre-funding. You need a co-founder with product skills, not a consultant
- Your problems are purely technical: Smart contract bugs, scaling issues, infrastructure. That's engineering, not product
- You just need marketing: Product consultants focus on the product experience. If your product is solid and you just need more eyeballs, you need a marketing person
What to Look For in a Consultant
If you're going to hire a Web3 product consultant, here's what matters:
- Track record: Have they actually built and shipped products? Not just advised on them. Built them
- Web3 depth: Do they understand on-chain mechanics, token design and dApp UX? Or are they Web2 consultants with a crypto veneer?
- Frameworks, not just opinions: Good consultants bring structured thinking. Methods you can repeat after they leave
- Honest communication: Will they tell you your idea is bad? Or just nod along and bill you? You want the person who pushes back
- Clear deliverables: What exactly will you get? Audits, roadmaps, frameworks, metrics? Avoid consultants who sell "strategy" without specific outputs
How JimmyGrow Works
At JimmyGrow, I offer two engagement models. Advisory at $1,500/month for teams that need strategic guidance. Full Service at $7,000/month for teams that need hands-on product leadership.
Both follow the same process: Discovery, Audit, Hypothesis, Prototype, Validate, Roadmap. The depth of involvement differs but the approach is the same.
Every engagement starts with a free 30-minute call. No pitch. No pressure. Just a conversation about your product and whether I can help.
See our services and book a call.
Frequently asked questions
When should a Web3 startup hire a product consultant?
Three good times: when you have a product but can't find product-market fit, when your retention metrics are poor and you're not sure why, or when you're a Web2 team moving into Web3 and want to avoid common mistakes. If you're pre-idea or pre-funding, it's usually too early.
How much does a Web3 product consultant cost?
It varies widely. Advisory-level engagement (weekly calls, async support) typically runs $1,500-3,000 per month. Full-service engagement (hands-on product leadership, audits, roadmapping) runs $5,000-10,000 per month. Most consultants require a 3-month minimum commitment because product work takes time.
What's the difference between a product consultant and a product manager?
A product manager is embedded in your team full-time and handles day-to-day product decisions. A product consultant works alongside your team (usually part-time) and focuses on strategy, frameworks and solving specific challenges. Consultants bring cross-project experience. PMs bring deep context on your specific product. Many teams use both.