Pangea Consultants recently penned a deal with a company that was reviewing several ERPs as part of their selection process. This is quite normal, and I would expect any company worth their salt to initiate a request for a proposal. In this blog, I will address the lessons that should be considered in the implementation process and some key takeaways from the competitors’ pricing.
During the implementation process, we asked pertinent questions such as:
As well as a myriad of required questions to a potential client, so you may put together an accurate proposal that makes sense both to our organization and to the clients.
Upon completion of our due diligence/diagnostic stage, we presented our final proposal to said client. The client was none too pleased with the numbers they saw. This client has four legal entities, two of which required full Supply Chain Management, as well as integrations with multiple legacy systems. This was by no means a next, next, your live type of project. We sat down with the CFO and staff to go over our proposal. We first went through the licenses as those tend to be straightforward (or so I thought).
The client required 45 licenses, and we quoted them 45 Microsoft Dynamics 365 Finance & Operations Supply Chain Management licenses with 4 Finance Attach licenses.
The number seemed very high to them; I explained that these licenses are published online for anyone to see. In addition, I mentioned that this includes all the functionality they will require for their organization.
After some back and forth, we identified why the client was completely bowled over on our license costs. They had received a lower cost quote from one of our competitors, a cloud-based ERP that tailor fits the solution to each client. I was completely thrown aback by the pricing structure as well as the approach.
Here were some key takeaways from the competitors‘ pricing:
Once that was resolved, we moved to implementation fees. Ours were admittedly higher. As mentioned, we were implementing two Legal Entities with full Supply Chain Management and two legal entities that are service-based and integrations with the client’s front-end systems. As we reviewed in-depth with the client, we learned that our competitor had quoted only one Legal entity; they did not include Supply Chain Management as part of the quote, only financials. The competitor’s response to not including Supply Chain Management was that the client did not need Supply Chain Management as a phase 1.
As previously stated, this client is a distribution company. Any consulting practice that would state that Supply Chain Management is not critical to a distribution company in phase 1 would be very hard-pressed to explain the reasoning.
Once the client completed a full analysis of both quotes, a decision to move forward with Microsoft Dynamics 365 Finance and Operations implementation was approved by the board.
Our client, as did we, learned some core lessons during this process: