How to Build Public-Sector Past Performance Before You Have Many Government References

A company entering the public sector often meets the same circular objection: the buyer wants relevant government past performance, but the company cannot create it without first winning government work. The tempting responses are to chase any small public logo, stretch a commercial case study until it sounds governmental, or join a partner’s proposal and borrow the whole team’s history. Those shortcuts produce a larger slide, not necessarily a more credible proposal.

Past performance is best understood as evidence about delivery risk. The evaluator is trying to judge whether the offeror can perform the work being bought successfully. A famous agency name attached to unrelated work may say less than a commercial deployment with comparable scale, integration constraints, service levels, and users. Conversely, a strong commercial reference cannot satisfy a solicitation that expressly requires a certain number or type of public contracts.

The operating principle: past performance is proof of relevant risk reduction, not a government-logo count. Build the proof honestly, then pursue requirements where that proof is likely to matter.

Use this as an evidence framework, not legal advice or a promise that a reference will be accepted. Public procurements differ; the solicitation and the contracting officer’s written instructions control.

What public buyers mean by past performance

Experience and past performance are related, but they are not identical. Experience asks whether you have done similar work. Past performance asks how well you did it. One describes the work; the other describes execution. A solicitation may evaluate either or both, impose minimum experience qualifications, request references, consult an official performance system, or use a different structure entirely.

For negotiated federal procurements, FAR 15.305 says agencies evaluate proposals only on the factors and subfactors in the solicitation. It describes past performance as one indicator of successful performance and directs evaluators to consider currency, relevance, source, context, and trends. It also says the solicitation must explain its approach, including treatment of an offeror with no relevant history. Offerors have an opportunity to identify similar federal, state, local, and private contracts, but the source selection authority determines relevance.

For federal commercial products and services, FAR 12.206 tells contracting officers to consider past performance from a wide variety of sources inside and outside the federal government, under the applicable procedures. That supports using well-matched commercial evidence when allowed. It does not create a universal rule that every commercial reference qualifies for every procurement.

SLED rules also vary. New York’s official procurement guidelines list past performance and references as possible technical criteria and say required references should be verified. Texas maintains a Vendor Performance Tracking System used in award-risk and best-value decisions. These are buyer-specific systems, not a national SLED standard.

Use an evidence ladder instead of waiting for the perfect logo

You can build stronger proof before you have a long prime-contract history. The evidence ladder below ranks forms of evidence by their usual proximity to a public requirement—not by an automatic evaluation score. A solicitation may reorder the ladder, exclude a rung, or require facts that your current portfolio cannot supply.

FAR 15.305 specifically allows consideration of relevant predecessor-company, key-personnel, or major and critical subcontractor information in appropriate cases, and contains separate treatment for joint ventures. SBA’s Mentor-Protégé and joint-venture guidance describes collective representation of past performance as one joint-venture benefit, subject to program and affiliation rules. None of that authorizes a vendor to collapse the parties into one undifferentiated history. Follow the competition’s instructions and identify ownership of every claim.

Build a reference matrix around relevance

Do not choose references by brand recognition alone. Create a matrix that compares each candidate project with the new requirement. The matrix should expose both strength and distance. A reference can be excellent on technical complexity and weak on public procurement; the proposal team should see both facts before deciding whether to use it.

A matrix also improves bid discipline. If every available reference is materially distant from the required scale, security environment, or scope, the answer may be to team, narrow the target, build proof through a smaller opportunity, or decline the bid. The broader public sector sales playbook explains how to make that decision before a deadline turns every gap into wishful language.

Five practical ways to create stronger proof

1. Repackage adjacent commercial work around buyer risk

A commercial case study usually leads with the customer logo and a headline outcome. A government reference package should be more forensic. Identify the comparable workload, implementation complexity, operating constraints, service levels, delivery team, schedule, and measured result. If a county seeks a resident-service platform, a regulated commercial deployment may demonstrate security and transaction scale while still leaving gaps in public records, accessibility, procurement, or policy workflow. Say that plainly.

Ask the commercial customer for permission before naming it or providing a contact. Prepare a redacted version for customers that permit facts but not attribution. Never invent an anonymous government customer, imply a private customer is public, or turn a product demo into a production deployment.

2. Subcontract where your work is mission-relevant

Subcontracting can be a rational first step because it lets a newer public-sector vendor contribute a defined capability while an experienced prime carries overall contract responsibility. SBA’s prime and subcontracting guide explains that subcontractors work for the prime rather than directly for the agency and identifies subcontracting as a way for firms not yet prepared to prime to participate in federal procurement.

Choose work that creates evidence you actually need: delivery of the core product, integration, training, adoption, or operational support—not a nominal team-member listing. Negotiate the right to describe your scope and request an attributable performance letter where permitted. Preserve acceptance records and measurable results. In future proposals, report the total contract for context but clearly separate your value, period, workshare, and outcome. For the commercial and relationship tradeoffs, see the guide to using a public-sector reseller without outsourcing your GTM.

