A truly well crafted app requires very little maintenance or support, and that maintenance/support has already been throught through and made easy to learn and

A truly well crafted app requires very little maintenance or support, and that maintenance/support has already been throught through and made easy to learn and do. These things are possible, and they fit economically somewhere in the 3-5 year maturity of a system. Years 1-3 are usually necessarily focused on features and releases, but far too many orgs just stop at that point and aren't willing to invest that extra year or two in work that will save time and money for many years to follow. I believe this resistance is due to the short-sightedness of buyouts/IPOs or simply leadership churn.