Here is an entertaining snippet from twitter:
Ben Hall asked
Wonder how TypeMock came up with the "Cut costs by as much as 40%" (twitter)
Daniel Fernandes answered:
TypeMock.Expect(x => x.GetMinimumCostSaving()).Return(.4) (twitter)
For those that want the real answer.
We do case studies from our customers and we measure the cost of development (including QA) before using Typemock and unit testing and after. We have witnessed many customers that once they start unit testing and getting up to speed with automating their code tests (I call this code integrity), the time to find and fix bugs is much shorter. Our customers have seen long QA process, that take both QA and developers time fall to 0 (yes zero.) thus saving 40% of their development costs!