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

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

5 Best Things about the Unified Interface for Microsoft Dynamics 365

The latest version of Microsoft Dynamics 365 moves most of the core functionality of sales and customer service to a new user interface - The Unified Interface client.  This user interface is not completely new as it was gradually introduced for the Hub features such as the Customer Service Hub in recent versions of the product. The new interface is quite different from the previous interface which was used from Dynamics CRM 2013 to 2018 with a few incremental changes.  This is the Unified Interface, using a form from InfoStrat's Grants Manager Plus Solution. Here is the same record shown in the previous interface which Microsoft calls Classic. Here are the top 5 features that I like best about the Unified Interface: Better menus and navigation . The sitemap on the left is more helpful than the classic menus for larger, more complex solution. Lefthand menu shortcuts are a great use of space and help users access the most popular areas.  Better subgrids .  Sub