Skip to main content

6 Simple CRM Tips for Small Government Contractors

My company InfoStrat works with government contractors to automate their capture management (sales) processes.  All government contractors strive to master GovCon capture processes to improve the sales results.

Large government contractors typically have mature and complicated processes which have many actors and steps.  Often they follow a sales process pioneered by Shipley Associates which helps companies win a higher number of bids through a more systematic business process and higher quality proposals.



What about small companies, or companies that are just getting started in government contracting?  Do they benefit from structured processes and sales force automation? How should their CRM system be different from a large company?

Here are some tips to get you started:

  1. Read everything you can find on government contracting.  You will learn from the extensive literature on the subject.  Many books on government sales are available on Amazon and in libraries. 
  2. Come up with a simple capture process and refine it based on your experience.  Include approval workflows and review processes during the proposal preparation phase. It may be as simple as four or five steps based on pre-solicitation stages and the status of a solicitation (RFI, RFP, etc.). 
  3. Track every opportunity in your CRM.  Use the CRM as the basis for pipeline review meetings, and insist on entering every opportunity in the system in order to chase it. Salesforce and Microsoft Dynamics CRM are the most popular cloud-based CRM systems for small businesses. 
  4. Ask stakeholders for their input.  Your CRM cannot succeed without adoption, and all your users will have valuable input on how the system should work.  Don't track information that people do not find useful or are unwilling or unable to enter. 
  5. Start with a template.   It's difficult to get user input from a blank sheet of paper, so a pre-built solution for government contractors can help people focus better. InfoStrat offers a GovCon solution template and a quick start implementation to go with it. 
  6. Walk before you run. Start with a core group of users in sales and senior management and add other groups later.  Be sure to build in a process to learn from your experience and improve your CRM over time.
Most large companies started as small companies, so you can learn from the experience of others to position yourself for growth as a government contractor.  Thinking about your business processes will help you refine your business and come up with creative new ways to win.

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