Skip to main content

GovCon: Tracking Government Subcontracting Opportunities in Dynamics CRM

Whether your company is a large or small government contractor, teaming arrangements are more important than ever.

To be successful in a government bid, you must not only offer the products or services that are sought by an agency, but you must also gain access to the appropriate contract vehicle. Agencies seek to streamline procurement by pre-competing contracts to limit the number of proposals they will receive for a given solicitation.  They also have targets for set-aside contracts for special groups such as minority-, veteran-, and woman-owned companies.  Agencies may choose one or more large system integrators to simplify shopping for tasks later and use them as the clearinghouse for project labor.

The disconnect between contract vehicles and capabilities means that contract holders need to find companies whose skills match the needs of the agency, and companies offering products and services need to form alliances with companies that hold the contract vehicles.

With just a few small Dynamics CRM customizations, you can track subcontracting opportunities along with your sales opportunities as a prime contractor.  For instance:
  1. Add a contract type field to the Opportunity, indicating whether it is a prime or subcontract.
  2. Add a team members entity to CRM, linking between Opportunities and Accounts.  In this entity, show each team member along with their role on the team. 
  3. Modify reports if you would like to differentiate between prime and subcontracts. 
InfoStrat's solution Dynamics CRM for Government Contractors includes these customizations, and offers a feature complete basis for automating your unique GovCon business processes.

For more posts on government contracting, see:









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

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

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