3 ms·
>You can spend countless hours making improvements but without a user base, you have no idea if they are needed or wanted. This is on the right track and I wou
by draker 11y ago
>You can spend countless hours making improvements but without a user base, you have no idea if they are needed or wanted.
This is on the right track and I would say that the improvements, iterations and additons to the product should be focused towards the revenue generating users.
It can be difficult to identify this segment, but it is worth the time to do so. Every user will have suggestions for improvement but if the person never intends to pay for the product or only requires the free features then you are wasting your time improving the product for them. This doesn't mean you should ignore the non-paying users, rather you should listen primarily to their suggestions for what the product requires for them to be a paying customer. If you find that a large number of non-paying users would convert to paid if you had X feature; determine the cost and potential revenue of adding the feature.