It's a very HN view of "companies" that one can simply "Talk to the CFO ... CEO, VP/sales, etc.".
Or the view of a highly motivated person. Take your pick.
On the other hand, if you're not in a position to go and talk to decision makers about your product, it's worth asking whether you're the right person to be building that product.
I agree to some extent that if problem itself is not noteworthy for them, it is good problem to solve for them? However in many cases people who are going to benefit directly are different from decision makers. So would it be better to talk to people who's life is going to get easier first and then ask them to redirect to decision maker?
With good reason - those people are accessible if you go about things the right way. In this particular case I don't you'd get very far because "What problems do you have?" is far too open a question. If you ask something specific and you make it straightforward to reply then you'll often get something back.
Would they be willing to spare their precious time to talk for some time? They might not be directly aware of gravity of problem if people who face it directly are engineers, PM's. In that case, would it be wise to ask them to point to correct person to talk to?
In this case start with the employee who sees the issue daily. If it's a real pain and your solution is good it will move up the chain of command
Problems related to data science mostly. Developers, Product Managers, Marketing departments are going to benefit from this. What do you suggest should I talk to people who are decision makers or someone who is going to benefit from it directly?
Could you explain problems related to data science?