Key takeaways
- A product manager owns the why and the what; engineering and design own the how.
- Prioritising means saying no to most requests, with reasons people can understand.
- Product marketing positions and launches what the product manager's team builds.
- Sales needs honest roadmap context, and product needs evidence from lost and won deals.
How a product manager decides what to build
A product manager decides what to build by weighing customer problems against business goals and the cost of solving them. Requests arrive from everywhere, so the job is less about collecting ideas and more about choosing the few that matter most now.
- Talk to customers and watch how they use the product.
- Read support tickets, sales notes and reasons for lost deals.
- Estimate effort with engineering and design.
- Rank options against the company's goals for the quarter.
- Write down what will not be built, and why.
Product manager vs product marketing manager
A product manager decides what gets built; a product marketing manager decides how it is positioned, priced and launched to the market. The product manager faces engineering and customers' problems, the product marketer faces buyers, sales and competitors.
The two work best as a pair. The product manager explains what a release does and who it is for; the product marketer turns that into messaging, sales material and a launch plan. When either side is missing, features ship that nobody hears about, or launches promise what the product does not do.
What sales needs from product management
Sales needs honest roadmap context from product management and gives back evidence from the field. A seller who knows what is coming, and what is not, can set fair expectations instead of guessing in front of a customer.
In return, product managers need more than a feature request. The useful version says which customer asked, what problem they were trying to solve, what the deal was worth and whether it was lost because of the gap. A B2B product manager reads that context far more closely than a list of votes.
The product manager as a software evaluator
When their company buys software, a product manager is usually a user or an evaluator rather than the budget holder. They take part in choosing research, analytics, feedback and roadmap tools, and they are often asked to check whether a tool fits the product the company sells.
They are practical evaluators: they want to see real workflows, clear limits and how data leaves the tool. Sellers who exaggerate get caught quickly, because product managers spend their days spotting the gap between what is promised and what ships.
Common mistakes in working with product managers
The common mistakes in working with product managers are treating them as order-takers and promising customers what they have not agreed. A seller who commits to a feature date in a deal puts the product manager in a position where every option disappoints someone.
The better habit is a regular, short exchange: sales brings patterns from customer conversations, product brings what is planned and why. That keeps promises realistic and gives the product team the evidence it needs.
Where Pebbles Ai fits
- CapabilityResearch & analysisResearch reads competitors' public pages and other sources and returns findings with numbered citations, so a product manager can check every claim before it shapes a decision.
- CapabilitySmartboxThe assistants' Gmail and Outlook tools read long customer threads, and an assistant can pull out the decisions, open questions and requests in chat.
Common questions
Does a product manager need to know how to code?
Not usually. Understanding how software is built helps them estimate effort and talk with engineers, but the job is deciding what to build rather than building it.
Who owns the product roadmap?
The product team owns it, with each product manager responsible for their area. Leadership sets the goals the roadmap serves, and sales and marketing inform it.
What makes B2B product management different?
B2B products have buyers who are not always the users, longer sales cycles and large customers whose requests carry weight, so product managers must balance individual deals against the wider market.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
