Launch your own profitable B2B SaaS for less than $750 – https://nxtstep.io/b2bsaas
Hey folks, Sean here and today what I wanna talk to you about is want to start doing with the feedback once you start getting it. Now that usage is ramping for your B2B SaaS. So I’ve incorporated a couple different ways to capture feedback, and if you haven’t done this yet, but you haven’t active SaaS application with users actively engaging with it, you need to add a few.
That way you can start getting feedback asynchronously from their usage, good, bad, and otherwise, which will inform what you might do with the product next. Two tools that I have incorporated, both of which have been helpful and are relatively low cost or no cost, depending on how much you use them, is Hot Jar and talk Talk as in T A W K talk is a chat tool, so that’ll enable folks to engage with any of your support or send you notifications if support is unavailable.
That tool is free and also has a mobile component so you can get notifications, your phone if you’re out and about, which is also convenient. And then Hot Jar is an analytics tool which incorporates a bunch of different pieces of feedback, which I all find very helpful. It has screen recordings. It has heat maps.
Get our awesome product content delivered daily-ish to your inbox
It also has the ability to capture survey responses as well also. So I’ve configured both of those for my podcasting tool, and I’m starting to get feedback, starting to get good feedback. Something I’ve been getting more recently is related to how the tool works and what users might like to see, instead of how it works by default at the moment.
So they’re looking for some advanced options. Now, one of the things that I’ll caution you with here is, As you’re starting to collect feedback, don’t necessarily feel the need to incorporate every little feature exactly how it’s requested from everyone that’s submitted feedback. Instead, I would recommend engaging with them if they’ve given you the permission to do so, to get a little bit more clarity in how whatever they’re requesting, essentially they would like it to work best, and that’s number one.
The second important element here is to. Make sure that you are building around the patterns of what’s being requested, as in one user may want to take the product in the left direction, and another user may wanna take the product in the right direction. Your objective is to try to find that middle ground between all of the feedback that you’re getting, which gives everyone progress, as in it might not be specifically exactly what everyone individually asked for, but.
If you try to build specifically in one direction for one user, you might build the product away from the direction of what some of the other users are requesting. So you want to make sure that you avoid that. Anything that you’re adding to your product experience, you want to try to do so, so that the maximum number of your users get additional value out of it.
That’s a good way to build a, as I call it, a data-driven product roadmap for the future direction in which you wanna drive your product.