Product management consulting
I join your team as the senior product person for a defined project, with output you can see every week.
This is the engagement for a specific, bounded problem: a roadmap that has stalled, a launch that keeps slipping, an idea nobody has validated but everybody has an opinion about. Fixed scope, a named outcome, and no handover deck at the end — because I'll have been building alongside your team rather than observing it.
What I get called in for
The specific problems, in roughly the order they come up.
- A roadmap that everyone privately knows is wrong and nobody can change.
- A launch that has slipped twice and is about to slip again.
- A vague strategic idea that needs to become a validated, scoped, buildable plan.
- Discovery that produces research nobody acts on.
- Specs that engineering has to reinterpret, so every sprint starts with an argument.
How I work
One senior person accountable for the outcome. No layers, no analyst, no deck at the end that summarises what you already told me.
- Product strategy and a roadmap you can defend under pressure.
- Discovery and validation — including killing the ideas that don't survive it.
- Delivery cadence, rituals and specs the team actually trusts.
- Working prototypes, not mockups, when a decision needs something real to react to.
Typical projects
Most engagements fall into one of these shapes. Each has a deliverable you can name before we start.
- Setting up product management where there is none — roles, process and the rituals that make decisions repeatable.
- Productisation: turning a services business or a pile of customer projects into one product you can sell twice.
- A product strategy and roadmap that holds up in front of a board or an investor.
- A discovery and validation sprint for a new product idea, ending in a build, change or kill decision.
- A product-process audit when delivery is busy and outcomes aren't moving.
Why the prototypes matter
I have an engineering background, and I build what I spec. A clickable prototype settles in one meeting what a twelve-page document argues about for two weeks — and it's why the specs that follow are buildable.
- Working prototype in days, not sprints.
- Specs written the way a developer reads them.
- Decisions made against something real instead of a simulation in someone's head.
Common questions
- How is this different from the interim engagement?
- Scope. Consulting is a defined project with an outcome; interim is holding the role and everything that comes with it. If you can name the deliverable, this is the right one.
- Do you write documentation or build things?
- Both, and the order matters — prototype first, then the spec, which is then two pages instead of twelve because the hard questions are already settled.
- Can you work with our existing PM?
- That's the usual arrangement. I'm not there to replace them; I'm there to unblock something and leave them better set up than I found them.
- What if the project turns out to be the wrong project?
- I'll tell you in the first two weeks, and we'll rescope. It happens, and it's cheaper than the alternative.
- Are you a freelancer or an agency?
- A freelancer. The person on the first call is the person doing the work — there is no team behind me that the project gets handed to.
- What does product management consulting cost?
- Projects with a nameable outcome are usually priced as a fixed fee; open-ended work as a day rate. Either way you get a number on the first call, not after three meetings and a proposal.
Scope a project
30 minutes to work out whether the problem you have is the problem you think you have.
Book a call