The 11-Month Salesforce Contract

The Transportation Security Administration's Salesforce license order reached its final day on Tuesday. A replacement went out on NASA's SEWP vehicle the same day, to the same reseller, for another 11 months.

On its own that is a routine software renewal at a mid-sized federal component. What makes it worth reading is where it sits. Three weeks ago the Department of Veterans Affairs awarded Salesforce a contract with a $1.6 billion ceiling. Six days ago Agentforce 360 cleared Impact Level 5 and Army Human Resources Command announced a deployment covering 9.2 million people. The announcements are measured in billions and in years. The purchase orders underneath them are measured in months.

That gap is the story, and it is not unique to TSA.

The Order That Ended Tuesday

Task order 70T03025F7667N084 was awarded on September 23, 2025 to Blue Tech Inc. The line item reads "salesforce software as a service licenses." The value was $15,611,331.31. It ran on NASA SEWP as a total small business set-aside, drew six bidders, and its period of performance ran from September 19, 2025 to August 11, 2026.

Eleven months. Not a base year with four option years. Not three years with a renewal clause. Eleven months, then back to the market.

The replacement landed on Tuesday, on the same vehicle, with the same reseller, on the same 11-month shape. TSA did not reduce its commitment to the platform. It re-signed for the shortest interval that still covers a full budget cycle.

Three Orders, One Anniversary That Keeps Moving

Pull the three awards side by side and the pattern gets sharper.

In September 2023, task order 70T03023F7667N057 went to Blue Tech for $14,596,464.31 as a HUBZone set-aside against a DHS indefinite delivery vehicle. Two bidders. In September 2024, task order 70T03024F7667N096 went to Blue Tech again, this time for $16,482,645.65 on DHS FirstSource II, still HUBZone, still two bidders, running to September 12, 2025. Then the 2025 order above: a different vehicle, a different set-aside, six bidders, and a lower number.

Three things moved at once in the 2025 cycle. Competition tripled, from two bidders to six. The price came down 5.3 percent against the prior year. And the term contracted, from roughly twelve months to eleven.

That third change has a compounding effect nobody planned. The 2024 order ran to mid-September. The 2025 order ended on August 11. The renewal anniversary has walked five weeks earlier in the calendar, and it will keep walking as long as each cycle is trimmed. A component that once made this decision once a year now makes it slightly more often than once a year.

One caveat before anyone reads too much into the flat spending line. These orders cover licenses only. Implementation and run services are bought separately, which is why TSA also has a Salesforce Center of Excellence task sitting with a different vendor entirely. The license number is not the program budget. It is the platform rent.

The Headline Contracts Have the Same Shape

The interesting part is that the pattern scales up rather than disappearing.

The VA award announced on July 24 is described as a three-year Agentic Enterprise License Agreement with a $1.6 billion value, covering Missionforce, Agentforce, Slack, MuleSoft, Tableau and Data 360 for more than 17 million veterans. Read the structure and it is a one-year agreement with two one-year options. The department committed to year one. Years two and three are decisions it has not yet made.

GSA's ADVANTAGESELECT Salesforce Enterprise License Agreement BPA carries a ceiling of $408,566,100. It was awarded to Carahsoft in July 2024 on the GSA Multiple Award Schedule with a single bidder, and the action obligation at award was $0.00. A blanket purchase agreement is a negotiated price list, not money that has changed hands.

Underneath both, the actual obligations look like TSA's. CBP's Office of Information and Technology holds a $24,982,017.25 order for Salesforce PaaS licenses through Carahsoft. USCIS ran an $11,571,146.80 task through SEWP for what the description calls annual license subscriptions and maintenance, with a twelve-month period of performance and three bidders.

Ceilings are multi-year and headline-sized. Obligations are annual or shorter. Both facts are true at the same time, and only one of them makes the press release.

Why Eleven Months and Not Three Years

Three forces are pushing in the same direction, and only one of them is about Salesforce.

The first is appropriations. Federal money is authorized against a fiscal year that ends September 30, and continuing resolutions have made the start of that year unreliable for several years running. A contracting officer who commits three years of license spend against money that may arrive late is taking a risk with no upside.

