The Army has locked in a decade-long path to buy Pegasystems software and services without a fresh competition for each purchase, giving program offices a single vehicle for Pega subscriptions, support and professional services through 2036. Pegasystems Inc., of Waltham, Massachusetts, received a $419,008,836 firm-fixed-price, indefinite-delivery/indefinite-quantity, enterprise contract, according to the Oct. 29, 2026 Department of War contract announcement. Army Contracting Command, Rock Island, Illinois, is the contracting activity under contract number W519TC-27-D-A019.
The announcement describes the scope as "Pegasystems commercial software subscriptions, technical support and outcome-based professional services." It also records a sole response: "One bid was solicited with one received." The $419 million figure is a ceiling on what the Army may order over the life of the contract, not money the service has obligated or must spend.
What the $419M Pegasystems Ceiling Actually Buys
The contract bundles three categories of work into one enterprise vehicle: commercial software subscriptions, technical support, and outcome-based professional services. The announcement does not say which Pega products are covered or which Army organizations will use them.
Enterprise contracts of this kind let a military department consolidate purchases that individual commands might otherwise buy separately. Instead of each office negotiating its own subscription terms, orders flow through a single contract with prices and terms already set. In general, a firm-fixed-price structure means the government pays the agreed price on each order regardless of the vendor's actual costs, which shifts cost risk to the contractor. The phrase "outcome-based" suggests the services portion is framed around defined results, though the announcement does not spell out how.
The announcement does not break the ceiling into subscription, support and services shares, and it does not list a minimum guarantee or any funds obligated at award. Several other entries in the same day's announcement report obligated amounts and funding sources; the Pegasystems entry does not.
Why Only One Bid Came In
The single-bid detail is the most consequential line in the entry for anyone tracking competition in Army software buying. The Department of War listing states plainly that one bid was solicited and one was received. The listing does not explain why the solicitation drew a single offer.
For proprietary commercial software, that outcome is common. When an agency already depends on a specific vendor's platform, the subscriptions and vendor-provided support for that platform are typically available only from the software owner or its authorized channels. The announcement does not cite the specific authority the Army used to limit the solicitation, and no justification document was among the sources reviewed for this article.
The single-source path does not extend automatically to every dollar under the vehicle. Whether outside integrators can compete for related implementation work depends on how the Army structures individual orders and on any separate contracts for systems integration. The announcement offers no detail on that point.
Orders Decide Where Work Happens Through Oct. 28, 2036
The contract does not fix a place of performance or a funding line. Per the announcement, "Work locations and funding will be determined with each order, with an estimated completion date of Oct. 28, 2036." That ten-year window is long for a software vehicle and gives the Army room to renew subscriptions and add services across multiple budget cycles without returning to the market for a new enterprise agreement.
Because funding attaches to each order, the actual spending will follow whatever Army organizations choose to buy and when. Fiscal-year appropriations, program priorities and any shifts in the Army's software portfolio will shape how much of the ceiling gets used. A contract ceiling that goes partly unused over its life is a normal outcome for IDIQ vehicles.
Army Contracting Command, Rock Island, Illinois, is named as the contracting activity, which places it as the office responsible for the contract and the orders that draw down the ceiling.
How the Award Fits the Oct. 29 Army Contract Slate
The Pegasystems award appeared alongside other Army entries in the same announcement, including a separate $37,490,565 firm-fixed-price, time-and-materials, indefinite-delivery/indefinite-quantity contract to Deloitte Financial Advisory Services LLP, of Arlington, Virginia, for flexible litigation augmentation support to the U.S. Army Judge Advocate General's Corps Headquarters. That Deloitte entry carried the same "One bid was solicited with one received" language, a reminder that single-offer awards are a routine feature of the daily contract listings rather than an exception.
OrangeSlices AI reported the same Pegasystems award details, including the single-bid solicitation, the order-by-order funding arrangement and the Oct. 28, 2036 estimated completion date.
No company statement on the award was among the sources reviewed, so Pegasystems' own description of the planned work, the Army commands expected to use the vehicle, and the specific products covered remain unconfirmed.
What It Means for Contractors
For Pegasystems resellers and implementation partners, the vehicle may define the channel through which Army Pega licensing and vendor support flows over the next decade. Partners that build or maintain applications on the platform should watch how the Army writes task orders for the "outcome-based professional services" portion, since that is the part of the scope most likely to overlap with work integrators perform today.
For competing software vendors, the award signals that the Army intends to keep Pega in its enterprise portfolio for years. Firms pitching replacement platforms will be competing against an incumbent with an ordering path already in place, and any migration case will need to account for that.
For small businesses, the single-award structure leaves little direct prime opportunity under this contract. Subcontracting interest should focus on services orders, where the Army may expect specific outcomes and where Pegasystems may bring in partners to deliver them.
Contracting officers and program managers also gain a simpler route: orders under an existing enterprise vehicle generally move faster than standalone procurements. Contractors supporting Army offices that run Pega-based systems should expect future buys for licenses and vendor support to route through W519TC-27-D-A019 rather than appear as separate solicitations on SAM.gov.
The ceiling value will draw attention, but the order history will tell the real story. Firms tracking this vehicle should monitor obligations posted against it in federal spending data to see how much of the $419 million the Army actually uses and which commands place the orders.
