Skip to main content

Saving Money with Microsoft Dynamics CRM -- the xRM Approach Part 1

We are putting the final touches on a white paper about using Dynamics CRM  to develop line of business solutions (Microsoft calls this xRM), so here is a preview of the highlights.

Budgets are tight for government at all levels, and agencies are forced to do more with less.    This is nearly always true but has become more acute since the 2008 economic slowdown and more recently with failure to pass federal budgets and resolve the federal debt.  

Information Technology (IT) is part of the problem, because government processes are so specialized that commercial software geared to other industries such as manufacturing or retail simply won't cut it for government.    The most common approach for these solutions has been custom software development -- the IT equivalent of tailor-made suits.  

My company InfoStrat has been in the custom development business for 26 years, but about five years ago we found a new alternative that makes sense for many government solutions.   Instead of custom development, we use Microsoft CRM as the baseline for a solution and then use a combination of off-the-shelf features, configuration, customization and integration to make the solution meet government functional requirements.  

One of the biggest drivers of costs in building any complex business application is the requirements analysis phase. This phase documents the business requirements including the data fields to be captured, the presentation of these data elements in forms, the associated workflows, and the reports for the proposed system.

Requirements analysis involves numerous meetings and iterations between the IT staff and the business users as they attempt to document every detail of features needed in the system to meet their information management needs. The task can be daunting because there are many decisions to be made and tradeoffs to consider. It is a major challenge for the end user of the system to envision every minute detail about every possible usage scenario of the new system A custom development approach essentially begins with a blank sheet of paper as the paradigm, and requires features to be defined from the ground up.

The xRM approach starts with pre-built off-the-shelf component parts and tools, so the requirements analysis phase becomes more of a “gap analysis” type of approach where only the missing functionality needs to be identified and described in detail.

The initial step in an xRM project is called the “Fit-Gap” phase which involves reviewing all of the functionality that comes “out of the box” and determining if it fits the business requirements already and, if not, identifying where the gap is, and describing the nature of the work (configuration or customization) that is required.  It is also much easier for customers to envision how the new system will look because they will be looking at Dynamics CRM “out of the box” as the baseline for the purpose of discussing needs and requirements for the new system.

Next -- saving on configuration instead of programming

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…

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…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …