Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I approach this question slightly differently, and I guess this only works while your product is small enough. I develop and sell a desktop app and I try to build as much relationship with my users as possible, and then ask them for feedback.

- I have installed a chat popup on my landing page and I always try to answer any question within 1 hour, and then follow up with those users afterward.

- I have a feedback portal (similar to canny). Whenever anyone leaves any kind of feedback, I write them a thank you email and try to elaborate more on the feedback they left, no matter if this is negative, positive feedback or feature request. For example, if they ask for a feature, I tell them when I plan to develop it.

- Whenever user purchases a license for my app, I also write them a thank you email, and ask for a small feedback. I try to do a short investigation on what user is doing and include some personal touch in it. Usually, 50% of such emails get an answer.

- If I see some bug report coming from a known user I immediately send them an email explaining why that bug has happened, how and when I'm gonna fix it.

I also keep a page in my notes called 'Followups' where I put the user's name and the reason why I should follow up with them. For example next week I'm preparing a new release of the app that has changes which I know are used heavily by a couple of users and I will reach out to them this week, give them an alpha build and ask for their feedback. Whenever I get an idea of how I can bring someone's attention to the product, I add their name to this list.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: