Skip to main content

You Won't Win Federal Business Opportunities on FedBizOps

If your company is new to federal government contracting, you might be thrilled to find that the federal government has a website which consolidates thousands of requests for products and services from the entire range of government agencies.  This site is FedBizOps (fbo.gov).

Unfortunately, it doesn't take long to find out that FedBizOps is not the best way to get your company started on government contracting.  As government contract experts point out, if you learn about an opportunity on FedBizOps, you are learning about it too late to win it.  

Although FedBizOps has thousands of opportunities, these do not represent all of government spending.  It's expensive, risky and time consuming to run a competitive procurement which is open to all bidders, so purchasing offices try to avoid full and open competition.  Agencies often award a blanket purchase agreement worth tens or hundreds of millions of dollars to one or more companies that covers many tasks. These tasks are then awarded either without competition or with a small and short competition among pre-qualified vendors.



Agencies must comply with requirements to award set-aside contracts to companies that are minority-owned, women-owned, Alaskan native corporations, and other special programs.  Many of these solicitations will never appear on FedBizOps. These companies in turn must find subcontractors capable of providing the required products and services.

If your company has a narrow focus and is primarily geared toward a commercial market, you may not want to invest the time and money to chase federal contracts as a prime contractor.  Instead, you may be better off to pursue the prime contractors such as large system integrators who are the gatekeepers for many federal agencies.

All this doesn't mean that FedBizOps isn't worth your time.  You can learn about who is buying what, and you can make note of whether your target agencies are using special set-aside contracts for their purchases so you can create teaming arrangements that will win.

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