Skip to main content

Essential Dynamics CRM Customizations for Government Contractors

Microsoft Dynamics CRM offers a rich set of features and a data model for sales force automation and marketing activities.  Each industry (and each company) requires some configuration changes in order to make it work according to their business processes.

For government contractors, here are some of the most common customizations:
  1. Change the focus from individuals to organizations.  You are likely selling to agencies (accounts) rather than consumers (contacts).  Add the relevant fields to forms and views.  For instance, marketing list members doesn’t show the account name by default. 
  2. Define the sales process in opportunities.  Define all the steps that an opportunity goes through before becoming a contract, such as sources sought, request for information (RFI), request for proposal (RFP), down-select, orals, best and final offer, and verbal approvals.  Be sure to allow for all your proposal review steps. 
  3. Add fields to track contract vehicles and types of competition.
  4. Add your own metrics. For instance, we often track how many users a software system will have in order to calculate license costs.
  5. Update reference table values if needed, such as the reason for an opportunity loss.  Do you want to add an option to show you decided not to bid?
  6. Update dashboards to show what you really care about.  Win ratios?  Proposal activity?
  7. Decide how to add the documents which accompany an opportunity, such as solicitations, amendments and proposals.  You could store them in SharePoint, in attachments to Dynamics CRM or in other repositories.
  8. Add your bid team to the opportunity, showing the roles for each person in the proposal.
  9. Allow for teaming if you pursue contracts as a subcontractor or if you hire subcontractors.
  10. Decide how to use the Leads entity.  Do you want to start there for the sake of email marketing campaigns?  Do you prefer to build out the list of targeted accounts and contacts instead?
InfoStrat has put all these customizations and many more in its solution Dynamics CRM for Government Contractors. 

Popular posts from this blog

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

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

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises