Recompetes and Incumbent Transitions for Software Companies: How Follow-On Contracts Work

2026-10-25#saas #federal-market

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

Most federal software and IT work is not new. Agencies buy a capability, run it for the base period and option years, and then compete the requirement again. That follow-on competition is a recompete, and for a software company it is one of the most predictable openings in the federal market: the requirement is known, the end date is public and the current contractor is identifiable.

This guide covers how recompetes are scheduled, how to find them, what the incumbent’s advantage really is, how bridge extensions and transitions work, and what to do after the award. The rules cited are from FAR Part 17 on options, FAR 37.110 and the FAR 52.237-3 Continuity of Services clause, FAR 52.217-8 and the small business rules in FAR Part 19 and 13 CFR Part 124.

Why recompetes happen on a schedule

A federal contract does not renew forever. Under FAR 17.204(e), unless approved under agency procedures, the base period plus option periods of a services contract may not exceed five years. When the last option year is used up, the agency either recompetes the requirement, changes it or stops buying it.

That makes recompetes forecastable in a way new requirements are not. The end of the period of performance is set when the contract is signed, and the agency has to start acquisition planning well before it. For a large or complex requirement, that planning commonly begins a year or more before the current contract ends.

Recompetes also happen inside larger vehicles. A task order issued under a multiple-award contract is competed again among the vehicle’s holders when it expires, which is one reason holding the right vehicle matters before the order comes up.

How to find a recompete early

The information is public; the work is in reading it before the solicitation appears.

Award data. USAspending.gov shows each contract’s awardee, agency, value and period of performance, including the current and potential end dates. A software or IT services contract with a potential end date in the next 12 to 24 months is a recompete candidate.
Agency forecasts. Many agencies publish procurement forecasts that list upcoming requirements, sometimes with the incumbent and a point of contact.
Sources sought and RFIs. An agency testing the market for a follow-on often issues a sources sought notice or RFI. A response is the earliest point at which a challenger can influence how the requirement is written.
Industry days and draft solicitations. These show how the agency is thinking about the next contract: whether the scope is changing, whether it is moving to a commercial product, and whether the set-aside decision is open.

The goal is to know the requirement well enough, before the request for proposals, that your proposal reads as a plan rather than as a first look.

What the incumbent’s advantage really is

Incumbents start ahead. They know the users, the systems, the data and the unwritten requirements. They have staff in place and past performance on the exact work being competed. Agencies weigh transition risk, and an incumbent carries less of it.

That advantage is legitimate. GAO has long held that an agency does not have to neutralize an incumbent’s natural advantage unless it results from preferential treatment or other unfair action by the government. A challenger should not expect the evaluation to be adjusted for it.

Incumbency is not a guarantee, though. Recompetes are where agencies change course: from custom development to a commercial product, from one large contract to several smaller ones, or from a contractor whose performance has slipped. A challenger’s openings are usually one of these:

A changed requirement. The agency wants something the incumbent’s approach does not deliver well, such as a modern commercial platform or faster delivery.
Performance concerns. Weak CPARS evaluations or user dissatisfaction make the agency more willing to accept transition risk.
A credible transition plan. If you can show how you would take over with little disruption, the incumbent’s main advantage shrinks.

If you are the incumbent, the same list is your risk register. Treat the recompete as starting on the first day of the current contract, not when the solicitation is released.

Bridge extensions and delays

Recompetes often run late. Acquisition planning slips, evaluations take longer than planned, and a bid protest can stop performance of a new award while it is decided. The agency still needs the service, so it keeps the incumbent running.

The first tool is FAR 52.217-8, Option to Extend Services, which lets the agency extend performance at contract rates for up to six months in total. When that is exhausted or was never in the contract, the agency may issue a short bridge contract or extension, usually to the incumbent, which requires a justification for other than full and open competition. The sole-source rules govern how that is documented.

For a challenger, a bridge means the start date moves, not that the competition is over. For an incumbent, it is continuity, not a renewal; the follow-on competition still has to happen.

Transitions under FAR 52.237-3

When services are vital and must continue without interruption, FAR 37.110(c) lets the contracting officer include FAR 52.237-3, Continuity of Services, in the contract. The clause binds the incumbent to help the successor take over. Under it, the contractor agrees to:

