I'm pretty sure this implementation gap is done partly for a good reason and partly for a bad reason. The good reason is even within an individual industry eac

I'm pretty sure this implementation gap is done partly for a good reason and partly for a bad reason. The good reason is even within an individual industry each company is different enough that the software needs to be extremely customizable or there will be too much adoption pain required. I don't think opinionated does it when you would need to enforce change across large swathes of people. I have seen this tried and be an expensive failure across more than one organization where malicious compliance basically killed multimillion-dollar rollouts of this kind because people simply weren't prepared to change their workflows. I've seen the CTO of a very large organization first instruct, then ask, then plead, then beg for people to adopt the CRM that had been installed at great cost all to no avail. The bad reason is that lots of big software companies (but definitely CRM people like Salesforce) rely on big consultancy firms to sell their product. Consultancy do that because they "don't sell software, they sell solutions", meaning they come in and do the implementation etc. They wouldn't do this if they didn't get the sweet sweet billable hours, so your software better be customizable up the wazoo for them to be interested in being your sales army. And then piled on top of that, salesforce have created an ecosystem of developers who do the customization. So if you're a small bank, you might want ncino to do your loan workflows etc. That means Ncino are selling salesforce everytime they sell their product etc.