Skip to main content

SharePoint or CRM for Government Contractor (GovCon) Capture Management?

If you are a government contractor and you are using Microsoft products such as Office 365, you may reach the point when you would like to automate your business development (capture management) process.  Which tool should you use?

Many companies start by keeping a list of opportunities in Excel, and emailing that Excel document to sales people and managers using Office 365.  These spreadsheets often grow complex as they are enhanced to capture all the data elements that you want to track.  While it is a simple approach, it has some disadvantages:

  1. Hard to track who has most recent version
  2. People can add more columns and worksheets without coordinating with one another
  3. Difficult to generate some pipeline reports 
  4. Grows quickly and may become unwieldy, especially if past wins and losses are accumulated in the spreadsheet

The next evolutionary step is to use SharePoint (included in Office 365) to store the sales spreadsheet.  This eliminates the version control problem, and establishes a single place where the latest spreadsheet is stored.

SharePoint is also an excellent platform for storing solicitation and proposal documents.  You can set up permissions to grant the right people access to the documents they need, and use SharePoint to organize proposal boilerplate items, staff resumes, and more. Documents created internally can be shared with potential subcontractors, subject matter experts, and other vendors under the security framework of Office 365.

SharePoint workflows can be used to automate review and approval processes. For instance, you can notify reviewers when new drafts are posted to a document library.

Some companies use SharePoint lists to store the information on the opportunities rather than Excel.  This offers additional levels of control and makes some reports easier to generate.

Dynamics CRM offers the most comprehensive set of features for capture management of all the Microsoft products.  It was designed for sales force automation, marketing, and customer service and includes hundreds of features that surpass what you can accomplish in SharePoint in terms of tracking sales.  Dynamics CRM has record- and field-level security along with the concepts of record ownership and an organizational hierarchy.  This means that you can assign opportunities to sales people and define rich permissions for who can access what data.  Dynamics CRM has mobile clients for tablets and phones, and even service scheduling and route planning.  It can be used to generate marketing emails, such as invitations to events.

InfoStrat developed the Dynamics CRM for Government Contractors solution which takes Dynamics CRM a step further, adding data elements, workflows, dashboards and reports that are geared toward government contractors.


Finally, using Dynamics CRM to track sales does not mean you should not be using SharePoint to track documents.  Business development involves both structured data (Dynamics CRM) and unstructured data (SharePoint).

You can even automate the process to track your emails to clients and prospects in Dynamics CRM without entering them manually.  An exciting new product called Komiko will search emails for those sent to companies and contacts that you are tracking in CRM and add them as activities.  This allows you to report on how many activities were required to close a sale, and see how new sales develop.


You don't have to adopt all this technology at one time.  You can chart a course to move at the best speed for your organization.

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/ by James Townsend 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