ResumeUp taught us the problem.
ProductBridge became our attempt to solve it.
The lesson I keep coming back to:
The best SaaS ideas don't always start with a market map.
Sometimes they start with a workflow you're tired of doing manually.
2
5
165
Three layers I wish I had explained better:
Observation = one distinct problem or request
Theme = a broader pattern across observations
Strength = something users consistently value
Not every insight is a feature request.
2
2
119
Enterprise feedback management isn't just "more feedback."
It's more context:
Which account?
Which segment?
Who owns the relationship?
How urgent is it?
What if we ignore it?
Volume creates a storage problem. Context creates a decision problem.
1
66
Every product team says their workflow is simple.
Then you ask about statuses 😄
That's why ProductBridge supports custom statuses, fields, tags, and categories.
But I still believe defaults should work before customization becomes necessary.
44
"Our users want X" is often a dangerous sentence.
Which users?
New or long-term?
Free or paid?
SMB or enterprise?
Aggregate feedback can hide very different needs.
That's why segmentation matters as feedback volume grows.
39
A roadmap item without evidence is an opinion with a status badge.
I want product work to carry its history:
Who asked?
How many times?
From which channels?
What problem were they trying to solve?
Context should travel with the work.
25
A feedback platform shouldn’t become another silo.
That’s why I like boring plumbing:
Zapier
Make
Pabbly
Webhooks
The exciting part is AI.
The useful part is getting the signal where your team already works.
29
Not every feedback source needs a full integration.
Sometimes the useful signal is on a webpage, in a competitor review, or inside an internal tool.
We built a Chrome extension so teams can capture feedback with context—without another copy/paste workflow.
1
23
Now that our MCP server is live, I’m looking for weirdly specific workflows.
Not:
“Summarize feedback.”
More like:
“Before I write this PRD, show me every complaint about this workflow from enterprise accounts.”
What would you build?
1
30
MCP isn’t interesting because it lets us say "AI" again.
It’s interesting because customer feedback becomes available inside the tools where product work already happens.
The goal: less dashboard tourism. More customer context at decision time.
18
Small trust detail I care about:
A feedback portal feels more like part of the product when it lives at:
feedback.yourdomain.com
instead of a random third-party URL.
Branding isn’t the core product. Removing trust friction matters.
19
Feedback portals have a hidden problem: login friction.
Ask users to create another account just to report an idea and many won’t bother.
Identity verification + SSO may sound enterprise-y.
To me, they’re feedback-volume features.
1
1
23
We didn’t want "add a feedback widget" to mean one rigid button.
Different products need different entry points:
→ floating button
→ inline embed
→ custom trigger
→ iframe
→ direct link
Feedback collection should fit the product, not interrupt it.
27
Founder at 11:58 PM:
“I’ll just check the latest app reviews before sleeping.”
The latest app review:
⭐
“Nothing works.”
Sleep cancelled.
17
A review says:
“Terrible app. Cancelled.”
Not very actionable.
But combine it with 18 support messages mentioning the same onboarding problem and suddenly it’s not a vague complaint.
Context turns sentiment into evidence.
15
One-star reviews are painful.
They’re also brutally direct product research.
The mistake is treating them only as a reputation problem.
A recurring complaint across reviews can become a roadmap signal—if it reaches the product team.
16
Which source contains the most valuable unstructured product feedback for your team?
Gong calls?
Zendesk tickets?
Slack communities?
App reviews?
Where do you have the most signal and the least structure?
25
Every integration looks easy in a diagram:
Source → ProductBridge
Reality:
different auth
different rate limits
different object models
different timestamps
different user identities
The connector is only the beginning. Normalization is the real work.
11
Support conversations are full of product feedback.
But asking agents to copy every request into another tool guarantees gaps.
For Intercom, we wanted 2 paths:
→ submit from the sidebar
→ analyze closed conversations for product signals
1
18
