Not necessarily. Convincing people to fit their workflow into your new software, effectively running their companies around it, is not as easy as it sounds. Coding it is not the hard part.
Truer words have never been said. Selling your vision/workflow/business structure/data presentation is the hard part. Many of the things one may code as a solution will directly and negatively effect the job security of the exact person your are selling to, but that is the challenge. The secondary effect is a chilling of innovation by limiting the automation gains/improvements in some way to limit the impact of value depreciation of current workers.
I ran into a client where they preferred their home-grown Perl script to our million-dollar solution because grep searches faster than we do, even though we have literally a billion more features.
It's not just a challenge with your startup trying to get name recognition. It's a challenge for the major players, too. Inertia is hard to overcome.
Did they need any of those features, or did they need to search?