Founder Bazaarby Jimmy
Home Work With Me Founder Lab About Me Book a Call
Independent product leadership

Everyone you hire gets paid to build. Nobody gets paid to tell you what not to build.

That is my job. I am Jimmy, and I work with founders on the one question no builder is incentivised to ask: what is the smallest thing worth building here, and is it worth building at all?

Most ideas do not die because they were wrong. They die because the budget ran out before anyone found out.

Jimmy, independent Product Manager
I do not get paid more if you build more.Fees and delivery costs quoted separately, always.
43% built the wrong thing Poor product-market fit is the leading cause of failure across 431 shutdown post-mortems (CB Insights, 2024).
70% ran out of capital CB Insights calls that the final cause, not the reason. The money went on a build that was never tested.
Eight years of watching it happen SaaS, marketplaces, eCommerce and public-sector delivery. Long enough to spot it in week one.
Start where you are

Which of these is you right now?

Pick the sentence you would say out loud. That is where we would start.

“I have an idea and a budget, and I am about to spend it.”

Right now the plan lives in your head and in a few conversations. The quotes you are getting vary wildly, which tells you the brief is not clear yet, not that one developer is cheaper. Spend eight weeks the wrong way and you have spent the learning budget on the wrong lesson.

What changes: a build-ready brief you can hand to any team, and a clear line between what you are testing now and what can wait.

Product Clarity Sprint →

“We are building, and I have lost track of what is actually happening.”

There is a backlog, there are standups, there is activity. What there is not is a straight answer to when a customer can use this. Every week that drifts costs the same as a week that delivers.

What changes: someone owning priorities and trade-offs, so decisions get made in days rather than left open for a month.

Fractional Product Manager →

“We have spent months and I still cannot show it to a customer.”

This is the hardest one to ask about, because the longer it goes on the more expensive it feels to question it. It is also the point where an independent view is worth the most.

What changes: an honest read on what has been built, what the real blocker is, and a recovery plan you can act on. Sometimes that plan is to stop. I will tell you if it is.

Product Rescue →

“We know AI could automate part of the business, but we do not know what the agent should actually do.”

There may be a workflow worth improving. The product decision is what the agent can do, which tools and data it can use, where human approval belongs and what result makes it worth running.

What changes: a build-ready AI product plan covering workflow, agent actions, integrations, guardrails, human controls, evaluation and operating cost.

AI Product & Agent Sprint →
The arrangement

I do not make more money if you build more.

My fee and any third-party delivery costs are quoted separately, always. That is not an administrative preference, it is the whole basis of the arrangement. The moment I profit from a bigger build, I stop being useful to you.

When you need design, development, AI or commercial support, I will bring in people I trust and you will contract them directly. I stay accountable for the product decisions.

How the work runs

Validate → Define → Deliver → Learn.

Proof, not promise. This is the discipline that keeps every decision tied to evidence rather than opinion.

1

Validate

Customer, problem and evidence. Whether there is anything here worth paying for.

2

Define

The smallest thing that proves it, what is cut, and how you will know it worked.

3

Deliver

Decisions made in days, a team held to account in its own language, testing that means something.

4

Learn

A real keep-or-kill decision, while there is still money and time to act on it.

What was decided

Three products, three decisions that changed the plan.

Read the case studies →
Draft narrative for review. The four beats are the structure from the playbook. Confirm or replace the specifics before this goes live.
HoomWork
THE SITUATION

A multi-sided home-services marketplace with a feature list built for both sides of the market at once.

WHAT WAS ACTUALLY WRONG

Not the app. Supply. No amount of product would fix a city with too few tradespeople to answer a job.

THE DECISION

Launch one city, one service category, and cut the customer app to a booking flow. Everything else waited.

WHAT CHANGED

Live to real customers on both sides, with journeys and cross-platform delivery taken from concept to launch.

YourHRM
THE SITUATION

HR and sponsor-compliance SaaS, scoped as a full HR suite competing with established platforms.

WHAT WAS ACTUALLY WRONG

The buyer was not shopping for an HR suite. They were frightened of a compliance audit they could not evidence.

THE DECISION

Build the sponsor-compliance workflow first and defer the rest of the suite until beta customers asked for it.

WHAT CHANGED

Discovery, workflows and requirements through to a beta in the market and a go-to-market story that fitted the buyer.

Smart City Procurement
THE SITUATION

A UK local-government procurement initiative with several supplier processes and no agreed workflow between them.

WHAT WAS ACTUALLY WRONG

A technology problem on paper, a decision-rights problem in practice. Nobody could say who approved what.

THE DECISION

Design the workflow and approval model before any platform choice, then onboard suppliers against it.

WHAT CHANGED

Procurement planning and supplier onboarding running to one agreed process rather than three competing ones.

Free, no call required

Find out what is unclear before a developer prices it.

Nine questions, two minutes. It will tell you which parts of your plan a team could build from today and which parts would come back as an estimate with padding in it.

Take the check →
Founder Lab

Read how I would decide it.

Explore Founder Lab →
Jimmy, independent Product Manager
Why I work this way

The ventures that struggled taught me more than the ones that worked.

I have been in the room where a build was going well and the product was going nowhere. That is the failure mode I am hired to catch, and I have seen it often enough to recognise it early.

Since then I have worked across SaaS, marketplaces, eCommerce and public-sector digital products, from early concept through discovery, workflow design, development, testing and launch. The commercial experience matters because product decisions are budget decisions wearing a different hat.

Read my story →

Bring me the decision you keep putting off.

Thirty minutes, no deck. You will leave knowing what to test next and roughly what it should cost.