Tradeoff vs. LPTA for Software Companies: How Agencies Weigh Price Against Quality

2026-10-22#saas #federal-market

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

Every competitive federal buy answers one question before the first proposal arrives: how much is the agency willing to pay for a better solution? The answer is written into the solicitation as the source selection method, and it should shape everything about how you bid, from how long your technical volume is to where you set your price.

For software companies the two methods you’ll meet most often are the tradeoff process and lowest price technically acceptable (LPTA). They reward very different proposals. This guide explains how each one works, how to tell which one you’re facing, and how to bid it.

The best-value continuum

FAR Part 15 describes “best value” as a continuum. At one end the agency is willing to pay more for a stronger proposal; at the other, anything that meets the requirement is good enough and price decides. The solicitation tells you where on that line the buy sits.

The FAR is being rewritten through the Revolutionary FAR Overhaul, and many agencies now apply the new text by class deviation, so section numbers and wording may differ. Check the solicitation and the current FAR text for the rules that apply to a given buy.

The tradeoff process

In a tradeoff, the agency may award to an offeror that isn’t the lowest priced, or isn’t the highest rated, if that gives the government the best overall value. The solicitation must:

list every evaluation factor and significant subfactor that will affect the award, and their relative importance
state whether the non-price factors, combined, are significantly more important than, about equal to, or significantly less important than price

When the agency pays more for a higher-rated proposal, the source selection authority has to decide that the extra benefit is worth the extra cost and write down why. That documented rationale is what a debriefing or a bid protest will turn on.

How to bid a tradeoff:

Write for strengths, not just compliance. Evaluators assign strengths for features that exceed a requirement in a way that benefits the agency. Name the requirement, show how you exceed it, and say why that matters to the mission.
Make the benefit concrete. “Faster onboarding” is hard to credit. “Agency users are productive in the product in one day, shown by the training plan in Volume II” is easier for an evaluator to write up as a strength.
Price to the weighting. If non-price factors are “significantly more important” than price, a modest premium for a clearly stronger solution can be defended. If they’re “approximately equal,” it’s harder.

Lowest price technically acceptable

Under LPTA, the solicitation sets out what “technically acceptable” means. Each proposal is rated acceptable or unacceptable against those standards, proposals aren’t ranked on the non-price factors, and no tradeoffs are allowed. Award goes to the lowest-priced proposal rated acceptable.

That has a blunt consequence: a capability beyond the stated minimum earns nothing. Extra features, a richer roadmap or a larger team don’t raise your rating. They only raise your price.

How to bid an LPTA:

Map every acceptability standard to a page. Missing one standard makes the whole proposal unacceptable, regardless of price. Build a compliance matrix from Section L and Section M and check it twice.
Strip the proposal to the requirement. Offer what’s asked for. Anything more should be priced as an option or left out.
Price carefully, not recklessly. An agency still has to find the price fair and reasonable, and some solicitations check for realism. A price you can’t deliver at is a risk the past performance record will carry for years.

Limits on LPTA for software and IT services

LPTA is a poor fit for many software buys, and federal rules now say so. The FAR lists conditions an agency must meet before choosing LPTA, including that the minimum requirements can be described clearly and that the agency would see little or no value in a proposal that exceeds them. Department of War buys are also governed by DFARS 215.101-2-70, which tells contracting officers to avoid LPTA, to the maximum extent practicable, for information technology services, cybersecurity services and other knowledge-based professional services.

These limits don’t ban LPTA for software. Commodity purchases, such as off-the-shelf licenses with a defined configuration, are still bought this way. But if a solicitation for complex IT services is structured as LPTA, it’s reasonable to ask the contracting officer, in writing and before the deadline, how the conditions were met.

Other methods you’ll see on orders

On task orders under IDIQ contracts and on GSA Schedule orders placed through eBuy, agencies have more freedom in how they choose. Some use a “highest technically rated offeror with a fair and reasonable price” approach: they rank the technical proposals, then check the top-rated offeror’s price and award if it’s reasonable. Others run a short tradeoff with fewer factors, or add a product demonstration as described in our guide to oral presentations and technical demos.

Read the order request the way you’d read a full solicitation. The method may be described in a single sentence, but it decides what you should write.

Telling them apart quickly

Look for these phrases in Section M or the order request:

Tradeoff: “best value tradeoff,” “may award to other than the lowest priced offeror,” “non-price factors, when combined, are significantly more important than price.”
LPTA: “lowest price technically acceptable,” “acceptable / unacceptable,” “no tradeoffs will be made.”
Highest technically rated: “the government will evaluate the price of the highest technically rated quote.”

If the wording is ambiguous, ask during the question period. The answer changes how you should write and price the whole proposal.

To see how your company measures against the factors evaluators tend to weigh, score your company’s federal readiness.

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.