Skip to main content

You May Not Need a GSA Schedule -- At Least Not Yet



When you decide to pursue government contracts, the first thing you may be asked is whether you have a GSA Schedule -- the most widely used contract for federal, state and local agencies to purchase goods and services.

A good place to start to learn more is the official GSA FAQ: http://www.gsa.gov/portal/content/122123

In general, government contractors need contract vehicles, and many will win a place on the GSA Schedule. Before you reach for your checkbook to hire a company to help you with your GSA Schedule, consider some cases in which you may want to wait:

  1. Yours is a new company.  GSA uses past performance and pricing to validate you as a government supplier. For example, GSA Schedule 70 for information technology calls for two years in business.
  2. You haven't nailed down your commercial pricing. GSA looks for a track record of pricing, and commercial prices are often the basis for government pricing.
  3. You aren't prepared to handle the administrative burden.  Government contracts don't manage themselves.
  4. You are in a hurry. If you have a hot prospect but no contract, you don't have time to win a GSA Schedule award. Ask your prospective customer what contract they would prefer to use, then contact contract holders. 
  5. When using another company's contract is better.   There are many companies, especially resellers and systems integrators, that are happy to bring you on as a subcontractor so you can use their contract to win business rather than your own.  In the short run, this is usually less costly than the effort to chase your own GSA schedule.
In short, don't let the lack of a GSA schedule hold you back from winning government work, or waste your time by pursuing one before you are ready. 

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