Savio

Understand the features your customers need to be successful

Visit Website
March 24, 2021 We launched a contrarian take on voting boards

After many requests to build public voting boards, we sat down to do it.

But we noticed that since UserVoice launched their first voting board in 2008, they'd rarely changed. 13 years later they look nicer and have a few more features, but it doesn't seem like anybody's actually asked: what's the goal of a voting board?

We realized current products were failing because they bias customers to give feedback that isn't necessarily true. And that causes software teams to waste money and time by building the wrong features.

So we built Savio's voting boards to help customers collect unbiased customer feedback on important feature requests.

They give you less biased feedback vs. existing boards because:

  • You decide which features to collect feedback on (features are private unless you show them on your board)
  • You can choose to hide upvotes (showing upvotes biases users to vote for popular features)
  • You can sort features randomly, alphabetically, or by number of upvotes (sorting by popularity biases users to vote for popular features)

You can read the full take here:
https://www.savio.io/blog/a-contrarian-take-on-voting-boards/

I just sent out our "close the loop" emails to people who requested voting boards, so we'll see how it goes!

2 Comments

  1. 1

    hide upvote counts? interesting.

    1. 2

      Yeah! Herd behaviour means people to do what others are doing instead of using their own information or making independent decisions. Vote counts and sorting by popularity are two features that encourage herd behaviour instead of independent decision making.

      https://www.behavioraleconomics.com/resources/mini-encyclopedia-of-be/herd-behavior/

April 2020 Launched!

Savio helps founders understand what features their customers need to be successful.

After several months of customer discovery and validation, and several more determining what our v1 featureset would be and actually building it, we launched Savio.

Launch meant:

  1. send it to people in discovery who had the pain we solve for
  2. send it to people in our network who might be interested

We got a few paying customers off the bat and then it was off to the races (or rather the long slow SaaS ramp of death...)

Comment

About

At our previous companies, customer feature requests were scattered in our support tool, CRM, email, etc which made it hard to know what features to build. Savio helps you understand what to build next.