Product consultation for finding the problem together.
A 1–2 hour working session for one product question. I work through the context and evidence with you. We agree scope and price before the session.
A few sentences are enough to start. Tell me what’s happening and what you need.
I follow the problem through the product, the data, and the code.
Who this is for, and what changes after.
Founders or product teams with one messy situation where users arrive, sign up, explore, try, or buy, but too few reach the outcome the business needs.
You get a focused read on the likely product leak, the metric or evidence to validate it, and the recommended next action.
This is not the full 2-week sprint. It is a scoped 1-2 hour consultation for a bounded situation, agreed after the free first touch.
Useful when you need more than a first read.
The consultation can begin with a metric, funnel, experiment, user journey, pricing step, retention issue, monetization concern, or a general feeling that the product is under-converting. I work through the question with you and identify what to do next.
- What this prevents
- fixing symptoms instead of leaks
- metrics drifting away from user value
- experiments being interpreted without context
- roadmap work based on partial evidence
What gets checked.
Current situation
Clarify what is happening, what the team has already tried, and why the current explanation does not feel complete.
Visible symptom
Name the surface problem: traffic, activation, trust, conversion, retention, pricing, monetization, funnel issue, or measurement doubt.
Likely leak
Work together to identify the most plausible mechanism causing users to miss the outcome and what evidence supports or weakens that read.
Evidence check
Review the relevant metrics, funnels, experiments, customer signals, or implementation details during the session where possible.
Next inspection
Decide what should be checked next if the issue is broader than one consultation can prove.
Scope decision
Decide whether the next step should be a fix, a test, a deeper sprint, or no further engagement yet.
How the consultation works.
Agree the scope
We agree by email or during the free 30-minute meeting whether a stronger consultation is the right next step.
Show the situation
You bring the messy context: product, metrics, screenshots, roadmap notes, experiments, user feedback, or anything else that explains the problem.
Separate signal from noise
I explain what looks useful, what looks misleading, and what cannot be concluded yet.
Name the next move
You leave with the recommended next action: fix, test, sprint, implementation support, or pause.
What I deliver.
Consultation Read
A plain-language read on what is most likely happening and where the product is probably leaking.
What I checked
Notes from the session across product logic, customer value, metrics, funnels, experiments, implementation, or roadmap context.
Metric Or Evidence To Validate It
The next evidence, user signal, technical check, or team question that would reduce uncertainty fastest.
Recommended Next Action
The smallest useful move, whether that is a fix, a sharper test, a deeper sprint, implementation help, or stopping a misleading line of work.
Use the free package to scope this properly.
Send the question by email, book the free 30-minute call, or do both. After that conversation, we can decide whether a 1-2 hour Product consultation is useful and what the scope should be.
Need a stronger working session?
Tell me about the problem. We can agree the scope and price for a 1–2 hour working session by email or on a call.