A previous employer had an application that was very successful (from a business perspective) because it <i>wasn&#x27;t</i> flexible - they did a lot of acquisitions (one a month at one stage) and if there were any questions around their internal systems they got this application inflicted on them. At first I was horrified (it was ancient, user hostile, completely inflexible) but I actually saw that it worked - the companies being acquired were all in the same industry and their core processes were all pretty much identical (even if the terminology was all different) - so they could all adapt to the new application and it actually ended up working pretty well.<p>More &quot;modern&quot; flexible applications ended up having multi-month&#x2F;multi-year &quot;implementation&quot; phases as teams tried to change their new application to their existing processes when it was actually easier to standardise the processes around a fixed application.