Hands-on product help
Everything on this site is what I actually do. If you want it applied to your product rather than read about, that is what this page is for.
How I can help
Four ways, roughly in order of how often people ask.
Discovery sprint
Two to four weeks. I run customer interviews with your team watching, build an opportunity tree from what we hear, and hand back a prioritised set of problems with evidence attached — not a list of features somebody imagined in a workshop.
Good when: the roadmap is full but nobody can say who asked for it.
Roadmap and prioritisation reset
A working session with the people who actually decide, then a scored backlog and a Now/Next/Later roadmap with confidence levels on it. You keep the scoring model, so the next argument resolves without me.
Good when: priorities change every time a senior stakeholder speaks.
AI feature review
Before you build: should this be a model at all, what breaks when it is wrong, and what it costs per user per month. After you build: an eval suite and a rubric so you can tell whether changes made it better or just different.
Good when: leadership wants AI in the product and nobody has run the numbers.
PM coaching
Fortnightly sessions with an individual product manager or a small team. Real situations, not curriculum — the stakeholder who keeps overriding you, the release that keeps slipping, the metric nobody trusts.
Good when: someone is doing the job without anyone senior to ask.
How it works
- A short call. Twenty minutes, free. You describe the situation; I say honestly whether I can help.
- A written proposal. Scope, what you get, timeline and price. One page, no retainer lock-in.
- The work. Done with your team rather than to them, so the capability stays after I leave.
- A handover. Everything documented — the artefacts are yours to keep using.
If your problem is engineering capacity, or an org design issue, or something you can fix yourself in a fortnight, I will say so rather than sell you a sprint. Sending someone away is cheaper for both of us than a disappointing engagement.
Pricing
Decide your day rate and put real numbers here — even a range, even "from £X". Pages with no pricing at all filter out serious buyers along with the tyre-kickers, because a budget holder cannot tell whether you are £500 a day or £5,000. If you would rather not publish figures, replace this with "Pricing depends on scope — ask on the call" so at least the omission looks deliberate.
Discovery sprints and roadmap work are priced per engagement. Coaching is a monthly retainer. Everything is fixed-price and agreed up front, so the invoice is never a surprise.
Start with a conversation
Tell me what is going wrong and roughly when you need it fixed. If I am not the right person I will usually know someone who is.