Furnish phase-in training and use its best efforts and cooperation to achieve an orderly and efficient transition to a successor, whether another contractor or the government itself.
Provide phase-in, phase-out services for up to 90 days after the contract expires, on the contracting officer’s written notice.
Negotiate a transition plan in good faith with the successor and submit it to the contracting officer.
Let the successor interview the incumbent’s employees and release those who agree to move.

The incumbent is reimbursed for reasonable phase-in and phase-out costs under the clause, with a limited fee. For a challenger, this is the mechanism that makes a transition plan credible: it is the agency’s assurance that the outgoing contractor has to cooperate.

What software companies should check before a transition

Software transitions have problems that pure services transitions do not.

Who holds the data and the code. What the government can hand to a successor depends on the contract’s data rights and software license terms. Custom code delivered with government rights can move; a proprietary product licensed to the agency usually cannot.
Data export. If the incumbent hosts the system as a service, the transition depends on getting the agency’s data out in a usable form. Read the contract’s data ownership and export terms early, as challenger or incumbent.
Authorizations. A replacement cloud product generally needs its own authorization to operate at the agency. A challenger’s authorization status is part of transition risk, and a self-attested security posture is not the same as a verified authorization.
Integrations. Interfaces to other agency systems are often documented only in the incumbent’s team. Ask about them in questions and industry days.

Set-aside status can change

The set-aside decision is made again for every acquisition. A requirement set aside for small business last time is not automatically set aside again; the contracting officer applies the rules again, including the rule of two in FAR 19.502-2. A requirement can also move the other way, from full and open competition to a set-aside, when market research shows enough capable small businesses.

The 8(a) program works differently. Under 13 CFR 124.504(d), a requirement accepted into the 8(a) program generally stays in the program unless SBA agrees to release it. If you are tracking a recompete, check how the current contract was awarded before assuming the competition will be open to you. The small business set-aside guide covers the programs.

After the award

If you lose, ask for a debriefing. A debriefing shows how the agency rated your proposal against the awardee’s. Request it promptly; the deadlines for a debriefing and for a protest are short and linked.
If you have grounds, decide on a protest quickly. Filing at GAO within the required window after award or after a required debriefing can suspend performance of the new contract while the protest is decided.
If you lose as the incumbent, your obligations under 52.237-3, if it is in the contract, continue through the transition. How you handle it shows up in your record for the next competition.
If you lose as a challenger, consider teaming with the awardee. Awardees taking over unfamiliar work often need specialist subcontractors.

What this means for a software company

Build a recompete calendar. Pull the software and IT contracts at your target agencies with end dates in the next two years, and note the incumbent, vehicle and set-aside status of each.
Engage before the solicitation. The sources sought response, industry day and draft RFP comments are where a challenger can shape the requirement. After the RFP is out, you can only answer it.
Write the transition plan first. For a challenger, a specific, staffed, dated transition plan is the most direct answer to the incumbent’s advantage.
Plan for delay. Bridge extensions and protests can move a start date by months. Budget for it.
Read the current rule text. The FAR is being rewritten under the Revolutionary FAR Overhaul. Confirm the clauses and provisions in the actual solicitation and contract rather than relying on a summary.

Where this fits

A recompete is a known requirement with a known end date and a known incumbent. That makes it one of the few federal openings a software company can plan for a year or more in advance. The companies that do well on recompetes treat them as a calendar, not a surprise.

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

Frequently Asked Questions

Does an agency have to offset the incumbent's advantage in a recompete?

Generally no. GAO has long held that an agency is not required to neutralize the advantage an incumbent has from performing the work, such as knowledge of the requirement or an existing staff, unless that advantage comes from preferential treatment or other unfair action by the government. A challenger competes by showing a credible, lower-risk path to the same outcome, not by expecting the field to be levelled for it.

What happens to the incumbent's contract if the follow-on award is delayed?

The agency usually keeps the service running on the existing contract. If the contract includes FAR 52.217-8, Option to Extend Services, it can extend performance at contract rates for up to six months in total. Beyond that, an extension usually needs a separate justification for other than full and open competition, which is why recompete delays and protests so often produce short bridge contracts with the incumbent.

If a requirement was set aside for small business last time, will the recompete be set aside again?

Not automatically. The contracting officer applies the set-aside rules again for the new acquisition, including the rule of two in FAR 19.502-2. Requirements in the 8(a) program are different: under 13 CFR 124.504(d), a requirement accepted into the 8(a) program generally stays there unless SBA agrees to release it.

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.