A time-and-materials contract without the materials — and with the same reason it exists: nobody can size the work yet
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
Last updated:
A labor-hour contract is a time-and-materials contract without the materials: the government buys hours at fixed hourly rates, and nothing else.
It sits in the same subpart of the FAR for the same reason. Both are permitted only when it is not possible to estimate the extent or duration of the work with reasonable certainty, both require a ceiling price, and both, in the regulation's own words, provide no positive profit incentive for cost control or labor efficiency.
For AI programmes that description is usually accurate — not because AI is mysterious, but because the contractor is expected to build the platform as part of the engagement.
When the platform already exists and comes with its source code, the justification for a labor-hour award weakens considerably, and a licence plus a defined integration becomes both cheaper and easier to defend.
by ibl.ai
Licensed platform, source included, bounded integrationby Federal contractors and integrators
Hours only, no materials (FAR 16.602)| Criteria | Owned Platform + FDE | Labor-Hour Contract |
|---|---|---|
| Who Carries Scope Risk | The platform's cost is fixed and already incurred; only the integration is variable, and it is scoped against something that exists. | Carried by the government, which carries every hour beyond the estimate up to the ceiling. |
| Is There a Ceiling | Yes — a flat licence plus the compute you choose to run. The ceiling is the price. | Billed as fixed hourly rates per labor category, hours only, so the total depends on how wrong the estimate turns out to be. |
| Incentive Alignment | Paid the same whether delivery takes six weeks or twelve, so the incentive is to finish. | No incentive for efficiency — the regulation says so explicitly. |
| Budget Defensibility | A known line item that survives a budget review and can be forecast years out. | Forecastable only as well as the underlying estimate, which is the thing in question. |
| Criteria | Owned Platform + FDE | Labor-Hour Contract |
|---|---|---|
| Reliability of the Estimate | High, because the platform is finished. What remains is integration with known systems. | Low on from-scratch builds — the reason this model is reached for at all. |
| Handling Changed Requirements | Absorbed as engineering, because you hold the source code and can change it directly. | Handled commercially, through re-estimation or change orders. |
| Time to First Production Workload | Weeks — the construction phase does not exist, because the platform already runs. | Quarters, most of them spent building infrastructure that is not specific to you. |
| Depth of Customization Available | Extensive, on top of a working base, with the source in your possession. | Unlimited in principle, which is exactly why it is unbounded in practice. |
| Criteria | Owned Platform + FDE | Labor-Hour Contract |
|---|---|---|
| Source Code Ownership | Full source under a perpetual licence, running on your infrastructure. | Determined by contract clauses rather than by the delivery model — commonly delivered effort, with data and software rights governed by separate clauses. |
| Ability to Operate Independently | Your team runs it; the platform is documented, supported, and maintained beyond any engagement. | Depends on knowledge transfer, which is the step most engagements shorten first. |
| Model Freedom | Model-agnostic by construction — run any LLM and switch without rewriting the platform. | Whatever was built in, and whatever the team is willing to maintain. |
| Deployment Flexibility | Any cloud, on-premise, or fully air-gapped, from the same deployment. | Whatever was engineered; air-gapped operation is significant additional scope. |
Because the alternative it prefers — a fixed-price arrangement against a known deliverable — becomes available as soon as the thing being bought actually exists.
A labor-hour award requires a Determination and Findings that no other contract type is suitable, plus a ceiling price and active surveillance. That overhead is the regulation compensating for absent efficiency incentives.
If a platform exists and can be licensed, the D&F for labor-hour becomes materially harder to write, which is a signal about the right structure rather than a paperwork problem.
A flat licence has a natural ceiling that requires no surveillance to enforce, because the price does not move with effort at all.
A ceiling caps exposure but does not align incentives. Programmes routinely reach the ceiling and then negotiate an increase, because the work is genuinely unfinished.
A ceiling is a limit on damage, not a mechanism for value. Prefer structures where the ceiling is the price.
A perpetual licence with the source code means the agency operates the system independently and can modify it without returning to the contractor.
Under labor-hour, software and data rights are governed by separate clauses that are easy to under-negotiate, and agencies regularly discover they cannot modify what they funded.
Hours purchased are not rights acquired. Settle rights explicitly, whichever structure is used.
A licence to a platform already in production makes the required Determination and Findings for labor-hour difficult to sustain, and usually costs less.
For short-term capacity against work that cannot be defined as a deliverable, labor-hour is the structure the FAR intends.
A platform that deploys air-gapped with the source code in the agency's possession satisfies operational requirements that an hours contract does not address at all.
Reaching a ceiling means the estimate was wrong. Re-baselining the same structure usually reproduces the outcome; changing the starting point does not.
Timeline: Four to eight weeks for a typical in-flight engagement
Timeline: Days to weeks to contract
ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.
ibl.ai gives an agency the structure the FAR prefers. The platform already exists and runs in production, so it can be acquired as a licence against a defined deliverable rather than as open-ended hours requiring a Determination and Findings. The licence includes the full source code under perpetual terms, deployed on agency infrastructure — including GovCloud or a fully air-gapped network with no outbound connectivity. Forward-deployed engineers handle integration with existing agency systems as bounded work. You own all the code and the data, run it model-agnostic across any LLM, with no per-seat pricing.
Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.
Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.
Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.
Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
See how ibl.ai deploys AI agents you own and control—on your infrastructure, integrated with your systems.