In my opinion its just not practical for most programmers to understand a book like "The science of programming" and consciously apply proofs each time they write code. Most programs can be delivered with bugs, These can be discovered and corrected over time. So having strong QA teams as an alternative to proofs should be the reason of having and abundance of reliable software.
Thanks davismwfl, what we do at forestpin is to help companies find mistakes and fraud in transactions, the customers who use the product really like it. How ever some of the discussion goes on and on. The longest sale took 2 years from the first meeting and the shortest sale was about three months. We pitch to the finance director of the company. In its pretty hard to find the correct influencer in the company since no body in a company is responsible for collective mistakes. Lot of companies have no insight to the cost of transactional mistakes they make. We got customers after doing proof of concept projects successfully. These take time, since once a POC is agreed, we need to depend on different teams to get data and the associated time lags. I had a one on one session with a YC partner (SUS online) and he recommended the book "Impossible to Inevitable" I am going thru the book these days its pretty helpful. Thanks again on your helpful insights. Hope you and your loved ones stay safe from COVID19