Adrian Lawrence FCA — Founder, Exec Capital
Executive search specialist · ICAEW practising certificate holder · Co. No. 13329383
Product leadership is one of the most frequently misassessed senior hires in technology businesses. The candidate who can describe a product framework fluently — Jobs to Be Done, continuous discovery, OKR alignment, dual-track agile — may or may not have the product sense to make good decisions when the framework runs out, which it always does. And the candidate who has genuine product instinct — who can identify a user problem worth solving, prioritise ruthlessly under resource constraints, and make the call that ships a product rather than perfects it — may not always be able to explain their decision-making in the structured terms a hiring process rewards. The Head of Product search that works assesses both: the structured process capability and the underlying product judgement. Exec Capital builds assessment around the decisions candidates have made, not the methodologies they can describe. To discuss a search, call 0203 834 9616.
Head of Product and CPO recruitment for UK technology businesses — assessment that separates product sense from product process, and the brief-building work that defines which profile the role needs
Exec Capital places Heads of Product, Chief Product Officers, and senior product leaders with UK technology businesses — from early-stage businesses making their first dedicated product hire to scale-ups building a product organisation and mature technology businesses replacing or upgrading product leadership. We run product leadership searches with the assessment rigour that the function demands — probing product decisions rather than product vocabulary, and building the brief around what the business actually needs from product leadership at its current stage of growth. For our CTO recruitment service, see CTO recruitment. For fintech product leadership, see our fintech recruitment page.
What Head of Product Recruitment Actually Requires
The framework vs judgement problem. Product management has accumulated more frameworks, methodologies, and structured approaches than almost any other function in technology businesses — and a candidate’s ability to describe them fluently is one of the weakest signals of whether they will make good product decisions. The candidate who can explain the difference between outcome-based and output-based roadmaps, who references Teresa Torres on continuous discovery, and who can articulate a Jobs to Be Done framework without prompting may or may not be able to sit in front of a confused user, identify what problem they actually have, and make the prioritisation call that solves it within the team’s sprint capacity.
The assessment approach that distinguishes genuine product leadership from well-read product management focuses on the specific decisions the candidate has made and the outcomes those decisions produced. What was the most difficult prioritisation call they made in the last twelve months? What was the last product bet they made that turned out to be wrong, and how did they discover it and respond? What did they ship that they are least proud of, and what would they have done differently? These questions reveal product judgement, intellectual honesty, and the ability to learn from failure — the qualities that define effective product leadership — in a way that framework discussion never does.
The discovery vs delivery balance. The most common structural tension in product leadership is between discovery — understanding what to build — and delivery — building it well and fast. Product leaders who are strongest in discovery can generate a compelling product vision and deeply understand user problems but may struggle to maintain the delivery pace and engineering partnership quality that converts insight into shipped product at scale. Product leaders who are strongest in delivery run efficient sprints and maintain strong engineering relationships but may gravitate toward executing what is already on the roadmap rather than challenging whether it is the right roadmap. The brief needs to specify which dimension the business most needs at its current stage — and the assessment needs to test both.
Stage fit. The Head of Product who excels at a ten-person startup — making quick, intuitive decisions, wearing multiple hats, acting as de facto researcher, designer, and PM simultaneously — is often not the right person to lead product at a 200-person scale-up where the challenge is building a product organisation, establishing clear processes, and managing a team of product managers rather than doing the work directly. And the VP Product from a 500-person company who has spent three years managing a product organisation will frequently be too slow, too process-dependent, and too removed from hands-on product work for an early-stage business that needs a player-coach. Stage fit is the most commonly overlooked dimension in Head of Product recruitment, and it is the one that most reliably predicts whether the hire will succeed.
Roles Exec Capital Places in Product Leadership
Head of Product. The most common title for the most senior product leader in a technology business — covering everything from the individual contributor PM who is the first dedicated product hire in a 20-person startup to the Head of Product managing a team of five PMs in a 200-person scale-up. The brief for a Head of Product search needs to be specific about team size, product scope, reporting line, and the balance between hands-on PM work and team leadership that the business needs from the hire. A “Head of Product” job description that does not address these dimensions will attract a candidate pool too wide to assess effectively.
Chief Product Officer (CPO). The CPO is the C-suite product leadership appointment — sitting on the executive committee, reporting to the CEO, and accountable for the overall product strategy, the product organisation, and the product’s contribution to the business’s commercial performance. The CPO search requires a candidate who can operate at both strategic and organisational levels: building the product vision and roadmap that the board believes in, while managing and developing the product team that executes against it. At listed and larger businesses, the CPO presents to the board on product strategy and performance. For CPO role detail, see our Chief Digital Officer guide for context on how product leadership relates to digital leadership at C-suite level.
VP Product. The VP Product title is most common in US-influenced technology businesses — either US-headquartered with UK operations, or UK businesses that have adopted American product management conventions. The VP Product typically sits one level below the CPO in larger organisations, managing a portfolio of product lines or a significant product area. The seniority and scope of the role varies significantly by business size and structure, and the brief needs to be specific about what “VP” means in that organisation’s context.
Product Director. In businesses with a more traditional corporate structure, the Product Director is the most senior product leadership role below C-suite — managing a product team, owning the product strategy for a defined area, and reporting to the CPO or CEO. The Product Director appointment is common in corporate businesses that are building product capability for the first time — moving from a feature-factory delivery model toward a more discovery-led, outcome-oriented approach — and the profile required is one that can lead cultural change in the product function as well as manage product delivery.
B2B vs B2C Product Leadership
The most important brief-building distinction in product leadership recruitment — more important than company size and almost as important as stage — is whether the product is primarily B2B or B2C. The two contexts develop materially different product instincts, and the candidate who has only operated in one frequently struggles to adapt to the other without a significant adjustment period.
B2B product leadership. B2B product leaders must manage the tension between the enterprise customer’s immediate feature requests and the platform’s long-term architectural health — a tension that does not exist in the same form in consumer products. They must understand the enterprise sales cycle — how the product is sold, what the buyer cares about versus what the user cares about, and how product decisions affect win rates and expansion revenue — and build a product strategy that serves both. The discovery process in B2B is fundamentally shaped by customer access: enterprise customers can provide detailed qualitative insight but may have idiosyncratic needs that do not generalise, and the Head of Product who builds a roadmap from a handful of large customer conversations without testing broader market validity will build a product that serves the existing customer base rather than the addressable market.
B2C product leadership. B2C product leaders work with quantitative data at a scale and velocity that B2B product leaders rarely encounter — millions of user interactions generating the signal that drives prioritisation decisions. The most effective B2C product leaders combine strong data literacy — the ability to design, run, and interpret A/B tests rigorously — with the UX intuition to identify the user problems that the data signals but does not explain. They understand growth metrics — activation, retention, engagement, virality — and build the product strategies that move them. The risk for experienced B2C product leaders moving to B2B is that they reach for quantitative data that does not exist at B2B scale, and undervalue the qualitative customer insight that is the primary discovery signal in enterprise product management.
Technical Depth in Product Leadership
The question of how much technical depth a Head of Product needs is one of the most debated in product management — and the answer depends heavily on the product, the engineering team, and the CTO relationship. The general principle is that the Head of Product needs sufficient technical literacy to be a credible partner to the engineering team — to understand the implications of technical architecture decisions for the product roadmap, to avoid building requirements that create unnecessary technical debt, and to earn the engineering team’s respect as a collaborator rather than a customer. They do not need to write production code or make architectural decisions.
In regulated technology businesses — fintech, healthtech, legaltech — where the product’s technical architecture has compliance and regulatory implications, a higher baseline of technical awareness is required. The Head of Product in a regulated fintech who does not understand the API architecture that connects the firm’s product to its banking infrastructure, or the data model that underlies the credit risk assessment, will make product decisions that create regulatory and operational problems that they cannot see coming. For fintech product leadership in particular, Exec Capital assesses technical awareness as part of the standard search process.
The Product-Engineering Relationship
The most important working relationship for a Head of Product is with the CTO or engineering lead — and the quality of this relationship is one of the strongest predictors of whether a product leadership appointment will succeed. A product leader who cannot build a genuine partnership with engineering — who treats engineering as a delivery resource rather than a co-creator, or who cannot engage credibly with the technical constraints and trade-offs that engineering manages — will produce a product organisation that is slower, more frustrated, and less innovative than it should be.
Exec Capital treats the product-engineering relationship as a core element of every Head of Product search brief. Where the CTO is a known quantity, we assess candidates specifically for compatibility with that CTO’s leadership style and technical philosophy. Where the CTO appointment is happening alongside or shortly before the Head of Product search, we advise running both searches in parallel and involving each candidate in the other’s assessment — because the product-engineering partnership is too important to leave to chance after both appointments are made.
Compensation in Product Leadership — UK 2026
Head of Product base salaries in the UK range from £80,000–£120,000 at early-stage businesses making their first product hire to £150,000–£220,000 at scale-up and growth-stage businesses with an established product organisation. CPO base salaries typically range from £180,000–£300,000 at technology businesses of meaningful scale, with equity forming a significant component of the total package at VC-backed and growth-stage businesses. In fintech, healthtech, and other regulated technology sectors, base salaries reflect both the product leadership premium and the regulatory environment premium, typically sitting toward the upper end of comparable technology business ranges. Annual bonus for Head of Product and CPO roles typically runs at 15–25% of base, structured against product performance metrics — feature adoption, NPS improvement, revenue contribution from new product lines — alongside company financial targets.
Hiring a Head of Product or CPO?
Exec Capital places Heads of Product, CPOs, and senior product leaders across B2B, SaaS, fintech, and consumer technology businesses. Assessment built around decisions, not frameworks. Speak with Adrian Lawrence FCA directly.