If you’re a product manager trying to figure out what you’re worth right now, here’s the uncomfortable truth: there isn’t a number. There’s a range so wide it barely functions as a benchmark, and it’s moving fast enough that data from eighteen months ago is close to useless.
Heidi Ram, who leads delivery for The Product Recruiter, had a name for it on our July 8 session: “the real Wild West.” Here’s what that actually looks like, and what to do about it if you’re the one being priced.
The range, and why it’s this wide
An AI-native product manager at a B2B SaaS, venture-backed company can land anywhere from $185K to $275K, sometimes more. Same title. Often similar company size. Wildly different outcomes.
Heidi’s explanation: “The IC compensation playbook has been thrown out the window, and anything could go; it depends on many things. Location, location, location, the degree to which the person has native AI experience and actually delivered products into the market that people are using and buying and paying for, whether the startup is in that zero to one, one to ten stage or further along.”
Andrew Shaw, who leads Martyn Bassett Associates’ search practice, has watched the same role reprice in real time. The closest comparable he could point to is the technical platform product manager role: “We were placing people in 2022 at salaries of 130,000. In 2024, we placed somebody at 170,000. Now I’m working on searches that are 250 base.” Same seniority band. Nearly double the number in four years.
What actually counts as “AI experience”
Here’s where most candidates get it wrong. Heidi pushed back hard on the idea that having used AI tools is the same as having AI experience that employers will pay for.
“I don’t think there’s anyone who doesn’t have AI on their resume,” she said. Everyone’s resume claims AI skills now. That’s not a differentiator anymore; it’s table stakes, and treating it as your headline story won’t move a number.
What actually counts is specific to what the employer is trying to solve. Heidi’s examples: a company might need “a product manager at a staff or principal level who’s going to be the first PM in the business, and they’re going to own our core product,” but also be building automations and efficiencies internally. Or a company doing contact-center transformation needs someone who understands voice and speech-driven engagement. Or a legal-tech company needs someone who gets how AI surfaces the actual disputed issues in a lawsuit across thousands of documents.
None of those are “I used ChatGPT to write user stories.” They’re specific, provable, and tied to outcomes a business actually needs. Her advice: stop thinking broad-brush about whether you “have AI experience,” and start thinking about whether you could solve the specific problem a specific employer is hiring for.
If you don’t have an AI story yet
Heidi’s message to anyone feeling behind: there’s still time, and there’s room for everyone.
“This industry is so large, it’s larger than what you understand it to be. Anytime I look around, there’s a new product being solved, a new category of software I’ve never even heard about.”
Her advice is blunt and practical: build something. Not for your resume, just to have hands-on experience with the tools. And if you don’t land the AI-native role this cycle, that’s not necessarily a career mistake. She drew the comparison to OpenAI circa 2016 to 2018, when plenty of good candidates passed on offers there because the opportunity didn’t look real yet, and took safer jobs instead. Some of those people are fine. Some probably regret it. Neither outcome makes you a failure for choosing differently from what the market rewarded in hindsight.
The one piece of advice that matters most
When asked for a single piece of advice for candidates positioning themselves in this market, Heidi didn’t point to skills or years of experience. She pointed to the story:
“Have your talk track ready. The before and after story of what you’ve done. Where was the product? Where was the business? What was the situation when you were hired? And then where is it now, or by the time you left?”
Not transferable skills. Not tactics. Outcomes, in numbers, that you can say out loud without hesitating. If you’re a VP or CPO candidate and you can’t state the revenue of the business when you joined versus now, that’s a gap to close before your next interview, not during it.
Setting compensation for a product management role? Book time with our team. We’re in these searches every week, and we can tell you what the role actually costs, not what a job board estimates.
This post is drawn from our July 8, 2026 live session, “What Venture-Backed Companies Are Actually Really Paying for Product Roles,” with Martyn Bassett, Heidi Ram, and Andrew Shaw. Watch the full recording at hs.mbassett.com/product-salary-webinar.