The second is the true-up. A short term lets a component recount seats, drop entitlements it stopped using, and add ones it now needs without waiting for a recompete. When an agency is mid-modernization, that flexibility is worth more than whatever multi-year discount it gives up.

The third is new, and it is the one worth watching. Agentic capability is not priced like a seat. Consumption-based components move with usage, and usage for an agent program that went live this quarter is a forecast rather than a fact. Nobody signs a three-year commitment against a rate they cannot yet model. Short terms are what buyers do when the unit of purchase is still being defined.

There is a fourth reason specific to the current procurement climate. GSA's OneGov push has been landing government-wide pricing agreements with expiry dates attached: the Salesforce collaboration announced in May 2025 put Slack Enterprise Grid at a 90 percent reduction and Slack AI for Enterprise at nearly 70 percent off per user, priced through November 30, 2025. When discounts arrive government-wide and then lapse, being locked into a long term means being locked out of the next one. Short cycles keep an agency at the table.

What the Cadence Does to Your Architecture

If you build on Salesforce for a federal customer, or for any customer whose renewal is an annual true-up, the entitlement set is a moving input to your design rather than a fixed one.

That has three practical consequences.

Keep a written map of every feature your design depends on against the entitlement that pays for it. Shield encryption, sandbox count, Data 360 credits, agent actions, MuleSoft connections. When a renewal trims one line, you want to know within an hour which flows and which agent topics are affected, not during the incident review.

Design so that a reduction degrades a capability instead of breaking a transaction. An agent topic that loses an action should fall back to a human queue. A flow that loses a premium connector should log and defer, not fail the record save. Graceful degradation is ordinary engineering practice, and a short renewal cycle turns it into a procurement requirement.

Instrument consumption from the first day of the term. The renewal conversation is now a usage conversation, and the evidence has to already exist when the window opens. On an 11-month order, the window opens around month eight.

The same discipline applies well outside government. Any customer buying agentic capability on a consumption line is going to ask the same question at renewal: what did we actually use. Teams that can answer with data keep their entitlements. Teams that answer with a roadmap lose them.

What August 26 Will and Will Not Tell You

Salesforce reports Q2 FY27 after the close on Wednesday, August 26, with the call at 2:00 p.m. Pacific. Guidance for the quarter was set at $11.27 billion to $11.35 billion, up 10 to 11 percent year over year. Agentforce annual recurring revenue was $1.2 billion at the end of Q1, up 205 percent.

Public sector wins are announced as ceilings and recognized as obligations, so none of the award values above will show up in a revenue line the way the headlines imply. The figure that carries the signal is current remaining performance obligation, because that is where a one-year federal commitment lands and where a three-year one would have landed differently.

If federal buyers keep committing in one-year slices while the platform pitch is a multi-year agentic transformation, that shows up as growth without duration. It is a real business, and it re-prices every year.

Also This Week

Salesforce ran a developer webinar on Tuesday titled "A Salesforce Developer's Guide to Headless 360," covering API and CLI-first patterns, Model Context Protocol connections, Slack as an orchestration surface, Trust Layer guardrails, human-in-the-loop confirmation gates and idempotent event handlers. If you are building agent actions that write to records, the last two items on that list are the ones to take away.

The two-day Virtual Community Sprint for nonprofit and education teams runs Tuesday and Wednesday, with Declarative Lookup Rollup Summaries and the Agentforce Nonprofit Best Practices Asset Hub among the assets being worked on. Community sprints are the reason DLRS is still maintained, which is worth remembering the next time you install it.

On the release calendar, Winter '27 pre-release org signups open Thursday, August 13. The release notes publish August 19, sandbox preview opens August 28, and production upgrades start the weekend of September 4. Preview orgs went live Monday, so the Flow Builder canvas rewrite is available to test now rather than after the notes drop. Dreamforce follows on September 15 to 17 at Moscone.

What To Do Next

Find the end date on your own Salesforce agreement and count backwards 90 days. That is when your renewal conversation actually starts, and it is almost certainly sooner than your calendar says. Then open your org's setup and write down two lists: every premium entitlement you are paying for, and every one your production configuration actually calls. On a short term, the difference between those two lists is the entire negotiation, and the side with the measurements sets the price.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He writes and edits salesforcedictionary.com, published by KineticBit Inc., to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.