Quantifying the cost of fixing vs preventing bugs
When you think about improving software quality, your first thoughts might be the cost of new tools and engineering labour to implement them, as well as the impact of 'slowing down' the development cycle by adding new processes.
But really, you need to first think about the current cost to your organization to find and fix bugs over the product life cycle. Beyond these direct costs, have you considered the opportunity cost associated with missed release dates, or the good will that is lost from unhappy customers, or product recalls?