There are only three variables that need to be understood before a software implementation project is started:
These three variables have to be prioritised. Each impacts on the other. If, for example, you have a vital need for functionality that is specific to your business, then the time it will take to implement your system will be longer than a standard NAV implementation and the cost will be higher. If you must have your system implemented in a short time frame then you will have to forgo additional functionality that cannot be developed within the time available. If limiting the cost is your priority then a rapid implementation of a standard system might be the most appropriate option; once again any thoughts of additional functionality may need to be abandoned.
When Fenwick is helping a client to plan a system we get the stakeholders together and ask them to rank these three variables, one through three. Often animated discussion follows, but once we explain the logic and the reasons why these priorities have to be clear, agreed and signed off, then the client is able to sort out what is really important to them and establish a plan that will ensure a smooth implementation. Misunderstandings are minimised; expectations will be realistic; and the project risk will be considerably reduced.
Sadly, it is just not possible to have unlimited functionality, delivered in very little time, at very little cost.