It depends on three numbers you control and one you don't. Hours per week, number of weeks, and how much of the role you cover are your decisions. The going rate for the person doing the work is set by the market. What follows is what moves each number, what the five common options really cost, and a formula you can fill in before you talk to anyone.
What drives the cost
Weeks of leave. Parental leave for a US product manager commonly runs twelve to sixteen weeks. The federal FMLA guarantees eligible employees up to twelve weeks of unpaid, job-protected leave, and plenty of employers go longer or pay part of it. Dates also move, so budget a few weeks of slack either way.
Hours per week. A role that is mostly executing a settled plan needs a fraction of the hours of one that carries live decisions: prioritization, stakeholder pushback, discovery. Count the meetings first. They are the floor.
Seniority of the coverage. A senior person bills more per hour and ramps faster. A junior person bills less and needs the director to fill in the judgment calls, which is a cost that lands on someone else's calendar.
How much you cover. Covering everything is the most expensive version. Covering the roadmap and the stakeholders while explicitly pausing discovery is cheaper, as long as you treat the pause as a decision with its own price. More on that below.
Overlap. A week or two of handoff before the leave and a short re-entry after it add hours. They are also the hours that decide whether the rest of the spend works.
Five options, and what each one costs
| Option | What you pay | What it hides | Risk |
|---|---|---|---|
| Do nothing | No new spend | Decisions drift, commitments slip, and the work lands on whoever sits closest to it | High A missed commitment or an overloaded team surfaces mid-leave, when it's hardest to fix |
| Internal stretch | Usually a title change or a bonus, plus the stretch person's own work going undone | A second job for someone already full, and a hole where their old role was | Medium–high Both jobs get done halfway, and the person stretched is a flight risk afterward |
| Contract PM | An hourly or day rate, plus the time to find and brief someone | Ramp on your product, and a thin pool for a short, fixed-end engagement | Medium The person doesn't land with the team, or leaves before the end date |
| Fractional coverage | Hours or a monthly fee for a defined scope, little sourcing time | Fewer hours than a full-time seat, so the scope has to be chosen on purpose | Low–medium Work outside the agreed scope drops unless someone owns it |
| Full-time backfill hire | Salary and benefits, recruiting fees or recruiter time, interviews, onboarding | Weeks of search before day one, then a ramp, for a seat that ends in a few months | Medium The hire starts after the leave does, and you have an extra seat when the PM returns |
Two of these cost nothing on paper, which is why they are popular. They also carry the most risk. The other three each have a visible price and a ramp. The difference between a contract PM and a fractional one is mostly in how the scope is set; this piece covers that distinction.
The costs that don't have an invoice
Paused roadmap work. If discovery stops for four months, the cost is whatever that discovery would have changed. Sometimes that is nothing. If a customer commitment or a renewal depends on it, it can exceed the whole coverage budget. Ask what has a date on it.
The returning PM's re-entry. Someone who comes back to four months of decisions they didn't make spends their first weeks reconstructing them. With a decision log and a handback, that takes days. Without them it takes weeks, and the quality of that return affects whether they stay. Backfill, redistribute, or pause goes through when each choice holds up.
A formula you can run today
Hours per week × weeks × hourly rate.
Add handoff and re-entry weeks to the weeks. Then add whatever recruiting or ramp time applies to the option you are pricing.
For example, say a leave runs fourteen weeks and you add two weeks of overlap, so sixteen weeks of coverage. At twenty hours a week that is 320 hours. At a hypothetical $150 an hour, that comes to $48,000. If you decide to cover only the roadmap and stakeholders at ten hours a week, it is 160 hours, or $24,000. The $150 is a placeholder to show the arithmetic. It is not a quote or a benchmark.
Actual rates vary by market, by seniority, and by scope, so put your own numbers in. The useful part is the comparison. Run the same arithmetic for a hire, with salary, benefits, and the weeks of search before anyone starts, and put the paused-work cost next to all of it.
Common questions
How much does it cost to cover a product manager on parental leave?
Roughly hours per week, times weeks, times an hourly rate, plus any recruiting or ramp time. Most leaves are bounded and known in advance, so you can estimate the number before talking to anyone. Rates vary by market, seniority, and scope.
Is it cheaper to redistribute the work than to hire coverage?
On the invoice, yes, because nothing is billed. The costs show up as slower decisions, an overloaded lead, and a returning product manager who comes back to choices they did not make. Whether redistribution is cheaper overall depends on whether the role carries live decisions.
How long is a typical parental leave for a product manager in the US?
Twelve to sixteen weeks is common. The federal FMLA provides up to twelve weeks of unpaid, job-protected leave for eligible employees, and some employers offer more or pay part of it. Plan for the dates to move by a few weeks.
If you have a leave date, the coverage plan template will tell you how many hours the role needs, which is the input the formula is missing. Here is how a coverage engagement is structured.
Want a number for your team?
Tell me the leave dates and what has to keep moving, and I'll scope it. If redistributing is the cheaper answer for you, I'll say so.
Let's scope itThe Product of Everything is where I write about product management and the discipline of building things well.
Subscribe on Substack