"Fractional" has become a common word, and like most common words it means different things to different people. Here is what it means when I do it.
A fractional product and AI lead is a senior person who owns product direction and the AI parts of a product, part-time or for a defined stretch, without becoming a full-time employee. In my case that also means hands-on design and build work, not only strategy documents.
What the role covers
The work usually falls into four areas.
- Product direction. What we are building, for whom, and in what order. A roadmap that names the next three releases, not the next three years.
- UX and front-end. Turning that direction into screens and flows people can actually use, and often building them in the stack that goes to production.
- AI features. Deciding where AI genuinely helps, scoping it, testing it against real cases and shipping it responsibly. Sometimes the right answer is less AI, not more.
- The team around it. Working with designers and engineers, reviewing their work, and helping with hiring when it is time to bring people on full-time.
The common thread is decisions. Most early products do not fail for lack of effort. They fail because important decisions were made late, made implicitly, or not made at all.
When you need one instead of a full-time hire
A full-time head of product is the right answer for many companies. A fractional lead tends to make more sense when:
- You are pre-product or pre-v1. You need someone who can scope, design and build, not someone to manage a product team you do not have yet.
- Your CTO is stretched. Engineering leadership is strong, but no one owns product decisions or the user experience, so they get made by whoever is closest to the code.
- You are adding AI to an existing product and want it done carefully, with clear limits on what the AI can and cannot do.
- You are not sure what the role should be yet. A few months of fractional work often tells you exactly what kind of full-time hire you need, and gives that person a clear foundation to start from.
It is usually not the right fit if you need someone in the office every day, or if the job is mostly managing a large team.
What the first weeks look like
Every engagement is different, but the first weeks follow a familiar shape.
Week one: listen
Calls and walk-throughs with the people who know the problem best: the founders, the team, and ideally a few users. I want to see how the work gets done today, including the spreadsheets and workarounds nobody likes to show.
Weeks two and three: write it down
Everything from those conversations goes into one requirements brief. From the brief comes a detailed spec, researched and sourced, that the whole team can read and challenge. Version one of the spec gets locked, so the build starts from a plan instead of a guess.
Then: make it real
A clickable prototype of the core flow, tested with real users, followed by the build itself. You get a working preview every few days, not a slide deck at the end of the month.
This is the same process I use on my own products, from Mentor Intelligence to BackTrack. It is not a special consulting method. It is just how I build.
What it is not
A few things a fractional lead should not be.
- Not a project manager with a new title. Tracking tickets is useful, but it is not product leadership.
- Not an AI cheerleader. I use AI heavily in my own work for research, specs, design and code. I also know where it falls short. Coding agents never touch production data in my projects, every change ships through a preview first, and people make the final calls.
- Not a black box. You should always know what I am working on, what I decided and why. I send weekly written updates, and the code, documentation and IP live in your accounts.
- Not forever. A good engagement either ends with a product live and a team that can carry it, or turns into a longer partnership because both sides want it to.
The goal is not to make you dependent on a fractional lead. It is to leave you with a product, a plan and a team that no longer needs one.
How engagements usually start
Most of my fractional work begins with a short, defined piece of work rather than an open-ended retainer. A Scoping Sprint of two weeks or more ends with a sourced spec, a tested prototype and a plan for the build. From there it can become a v1 build, an ongoing fractional role, or a build partnership, depending on what the product needs.
Starting small is good for both sides. You see how I work and what I produce before committing to anything longer. I get to understand the problem properly before promising timelines.
Where I come from
I have spent more than 30 years in technical UX, front-end engineering and product strategy, shipped more than 50 platforms, sold my startup, Stacks, to EBSCO, and worked for companies including Adobe, Apple, Microsoft, BMW, Pepsi and The Home Depot. The range matters less for the logos than for the pattern recognition. Most product problems have been solved before, just not in your context.
If you are a founder or CTO wondering whether a fractional lead is the right next step, email me with what you are building and where it is today. I will tell you honestly if it is not.