As an application matures past the initial development stage, it’s inevitable that maintenance will be required to maintain the required functionality.

Much like your house, your obligations are not complete the second you pay off your mortgage. You need to maintain the asset in order to get the best value from it. Just as you mow your grass, pay insurance, property taxes, and service your appliances, the same is required of your software applications.

To ensure continuous benefit for your users, maintenance is paramount. At Broadway Lab, we have a philosophy on maintenance that allows us to create well-crafted applications and minimize downtime for our customers.

Maintenance is being there if something breaks. Maintenance is continuously improving the product through automated testing, refactoring, architecture review, documentation and many other strategies that add value to your software project long-term.


While we have clear support timelines based on SLAs, our goal is to continuously develop your software to prevent any urgent matters from causing downtime.

This illustration outlines the investment in development of a software application vs. the required maintenance.

Maintenance Graph

Minimum Maintenance
Agreement (MMA)

Corrective Maintenance

Amazon S3 is a cloud computing web service offered by Amazon Web Services. Amazon S3 provides object storage through web services interfaces.

Adaptive Maintenance

Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment.

Perfective Maintenance

which typically results from user feedback, is modification of a software product after delivery to improve performance or maintainability.

Preventative Maintenance

Modification of a software product after delivery to detect and correct potential faults in the software product before they take effect.