Skip to main content

Acquisition guide · Performance-based software

Buy a result your team can put to work.

Define what the mission needs to accomplish and how you’ll judge the result. Compare acquisition options with the uncertainty and decision rights in view, using the FAR and GSA path from mission need through closeout.

What to bring

You do not need a finished requirement.

Bring what you know about the problem and the result you need. We’ll work through these four questions with you. Buyer-side acquisition support is a separate role screened for organizational conflicts of interest. Government officials keep acquisition decisions.

  1. A mission problem that needs solving

    Tell us what people are struggling to do today and what needs to change.

  2. A delivery window

    Tell us when you need it to work and what happens if it’s late.

  3. Known constraints and dependencies

    Identify the systems, data, policies, approvals, and people the outcome depends on.

  4. Access to decision makers

    Bring together the program, acquisition, technical, security, privacy, and accessibility staff who can resolve tradeoffs.

What you do not need to bring

You don’t need a perfect performance work statement, staffing plan, finished architecture, or complete acceptance plan. We develop those from the mission result and acquisition strategy.

Three different things to buy

Fixed price alone does not create aligned interests.

Define the useful result and how the Government will assess it. Then choose a lawful contract type that fits the uncertainty. We can work within any of these models when the Government selects one.

Model 1

Time-and-materials

What it buys
Direct labor hours at fixed hourly rates, plus materials at cost.
Delivery incentive
You pay for the labor hours and materials used.
Responsible use
The extent, duration, or cost of the work cannot be estimated with reasonable confidence.
FAR 16.601

Model 2

Labor-defined firm-fixed price

What it buys
A fixed-price labor bundle or prescribed roster, even when described as a deliverable.
Delivery incentive
The price risk is fixed, but the operating model can still revolve around filling roles and managing activity.
Responsible use
The Government needs a defined staffing service. Choosing fixed price alone does not establish that fit.

This describes a labor-shaped requirement; it is not FAR terminology.

FFP anchor: FAR 16.202-1

Model 3

Outcome-defined firm-fixed price

What it buys
One bounded result, measurable standards, objective evidence, and Government acceptance.
Delivery incentive
The contractor carries firm-fixed-price cost risk and benefits by reaching the accepted result efficiently inside the agreed boundary.
Responsible use
The useful result and material risks are bounded enough to price and assess responsibly.

This is Intelligrit shorthand for performance design within FFP, not a new FAR contract type.

FAR 37.102 and 37.602
The precise FAR anchors behind this comparison

FAR 16.601 defines time-and-materials as direct labor hours at fixed hourly rates plus materials at cost. It permits T&M only when the extent or duration of the work or its costs cannot be estimated with reasonable confidence, and states that T&M provides no positive profit incentive for cost control or labor efficiency.

FAR 16.202-1 says a firm-fixed price is not adjusted based on the contractor’s cost experience. The contractor assumes maximum cost risk and has an incentive to control costs and perform effectively.

FAR 37.102 makes performance-based acquisition the preferred method for acquiring services and places firm-fixed-price performance-based acquisition first in its stated order of precedence.

FAR 37.602 directs agencies to describe required results rather than how the work is performed or a number of hours, and to use measurable performance standards and assessment methods.

Use it where it fits

Understand the risks before agreeing on a fixed result.

Strong fit

A useful result can be bounded and assessed.

  • The mission result matters within a real delivery window.
  • Success and failure can be observed through agreed evidence.
  • Dependencies, decision rights, and exclusions can be named.
  • The increment will be useful even if no follow-on is awarded.

Do not force the fit

The learning itself is still the primary result.

  • Material technical feasibility is unknown.
  • Critical data, environments, approvals, or owners are unavailable.
  • The desired result cannot yet be distinguished from a solution idea.
  • Acceptance standards would be invented after delivery begins.

Start with a bounded discovery or prototype that produces the evidence needed for the next decision.

A familiar Government path

Eight steps from mission need to clean closeout.

This guide summarizes GSA’s Government-wide Steps to Performance-Based Acquisition. Agency policy, legal review, and contracting officer judgment still govern.

  1. 01

    Build the team

    Bring the people who understand the mission, acquisition, users, technology, and approvals.

  2. 02

    Name the problem

    State the mission objective and required result. Prescribe staffing only when the acquisition strategy requires it.

  3. 03

    Learn the market

    Test feasibility, delivery patterns, risks, and what capable vendors can own.

  4. 04

    Write the result

    Define the required outcome, boundary, constraints, dependencies, and Government-furnished inputs.

  5. 05

    Set the evidence

    Choose measurable standards, assessment methods, incentives, surveillance, and acceptance authority.

  6. 06

    Select the source

    Evaluate demonstrated understanding, credible methods, risk controls, and ability to deliver.

  7. 07

    Manage performance

    Inspect working software and agreed evidence. Record and resolve dependencies and changes.

  8. 08

    Close with intent

    Accept the work, transition it, document performance, and close out. Decide separately whether another objective is needed.

Read GSA’s full eight-step guide

The honest risks

An outcome is only as sound as its boundary.

Clear results and responsibilities define what the contractor must deliver. Cost risk follows the contract type. Dependencies, oversight, and formal change control still apply.

An ambiguous outcome invites disagreement

Control: Before pricing delivery, agree on the result, exclusions, standards, assessment method, dependencies, and acceptance authority.

Hidden dependencies can make a fixed promise artificial

Control: Name Government-furnished inputs and decision deadlines. Start with paid discovery or a prototype when significant uncertainty remains.

A contractor can optimize for the metric instead of the mission

Control: Use balanced functional, security, privacy, accessibility, operability, and transition standards. Avoid relying on one vanity measure.

Changes can become scope disputes

Control: Maintain a shared decision record and use formal change authority when the outcome, boundary, assumptions, or dependencies change.

Speed can conceal shortcuts

Control: Make evidence part of the deliverable: tests, controls, accessibility results, deployment readiness, documentation, and known limitations.

Acceptance creates a real decision

Complete the objective. Then choose what happens next.

Path 01

Transition and close out

Deliver the agreed source, data, documentation, evidence, training, and operating knowledge. Resolve closeout items and leave an independently useful capability.

Path 02

Separately authorize the next objective

Use accepted performance and current mission evidence to define another increment. A follow-on needs a separate decision. The completed work must be useful on its own.

Primary sources

Verify the approach in Government guidance.