How we are reducing churn by allowing users to vote on features
Tags: showdev, design, webdev
Published: 2020-06-14 07:01:20

---
title: How we are reducing churn by allowing users to vote on features
published: true
description: We were basically trying to solve — “What feature should we build next for our product that would work well with users?”
tags: showdev, design, webdev
cover_image: https://hellonext.co/uploads/hn-blog-feature-voting-tool.jpg
---
_This post was originally written for [Hellonext.co ↗](https://hellonext.co/blog/why-allow-your-users-to-vote-on-features?utm_source=devto&utm_campaign=article_link_whyvote&utm_medium=social)_

We love it when our users grow with our product. Reducing churn and improving the revenue are two big growth factors for any SaaS product. In this post, let us tell you why we saw value in building feature voting tool, and what value it has added to our users.

We were basically trying to solve — _“What feature should we build next for our product that would work well with users?”_

## Why use a feature voting software?

No matter the stage of growth you are in with your SaaS product, you need to have way of managing feedback from your customers.

If you are small business like us, you would receive feature requests, feedback, and other suggestions from your users from various channels like email, Twitter, so on and so forth.

This was very chaotic for us, and we quickly realized the value of “[organized customer feedback](https://hellonext.co?utm_source=devto&utm_campaign=article_link_whyvote&utm_medium=social)” system.

## How to manage new feature requests

Organizing feedback is simpler than what it used to be earlier, where we relied on Google forms, or some other contact form submission methods.

You need a tool that can **help you bring all your users together**, avoid duplicate feedback, know what are the most requested features and to keep all your users updated about the progress you are making to reduce churn.

So we went ahead and invested in building a product that would solve just this problem for us — feature upvote tool for users.

## What solves it: Feature upvoting tool

When you show your users what you are up to next, they automatically tend to give you their feedback. Putting your work out there to all the users of our product made is easy for us to measure how users were responding to new features we were building.

Above all, with “[feature voting](https://hellonext.co?utm_source=devto&utm_campaign=article_link_whyvote&utm_medium=social)”, **users can vote on feedback** that others have submitted earlier. Or submit a new feature that others can upvote to push it up the development cycle for us.

![Hellonext feature voting app for feedback](https://hellonext.co/uploads/hn-white.jpg "Hellonext feature voting app")

This saved both users time and our time, since they voted on features quickly, or submitted a new one. The feature upvote tool also **set the expectations straight** for the users about what they can expect next from us.

**Pro tip:** When choosing a user voting tool for your product, make sure it is [well designed for your users](https://hellonext.co/blog/design-principles?utm_source=devto&utm_campaign=article_link_whyvote&utm_medium=social) to provide feedback. After all, they should find it easy to use.

## Data backed feature building

Since our users voted on new features that they wanted us to build, it was easy for us to prioritize what we need to build next.

Also, we knew what would add value to the users, and how many would get a direct impact from this new feature when released.

## How has feature voting helped us

Allowing our users to vote on new or existing features made us realize that users are starting to trust us more that we would do what they are expecting.

Simply put, users tend to wait it out for the next feature to come, before they completely make a jump to another product.

Users, when they [vote on features](https://app.hellonext.co/users/sign_up), become a part of the product building process. This has created a sense of community, where us and our users live in the same reality. **_They see what we see_**.

No product has ever failed because of their community. They have only grown exponentially.

## What benefit did our users get out of feature voting

The benefits our users got were measurable and straightforward:

- Customer happiness improved
- Users knew what was coming next for them for the money they paid
- Every upvote was a strong communication to us that we need to care about them
- Users were kept in the know about the progress we were making for the feature they supported

## Impact was real & visible

The formula for us became simpler after our users started voting on features:

**Number of happy customers = less churn = more revenue**

\#EveryVoteCounts