Measuring product marketing gets complicated quickly. Ask Sales, Product, and Marketing what a PMM should deliver, and you will hear different answers: pipeline, adoption, win rate, positioning, a successful launch.
Each answer covers part of the job. Much of a PMM's work shows up in results shared with other teams, which makes it hard to separate your contribution from everyone else's. You still need to know whether the work is helping.
Across 25 years in marketing, including 15 in deep tech, I have found four areas useful to look at: adoption, sales impact, positioning, and how early PMM gets involved in decisions. For each one, I want numbers and feedback from the people doing the work.
Why does no single number work?
Product marketing connects Product, Sales, Marketing, and Customer Success. The priorities depend on the company, but the work usually crosses several teams.
A pipeline target can tell you something about commercial impact. It tells you less about whether customers understand a new feature or whether the product team is solving the right problem. A launch calendar tells you what shipped, but you need to look further to find out what happened afterward.
I use the four areas below to work out what to measure. They give me a fuller picture than any one metric can.
Do your launches keep working after launch day?
Launch week gets a lot of attention. I also want to know what customers are doing a few months later. Did the intended segment try the feature? Did they find enough value to keep using it?
The Product Marketing Alliance's article on how technical product marketers measure success is a useful reference for thinking about adoption and retention alongside launch activity.
Depending on the product, I would look at:
- Feature activation rate
- Onboarding completion
- Adoption among the intended users
- Retention and expansion
Before launch, I set objectives and build the messaging. After launch, I look at usage, collect feedback, and work through what needs to change. Sometimes the message needs work. Sometimes customers need more help getting started. You only find that out if someone keeps paying attention after the announcement.
At Visual Layer, we went from zero to acquisition in a year. That is a company result I am proud to have contributed to. To understand how the launch itself performed, I would still look at who adopted the product and what they did with it.
Does Sales use your work?
A battlecard can be accurate, well written, and completely unused. Before making another one, I want to understand why.
Useful sales material fits the conversations reps are having. A competitive card helps them answer an objection. A deck gives them a clearer way to explain the product. When reps come back with questions or ask for an update, that feedback helps me understand what they need.
The measures I would look at include:
- Win rate and reasons for wins and losses
- Deal velocity
- Use of sales materials
- Influenced pipeline and revenue
At Coro, my work contributed to $1M+ in quarterly annual contract value (ACV) and 300% year-over-year company growth. At Lytx, on the Surfsight line, we saw a 65% increase in market share. Those were shared results. I would look at them alongside sales feedback and use of the materials to understand my contribution.
Does everyone tell the same story?
Positioning starts to work when people can explain the product consistently without reading from a document.
Listen to how Product, Marketing, and Sales describe it. Do they agree on who it is for, what problem it solves, and why someone would choose it? Then listen to customers. What do they understand, and where do you still have to explain?
Useful signals include:
- Website conversion rates
- Sales feedback on the messaging
- Share of voice
- Analyst mentions and how analysts describe the product
None of these tells the whole story. Website conversion depends on more than the words on the page, and an analyst mention does not necessarily mean your positioning landed.
I find sales calls especially useful. I listen for the questions buyers ask, the explanations that help, and the points where the conversation stalls. That gives me something specific to investigate before changing a headline.
The same applies before writing new positioning. I interview stakeholders, review existing material, and identify the assumptions we need to test. If the premise is wrong, better wording will only take you so far.
How early do you get involved in decisions?
Some of the most useful signs of PMM success are harder to put on a dashboard.
Product asks for your customer insight while the roadmap is still open. Sales brings you recurring objections so you can work on them together. Marketing involves you while a campaign is taking shape.
These are signs that people trust your contribution. They also give you more opportunity to help. If you first hear about a feature when the specification is final, many of the decisions your research could have informed have already been made.
I would ask the teams directly whether PMM is involved early enough and whether that involvement helps them make better decisions. Their answers can tell you where the working relationship needs attention.
How does success change by company stage?
The company's stage changes what useful progress looks like.
At a Series A or B startup
You may be defining the first ideal customer profile (ICP), establishing baseline messaging, and looking for signs of product-market fit. There may be little reliable data to compare against, so part of the job is deciding what to track and building that baseline.
At an enterprise
You are more likely to have an established product, customer base, and set of measures. The priority might be adoption of a particular feature, cross-sell, or expansion within an existing segment. Agree on the outcome you want to improve and how you will assess PMM's contribution.
I have worked as a solo marketer across ICP, messaging, and GTM planning, and built a 300-page developer portal. That breadth matters when you are establishing the foundations. In a more established team, the remit may be narrower. The scorecard should reflect the job you need done.
How do you know yours is working?
Start with four questions:
- Are customers still using what we launched a few months later?
- Do reps use the materials in their sales conversations?
- Can customers and colleagues explain the product consistently?
- Does PMM get involved while there is still time to influence a decision?
The answers will not replace your metrics. They will help you interpret them and decide where to look more closely.
If reps are not using the materials, find out why before counting the next batch as progress. If adoption is low, investigate where customers get stuck. Those conversations give you a better starting point than the number of assets or launches delivered.
I want a PMM review to cover what changed, where the work helped, and what still needs attention. The other teams' experience belongs in that discussion.
Key takeaways
- Assess PMM's contribution across adoption, sales impact, positioning, and collaboration.
- Use feedback from customers and colleagues to help explain the numbers.
- Choose measures that reflect the company's stage and PMM's remit.
- Review what people use and what changes as a result of the work.
Where does your scorecard need work?
If your current measures leave you unsure where product marketing is helping, start with one of these areas and talk to the people closest to it.
For a second set of eyes, bring your current scorecard to a free 30-minute call.
