Someone
You are the founder or product owner trying to move an idea, team or product forward.
What do you really want?I’m Jimmy. I’ve been close to products from the founder side, the commercial side and the delivery side. That experience changed how I work: the founder should stay the hero, the build should stay accountable to the problem, and the next spend should be earned by evidence.
Every engagement starts with your situation, not with my service list.
You are the founder or product owner trying to move an idea, team or product forward.
What do you really want?Something feels uncertain: scope, progress, product-market fit, timing or the size of the next spend.
What is not working?Complexity, unclear ownership, fragmented advice or a build team solving a different problem.
What is in the way?Time and budget move before enough learning happens, and momentum starts replacing judgement.
What happens if nothing changes?I step in as the Product Manager: frame the problem, challenge assumptions, define scope and own the product decisions.
What needs structuring?You can see what is being built, why it matters, who owns the decision and what evidence earns the next investment.
What becomes clearer?When nobody owns the product decision, founders end up translating between commercial goals, customer needs and delivery teams themselves. Scope grows through conversations, technical choices start shaping the product, and the person carrying the commercial risk becomes the least informed person in the room.
I do not think founders should have to become full-time Product Managers just to keep the build connected to the original problem.
The category changes. The product discipline does not.
HR management, recruitment and sponsor-compliance workflows translated into a digital product.
A marketplace connecting customers, tradespeople and suppliers across mobile, web and admin experiences.
A UK local-government initiative translating complex procurement and supplier participation into clearer workflows.
These are the principles I carry into every founder engagement.
Start with the customer problem, the evidence and the business decision that needs to be made.
A busy team can still be learning very little if nobody owns the product question.
Specialists should challenge feasibility, but product trade-offs need one accountable decision layer.
Continue, reduce scope, change direction or stop. All four can be good product decisions when the evidence supports them.
You do not get sold by one person and handed to someone else to interpret the brief.
User value matters, but so do cost, timing, risk, cash and the reason the product exists.
Requirements have to survive contact with real design, engineering, QA and technical constraints.
I do not make more money because your build becomes bigger. Product and delivery costs stay separate.
After working together, the founder should have less ambiguity, not more process.
Tell me what you are building, what is unclear and where time or money is at risk. We will work out whether I am the right person to help and what the sharpest next step is.