If you do not know Dynamics CRM and yet you get applications and .NET here are some things to think about.
If you are looking at a project consider these two big picture questions.
1) Does the project require the need to track any type of relationships?
If yes then the CRM Framework is definitely something to consider. These relationships can include relationships between two people, relationships between companies, relationships between a person and a company, relationships between things, relationships between animals, relationships between parts and a final product, relationships between things and people, and more.
2) Does the project require the need to automate and/or document process?
If yes then the CRM Framework is definitely something to consider. These automated processes can include standardizing the steps that need to happen to get a project done. Scheduling and completing specific steps, historical reference to the completed steps, the application of specific steps to specific people. The tracking of specific steps associated with a specific person. The automation of alerts and notices and more.
Additionally there is another core reason why including CRM as part of your development might make a lot of sense. This core reason is that built within the Dynamics CRM framework is a multi-layered configurable security system that helps you control who can do and who can access what and pre-built authentication options. Items you do not have to write. You also have the long term upgrade and update support from a maturing product, the development control and the CRM SDK. AND .. the added features that you might not have time to write such as duplicate checking, User Friendly Reporting, Integration to MS Office and layers of data import options.