Monday, July 10, 2017

What, You Don't Have a Capability Statement?

From SampleTemplates:

When a private company wants to partner with a potential stakeholder, clients or supplier for a particular project, the capability statement shows the private companies' achievements, competencies, and qualifications to be able to get the deal on a proposed project. The presenting tool must be simple and short which only highlights the companies’ competencies and outstanding performance to do business with them.

A Capability Statement should be very brief (only 1 or 2 pages), to the point and written specifically to the individual agency's needs. Ideally, it is a living document that changes depending on the targeted agency.
Why is this? Because savvy companies know each agency has its own mission and focus, and the capability statement speaks directly to those needs

The five key areas included in a successful statement are:
1. Core competencies - This is NOT everything a firm is able to do, but the core expertise of a firm
2. Past performance - past customers for whom your business has done similar work
3. Differentiators - a succinct, clear statement that relates to the specific needs of the agency is what will help the procurement and purchasing staff, the program managers and end users understand why to choose your firm over others
4. Corporate data - Include one or two short sentences with a company description detailing pertinent history. Include the size of the firm, annual revenue, the number of employees and the typical geographic area you serve.
List Specific Pertinent Codes
􀁸 Socio-economic certifications: 8(a), Minority-Owned, HUBZone, SDVOB, etc.
􀁸 NAICS (all) - include code descriptions
􀁸 CAGE Code - SAM Active
􀁸 Payment Terms i.e. Accept Credit and Purchase Cards
􀁸 GSA Schedule Contract Number(s)
􀁸 Other federal contract vehicles
􀁸 BPAs and other federal contract numbers
􀁸 State Contract Numbers
5. Contact information
􀁸 Name (a specific contact person)
􀁸 Address
􀁸 Phone (main and cell)
􀁸 Email (a person’s email, not info@)

No comments: