Having a CRM database in your CRM applications suite is integral to proper customer relationship management so much so that the relationship between a CRM database and CRM applications is like love and marriage. You cannot have a CRM system without a CRM database it just does not make sense because CRM is about sharing information about the same set of customers. Without the ability to share the CRM database content and without your fellow users, all you have is a set of code but that does not make it a CRM application code.
Nowadays, your CRM database is part of the CRM software you chose for your organization. To access your CRM database, the developer should create a simple user interface that is easy for multiple users to learn. This does not mean your layout is a plain Jane layout rather, you should strive for a pleasant looking layout design that will not detract from the need for functionality and reliable access. In short, you should make sure your multiple users are not confused as to how best to use your system.
Some developers think that if they try to sub-categorize a lot that this results in a good functional system. Actually, you may wind up losing CRM customers that way because many non-techie CRM folk do not want to have to adjust to a very complicated system. This shows that there are actually two routes to CRM software development either the customer adjusts to the software developer or the customer is the one the software will adjust to.