Product marketing has always had an identity crisis. It’s the rare function that can belong either to the Product org or to Marketing (or Revenue) — and be right in both cases.
One foot in the product, helping define what gets built and how users adopt it. The other foot in the market, ensuring the story wins hearts, minds, and deals. The reporting line simply amplifies one side of that duality.
Over the last decade, I’ve seen PMM succeed under both roofs — sometimes in the same company, at different stages. The choice isn’t ideological; it’s contextual. It’s about where your growth constraint lives and how your organization wins.
Let’s break that down.
When PMM Lives Under Product
Inside the Product org, Product Marketing becomes part of the product loop itself. PMMs attend roadmap reviews, write launch briefs, influence packaging and pricing, adoption of features, and test messaging inside betas & early launch programs, and sometimes even customer trainings. They sit shoulder to shoulder with PMs, shaping the customer experience before the first line of code ships.
The benefits are obvious: PMM influences what’s built, not just how it’s sold. Product adoption and activation improve because the narrative aligns with actual in-product value.
But there’s a price: market time shrinks. PMM becomes inward-facing, deeply embedded in product development but slightly detached from sales reality.
This setup shines in product-led organizations — especially those running a PLG motion. When your product is the main revenue driver, PMM belongs close to it. They can craft activation paths, define Product Qualified Leads (PQL), and translate user behavior into upsell triggers. Think of modern dev tools, collaboration SaaS, or any product where revenue begins with sign-up, not a sales call.
A typical case study could be a developer-first SaaS where PMM moved from Marketing to Product, started co-owning onboarding flows and PQL metrics, and saw trial activation double within two quarters. Market campaigns stayed minimal — the product itself did the heavy lifting.
When PMM Lives Under Marketing or Revenue
Flip the org chart, and PMM becomes market muscle. Their world is segmented into messaging, sales enablement, competitive plays, analyst briefings, and revenue programs. They’re judged on pipeline, win rate, and market share.
It’s the right move when sales-led or enterprise-led growth dominates — when buying decisions involve committees, proof points, and procurement cycles.
Here, PMM becomes the storyteller-in-chief. They own the category narrative, turn competitive insight into deal strategy, and equip reps with talk tracks that close business.
A typical case study could be an enterprise software company where one of the primary OKRs of PMM is to drive the pipeline. They build industry-specific plays, win/loss analyses, and executive proof points. Within six months, deal velocity improved, and the win rate jumped by nearly ten points.
But, again, trade-offs exist. Proximity to Sales can distance PMM from the roadmap. Without deliberate alignment, they risk becoming “slide factories,” disconnected from what’s actually possible in-product.
How the KPIs Diverge
While this comparison is not apples to apples and one could argue PMMs cannot do away with one while focusing on the other, I believe the shift of focus and the importance given moves as below:
Under Product:
- Activation rate, time-to-value, feature adoption
- Product-qualified leads and expansion usage
- Product-sourced revenue and NRR
- Content created for customers/launch/adoption
Under Marketing/Revenue:
- Pipeline created or influenced
- Win rates, deal velocity, and ACV growth
- Competitive takeouts and enablement effectiveness
- Content created for lead generation/sales plays
In reality, both need a balanced scorecard. A good rule of thumb: if PMM sits in Product, 60% of KPIs should focus on adoption, 40% on revenue; reverse that when PMM sits in Revenue.
The trick is to measure impact, not just output. Don’t judge a Product PMM by launches shipped, or a Revenue PMM by content produced. Measure how each moves the business forward.
PMM’s Influence
Under Product, PMM has a deep influence early in the lifecycle — feature definition, naming, pricing, and onboarding. They shape customer value from the inside out.
Under Revenue, influence shifts to the field — deal strategy, sales messaging, objections, and competitive positioning. PMM’s voice carries weight in pipeline reviews and executive forecasts, because they’re directly tied to bookings.
Neither is inherently better. But the visibility differs: PMMs in Revenue often enjoy more executive airtime because their work shows up in the numbers sooner. PMMs in Product have slower, subtler wins — but more lasting ones when it comes to retention and expansion.
Having said that, the biggest trap in both:
If you are considered someone just to create a brochure, “beautify” the deck, or manage a web page, your value is not understood or appreciated in either function!
When a re-org may be on the cards
I often wonder, is there a right time to place PMM in different functions? Like the Product Life Cycle, I believe placing the PMM role in the product works best when:
- You have a real PLG or product-assisted motion.
- Adoption and usage are your growth levers.
- Feedback loops are fast — days, not quarters.
I believe having PMM function report into Revenue works best when:
- Sales and marketing are the growth engines.
- Buyer education is key (think category creation, enterprise sales or compliance-heavy industries).
- You need close alignment with Sales Ops, Partner Marketing, or AR/PR.
I have also seen hybrid models. Many mature orgs run dual PMM tracks:
- Product-line PMMs in Product — handling launches, packaging, and adoption.
- Solution or Segment PMMs in Revenue — handling plays, enablement, and messaging.
How can we forget AI?
A common comment I hear these days, Can’t AI do it?
A person who doesn’t know a single line of code has become a professional software engineer overnight.
A person who doesn’t have a knack for design has become a perfect graphic designer overnight.
A person who doesn’t have a flair for writing started writing perfect grammar content overnight.
AI is blurring the lines in a PMM’s life as well. With tools that instantly summarize win/loss data, auto-generate enablement content, and test messaging at scale, PMM’s influence has expanded in every direction.
I think PMMs under Product can now iterate on messaging inside the product daily. PMMs under Revenue can train sales teams with dynamic, data-driven talk tracks.
No matter where they sit, AI gives PMM a new superpower: the ability to connect market signals and product signals in real time. The org chart matters less than the data contract between them.
So, Where Should PMM Live?
After years of being in and building this function, here’s the simplest truth:
Put PMM where your current bottleneck is.
- If your problem is adoption or expansion, move PMM closer to Product.
- If your problem is awareness, pipeline, or win rate, move PMM closer to Revenue.
- If you’re doing both — split it.
And remember: reporting lines matter less than rituals. Keep two standing meetings sacred — a monthly win/loss readout and a monthly adoption report. Those two touchpoints guarantee PMM stays bilingual, fluent in both product and market.
In the end, Product Marketing’s power lies in being the bridge, not in which shore it stands on. The best teams I’ve seen know how to seamlessly transition between Product and Market, regardless of the organizational chart. Because PMM, at its core, isn’t about where it sits — it’s about where it makes the biggest difference next.