“We’re going to use the system out of the box to the greatest extent possible.” Awesome. Do this.
“We’re going to minimize coding and customization.” Also great. Do this.
“We’re going to take customization [x] out of scope and use a workaround to conserve budget.” Take caution. Yellow light at the crossing.
Are Workarounds the lurking hidden costs in your ERP? Now I’m certainly not saying you shouldn’t ever take some customizations out of scope. It’s often prudent to do so. But all too often I’ve had clients fall into the trap of not understanding the workaround and finding that it ended up costing more than the original customization itself. Want a nice little example? One cautionary tale I’ve seen play out time and time again is commissions – it’s a classic. If your business doesn’t use commissions, keep reading. You’ll still get the allegory, I promise.
Early on in a project, perhaps even during the sales process, we talk with clients about their options for commissions. You can either use Dynamics 365 for Finance and Operations out of the box for commissions, you can purchase an ISV solution to add on to the functionality or you can customize the functionality to make it work exactly how you want. Let’s say we’re talking about a manufacturer who has relatively simple commissions requirements. They pay a flat percentage of invoiced dollars when an invoice is fully paid. And that’s where the requirement gap is. D365 for Finance and Operations can’t do “pay when paid” commissions out of the box.
ISVs & Customization
So then we talk about ISVs and we talk about customization. For fun, let’s just say the ISV is $20K and the customization is $10K. And the client says “I don’t want to spend the money for this when I can just do it in a spreadsheet”. The client has done the easy math that says if it takes the assistant controller an hour a month to do the spreadsheet, that’s only 12 hours a year which would take about 3 years to surpass the cost of the customization and even more for the ISV. But there’s one key missing piece.
The workaround. The slippery slope. Call it what you will, it’s where the costs hide. The workaround in our commissions example is getting the data out of the system. D365 has some really great ways to get data out of the system. But you still need to understand how to configure the system and perform the extractions. What’s key about this example is that you need data from multiple sources in D365. You need sales order invoices to tell you what was invoiced. You need customer payments to understand what was paid, settlement information to understand how much of each invoice has been paid and when, product category so you can apply the right commission percentages, etc, etc.
The workaround has now turned into at least four data extractions that need to be configured and a spreadsheet that ties all the data together. Then it gets slipperier when we start asking questions like “what if someone invoices something in a past period because the controller reopened the fiscal period?” or “what if I need to make a retroactive change to someone’s commissions?” Not only do the client’s internal labor costs start to rise to handle commissions outside the system but the truly hidden cost emerges – the cost of consulting hours to help the client deal with all these questions and reconfigure the system to address them. The ROI of the customization has just shifted.
Is it a good idea?
Surely the moral of the story has emerged here. Does it seem like a good idea to take known customizations out of scope if they don’t measure up to the “secret sauce of the business” rule? Sure. Is it always a cost-effective move? Not necessarily. Is this something specific to Dynamics 365 or other specific software solutions? Nope – chalk it up to life in ERP. Happy scoping!