In small companies, product leadership and technology leadership are not two jobs. They are two halves of the same job, and splitting them across two outside hires usually produces two people guarding two halves of the same problem. That is the thesis of how we run fractional CPO work.

You are likely here because product is drifting. The roadmap is reactive. Customer feedback is not making it into prioritization. Engineering and the rest of the company are pointing in different directions. The founder is doing product on top of everything else, and it shows.

How the work shows up

Roadmap tied to the strategy of the business, not the loudest customer of the week. Prioritization that survives the next quarter. Customer discovery that engineering can use. The interface between product and engineering — sequencing, scoping, and the conversations about what is actually shippable. Hiring product staff and structuring how they report. Working with sales and customer success so commitments do not sail past what the team can deliver.

When the gap is more product than engineering, we run a CPO scope. When the gap is both, we run CPO and CTO together with a single point of accountability — yours.

Who this is for

Most fractional CPO work at this stage starts in Founders & small teams. The shape varies — a pre-hire bridge while the company runs a full-time CPO search, a post-departure stabilization, or the dual gap where the founder is acting as both head of product and head of engineering and neither is getting what it needs.

How we engage

Grant Ingersoll leads every engagement, supported by senior product and engineering practitioners. Most engagements are embedded for a defined number of days per month; some start as a fixed-scope roadmap or product-org review and convert into ongoing work.

Tell us what is breaking between product and engineering. Book a Discovery Call.

Grant Ingersoll

Led by Grant Ingersoll

Every CPO engagement is overseen by Grant — former Wikimedia Foundation CTO and Lucidworks co-founder/CTO — supported by a team of senior product and engineering practitioners. Most CPO engagements run alongside a CTO scope so product strategy and technical execution stay aligned.

  • CTO, Wikimedia Foundation — 18 engineering teams, 150+ people
  • Co-founder & CTO, Lucidworks — scaled to 80+ engineers
  • Author, Taming Text · Apache Lucene committer · Apache Mahout co-founder

Fractional CPO — Frequently Asked Questions

Common questions from founders, CEOs, and boards considering fractional product leadership.

What does a fractional CPO do?

A fractional CPO provides senior product leadership on a part-time, embedded basis — typically a fixed number of days per month over six to twelve months. The work spans product strategy tied to the business plan, prioritization and roadmap discipline, customer discovery that engineering can actually use, the interface between product and engineering, and hiring and structuring the product function as the company scales. It is leadership and judgment, not a senior product manager and not an extra pair of hands on the backlog.

Fractional CPO vs. a senior product manager — what is the difference?

A product manager owns a product area and ships against a defined roadmap. A CPO sets the strategy that produces the roadmap, decides what the company is and is not building, structures the product organization, and represents product to the CEO, the board, and the rest of the executive team. If you need someone to run discovery and write specs for a single product line, you need a product manager. If the question is what the company should build next year and how product and engineering should be organized to deliver it, you need a CPO.

How much does a fractional CPO cost?

Engagements are scoped to the situation — typically a fixed number of days per month under a monthly retainer, or a fixed-scope review with a written deliverable. Cost depends on engagement depth and duration, but a fractional CPO is materially less than a full-time hire (which lands well into six figures plus equity) and avoids a six-month search while product continues to drift. We send a written scope and price before any commitment.

When do I need a fractional CPO?

The pattern is usually one of these: the roadmap is reactive and the loudest customer wins the week; engineering is shipping but not the things that move the business; the founder is doing product on top of running the company and it shows; you are between full-time product leaders and the search will take months; or product and engineering are pointing in different directions and the seam between them is where work falls through. If two or more are true, a fractional CPO — often paired with CTO scope — is usually the right call.

How fast can you start an engagement?

Most engagements start within one to three weeks of an initial discovery call. Fixed-scope reviews (roadmap audit, product-org review, prioritization reset) typically begin the same week. We will tell you on the first call whether we are the right fit, whether the scope is CPO, CTO, or both, and what a realistic start date looks like.

Ready to talk?

Tell us about your product and where you need senior judgment. We will get back to you within one business day.