Skip to main content

Dynamics CRM Customizations for Government Contractors

If your business focuses on government contracting, you can tailor Microsoft Dynamics CRM to help you manage your business development efforts.  Out of the box, Dynamics CRM is missing some of the data elements you will need to track opportunities, and the standard business processes will probably not match your requirements.

You may want to consider how you approach marketing and determine whether or not you want to use the Leads entity or purchase mailing lists for marketing purposes.  Our experience is that many traditional marketing approaches do not work well for government customers.  One reason is that government separates the people who need products and services from people who purchase them.

You can populate the Accounts entity with all the agencies and sub-agencies that you sell to.  Be sure to enter the data to reflect the hierarchical nature of government agencies, departments, branches and offices. This data is available from several sources for import if you would like to speed up the process.  You should be sure to enter the purchasing contacts as well as the actual customers for your company.

Opportunities requires the greatest number of additional fields such as contract type, contract vehicle, and provisions for the key dates in the proposal process such as sources sought, request for information, request for proposal, orals, and best and final offer.

If, like most government contractors, you join teams for contract pursuits, but sure to customize Dynamics CRM so that the teaming relationships are accurately reflected.

SharePoint is an excellent tool for managing the proposal documents.  Dynamics CRM has built-in integration with SharePoint, but you may want a more sophisticated approach to create document libraries and assign proposal roles.

InfoStrat's Dynamics CRM solution for government contractors provides these customizations and additional features to streamline the government contract sales process.

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