Customer Case: Boei

What they wanted

Boei is a friendly lead widget that helps convert website visitors into leads through contact forms, WhatsApp, Facebook chat, and more. With a lead widget you always show the most important buttons on your website (like a WhatsApp button). Boei serves thousands of websites worldwide and, as a result, receives a steady stream of feedback from users across Twitter, email, Facebook, and WhatsApp.

Boei wanted to centralize user feedback and allow users to provide input without overburdening customer support. They aimed to prioritize work, gather structured feedback, and involve users in decision-making.

The challenge before ProductLift

Before adopting ProductLift, Boei's feedback lived in scattered channels. Feature requests arrived through support emails, Twitter DMs, WhatsApp messages, and Facebook comments. The team had no single source of truth for what users actually wanted. This created several problems:

• Duplicate requests went unnoticed. The same feature might be requested ten times across three channels, yet it would never register as a top priority because the requests were never aggregated.
• Prioritization was guesswork. Without vote counts or usage data attached to requests, deciding what to build next relied on gut feeling rather than evidence.
• Users felt unheard. When someone submitted a feature idea via email, there was no easy way to follow up later and let them know the feature shipped. Many users assumed their feedback disappeared into a void.
• Support time was consumed by status questions. Customers frequently asked "Is feature X on the roadmap?" or "When will you add Y?" because there was no public place to check.

Boei needed a system that would collect feedback in one place, let users vote on what matters most, and keep everyone in the loop as features progressed. That is exactly where ProductLift's feedback boards came in.

What they said

We love to be able to prioritize new developments based on user feedback. We know exactly what users believe is important and we use that for our decision making.

Results at a glance

What we did

ProductLift has become an integral part of Boei's product development process, offering a range of features that enhance collaboration, prioritize work, and keep everyone informed.

With features like the sidebar widget, the impact/effort prioritization matrix, and transparent update emails, Boei achieved strong engagement and alignment with user needs. The seamless Single Sign-On integration made participation effortless.

Gathered all feature requests in one organized place

Boei empowers its users by giving them the opportunity to suggest, vote, and comment on the wish list. This democratic approach ensures that the most popular and highly requested features are given priority, aligning the product development roadmap with the needs and desires of the user community.

By involving users in the decision-making process, Boei can enhance their product in a way that resonates with their target audience, leading to higher satisfaction and adoption rates. Instead of sifting through inboxes and chat logs, the team now opens a single feedback board to see exactly what users care about, complete with vote counts and threaded discussions.

For tips on running an effective voting process, see our guide on feature voting best practices.

Prioritized the roadmap with the impact/effort matrix

The impact/effort prioritization matrix in ProductLift was a game-changer for Boei. With all feature requests consolidated into a single list, along with customer data like plan type and company size, the Boei team can easily assess the popularity and importance of each feature.

The matrix helps them identify the features that have the highest impact and align with their strategic goals, enabling them to focus their efforts on the most valuable enhancements for their users.

Here is how the process works in practice:

1. Collecting. New feature requests flow in through the feedback board, the in-app sidebar widget, and SSO-authenticated user submissions. Every request automatically receives its own page where users can vote and leave comments.
2. Scoring. During a regular review session, the Boei team assigns impact and effort scores to each request. Impact reflects both the number of votes and the strategic value of the feature. Effort captures the estimated development time and complexity.
3. Plotting. The impact/effort matrix visualizes all scored requests on a two-dimensional chart. Features in the high-impact, low-effort quadrant become obvious quick wins. High-impact, high-effort items are scheduled for longer development cycles.
4. Deciding. The team picks the top candidates from the matrix and moves them into the "Planned" column on the public roadmap. Users can see exactly what is coming next.

The Boei team reviews the matrix on a regular cadence. This keeps the roadmap fresh and ensures that newly popular requests don't sit unnoticed for months.

This structured workflow helped the product manager build a roadmap that truly reflects user demand.

Closed the feedback loop

Closing the feedback loop is one of the most impactful things a product team can do, and Boei takes it seriously. Every feature in the wish list comes with a list of all the users who upvoted it. When the status of a feature changes (from "Under Review" to "Planned" to "Shipped"), ProductLift sends automatic update emails to every voter.

This means users who upvoted a particular feature are directly informed about the progress and can start using the feature as soon as it becomes available. The result is a virtuous cycle: users see that their feedback leads to real changes, so they continue to engage with the board, submit new ideas, and vote on existing ones.

Beyond automated emails, Boei also uses the changelog to announce shipped features publicly. This gives the broader user base visibility into what was built and why. Users who did not vote still benefit because they can discover new capabilities they might have missed otherwise.

The combination of automated notifications and a public changelog transforms a one-way feedback form into an ongoing conversation between the Boei team and their users.

Seamless within their product

Boei uses the sidebar feature from ProductLift. The sidebar widget showcases what's new, keeping users informed and engaged with the latest updates and enhancements.

It also enables users to request new features effortlessly, without leaving the Boei app. This is critical for capturing feedback at the moment of inspiration. When a user thinks "I wish this tool could do X," they can submit that idea in seconds rather than switching to a separate website or sending an email.

Another major advantage for Boei is the seamless integration of Single Sign-On (SSO) with ProductLift.

Boei users are automatically logged into ProductLift without the need to create a separate account. This removes a significant friction point. Every extra step in the submission process costs you potential feedback, so eliminating the signup barrier means more users participate and the data becomes more representative of the actual user base.

What we achieved

ProductLift brought structure and clarity to Boei's product development, ensuring they built features that mattered most to users.

With 1,600+ votes on 350+ features, Boei is constantly receiving valuable feedback from their users and translating that feedback into shipped improvements.

Key takeaways

If you want to replicate Boei's success, here are the actionable lessons from their experience:

1. Centralize feedback from every channel. Scattered feedback is invisible feedback. Bring all requests into a single feedback board where they can be counted, discussed, and tracked.
2. Let users vote so priorities are evidence-based. Gut feeling is useful, but vote counts provide a clear signal of demand. Learn more in our feature voting best practices guide.
3. Use a prioritization framework consistently. The impact/effort matrix gives you a repeatable way to decide what to build next, balancing user demand with development capacity.
4. Make your roadmap public. A public roadmap reduces "when will you build X?" support tickets and builds trust with your user community.
5. Close the loop every time. Notify voters when their requested feature ships. This single habit turns one-time feedback submitters into long-term engaged users. Read our full guide on building a customer feedback loop.
6. Embed feedback collection inside your product. An in-app widget captures ideas at the moment they occur, dramatically increasing the volume and quality of submissions.

Ready to bring the same structure to your own product development? Follow in Boei's footsteps and give ProductLift a try.