The term quantitative refers to a type of information based in quantities or else quantifiable data (objective properties) —as opposed to qualitative information which deals with apparent qualities (subjective properties)
Fear, uncertainty, and doubt (FUD) is a tactic of rhetoric and fallacy used in sales, marketing, public relations, politics and propaganda. FUD is generally a strategic attempt to influence public perception by disseminating negative and dubious/false information designed to undermine the credibility of their beliefs.
Top 5 FUD Tactics in Software and what you can say to end user to retain credibility
1) That software lacks reliable support- our support team has won top prizes in Customer Appreciation for past several years.
- Our software release history-
- graph of bugs filed-
- turn around time box plot for customer service issues
- quantitatively define reliability
2) We give the best value to customers. Customer Big A got huge huge % savings thanks to our software.
- Pricing- Transparent – and fixed. For volume discounts mention slabs.
- Cost to Customer- Include time and cost estimates for training and installation
- Graphs of average ROIC (return on capital invested) on TCO (total cost of ownership) not half a dozen outlier case studies. Mention Expected % return
3) We have invested a lot of money in our Research and Development. We continue to spend a lotto of money on R &D
- Average Salary of R and D employee versus Average Tenure (Linkedin gives the second metric quite easily)
- Mention Tax benefits and Accounting treatment of R&D expenses
- Give a breakdown- how much went to research and how much went to legacy application support
- Mention open source projects openly
- Mention community source projects separately
4) Software B got sued. Intellectual property rights (sniff)
- Mention pending cases with your legal team
- Mention anti trust concerns for potential acquisitions
- Mention links to your patent portfolio (or even to US PTO with query ?=your corporate name )
5) We have a 99.8% renewal rate.
- Mention vendor lock in concerns and flexibility
- Mention What-If scenarios if there are delays in software implementation
- Mention methodology in calculating return on investment.
- Google Shows It Can Sling The FUD (lockergnome.com)
- Anatomy of a Flawed Clojure vs. Scala LOC Comparison (codemonkeyism.com)
- Jenkins: WikiLeaks and the Cloud Wars (online.wsj.com)
- It’s Not About Linux on the ‘Desktop’ (techrights.org)