[chime]

Quite the opposite. It reduces the BS for me. Seeing 'FDA CFR Part 211' on a software vendor's site tells me they have spent time assessing the needs of my industry and I don't have to start from scratch. Dropbox.com doesn't need to do this. But http://www.mastercontrol.com/out_of_specification/oos_softwa... does. I care about HL7 and HIPAA when working with clients in Healthcare and need IFRS when dealing with accountant firms.

Now a lot of sites do a horrible job at this. Putting a stock photo of a nurse next to a patient does not make me feel any better. But mentioning in 'Healthcare' industry section that your data-logging software can export to a format usable by EPIC EMR makes my day. Or mentioning in the 'Process Manufacturing' industry section that the same software can import data from OHaus Defender scales makes me choose you over your competitors.

To put it simply, breaking down by industry is just organizing the list of features in a different way. If your software can do 1000 things, you don't want to put it all in one page. Listing them by software/technical taxonomy would not be useful either because then I'd have to go over all the categories to find which features apply to my project. Properly organizing them by industry shows me all the key features of the software AND the ones that best relate to my needs.

There is nothing wrong in not catering to specific industries. After all, the software should be flexible enough that anyone from aeronautics to zoology should be able to use it. But specifying that 'yes, it will work for you because X, Y, Z' where X, Y, and Z are regulations, standards, and requirements specific to my own industry, will make it an easy sell for all parties involved. And when you're talking about software starting in 5-figures, you want to make it easy for the tech guys to sell it to the management.

[kiskis]

you need tibco spotfire then:

http://spotfire.tibco.com/en/discover-spotfire/who-uses-spot...