3. Design a small first award or pilot to produce a decision

A small initial engagement is useful when it is a real, authorized purchase with a bounded problem and an evaluation plan. Define scope, permitted users and data, security obligations, delivery milestones, success measures, decision rights, and what happens when the period ends. The goal is not to create a ceremonial pilot logo. It is to perform useful work, let the buyer evaluate it, and leave an auditable record.

Do not use a free trial to evade procurement, security, privacy, records, or ethics requirements. Ask the buyer which path is permissible and document it. Even when the engagement succeeds, describe it at its true size. Evidence from twenty users over six weeks may reduce one category of risk without proving an enterprise rollout.

4. Use teaming to close a named gap, not decorate a cover page

A strong partner contributes past performance, contract access, delivery capacity, customer trust, or a capability the requirement genuinely needs. Before bidding, map which entity performs each critical task, which record supports it, who owns the customer relationship, and what evidence can be used later. Confirm that the structure, workshare, representations, and eligibility comply with the solicitation and applicable rules.

The same rule applies to capture. If early market research shows that a partner fills a real requirement or access gap, engage before the team is forced together by an RFP deadline. The guide to moving from white paper to RFI to RFP explains how to contribute useful market information without treating early engagement as permission to write private requirements.

5. Make reference capture part of delivery

The worst time to reconstruct performance is forty-eight hours before a proposal is due. At kickoff, record the baseline, requirements, success measures, milestones, customer roles, and evidence owners. During delivery, retain acceptance, schedule, quality, issue, and corrective-action records. At closeout, confirm the outcome, reference permissions, approved facts, contact information, and any restrictions on disclosure.

For federal contracts, FAR Subpart 42.15 makes CPARS the official federal source for covered past-performance evaluations and centers the record on requirements, cost control where applicable, schedule, management or business relations, and supporting narrative. Not every engagement produces a CPARS evaluation, and CPARS is not a public case-study library. Contractors should monitor covered evaluations, review the supporting facts, and use the formal comment process when necessary while maintaining their own permitted reference file.

Build a reference package that can survive verification

Create a standard one-page record for every candidate project, then adapt it to the solicitation rather than pasting a generic case study. At minimum, capture:

• Identity and authority: legal customer, contracting entity, agreement or contract identifier where allowed, and the party whose performance is described.
• Dates and value: period of performance and the requested value information, distinguishing total program value from your own workshare.
• Role and scope: prime, subcontractor, partner, or vendor status plus the precise products, services, deliverables, and locations you owned.
• Relevance: a short comparison to the new requirement across scope, scale, environment, complexity, and team.
• Performance: baseline, measurable outcomes, quality, timeliness, management, problems encountered, and corrective actions.
• Verification: an authorized reference with permission, current contact information, backup path, and any limits on disclosure.

Brief the reference before submission. Confirm the solicitation, deadline, expected call or questionnaire, project facts, and the claims you made. Do not script praise or pressure an official to endorse the company. Give the reference a fact sheet so the buyer can verify the same work you described. If the reference cannot participate, disclose that constraint early and follow the contracting officer’s instructions for alternatives.

Include problems and recovery when requested. FAR 15.305 expressly allows offerors to explain problems and corrective actions, and a factual recovery story can be more credible than a frictionless narrative. Do not hide material failures or blame the customer. Explain the issue, response, result, and control added to prevent recurrence.

Let your strongest proof shape where you hunt

Past performance is usually treated as a proposal asset. It should also be an account-selection input. A team with excellent proof in high-volume benefits operations should prioritize agencies, programs, and buying events where that operating pattern is visible. It should not treat every software RFP as equally attractive simply because the product can be configured to respond.

Build a simple fit profile from the reference matrix, then monitor target accounts for source-backed evidence: budget language, leadership priorities, expiring contracts, RFIs, grants, board materials, and relevant solicitations. For each item, preserve the source, explain the fit, identify the stakeholder or proof gap, and assign the next action. That is the connection between evidence strategy and pipeline strategy.

Settle supports that operating layer by bringing together relevant signals and RFPs, fit context, buyer and stakeholder context, recommended next actions, and grounded response work. It is additive to official portals, market-intelligence products, partner networks, and the CRM; it does not replace the buyer’s evaluation or guarantee that a reference will be accepted. See how Settle works from early signal through response.

The honest gap is part of the proof

A new entrant does not need to pretend it has decades of government history. It needs to understand the buyer’s risk, verify the work it claims, and show a credible plan for the gaps. That may mean combining adjacent commercial evidence with a qualified partner, starting smaller, or declining a requirement too far from the present record.

The strategy changes two systems at once: delivery preserves proof, and go-to-market pursues buyers whose risks that proof can reduce. Public-sector references then accumulate as the result of a sound operating motion, not a substitute for one.