Key Personnel for Software Companies: Naming, Committing and Replacing the People You Propose

2026-10-26#saas #federal-market

By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.

A federal evaluator can’t test your product team the way a buyer in a commercial sale can. So many solicitations ask you to name the people who will do the work, score their résumés, and then write those names into the contract. Those people are your key personnel, and how you choose, commit and later replace them affects both whether you win and how the contract runs.

This guide covers what key personnel are, how they are evaluated, letters of commitment, substitution after award, and the bait-and-switch rule. It is written for software and SaaS companies, where the team is small, engineers move between projects, and the founders are often the most qualified people you have.

What makes someone “key”

The solicitation decides. A typical services or software development solicitation designates a few roles as key, such as program manager, technical lead or architect, security or compliance lead, and sometimes a data or DevSecOps lead, and asks for a résumé for each named person, often with minimum education, experience or certification requirements.

There is no single key personnel clause that applies across the whole FAR. Agencies use their own clauses and solicitation language. Examples include the Department of Health and Human Services’ HHSAR 352.237-75, Key Personnel, and NASA’s NFS 1852.235-71, Key Personnel and Facilities. The common thread: the people listed in the contract are expected to perform it, and substituting them requires the contracting officer’s involvement.

On subscription buys of a commercial product, key personnel are less common, because the agency is buying access to a service, not labor. They show up when the contract includes implementation, integration, custom development, managed services or labor-hour support around your product.

How key personnel are evaluated

FAR 15.304 requires every source selection to address quality through one or more non-cost factors, and it lists personnel qualifications among the examples. In practice, key personnel are usually scored inside a technical or management factor. Evaluators check each résumé against the minimums, then look for strengths: directly relevant experience, clearances, certifications and time with similar agencies.

A few things that matter more than founders expect:

Meet every stated minimum, explicitly. If the solicitation asks for ten years of experience and a certification, show both on the résumé, with dates. An evaluator will not infer a qualification you didn’t write down.
Match the résumé to the role. A brilliant CTO résumé that never mentions program management is a weak program manager résumé.
Be consistent. The names in the staffing plan, the résumés, the oral presentation and the price volume must line up. Inconsistencies read as risk.
Show availability. If a key person is splitting time across contracts, say how much of their time this contract gets, and make sure it matches what the solicitation requires.

Letters of commitment

You don’t have to employ every key person when you submit. Many solicitations allow contingent hires, and teaming partners routinely supply named staff. In both cases, solicitations often require a signed letter of commitment or letter of intent in which the person confirms they agree to be proposed and to work on the contract if it is awarded.

Treat those letters as real commitments, not paperwork. Talk to the person about timing, compensation and what happens if the award slips by months, as federal awards often do. If a key person comes from a subcontractor, settle in the teaming agreement who replaces them if they leave.

Unavailability before award

Federal source selections take time, and people change jobs. GAO protest decisions have held that when an offeror learns before award that a proposed key person is no longer available, it should notify the agency rather than stay silent. The agency then generally has two paths:

Evaluate the proposal as it stands, without that person. Where key personnel are a material requirement, this can make the proposal unacceptable.
Open discussions with the offerors so that proposals can be revised, including a substitute.

Agencies are not required to accept a substitute outside discussions, and the rules here come from protest decisions with fact-specific outcomes. The practical lesson for a small company: propose people who are likely to still be with you when the award comes, and keep in contact with them while you wait.

Bait-and-switch

The opposite failure is proposing impressive people you never intended to provide. GAO calls this a bait-and-switch. In deciding a bait-and-switch protest, GAO generally considers whether the offeror represented that it would rely on specific personnel, whether the agency relied on that representation in its evaluation, and whether it was foreseeable that those people would not be available to perform.

A sustained protest can overturn your award. Even without a protest, swapping out key personnel soon after award damages the relationship with the contracting officer and the program office, and can show up in your performance evaluations. See past performance for how those evaluations follow you into later bids.

Substitution after award

Once the contract is signed, key personnel clauses typically require you to:

Notify the contracting officer in advance, in writing, often within a set number of days before the change.
Propose a substitute whose qualifications are equal to or better than the person being replaced, with a résumé.
Wait for approval before the substitute starts in the key role.

Read the clause in your own contract, since notice periods and approval rules differ between agencies. Unapproved substitutions are a common source of contracting officer friction and can lead to formal corrective action. Approved substitutions are often documented in a contract modification.

On time-and-materials and labor-hour work, a related rule applies to everyone you bill, key or not: each person must meet the qualifications of the labor category you bill them under. On IDIQ task orders and schedule orders, check the labor category descriptions before you staff the order.

Clearances and access

If the contract involves classified work or controlled spaces, a key person may need an active security clearance or must be able to obtain one in time. Clearances belong to the person, but the company generally needs a facility clearance to sponsor them for classified work. See facility security clearances for software companies. A proposed program manager without the required clearance can sink an otherwise strong proposal.

What this means for a software company

Pick key personnel you can keep. Name people with the qualifications, the availability and a real commitment to the work, not the most impressive résumés in the company.
Don’t rely on founders alone. A small team that names the CEO as program manager and the CTO as technical lead for every bid will hit an availability problem the first time two proposals win.
Write résumés against the solicitation, showing every stated minimum with dates.
Get signed letters of commitment from contingent hires and teaming partners’ staff.
Report unavailability to the agency if a key person leaves before award.
Plan for turnover. Know who could step into each key role and keep their résumé current, so a substitution request is ready when you need it.
Read the current rule text. The FAR is being rewritten under the Revolutionary FAR Overhaul, and agency key personnel clauses differ. Confirm the clauses in your solicitation and contract, and involve government contracts counsel on disputed substitutions or protests.

Where this fits

Key personnel are part of the technical and management volume of a proposal, alongside the approach that Sections L and M ask for. They matter again at oral presentations, where key personnel are often expected to present, and at recompetes, where the incumbent’s team is part of what every bidder is pricing against.

Score your company’s federal readiness to see how your team and compliance profile look next to the other categories federal buyers review.

Frequently Asked Questions

What are key personnel in a federal contract?

Key personnel are the specific people a solicitation asks you to name, such as a program manager, technical lead or security lead, whose qualifications are evaluated during source selection and who are written into the contract. Once they are in the contract, you generally cannot replace them without notifying the contracting officer and getting the substitute approved.

Can I propose someone who does not work for my company yet?

Often yes. Many solicitations allow contingent hires but ask for a signed letter of commitment or letter of intent showing the person has agreed to work on the contract if you are awarded it. Read the solicitation's instructions: some require letters for every key person who is not a current employee, and a missing letter can make the proposal unacceptable.

What happens if a key person leaves before award?

GAO protest decisions have held that an offeror that learns a proposed key person has become unavailable before award should tell the agency. The agency then generally either evaluates the proposal without that person, which can make it unacceptable when key personnel are a material requirement, or opens discussions so offerors can revise. The rules come from protest decisions and details vary, so involve counsel.

What is a bait-and-switch in federal contracting?

It is when an offeror wins by proposing people it does not expect to provide. GAO generally looks at whether the offeror represented that it would use specific people, whether the agency relied on that representation in the evaluation, and whether it was foreseeable that those people would not be available. A sustained bait-and-switch protest can cost you the award.

The CMMC brief

What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.