What does a product advisor actually do in two weeks?
- Reads what you have, talks to the people who know, and writes down the call with the trade-off named. Specs, the funnel if there's one, and your engineers, because the constraint is usually in the build and not in the roadmap. You get a recommendation you can act on.
How is this different from hiring a consultancy?
- A consultancy sells a team and a process, and the engagement grows. This is one person, one decision, two weeks, and a fixed fee agreed before anything starts. That's the whole shape of it. There's no discovery phase to buy first, and nothing to extend into.
Who is it for, and who is it not for?
- For API products, developer platforms, and teams wiring an agent into something that already has customers. Not for code, and not for running a growth team. If the decision is really about pricing or distribution rather than product, I'll say so on the call and point you at someone better.
What if the recommendation is one we disagree with?
- Then you've got the reasoning in writing and can argue with it, which is more than most engagements leave behind. The record on the home page includes two calls that didn't work and says so, because a decision practice that only publishes its wins is marketing.
What does it cost?
- Two weeks, $2,500, fixed. Scope is agreed before anything starts. A 30-minute call costs nothing and you'll leave it with a straight read either way.