You Don't Need a Full-Time PM. (Or Maybe You Do.)
A practical framework for making one of the most expensive hiring decisions in your product org.
5 min read
I've had some version of this conversation dozens of times.
A founder, a COO, or an HR leader reaches out. They know they need product help. They've got a backlog that nobody owns, a roadmap that exists only in someone's head, and an engineering team asking questions that nobody can answer. They're thinking about hiring a full-time product manager.
Sometimes that's exactly the right call. But more often than not, they're about to spend $150,000–$225,000 a year on a problem that doesn't actually require it.
Here's how to figure out which situation you're in.
Be honest about what you actually need
Before you post a job description, get specific about what's broken. Most product gaps fall into one of three buckets:
You need strategy and clarity. You're not sure what to build next, why, or for whom. You have competing priorities and no framework for making tradeoffs. You need someone to help you think, not just execute.
You need execution and delivery. You know what you want to build. You need someone to write requirements, manage the backlog, run sprints, communicate with stakeholders, and ship things on time.
You need both. You're building something from scratch, or you're at a pivot point. You need someone who can define the vision and carry it forward.
Most companies think they need everything. Many actually need clarity. And the cost, commitment, and org design implications of each are very different.
The case for fractional
A fractional PM is a senior product leader who works with you on a part-time or project basis — typically 10 to 20 hours a week — embedded in your team but not on your payroll full-time.
The model works especially well when:
You're pre-product-market fit. You need sharp strategic thinking more than you need someone managing a sprint board 40 hours a week. A fractional leader can help you define what to build and why, without the overhead of a full-time hire you might not be ready to support.
You have a specific, bounded problem. You're launching a new product line, rebuilding your roadmap process, preparing for a funding round, or cleaning up years of accumulated technical and product debt. These are finite projects. Hiring a full-time PM to solve a finite problem leaves you with an awkward conversation in six months.
Your team isn't ready to be managed yet. A common mistake: hiring a full-time PM into a company that doesn't yet have the processes, culture, or clarity to absorb them. A fractional engagement can help you build those foundations first — so when you do hire full-time, you're setting that person up to succeed.
You need senior judgment on a junior budget. The fractional model gives you access to someone with 15–20 years of experience at a fraction of the cost. That's not a workaround. For many companies, it's the smarter allocation.
You're between product leaders. Your CPO just left. You have a VP search underway that will take 3–6 months. You can't leave your team rudderless. A fractional leader can maintain momentum, make the real decisions that need making, and help you hire and onboard their own replacement.
The case for full-time
Full-time still wins in plenty of situations. Don't let fractional become the default just because it's cheaper.
You're at scale and in execution mode. If you have a large engineering team, multiple product lines, and a complex roadmap that requires constant coordination, you need someone fully embedded. A part-time PM can't run a daily standup, a weekly stakeholder review, and a quarterly planning cycle across three product areas.
You need deep institutional knowledge. Some products are complicated enough that onboarding takes months. If your PM needs six months just to understand the system before they can add value, fractional math doesn't work.
Culture building is part of the job. If you're building a product team from scratch and the PM role is fundamentally about hiring, coaching, and establishing a culture — not just shipping features — you need someone in the room full-time.
Your team needs a day-to-day presence. Engineers, designers, and stakeholders sometimes just need someone to make a call. If the answer is always "I'll check in Thursday," that's friction. Know your team's working style before you decide.
The decision framework
Here are seven questions. Answer them honestly, and the right answer will usually reveal itself.
1. Do you have a specific, defined problem to solve — or an ongoing operational need? Specific problem → fractional is worth exploring. Ongoing operational need → lean toward full-time.
2. How many hours per week does this role actually require right now? If you can't articulate meaningful work to fill 30–40 hours a week, you're probably not ready for a full-time hire. Hiring full-time before you're ready wastes money and burns out good people.
3. What's your budget reality? Be honest. A fractional PM at 15 hours per week typically costs $3,000–$7,500 per month depending on experience and scope. A full-time senior PM is $130,000–$250,000 in salary plus benefits, equity, and recruiting costs. If you're early-stage or capital-constrained, the math often points one direction.
4. How long is the engagement? If you can see a natural end — a launch, a funding milestone, an interim period — fractional is almost always the better fit. If you genuinely need this person two years from now doing the same work, plan for full-time.
5. What does your team need to function day-to-day? Talk to your engineers and designers. Do they need someone in every standup? Do they need someone available on Slack at 3pm? Or do they need a weekly strategic reset and a strong decision-maker on call?
6. Where are you in your product maturity? Very early or very late stage — fractional often fits. Middle stage (Series A–B, scaling a known product) — full-time tends to win.
7. Have you had a full-time PM fail here before? If yes, don't assume the next hire will fix it. Sometimes the problem isn't the person — it's the environment. A fractional engagement can help you diagnose the real issue before you repeat the same expensive mistake.
A note on the hybrid path
Some of the best outcomes I've seen don't start as either/or.
A company brings in a fractional PM to solve an immediate problem — get the roadmap in order, ship a neglected feature, build out the discovery process. Four months later, they're clearer on what full-time product leadership actually looks like for them. They hire with better requirements, better onboarding, and a foundation that the new hire can actually build on.
Fractional doesn't have to be permanent. Sometimes it's the on-ramp.
The bottom line
There is no universally right answer. But there is almost always a clearer answer — and it comes from asking sharper questions about what you actually need, when you need it, and what your company is actually ready to absorb.
If you're wrestling with this decision and want a gut check, I'm always happy to talk it through.
Jen Foley is the founder of Ballast Advisory, a fractional product management consultancy. She's spent 20 years in software and product, with senior roles at Wayfair, Babylist, Pivotal Labs, and Cognizant — and the last six as a fractional leader working across early-stage startups, nonprofits, and growth-stage companies.
