Production is not the only environment where downtime has a financial impact on the company/organization. At any point in the software development life cycle, an engineer that is blocked, or making unplanned fixes is a financial drain. Many organizations struggle with downtime in their integration environments, which can halt development and testing. When environment creation is fully automated, and parameterized correctly, short lived environments can be used for basic integration testing before changes are merged into the main line. In turn you maintain more stable environments for QA, and UAT. This shift lowers the amount of unplanned maintenance and engineer time waiting for integration before moving on to a new task.