Skip to main content

Estimating the Cost of Dynamics CRM Implementations: Part 7 -- Support

This week we examine alternatives and costs for supporting your Dynamics CRM (xRM) implementation. In the long run, it is not unusual for the support to end up costing more than the implementation itself, but cutting corners on support can put user satisfaction and adoption at risk.

The first step is to determine what support arrangement you have with Microsoft?   Who is authorized to create Microsoft support incidents?   Does your organization have assigned Microsoft technical support managers? Microsoft can help with product questions and issues that arise from software updates.   In most cases, they will not be familiar with your specific implementation. 

Next, do you have a help desk or do you need to hire an outside company to provide help desk services?   Do you need coverage during business hours or 24 hours x 7 days a week?  Will your users call your help desk to report their initial issue?

How will you handle enhancements to your solution? Do you intend to publish new versions on a periodic basis?   At what interval (weekly, monthly, quarterly or other)?  If so, how large a team is required for these iterations?   Will the team that did your implementation be available?

For how long a period do you want to budget?  You can expect the level of enhancements to drop after the first year unless new business requirements are introduced.

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

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), 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 post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun