Quality of feedback depends on quality of your beta users

When you've gotten your first beta users, it's tempting to say yes to all feature requests in the hopes they'll become paying customers. Not all users are created equal though.

For example, let's say you've built an MVP for a Customer Support SaaS. Customers can create support tickets through a feedback form or talk to someone live through a chat widget. The majority of your signups may read your landing page, understand it's a customer support tool and sign up with that correct mental schema in mind. Other customers however may read about your chat widget feature and sign up to use it to convert sales on their landing page. Now you have users that are pushing your product in the direction of a customer support tool and other users pulling it in the direction of a CRM tool. Listening to both these customer segments results in building a Frankenstein product with a confusing feature set and confusing positioning, which will hinder conversions rather than help.

It's important to have a direction in mind for your product and an Ideal Customer Profile that aligns with that direction. Not only does this customer profile help you build features that your customers want but it also helps you filter out the customers you don't want.

P.S. If you want to start capturing your own feedback, I've built a little thing that might help you out.