Skip to main content

Estimating the Cost of Dynamics CRM Implementations: Part 4 -- Integration

If you have been following this series, part four takes us from the relatively clear formulae of software licensing and the function-driven, gap analysis of customization, into the wilds of software integration.   The cost of integration cannot be derived from the number of users or even the complexity of the xRM solution.  It can only be determined with a thorough understanding of the systems to be integrated and the nature of the integration that is required.

We often encounter implementation solicitations that include integration requirements.  Usually, there is a line in the long list of requirements that says something like "integrate with our accounting, timesheets, federal systems, etc." We always say that the price of an unspecified feature cannot be specified.  In order words, without a detailed definition of how two systems will be integrated, an estimate of scope is useless. That little et cetera often found in requirements is of course the worst three letters you could include in a fixed price RFP.

When forced to bid on integration without specifications, conservative companies will bid high to cover the risk inherent in the ambiguity.   More aggressive companies will bid low and place a bet on a combination of optimism and use of change orders once the deal is done.

Here are some of the details that can help derive a better estimate for integration:

  1. Provide documentation for the systems to be integrated, including the data models and options for integration such as web services.
  2. Define functional requirements for the integration.   Spell out how the scenario would work, where the data would be entered, how it is processed in each system, and where it ends up.
  3. Choose the direction of the integration (one-way or two-way).   Which is the authoritative system in the event of a conflict?
  4. Spell out any tools that you would prefer for data integration.   Do you own middleware or enterprise application integration software that would help.

If you are starting from scratch with an xRM application, you may want to hold off on including the integration requirements if they are subject to change based on how the xRM solution itself is developed.    You may even save money by having one vendor implement the solution and another perform the integration.

Dynamics CRM provides a modern, web services interface to allow integration.    You may want to assign the integration task to developers who are proficient in the other system with which you are integrating, especially if it uses a less open and modern architecture.

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 PowerApps Portal and shifted to the PowerApps 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. for 100 dail…

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.  Subgrids are important for en…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…