Involve your team - and not just those who are computer savvy

[joyuntochandr656]

In fact, deliberately involve those who are not tech savvy. See the bloke who asks how to do a sum in Excel every week? Include him, as he needs to use the system as much as anyone else. Your team will rely on this system for fifty or so hours per week, so include them in the entire process - from requirements gathering to selection.


2. Consider EVERY single requirement suggested
Spend a significant amount of time on your GAP analysis and requirements gathering. No matter how unimportant it might seem, consider every single requirement.


3. But be realistic about them
There is no recruitment CRM that will do everything that you want. Rank your austria phone number list requirements based on Must Have, Nice To Have, and Luxury. Then, disregard all of the Luxury items and most of the Nice To Have items (unless you intended on building the CRM yourself).


4. Spend time sizing the market
I spent a significant amount of time simply identifying then assessing (at a high level) as many potential suppliers in the market as I could.


5. Treble - at least - the amount of time that providers suggest is adequate for migration
No offence to them, but ignore or, at least, treble the length of time that you are quoted for a successful data migration. There will always be issues unless you have significant in-house technical resource available.


6. Make sure you know what infrastructure the system is hosted on
Most of the time, you will go for a SaaS solution. But make sure you know what it is hosted on. Amazon, Azure, Google - check it out and know what the service levels are between the host and the provider.