Have you ever thought about how wrong the Project Management Triangle is for software development?
The idea of balancing cost vs speed vs quality might work for projects or services you only do once, but software is not like that.
You will have to maintain your software for decades. If you at any point start treating quality as negotiable you will not pay only in that moment, but you will live with a quality debt for excruciatingly long time, and that quality debt is paid with a crushingly high interest generally bundled with the term of technical debt. If you deviate from the built-in quality mantra your software quickly become tangled and become both time-consuming and costly to maintain.
Poor quality software is never an option. Take your time doing quality assurance right.
You'll save a lot of money in the long run.
And less headaches and worries.
And future development speed.
And agility.