37 direct answers on fractional product leadership, getting from idea to MVP, AI product work, product management and starting a company. Short answer first, then the practice behind it.
Everything founders ask before hiring a fractional Chief Product Officer — cost, scope, hours, KPIs and the comparisons that decide the hire. Answers come from running product at Just Eat and Sage, and from fractional engagements with pre-seed and seed teams.
A fractional CPO is a senior product executive who owns product strategy, discovery and delivery for one to three days a week instead of full-time. They set the product direction, decide what gets built and what gets cut, run the operating cadence with engineering, own the product metrics reported to the board, and coach or hire the permanent product team that eventually replaces them.
Read the answerA fractional CPO costs roughly £4,000–£10,000 per month in the UK, or $6,000–$15,000 in the US, depending on days per week. One day a week sits at the bottom of that range, two-plus days at the top. There is no employer's National Insurance, pension, equity or recruiter fee, so the loaded cost is close to the headline number.
Read the answerHire a fractional CPO when product decisions have become the bottleneck but you cannot yet justify a full-time executive. In practice that is after you have engineers building and before you have product-market fit: usually pre-seed to Series A, three to fifteen people, with a roadmap that keeps growing and a founder who no longer has time to run discovery properly.
Read the answerA fractional CPO is worth it when product decisions are costing you more than the retainer — which, with four engineers on payroll, happens fast. One quarter of misdirected engineering costs £50,000–£80,000 in salary alone. The retainer pays for itself if it prevents a single wrong quarter. It is not worth it if you lack build capacity, or will not give the role decision rights.
Read the answerMost fractional CPOs work one to three days a week — roughly 8 to 24 hours — split across fixed on-site or on-call days plus asynchronous availability in between. One day a week is direction and cadence. Two days adds hands-on discovery and delivery. Three days is close to an interim executive and is normally reserved for turnarounds or funding-round sprints.
Read the answerA product manager executes within a strategy: discovery, specs, backlog, shipping one product area. A fractional CPO sets that strategy: what the company builds, what it refuses to build, which metric matters, how the product function operates, and who to hire. If nobody has defined the direction, a PM will fill the gap with activity — which looks like progress and is not.
Read the answerA product consultant analyses your situation and hands back recommendations; accountability stays with you. A fractional CPO takes a seat in the company, holds decision rights, and is measured on whether the product metric moves. Consultants suit one-off diagnostics, due diligence and audits. Fractional leadership suits companies that already know roughly what is wrong and need someone to own fixing it.
Read the answerA CPO should track one primary metric per quarter plus a small guardrail set. Pre-PMF: activation rate, week-four retention and time-to-value. Post-PMF: net revenue retention, expansion rate and revenue per active user. Always: cycle time and rework rate as health metrics. If your product dashboard has more than seven numbers on it, nobody is accountable for any of them.
Read the answerDefine the mandate before the title. Write the one outcome this person owns for the next four quarters, then hire against that: a zero-to-one leader for pre-PMF, a scaler for post-PMF — they are different people. Run a four-stage loop with a real working session on your actual problem, reference on decisions made rather than teams managed, and expect eight to fourteen weeks.
Read the answerA Head of Product runs the product function — team, process, roadmap execution — and usually reports to a founder or CEO. A CPO sits on the executive team, owns product as a business line alongside revenue and engineering, and is accountable to the board. The practical difference is scope of accountability: function versus company. Titles inflate at startups, so check the mandate, not the label.
Read the answerA chief product officer salary in the UK is typically £140,000 to £200,000 base in 2026, with £120,000-£150,000 at seed and Series A, £160,000-£200,000 at Series B and beyond, and £220,000+ at scale-ups and listed companies. Loaded cost — employer National Insurance, pension and recruitment — adds roughly 25%. Fractional CPOs charge £800-£1,400 a day instead.
Read the answerThe questions founders ask between having an idea and having something real in front of paying users — scope, cost, timeline and validation. Answers reflect the Crossley Method: discover, validate, prototype, build, launch, first revenue.
Build an MVP by picking one job a specific user will pay to have done, designing the single shortest flow that completes it, and shipping only that. Validate demand before building — interviews plus a paid or committed signal. A focused build can take four to six weeks; allow roughly six to twelve weeks from idea to public launch when validation, pilot users and fixes are included.
Read the answerIn the UK, a focused commercial MVP with one core user journey typically costs about £12,000–£25,000 with a product-led, AI-assisted build. A clickable or lightweight validation prototype can cost roughly £3,000–£8,000. Multiple user roles, complex integrations, RAG or agentic AI, specialist compliance or premium design can move the project above £25,000; larger agency builds can reach £60,000–£150,000.
Read the answerBuild an AI MVP by choosing one task where being right 80% of the time is still useful, wrapping a hosted model rather than training your own, and designing the interface around correction — users must be able to see, edit and accept output. Set an evaluation set before launch, measure task success and human-override rate, and only consider fine-tuning once the workflow itself is proven.
Read the answerYes. A non-technical founder can build and validate an AI app in 2026 using tools such as Lovable, Cursor or Bolt without first hiring a full engineering team. The founder still needs to own the customer problem, scope, accounts, data access, AI quality, costs and launch decision. Use specialists for the parts where a mistake creates real security, reliability or commercial risk.
Read the answerAfter your Lovable app works, do not automatically rebuild it. First validate that real users want the core journey, then audit authentication and data access, billing, error handling, backups, monitoring, AI quality and cost per user. Fix launch blockers in risk order and add analytics before public release. Rebuild only when the existing architecture genuinely cannot support the business you have evidence for.
Read the answerA focused MVP goes from idea to launched product in six to twelve weeks: one to two weeks of discovery and validation, four to six weeks of build, one to two weeks of pilot and fixes. Complex, integrated or regulated products take four to nine months. Delays almost always come from scope changes and slow decisions, not from engineering speed.
Read the answerPractical answers about applying AI inside real products and companies — what it costs, what it changes about the product role, and where it genuinely reduces cost or improves experience.
No, but it is removing a large part of what product managers used to spend their week doing. AI already writes specs, summarises research, drafts tickets, analyses feedback and builds prototypes. What it cannot do is decide what a company should refuse to build, hold accountability for a metric, or persuade a room. Roles weighted towards documentation are shrinking; roles weighted towards judgement are becoming more valuable.
Read the answerStartups use AI in three places: inside the product as a feature that completes a user task, inside operations to remove repeated manual work, and inside go-to-market for research, content and support triage. For a small company, internal operational work is often the easiest first use to measure because the baseline task already exists and the team can compare time, quality and cost before and after.
Read the answerFounders need four categories, not forty tools: a frontier chat assistant for thinking and drafting, an AI-assisted build tool for prototypes and MVPs, a research and synthesis tool for customer and market work, and automation for repeated operational tasks. Pick one per category, use it deeply, and add another tool only when a specific recurring task justifies the subscription and context-switch cost.
Read the answerFor a UK founder, a focused commercial AI MVP with one core journey typically sits around £12,000–£25,000 in the pricing model used on this site. A prototype or narrow validation build can be roughly £3,000–£8,000. Multiple user roles, RAG or agentic workflows, several integrations, sensitive-data requirements or bespoke design can push the build above £25,000. Model and infrastructure running costs should be measured separately per successful customer task.
Read the answerChoose an AI product consultant when the uncertainty is the customer problem, scope, AI use case, evaluation, pricing or what should be built at all. Choose a developer when those decisions are validated and the bottleneck is implementation capacity. Early founders often need a product-led build that combines both: senior product judgement to cut the scope and enough engineering execution to ship the one journey that matters.
Read the answerAI can reduce operating cost when it shortens repeated, reasonably consistent tasks such as support triage, data extraction, research, first-draft responses and QA. Do not start with a generic savings percentage. Measure the current handling time, error or correction rate and cost of the target task, pilot the AI workflow with human review, then compare the full post-AI cost including model usage, tools and review time.
Read the answerAI improves customer experience mainly by shortening time-to-value and removing waiting: answers grounded in your own documentation, faster onboarding through assisted setup, proactive detection of stuck users, and guidance based on relevant product context. It damages experience when it hides humans, guesses confidently, or personalises in ways the customer did not expect.
Read the answerAnswers to the questions product managers and founders actually ask — written from running product at Just Eat and Sage, and building products from zero as a founder.
You become a product manager without a degree by producing evidence instead of credentials: ship something real, own a metric in an adjacent role, and document decisions publicly. Support, sales, operations and QA are the highest-converting entry routes because they give you customer contact and data. Hiring managers screen for judgement and shipped outcomes; almost none check for a degree at interview stage.
Read the answerFour skills carry most of the job: customer discovery, prioritisation under uncertainty, written communication, and data literacy. In 2026 add two more: AI-assisted execution, and evaluation design for AI features. Frameworks, roadmapping tools and ceremonies are teachable in weeks; judgement about what not to build is the skill that separates senior PMs from everyone else.
Read the answerProduct managers usually fail for structural reasons, not talent ones: no clear mandate, no owned metric, no direct customer contact, an organisation that rewards shipping over outcomes, and an unwillingness to create conflict by saying no. Four of those five are fixable by the company. The fifth — avoiding conflict — is the personal skill most often missing in PMs who stall at mid-level.
Read the answerProduct managers use AI to compress the artefact half of the job: synthesising interviews, drafting specs and tickets, building clickable prototypes, summarising support and review data, and pressure-testing decisions. The best PMs also use it inside the product, designing evaluation sets and quality metrics for AI features. What they do not delegate is the decision, the customer conversation or the accountability.
Read the answerProduct-market fit is the point where a defined group of customers keeps using and paying for your product without you pushing them, and demand grows faster than you can comfortably serve it. Practical signals: week-four retention that flattens rather than decays, over 40% of users saying they would be very disappointed to lose it, organic word of mouth, and shortening sales cycles.
Read the answerPrioritise against one metric for the quarter, not against a scored list. Ask of each candidate: what evidence says this moves the metric, what is the smallest version that would test it, and what comes off the roadmap to make room. Scoring frameworks like RICE are useful for structuring a conversation, but they launder opinion into numbers if the inputs are guesses.
Read the answerA product roadmap is a statement of what problems you intend to solve, in what order, and why — not a dated list of features. The format that works is three horizons: what is being built now with committed scope, what is next with a defined problem but flexible solution, and what is later as themes. Dates belong on the now column only.
Read the answerA technical product manager owns products where the main complexity is technical rather than customer-facing: APIs, platforms, data pipelines, infrastructure and AI systems. The job is the same as any product manager — decide what to build and why — but the customers are often engineers, and the trade-offs are architectural. It requires enough technical depth to argue with an engineer without pretending to be one.
Read the answerThe questions first-time founders ask before and just after they start building — validation, co-founders, frameworks and the mistakes that cost a runway cycle.
Start a SaaS company by choosing a narrow, expensive, recurring problem for a specific group you can reach, validating that they will pay before you build, then shipping the smallest product that solves it end to end. Get to first paid customer before hiring, raising or automating anything. Distribution — how you reach that group repeatedly — matters more than the software.
Read the answerTechnical co-founders come from people who already know you — former colleagues, communities you contribute to, and open-source or startup circles — far more often than from matching platforms. What makes them say yes is evidence: a validated problem, early customers, and a prototype you built yourself. In 2026, many founders should first ask whether they need a co-founder or a contractor plus AI tooling.
Read the answerFirst-time founders consistently build before validating, scope too wide, hire too early, price too low, chase funding instead of revenue, and measure activity instead of outcomes. Each individually is survivable. Combined, they burn a runway cycle before anyone learns whether the core idea works. The counter-move is uncomfortable focus: one segment, one problem, one metric, one channel.
Read the answerFounders need one sequence, not a shelf of frameworks. A workable one: discover the problem, validate willingness to pay, prototype the flow, build the MVP, launch narrow, get first revenue, then scale what works. Borrow specific tools where they help — jobs-to-be-done for framing, opportunity solution trees for discovery — but a framework that produces artefacts instead of decisions is overhead.
Read the answerValidate a startup idea by testing willingness to pay, not enthusiasm. Run ten to fifteen interviews about what people did last time they faced the problem, then ask for a commitment — a deposit, a paid pilot, a signed letter of intent. Set your pass thresholds before you start. Two weeks of this routinely prevents six months of building the wrong thing.
Read the answerEXPLORE NEXT
Every stage from first idea to first revenue, mapped end to end.
Done-for-you six-week build turning a founder idea into a launched AI app.
Read moreFree 20-question check for customer evidence, access and data, reliability, AI quality and commercial launch readiness.
Read moreHow a shared-travel marketplace was scoped down to one journey worth building.
Read moreThe seven-stage framework that takes an idea to first revenue.
Read more