Skip to main content

Estimating the Cost of a Dynamics CRM Implementation: Part 3 -- Customizations

In the last installment of our saga, we looked at the Microsoft licensing cost for a Dynamics CRM solution.    Now let's take a look at the cost of customizations and software development.  This is significantly more complex than deriving the licensing costs, and is derived based on functional requirements for the specific solution.

The least expensive solutions usually are for the most common CRM scenarios, such as sales force automation, customer service, and marketing (or outreach).   These scenarios match the out-of-the-box functionality of Dynamics CRM well to begin with.   You are likely to require some additional data elements and reports, and nearly certain to need some workflows to match your business processes, but will not need too many new fields or entities.

The most expensive xRM solutions are those that do not match the out-of-the-box entities, forms and reports, and which require integration with other systems.   At the extreme end of customization, the cost will approach that of pure custom development.

Here are some of the key items to count and characterize:

1. Identify all the data elements you need to track, and map them to the Dynamics CRM data model.   This exercise will show which attributes you need to add to existing entities and which new custom entities you will need to create.

2. Examine the user interface and determine whether you need customizations to the look and feel.   If you want distinct forms for each user role, for instance, the cost of the implementation (and subsequent maintenance) will increase.

3.  Enumerate and specify all the reports you will need.    Try to categorize them by complexity to simplify estimation.     We usually break them into simple (lists), moderate (some aggregation) and complex (multi-entity and more complicated calculations). Every Dynamics CRM implementation we have done requires some custom reports.   Be sure to take a look at Advanced Find to see if it can satisfy any of your reporting requirements.

4.  Determine which dashboards you will need.    Dashboards combine business graphs with views into records.    Dynamics CRM comes with standard dashboards for sales, marketing and customer service, but these may not make sense for xRM solutions. 

5. Specify the workflows that will be created.  Again, categorize them into groups based on the complexity of the workflows.    If your workflow has a large number of exceptions you may want to reconsider whether it should be automated at all.

Armed with these lists and specifications, you can approach a Dynamics CRM expert and get a realistic idea of the cost.  If you are familiar with Dynamics CRM yourself, you can use these metrics to create your own estimate.   For instance, you may want to plan four hours for a simple report and twenty hours to create a complex report.

See our Dynamics CRM implementation cost calculator

Popular posts from this blog

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Microsoft Dynamics 365 for Community Business Development

Local governments agencies such as the Office of the Deputy Mayor for Planning and Economic Development in my hometown of Washington, DC, - work on behalf of residents to improve living conditions, create economic opportunities and jobs by attracting businesses and helping businesses thrive. A customer relationship management system is key to work in community business development.  If you are a Microsoft customer, which apps in Dynamics 365 should you use for business development?
Core functions - All the Dynamics 365 modules track accounts (companies) and contacts (individuals) as well as activities such as phone calls, emails, letters, and meetings. Sales - Dynamics 365 for Sales provides the ability to track opportunities to attract startup businesses or businesses that are relocating from another area. Sales includes functions for qualify opportunities and working through all the steps in your workflow through a successful win.  You can ascribe dollars to opportunities as well as…

Key Concepts for Microsoft Dynamics 365: Entities and Attributes

To understand Microsoft Dynamics 365 (formerly Dynamics CRM and Dynamics 365 Customer Engagement), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This is the second post in a series, and covers entities and attributes.

Entities are the most fundamental part of Dynamics 365 in terms of storing your business data.  They are similar in concept to database tables, and the relate to one another like tables in a relational database. For instance, Dynamics 365 has an entity called Contacts that stores data such as name, address, and email address of people that you track.   Accounts is a related entity that describes the organizations to which Contacts may belong.

Although they are similar to database tables, Dynamics entities allow you to do some customizations that are not possible in a standard database table.  Field labels, for instance, are part of an entity, and they may differ from …