Strategic initial callChoose a time
Who I am Competencies References Services Process Insights DownloadsNEW Contact
Book a call
Sales Enablement 7 min read

Why Sales doesn't send product feedback back and how to build a feedback culture that lasts.

The knowledge is there every day. Sales hears it in every customer conversation, every price negotiation, and every objection. It never reaches the product manager. That's not a communication problem. It's a structural vacuum.

IF
Irene Flaming
Commercial Architect · B2B

I've seen this pattern in almost every B2B company: The product manager is working on the next feature. Sales is talking to customers every day and hearing (casually, incidentally, but consistently) what actually frustrates them, what's missing, and what isn't working. That knowledge stays in people's heads. Maybe it gets mentioned in the next standup. Maybe it doesn't.

This isn't a problem with individual employees. It's a problem with the system or, more precisely, the lack of one.

Four reasons Sales doesn't send feedback back

Before you demand a feedback culture, you need to understand why one doesn't emerge on its own. The reasons are almost always the same.

01
No clear path
There's no platform, no form, and no defined process. Where is the feedback supposed to go? Slack? Email? Should someone mention it in the next team meeting? When the path isn't clear, nothing happens.
02
No feedback on the feedback
Sales has shared feedback before. Nothing happened. No acknowledgment, no response, and no visible consequence. If people never see their input lead to anything, eventually they stop providing it.
03
No shared understanding
What counts as “product feedback”? A feature request? A complaint? A strategic observation? If nobody has defined what should be reported, everyone reports something different, or nothing at all.
04
No ownership
When everyone is responsible, no one is responsible. There's no designated person actively asking, collecting, and structuring the input. Without clear ownership, feedback remains a matter of chance.

What's structurally missing from the team

You can't demand a feedback culture into existence. It emerges when three structural elements are in place, elements that are missing in most companies.

The Listener
One person responsible for each team or channel who actively collects feedback instead of waiting for it. They ask questions, consolidate observations, and make sure feedback doesn't die in someone's head.
The platform
One central, simple system for everyone. Not an Excel sheet. Not a chat channel. A structured tool where everyone records what they heard, along with the date, customer, segment, and impact.
The core team
3–5 people who regularly review, prioritize, and decide. This team closes the loop by making decisions and communicating those decisions back to the people who provided the feedback.

The complete feedback loop

Feedback that doesn't lead to action is an exercise without an outcome. The loop needs to be complete, from the initial observation all the way back to Sales.

Today: The broken path
Customer conversation
→
Sales
→
??? no path
→
Product Manager
→
Roadmap
The complete loop: How it should work
1
Capture
Sales records the feedback in a structured format: date, customer, what was said, and impact
2
The Listener
Consolidation: What's an isolated signal, and what's a pattern?
3
Core team
Evaluate based on frequency, urgency, and strategic fit
4
PM input
A prioritized briefing. Not a wish list, but structured market insight
5
Feedback
Sales learns what happened with the input, making them even more likely to share the next piece of feedback

How the core team evaluates feedback

Not all feedback is equally important. The core team decides what gets addressed, when, and how. Four dimensions help.

Frequency: How often does this issue come up?
Urgency: Are we losing deals because of it right now?
Strategic fit: Does it align with the product vision?
Segmentation: Which customer segment does it affect?
Feedback card: Template for every entry

Date: [MM/DD/YYYY]
Customer: [Company · Segment · Size]
What was said: Quote or paraphrase, as close to the original wording as possible
Context: In what situation? Initial conversation · Price negotiation · Objection
Impact: What does the problem cost the customer? Time · Money · Risk
Deal relevance: Did the feedback influence the buying decision? Yes · No · Unclear

How close is the product manager to Sales?

One of the most underestimated levers in practice isn't a tool or a process. It's physical proximity.

I once worked in a MedTech company where I sat in the same office as Sales. It wasn't planned. It wasn't strategic. It just happened. And it became one of the most valuable product management experiences I've had. I heard price negotiations live. I heard what objections actually sounded like, in the customer's own words, not in the cleaned-up summary presented at the next team meeting. I understood why Sales sometimes didn't have an answer in the moment, and exactly what information was missing when they needed it.

That proximity creates a shared picture of reality that even the best-designed feedback platform can never fully replace.

If physical proximity isn't possible, you need active alternatives:

The question isn't whether the PM has time for this. The question is whether they can afford not to.

What Sales needs from the PM in seconds

When a customer conversation is underway and an objection comes up, Sales doesn't have three minutes to search internally. What they need has to be accessible within seconds, and the PM is responsible for making sure it exists.

Tool 01
Product alternatives on demand
If the primary product isn't the right fit, Sales needs to know immediately what to offer instead. Not after the conversation. Now. The PM creates a simple overview: Situation → Alternative → Argument.
Tool 02
Objection-handling guide
The most common objections are known. They come up again and again. The PM structures responses that are accurate and defensible from a product perspective. Sales translates them into their own language. No improvisation at the moment that matters.
Tool 03
Messaging for each product
One product, one core message. Clear, concise, and free of jargon. The PM owns this message, not Marketing, not Sales. The person who understands the product needs to define how it should be communicated.

These three tools sound simple. Yet most companies still don't provide them because nobody has clearly defined them as part of the product manager's responsibility. That's a structural issue, too.

Culture is the prerequisite

No system works without the right culture. And a feedback culture isn't created by a one-time initiative, a kickoff presentation, or the rollout of a new tool.

It emerges when leadership leads by example. When feedback doesn't disappear in a meeting, but shows up three months later as a feature. When Sales sees that the tiny detail a customer mentioned in passing eventually makes its way into the product.

Even the smallest piece of feedback can be the beginning of an innovation. A new product. A service extension. Positioning that suddenly works. The moment a customer says, “What I really need is...” isn't just a comment. It's a strategic signal.

Companies that understand this don't just build feedback forms. They build a culture where no signal gets discarded before someone has heard it.

“A product manager who isn't in the room with Sales will always build past the customer, with good intentions, but incomplete information.”

For more on why Sales and Product fundamentally operate on different time horizons, and how to structurally connect the two, read Why Sales and Product rarely understand each other. And for how to build customer feedback as a system rather than an event, read Are you really talking to your customers?

IF
Irene Flaming
Commercial Architect · B2B

I build commercial systems for B2B technology companies in MedTech, industrial, and SaaS: go-to-market, sales enablement, and pricing. Built to be used, not just presented.

Start a conversation →

More articles