Skip to main content

In Federal Sales, Don't Follow the Herd

Our government contractor clients who are implementing Dynamics CRM for Government Contractors want to know how to increase their sales to the federal government.

For small companies and newcomers to the federal marketing, the challenges are quite daunting.  You need to have a government contract vehicle such as a GSA contract, but the best way to get a vehicle is to have past government contracts. 

The sheer volume of contracts makes it seem it wouldn't be that hard to win a few million out of the billions that are spent each year, but this ignores the nature of competition in government contracts.  If you are new to government contracts, perhaps you should be selling to the prime contractors rather than trying to establish your company as a prime contractor.

Although you can learn from large government contractors, their sales model simply will not work for small business.  You can't spend a year or two and teams of lawyers and contract specialists to win a contract which is essentially a hunting license within a federal agency or two. You probably do not want to have a 90 step process for evaluating opportunities and writing a proposal. 

Using only the most widely available information will not give you a competitive edge.  You need to analyze deeper than reviewing FedBizOps and GovWin IQ to really understand what your customers need.  If all you do is look for contracts to expire and try to beat incumbents at renewal, your company may create far more sales activity than sales success. 

Ask yourself how you create value for your customers.  Find ways to surpass the ordinary and go beyond the typical herd mentality in government contracting.

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