Perhaps it is also worth rephrasing it as "a burning problem for the buyer", which might most likely be a stupid unscrupulous solution that doesn't make sense like those sensors they have in hotels to detect employee whereabouts. Stupid and completely useless, but still "a burning problem" for hotel managers.
First thing should not be finding out what what your customers want.
First thing should be finding out IF THERE EVEN ARE CUSTOMERS for your product.
A product idea that doesn't have any market won't be successful. So find out if there are people who have a problem that can be solved, then try to solve that problem. Additionally the problem has to be annoying enough so people are willing to pay to make it go away. If you have those two, it's a great start.
All the enterprise features like SSO, integrations, audit trails, etc can be built when a customer is asking for them — these are largely solved problems. These are probably attractive problems because they are engineering problems and you are an engineer.
Ignore them and focus on the business problem. “Does my app solve a burning need for my customers?”. Read “The Mom Test” to get in the mindset of answering that question. That is all that matters right now.