How are you getting feedback, though? Do you have people using your software but are not paying? If you have users, what are the analytics telling you? >One of

How are you getting feedback, though? Do you have people using your software but are not paying? If you have users, what are the analytics telling you? >One of these potentials mentioned after a demo that they would pay me $100 per month per user if I could offer a bunch of additional features Why are they asking for those features? What problems do they have that these features would solve? What are they doing right now to solve those problems? When was the last time they dealt with those problems and how did they deal with them? Dig deeper. A customer requesting a feature is like a patient telling their physician what drug to prescribe. A physician wouldn't just comply; they'd dig deeper to find the root cause of the symptom the patient is trying to fix. In other words, a feature request is an "owie", and it's up to you to figure out what caused that, and how to fix it. Many times, there are false problems. They'll request a feature and when you dig deeper, the problem is something else (see XY problem: https://en.wikipedia.org/wiki/XY_problem https://en.wikipedia.org/wiki/XY_problem) >(I had most of these in backlog) How are you filling up that backlog? What's going in, and why is it going in? One has to be very careful with product road-maps. What's the impact of that feature/bug fix? You'll have ideas for all kinds of features, but you'll have to prioritize them somewhat and sort them. What's your prioritization algorithm? What makes that you're implement X feature before Y? Again, be careful about that.