Intro to Sales Engineering and Solutions Consulting: Gathering Feedback for Product Management

Gathering Feedback for Product Management

Gathering Feedback for Product Management: A Demo-Ready Study Guide

For Engineers → SEs, BDRs Upskilling, and SEs Sharpening Their Craft

What This Is

Gathering feedback for Product Management (PM) isn’t just about logging bugs—it’s a strategic weapon to win deals, retain customers, and shape your product’s roadmap. Think of it like this: During a competitive POC for a cloud security platform, the prospect’s CISO says, “Your DLP rules are too rigid—we need custom regex support for PCI compliance.” If you dismiss this as a “nice-to-have,” you lose the deal. If you capture it as a validated customer pain, you: 1. Win the deal by showing you listen (and may even fast-track a fix).
2. Arm your PM team with real-world data to prioritize features that close future deals.
3. Turn the prospect into a champion who advocates for you internally.

This guide teaches you how to extract, document, and leverage feedback like a top-performing SE—without sounding like a product manager.

Key Terms & Frameworks

• Voice of the Customer (VoC): Raw feedback from prospects/customers about their pain points, desires, and objections. Used to qualify deals (MEDDIC “Pain”) and influence roadmaps.
• Discovery Call: Early-stage conversation to uncover technical and business pain. Goal: Map feedback to demo stories and PM priorities.
• POC Feedback Loop: Structured process to capture, triage, and act on feedback during a technical evaluation. Critical for competitive bake-offs.
• MEDDIC “Pain”: The prospect’s quantifiable problem (e.g., “We lose $2M/year in fraud due to weak authentication”). Used to justify ROI and prioritize PM feedback.
• Champion: A prospect who publicly advocates for your solution. Their feedback is gold—they’ll tell you what’s missing to win the deal.
• Technical Win: When the prospect’s engineers prefer your solution over competitors. Feedback from these users validates your product’s strengths.
• Objection Handling: Turning pushback (e.g., “Your API lacks webhooks”) into actionable PM feedback while keeping the deal alive.
• Feature Request vs. Bug: A feature request is a new capability (“We need SAML support”); a bug is broken functionality (“The SAML login fails”). Triage both—but know which one wins deals.
• Roadmap Influence: Using deal-winning feedback to shape PM priorities. Example: “3 of our top 5 pipeline deals need Kubernetes support—let’s fast-track it.”
• Competitive Differentiation: Feedback that reveals why prospects choose you over competitors (e.g., “Your UI is 10x faster than [Competitor]”). Used in demo storytelling and PM positioning.
• Customer Advisory Board (CAB): A group of high-value customers who provide strategic feedback. SEs often recruit champions into CABs.
• Feedback Triage: The process of prioritizing feedback based on deal impact (e.g., “This feature request came from a $5M deal—escalate to PM”).

Step-by-Step / Process Flow

1. Prep: Set Up Your Feedback Capture System

Goal: Ensure no feedback slips through the cracks.
How:
- Tool: Use a shared doc (Notion, Coda, Google Docs) or CRM (Salesforce, HubSpot) to log feedback. Tag by: - Deal stage (Discovery, POC, Negotiation) - Source (Champion, Technical Buyer, Economic Buyer) - Impact (Deal-blocking, Nice-to-have, Competitive differentiator) - Template:
| Feedback | Source | Deal | Impact | Status | PM Ticket | |--------------|------------|----------|------------|------------|---------------| | “Need SOC 2 Type II report” | CISO (Champion) | Acme Corp ($2M) | Deal-blocking | Escalated | JIRA-1234 |

Sample Phrase:

“I’m going to log this in our feedback tracker so we can follow up. Can I summarize what you said to make sure I got it right?”

2. Discovery: Uncover Pain & Priorities

Goal: Identify deal-winning feedback early.
How:
- Ask open-ended questions to surface technical and business pain: - “What’s the biggest challenge your team faces with [current solution]?” - “If you could wave a magic wand, what’s one thing you’d change about [competitor’s product]?” - “What’s the impact of this problem on your revenue/operations/security?” (MEDDIC “Metrics”) - Map responses to PM priorities: - If they say “We need better audit logs for compliance,” note:
- Pain: Compliance risk → MEDDIC “Pain”
- Feature Request: Enhanced audit logging → PM feedback
- Demo Hook: “Let me show you how our audit logs solve this—here’s how they helped [Customer X] pass their SOC 2 audit.”

Sample Dialogue:

Prospect: “Your competitor’s dashboard is way more customizable.” SE: “Got it—customization is key for you. Can you walk me through a specific use case where their dashboard falls short? I’d love to share this with our PM team to see if we can improve.”

3. Demo/Presentation: Validate & Capture Feedback

Goal: Turn demo reactions into actionable feedback.
How:
- Watch for non-verbal cues: - Positive: Leaning in, nodding, saying “That’s exactly what we need.” → Log as a competitive differentiator.
- Negative: Frowning, crossing arms, saying “We’d never use that.” → Dig deeper (“What’s missing for you here?”).
- Use the “Demo Feedback Sandwich”: 1. Show a feature (e.g., “Here’s our API rate limiting”).
2. Ask for feedback (“How does this compare to what you’re using today?”).
3. Log the response (“Got it—you’d like higher limits. I’ll note this for our PM team.”).

Sample Phrase:

“I’m showing this feature because it’s a common pain point for teams like yours. How does this land for you—does it solve the problem, or is there something missing?”

4. POC: Structured Feedback Collection

Goal: Win the technical evaluation by addressing feedback in real time.
How:
- Set up a feedback cadence: - Week 1: Kickoff call → “What are your success criteria for this POC?” - Week 2: Check-in → “What’s working well? What’s missing?” - Week 3: Final review → “What’s the one thing that would make this a no-brainer for you?” - Triage feedback during the POC: - Deal-blocking? Escalate to PM/engineering (e.g., “They need SAML support to sign”).
- Nice-to-have? Log for future roadmap (e.g., “They’d like a dark mode”).
- Competitive gap? Highlight in your final POC report (e.g., “Unlike [Competitor], we support multi-cloud deployments”).

Sample Dialogue (POC Check-in):

SE: “You mentioned in Week 1 that you needed to test our API performance under load. How did that go?” Prospect: “It was good, but we hit a bottleneck at 10K requests/sec. [Competitor] handles 20K.” SE: “That’s helpful—I’ll log this as a feature request and see if we can prioritize it. In the meantime, let me show you how we optimize for cost at scale, which is where [Competitor] falls short.”

5. Post-Deal: Close the Loop with PM

Goal: Turn feedback into roadmap wins.
How:
- Summarize feedback in a deal debrief: - “Acme Corp ($2M deal) needed SOC 2 Type II reports to sign. They chose us over [Competitor] because we committed to delivering this in Q3.” - Escalate high-impact feedback: - Template for PM:
> “Hi [PM], here’s feedback from 3 deals this quarter that all requested [Feature X]. [Customer A] said it was a deal-breaker, and [Customer B] chose us over [Competitor] because we committed to it. Can we prioritize this?” - Follow up with the customer: - “We shared your feedback with our PM team, and they’ve prioritized [Feature X] for Q3. Would you be open to a quick call to review the spec?” (This turns customers into champions and validates your roadmap.)

Common Mistakes

Mistake 1: Treating Feedback as a “Nice-to-Have”

• What happens: SE logs feedback but doesn’t tie it to deal impact.
• Correction: Always ask, “How would this feature help you choose us over [Competitor]?” or “What’s the cost of not having this?” (MEDDIC “Metrics”).
• Why: PM teams prioritize deal-winning feedback, not “cool ideas.”

Mistake 2: Overpromising on Roadmap Items

• What happens: SE tells a prospect, “We’ll have this in Q2!” without checking with PM.
• Correction: Use hedging language:
• “This is a great idea—I’ll share it with PM and get back to you on timing.”
• “We’re actively working on this, but I can’t commit to a date yet.”
• Why: Never lie about roadmaps—it destroys trust and can kill deals.

Mistake 3: Ignoring “Soft” Feedback

• What happens: SE focuses only on technical feedback (e.g., “Your API lacks webhooks”) and misses business feedback (e.g., “Your pricing model doesn’t scale for us”).
• Correction: Log all feedback, but tag it by type (Technical, Business, UX, Pricing).
• Why: Pricing objections can be just as deal-blocking as missing features.

Mistake 4: Not Following Up on Feedback

• What happens: SE logs feedback but never closes the loop with the prospect or PM.
• Correction: Set a reminder to follow up (e.g., “I’ll circle back in 2 weeks with an update on this”).
• Why: Prospects remember who listens—this builds champion relationships.

Mistake 5: Assuming Feedback = Feature Request

• What happens: SE hears “Your UI is clunky” and logs it as a feature request.
• Correction: Dig deeper:
• “What specifically about the UI is clunky?”
• “Is this a deal-breaker, or would you still buy if we fixed it in a future release?”
• Why: Not all feedback requires a product change—sometimes it’s a demo storytelling or training issue.

SE Interview / Practical Insights

1. “The Prospect Asks for a Feature You Don’t Have”

Tricky Situation: During a demo, the prospect says, “We need [Feature X], which [Competitor] has. Can you do that?” How to Handle It:
- Acknowledge: “That’s a great point—[Feature X] is on our roadmap, and I’ll share your feedback with PM to prioritize it.” - Pivot to strengths: “In the meantime, let me show you how our [Feature Y] solves [Related Pain]—this is where we see customers get the most value.” - Ask for context: “How critical is [Feature X] to your decision? Would you still move forward if we committed to delivering it in [Timeframe]?”

Why This Works:
- Shows you listen (builds trust).
- Keeps the conversation going (avoids a hard “no”).
- Gives PM actionable feedback.

2. “The Champion Says Your Product is Missing a Deal-Breaker”

Tricky Situation: Your champion (who loves your product) tells you, “The CFO won’t sign unless we have [Feature Z].” How to Handle It:
- Validate: “That makes sense—[Feature Z] is important for compliance. Let me check with my team to see if we can fast-track this.” - Escalate internally: “This is a $3M deal—can we prioritize [Feature Z] for them?” - Offer a workaround: “In the meantime, here’s how [Customer X] solved this with our current features…” - Set expectations: “I’ll get back to you by [Date] with an update.”

Why This Works:
- Turns a deal-breaker into a roadmap discussion.
- Shows the champion you’re their advocate.

3. “The Prospect Says Your Product is ‘Too Complex’”

Tricky Situation: During a POC, the prospect’s engineer says, “Your product is powerful, but it’s too hard to use.” How to Handle It:
- Ask for specifics: “What’s the most frustrating part of the workflow?” - Log as UX feedback: “I’ll share this with our PM team—would you be open to a call with them to walk through your pain points?” - Offer training: “We have a dedicated onboarding team—would you like a session to get your team up to speed?” - Pivot to ROI: “I hear you—let me show you how [Customer Y] reduced their onboarding time by 50% using our [Feature]…”

Why This Works:
- Turns a negative into a collaboration.
- Shows you’re proactive about solving their problems.

Quick Check Questions

1. A prospect says, “Your competitor’s reporting is way better than yours.” How do you respond?

Answer:
- Acknowledge: “I appreciate you being honest—reporting is a key part of your workflow. Can you walk me through what you like about their reports and what’s missing in ours?” - Log feedback: “I’ll share this with our PM team—would you be open to a call with them to review your requirements?” - Pivot to strengths: “In the meantime, let me show you how our [Feature X] solves [Related Pain]—this is where we see customers get the most value.”

SE Mindset: Turn objections into feedback opportunities—don’t get defensive.

2. During a POC, the prospect’s engineer says, “Your API rate limits are too low for our use case.” What do you do?

Answer:
- Ask for specifics: “What rate limits are you hitting, and what would be ideal for your workload?” - Log as a deal-blocker: “This is critical for your decision—I’ll escalate this to our engineering team today.” - Offer a workaround: “In the meantime, here’s how [Customer X] optimized their API calls to stay within limits…” - Set expectations: “I’ll get back to you by [Date] with an update.”

SE Mindset: Triage feedback by impact—deal-blockers get escalated immediately.

3. Your champion says, “The CFO loves your product, but they want a 3-year price lock.” Your pricing team says no. How do you handle it?

Answer:
- Acknowledge: “I understand—price stability is important for budgeting. Let me check with my team to see what flexibility we have.” - Escalate internally: “This is a $5M deal—can we offer a 2-year lock with a 5% annual increase?” - Offer alternatives: “If a price lock isn’t possible, here’s how we can structure the deal to reduce your total cost of ownership…” - Set expectations: “I’ll get back to you by [Date] with our best offer.”

SE Mindset: Never say “no” without exploring alternatives—always escalate and negotiate.

Last-Minute Cram Sheet

1. VoC = Deal-winning feedback—always tie it to MEDDIC “Pain” and “Metrics.”
2. Discovery questions: “What’s the impact of this problem?” → Log as PM feedback.
3. Demo feedback sandwich: Show → Ask → Log.
4. POC feedback loop: Kickoff → Check-ins → Final review.
5. Triage feedback by impact: Deal-blocker? Escalate. Nice-to-have? Log for roadmap.
6. Never overpromise roadmap items—use hedging language (“I’ll share this with PM”).
7. Follow up on feedback—prospects remember who listens.
8. Turn objections into feedback: “What’s missing for you here?”
9. ⚠️ Never dismiss “soft” feedback (UX, pricing, training)—it can kill deals.
10. Close the loop with PM: “This feedback came from a $5M deal—can we prioritize it?”