Skip to main content

Microsoft SharePoint or Dynamics CRM for Government Contracts?

If your company is a government contractor, you must face long sales cycles and complicated proposal processes in order to win business, especially in federal government.  An opportunity usually takes months to go from a client need to a request for information, then request for proposals, best and final offers and ultimately a contract award.  During this process you will have to create dozens of documents including proposals, schedules, resumes, pricing, and legal terms and conditions.

Which Microsoft product is best for this? 

SharePoint can handle document storage and collaboration, and even a Wiki to store your best practices for proposal writing.  It may be used as an intranet or as an extranet to make it easier to collaborate with team members outside your company. At InfoStrat, we use SharePoint for both our intranet and our extranet.  When we have teammates on a proposal, we share an extranet site with them so we can work on proposal documents together.  You can also share documents using SharePoint with Office 365.

While you could build custom lists in SharePoint to track your opportunities, Dynamics CRM is designed with sales force automation in mind, and includes a complete data model and advanced functionality for tracking leads, marketing to prospects, sales reports and dashboards.  You could insert documents as attachments in Dynamics CRM, but if you are editing them and would like version control and collaboration, SharePoint is much better.

The Dynamics CRM for Government Contractors solution adds the fields and business processes required by government contractors to Dynamics CRM. 

Microsoft includes integration between Dynamics CRM and SharePoint.  Dynamics CRM shows a view into SharePoint for documents, and you can add custom web parts to SharePoint to show data from Dynamics CRM. You can also extend this integration to meet your needs.  For instance, you may prefer to create separate SharePoint sites or folders, or to consolidate documents within a single document library.

The bottom line is that SharePoint and Dynamics CRM each provide tools that are essential for government contractors to make their capture processes more efficient.  The two products work better together than trying to make either product fulfill all the necessary features.


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

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

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