I've been running tl;dl for a while now.

I've talked to PMMs at Clay, Peloton, Tubi, Hinge, Instant. People who've built product marketing functions from scratch at fast-moving companies. People who've redefined what the role means in their orgs.

And after all of those conversations, one thing keeps coming up.

Not as a complaint. More like a quiet frustration.

PMM is finally becoming what it was always supposed to be. And most companies are still treating it like a support function.

What I keep hearing from guests

Tanvi at Clay said it plainly: features don't sell. Solutions do. Her job isn't to write product descriptions. It's to understand how customers talk about their problems, and make sure every person on the go-to-market team speaks that language.

Shriya at Peloton talked about launching Strength Plus into an existing subscriber base. The job wasn't marketing a new product. It was repositioning an entire brand relationship. That's a strategic call, not a content request.

Rahul at Tubi (coming soon!) talked about building positioning in a market where most people don't even understand your category yet. Where your job is to create the frame before you can win the argument.

These are not support roles. These are not "write the one-pager for the sales team" roles.

These are people who sit at the intersection of customer insight, product direction, and revenue strategy. And they're operating that way because the companies they work for let them.

The gap

Most companies don't.

Most companies hire a PMM to write copy, update the website, prep the launch email, and sit in the product review meeting to take notes. They want someone who can "translate" technical features into customer language.

That is a real skill. It's not nothing.

But it's also not what the best PMMs are actually doing. And it's not what makes PMM valuable as a function.

The PMMs I've talked to who are doing their best work are doing three things most orgs don't explicitly ask for:

They own the customer insight layer. Not just buyer personas in a slide deck. Live, updated intelligence about how customers describe their problems, what's driving buying decisions, and where the category narrative is heading. They feed this upstream to product and downstream to sales.

They make positioning decisions, not just positioning documents. There's a difference between writing a message map and actually deciding what your company is and isn't. The second one requires authority, access to leadership, and a seat at the table before decisions are made. Most PMMs don't have that. The good ones fight for it.

They treat launches as revenue events, not announcements. A launch isn't a blog post and a LinkedIn update. It's a coordinated moment to accelerate pipeline, expand existing accounts, and shift how the market thinks about you. That requires cross-functional ownership, not cross-functional coordination.

Why most teams aren't ready

Part of it is structural. PMM often reports into marketing, which means the default ask is marketing output: content, campaigns, assets.

Part of it is that the function is still young. A lot of leadership has never seen what great PMM looks like. They don't know what to ask for.

And part of it is on us. When PMMs accept the support role, they reinforce the expectation. When they take every content request without pushing back on the strategy behind it, they train their org to see them as executional.

I've done this. Most of us have.

What changes when PMM is actually strategic

The Clay launch cadence works because Tanvi's team is upstream of every feature decision, not downstream. They don't get handed a product and asked to market it. They're part of figuring out what gets built and why.

That changes everything about how launches land.

It also changes how sales talks to customers. How the product team prioritizes. How leadership thinks about market positioning. Good PMM has an outsized return because it touches every customer-facing surface.

The question isn't whether PMM should be strategic.

It's whether you're operating at a company that understands the difference between a PMM who writes things and a PMM who thinks first.

If you're not, that's worth knowing. And worth changing.