SynapticThe Next Computing Bill
Chapter 08 · Interactive edition

What becomes of a seat?

A seat disappears from the renewal. Follow the money that returns to the buyer, the fees the platform keeps and the price an AI supplier can defend.

The most expensive person on the bank’s software bill may be somebody who left in February. Their manager returned the laptop. Payroll stopped the salary. A name survived on an order form, where it costs exactly as much as the name of the colleague who opens the application every morning. An AI company bidding for the bank’s work would love to lay claim to that money. The first person I would invite to its sales presentation is the buyer who can take the name off for free.

Consider a different employee. She opens the case system to find the disputed transaction, checks a second window for the merchant’s response and types a summary into a third. Her account shows activity every working day. A software inventory will give her seat a clean bill of health. Yet an agent that can assemble the evidence, preserve the links to the original entries and submit the file for her approval might remove the need for her to hold the full licence. The seat that looks indispensable in the usage log is the more interesting commercial prospect. Winning it requires someone to change how work gets done. The buyer can settle the departed employee’s account with an email.

A portfolio, a market and a seller

What does a business actually spend? Among organisations in Zylo’s 2026 SaaS Management Index, median annual software-as-a-service spending was $20.6 million. The mean was $55.7 million. The corresponding portfolio counts were 240 applications at the median and 305 on average. Those are customers visible to a software management provider. A provincial architecture practice with twelve employees has little reason to expect either bill. Even inside this dataset, the mean would give a procurement director a substantially larger comparison budget than the median. Neither tells her what a given application costs without the contract. 34

For a worldwide measure I use Futurum’s forecast for the SaaS delivery of enterprise applications across its twelve product segments. The April 2025 forecast put calendar 2026 at $323.3 billion. Its publication date was July 2025. This gives us a denominator with a date and a boundary. Payroll for the employees using those applications is outside it. So are the consulting invoices for redesigning their jobs. Those expenses may fund the same AI purchase. A seller that gets paid from three budgets can report one sale while an analyst who claims the entire sale against each industry has manufactured two extra markets. 26

Look from the other side of the invoice. Salesforce reported $10.8 billion of subscription and support revenue in the quarter ended July 31, 2026, including $440 million from Informatica. Four quarters at that pace would yield about $43.2 billion. This annualisation holds the July quarter constant. Salesforce separately reports recurring-revenue metrics for particular products, and neither measure is a count of removable human seats. A company can lose a thousand logins at one bank, add a data subscription at another and collect a larger support payment from a third. Looking at aggregate growth, an investor would have no way to reconstruct any of those three renewals. 29

What a buyer has already taken back

Flexera published an unusually revealing account of buying software for its own employees. It signed a three-year agreement worth $46 million, covering a mixture of SaaS, cloud and installed software. Its report assigns $1 million to hard savings on SaaS and $1.5 million to hard savings on the other licences. It records a further $4.5 million under cost avoidance. More than 300 duplicate productivity seats came out after an acquisition. Flexera sells the management tools its team used. The figures are its account of the negotiation, and it has not released the two invoices that would allow a reader to reproduce the calculation. 38

The distinction matters even if you accept every dollar. One set of terms reduces what the buyer has to pay. Another prevents a price increase the seller wanted. Both make the finance director better off than signing the opening offer. Only a fraction of the headline belongs to SaaS, and none of the reported savings establishes a fee paid to a model developer. Procurement has bargaining power of its own. Treating the entire improvement as a prospective AI sale gives the challenger credit for a negotiation it never attended.

Zylo puts a value on the discrepancy it sees across customer estates. Its buyer guide reports that 54 per cent of purchased licences are used and estimates about $19.8 million of annual unused spend for a typical large organisation. The percentage counts licences. The dollar figure values entitlements. Applying the unused fraction to every dollar of the global forecast would assume the same price for every seat, comparable activity across every vendor and a right to cancel every idle entitlement. The evidence establishes none of those conditions. It does tell a buyer where to start looking. 43

An audit of our hypothetical bank would begin with an awkward conversation about the definition of use. A recovery officer might sign in only when a payment system fails. A supervisor who approves quarter-end adjustments may look dormant in a February extract. A test account may be indispensable to the team that releases changes. Someone needs to establish what happens when each identity goes away. The quickest route to an impressive saving on a spreadsheet is to remove the people the business needs on its worst day. The first live incident is an expensive time to discover the error.

The same care applies to time. Suppose a revised workflow saves three minutes on each of 20,000 accepted cases. That is 1,000 staff hours over the year. Ask the branch manager where those hours go. If the team closes a backlog during regular shifts, customers receive faster service. If an agency agreement falls by a thousand billed hours, cash comes off a different invoice. If nobody changes the roster or the queue, follow the cases to find out whether the saving was measured end to end. In the subscription comparison below I give the bidder zero credit for payroll. A second budget can be introduced when its owner can identify the expenditure it will release.

The price of the hundred and first seat

Give the bank a thousand seats at a negotiated $600 per year. Its annual invoice is $600,000. An internal review finds 160 seats with very little recent activity. Sixty have a continuing purpose, including seasonal reviews and emergency cover. The other hundred can go in the ordinary renewal. Ask for two quotes on the same afternoon. One simply trims the estate. The other changes how the bank prepares the file, so another 120 employees can do their jobs without full access. Assume the access rights for the substitute workflow have been agreed in writing. Otherwise the buyer has a demonstration and a licensing question.

Exhibit 20 / Renewal model

The missing seat and the new action

Start with 1,000 bank seats at $600 each. Procurement can remove 100 on its own. A different workflow could release 120 more. Test which savings survive the contract.

Where the old seat bill goes

Sankey · year one

Winning route · AI supplier. Ribbon width measures annual dollars.

Old bill$600kPaid$524kKept$76k
SaaS vendor$488,000
AI supplier$30,000
Transition$6,000
Baseline saving$60,000
Extra saving$16,000

AI supplierOf the $30,000 fee, $22,000 covers delivery and $8,000 remains before overhead.

Seat discounts and action charges
Buyer’s fee ceiling$46,000
Supplier delivery cost$22,000
AI revenue at this bid$30,000

At a $30,000 bid, the supplier takes 5.0% of the original seat bill. The buyer saves $16,000 against its best alternative. The supplier has $8,000 left before overhead.

Inspect the before-and-after invoices
One year · USD · same 20,000 accepted cases
Current seat bill$600,000
Renewal after ordinary cleanup$540,000
Best qualifying alternative$540,000
Remaining seats with AI$480,000
Metered actions with AI$8,000
First-year transition$6,000
Supplier bid$30,000
Total first-year buyer cost at bid$524,000
Buyer advantage at bid$16,000
Fee ceiling at buyer indifference$46,000
Supplier delivery cost$22,000
Supplier revenue if awarded by model$30,000
Contribution if awarded, before overhead$8,000
Figure 20. Illustrative bank, first year. The Sankey reconciles the old $600,000 bill to first-year outlay and money the buyer keeps. The benchmark saving is available through the best competing renewal. The frontier holds discounts and action charges fixed while varying both contract terms. Each award requires a lower total cost than the best alternative and a positive supplier contribution. Action price basis
Model, prices and acceptance rule

The current invoice and cleanup quote use $600 per seat. The AI route applies its own discount to an assumed $750 list. The floor applies to both seat routes. The optional incumbent bid is a separate, all-in offer for the same service. The buyer pays any metered actions above its allowance at $0.10 each, plus $6,000 of first-year transition cost. The supplier pays $0.70 per case and $8,000 fixed for delivery. All three routes preserve the same service, exception handling and bank approvals. Unchanged operating costs cancel. Time released has zero cash value here. These are scenario terms. Salesforce publishes the underlying credit and standard-action prices.

At an 800-seat minimum, ordinary cleanup takes the bank to 900 seats and $540,000. The revised workflow needs 780 full seats, yet the supplier will bill 800. The seat order therefore comes to $480,000. Of the $120,000 apparently removed from the original renewal, exactly half was available to the bank without the lab. The last twenty technically redundant seats still have a buyer. This is why the size of a price concession can turn on a purchasing clause that nobody on the AI project team has read.

Now let the application vendor charge for some of the work the agent performs inside it. Salesforce lists 100,000 Flex Credits at $500 and a standard Agentforce action at 20 credits. The resulting list price is ten cents per standard action. Our contract assumes five metered actions for each of 20,000 accepted cases, with 20,000 actions included in the annual agreement. That leaves 80,000 to buy, or $8,000. An actual bidder would need a trace showing which operations invoke those meters. Ordinary API requests have their own terms. Counting every database read as a paid Agentforce action would be as careless as assuming all execution is free. 16

The bank pays $6,000 in the first year to qualify the new route and migrate the files. Before the AI supplier collects a cent, the buyer has committed $494,000. Against the $540,000 cleanup alternative, the most the bank could pay for the AI service and still break even is $46,000. The lab quotes $1.50 for each accepted case, or $30,000 for the year. Its customer spends $524,000 and retains a $16,000 advantage over ordinary cleanup. The lab earns five cents of each dollar on the original seat bill if it wins. The customer’s total saving against the old invoice is $76,000. Those two gains have different owners.

When the deal can clear

There is a seller’s reservation price too. Assume that inference, exception review and support cost the lab seventy cents per accepted case, and that it must spend another $8,000 a year to keep this customer running. At the stated volume, delivery costs $22,000. A $30,000 contract leaves $8,000 to cover corporate overhead and reward the capital at risk. At $22,000 the buyer would like the deal more, and the supplier would have nothing left for either purpose. This gives both sides of the bargaining range. On these assumptions, a price above $22,000 and below $46,000 gives the parties something to divide.

Invite the incumbent to the table. It puts an all-inclusive $520,000 offer in front of the bank for the same accepted work. The most the lab can now charge at buyer indifference falls to $26,000, because the other $494,000 of its route is already spoken for. Its original $30,000 bid loses. A revised price of $1.20 per accepted case would produce $24,000 of revenue, $2,000 of contribution before overhead and $2,000 in savings for the customer against the incumbent bid. A single difficult implementation could consume the supplier’s entire cushion. A business that can persuade investors it has access to a large pool of annual subscription spending may still walk away from this particular bank.

Try the 900-seat floor in the exhibit. At the original seat discount, the bank would owe the same $540,000 for seats under both designs. Actions and transition then make the external route more expensive before anyone charges for intelligence. Or keep the 800-seat minimum and remove the volume discount on the smaller AI-assisted order. At $750 each, the remaining seats alone cost $600,000. This is the commercial force of a bundle. Engineers can show a hundred employees finishing their work without the full application. The vendor can acknowledge the demonstration and present a revised price schedule that absorbs the benefit.

An AI supplier has a defensible answer when it can change more than the count. It might keep the expensive application for authorised writes and give the bank a cheaper independent work surface for preparing evidence. It might demonstrate that a light-access licence really covers the supervisors who approve its work. It could finance the transition against a longer commitment. Each proposal moves a specific term of the comparison. Financing pushes a cost into a later year. A cheaper licence requires written rights. A longer commitment asks the customer to surrender some of the competition it would otherwise enjoy at renewal. Those concessions have prices of their own.

The incumbent can sell the result

On September 10, 2026, Salesforce completed its acquisition of Fin, formerly Intercom. A week later, Fin’s billing guide described a $49 monthly plan including 50 resolutions on a customer’s helpdesk and a charge of $0.99 for additional outcomes. Read the definition before comparing that number with the bank’s $1.50. Fin can count a resolution when a customer confirms success or stops asking for help after an answer. A configured procedure that successfully hands the matter to a human can also count as an outcome. Our bank pays on an accepted case file. Silence, a handoff and a reviewed disposition are three different things a supplier can competently deliver. The procurement document must specify which one the buyer is purchasing. 39 40

Salesforce’s acquisition changes the arithmetic of market share. A company can retire seats, move support work onto an outcome-priced service and still send the new revenue to the same corporate group. For the product owner, that is a considerable change in how software works. For the shareholder predicting a transfer out of Salesforce, the identity of the payee settles the question. There is a related possibility for Anthropic. Its August partnership announcement with Salesforce describes both Salesforce skills inside Claude and Claude reasoning inside Salesforce. The document gives a prospective customer two places to begin work. It gives an analyst no price split from which to infer who earns more on a completed case. 41

Exhibit 21 / Contract scenarios

Who can raise the price?

Keep the same bank and the same disputed payment. Change who runs the workflow and see who can set a price at renewal.

Responsibility by capability and contracting party. The coloured cells mark the lead role.
CapabilityBankAI supplierSaaS platform
IdentityWho may act?Lead role. Sets authorityUses a delegated identityEnforces permissions
OrchestrationWho sequences the work?Sets acceptance rulesLead role. Runs the case and quotes the next oneExposes approved actions
ExecutionWho can commit a change?Approves exceptionsCalls the authorised actionLead role. Validates and writes
Case recordWho can reproduce the decision?Requires an exportKeeps the work traceLead role. Retains the case history

The lab can reprice the completed case. The platform can reprice the actions the lab needs. A bank that cannot export the history has two renewals to negotiate.

Figure 21. Each coloured cell marks the lead party for one decision in a hypothetical agreement. One party can control the workflow while another controls the authorised write. Product documentation supports the capabilities. The allocation of bargaining power is the author’s inference.
Product evidence behind the scenarios

Salesforce documents the external identity for its Agent API and the action meter. The Claudeforce announcement describes workflows that start in either company’s interface. A Snowflake lending-agent guide shows a separately metered data path. Databricks Agent Bricks documents Unity Catalog permissions and stored evaluation traces. Export rights and renewal terms require the customer’s contract.

For the bank, the most valuable part of an application may sit several steps away from the interface its employees see. An external system calling Agentforce needs an authorised client and an identity permitted to act. Someone still owns the rules for changing an account. A financial workflow can also invoke services outside the CRM. Snowflake’s lending-agent guide distinguishes charges for AI from warehouse usage. Databricks documents permissions over the data and tools an agent can use and traces that can be stored for later examination. A lab bidding a fixed price has to find out which of those bills comes to it, which goes to the customer, and who answers when a case crosses the boundary between them. 42 17 18

I would ask the three bidders to return with last month’s hardest reopened case. Give each the original evidence, the policy version in force that day and the supervisor’s recorded objection. Ask for a corrected file and an itemised price for producing it a second time. A platform that owns the history may be able to do that cheaply using its existing support staff. A lab working across several applications may recover evidence the incumbent never captured. The bank that can export the whole file can put both accounts of their advantage to a test. A product demonstration built from a clean new case leaves the costliest part of the competition unresolved.

What I would count at the next renewal

There is good evidence that assistance can change throughput. Brynjolfsson, Li and Raymond studied 5,172 customer-support agents and found an average increase of about 15 per cent in issues resolved per hour with AI assistance. It is an important result for someone responsible for a queue. It also shows why employee count makes such a poor shortcut for pricing this market. A service team can use the gain to shorten waits or train new staff, still renew every seat, and willingly pay for the assistant on top. That would create a new revenue stream from better service. Calling it cannibalised SaaS revenue would assign it to the wrong budget. 20

My prediction for this market is narrower than a wholesale abandonment of enterprise software. A lab can take the renewal when the job crosses applications, the buyer can remove a contractual expense, and the lab will stand behind a result the incumbent finds costly to match. At $30,000 apiece, a hundred wins like the illustrative one would bring in $3 million over a year at the stated volume. Finding a hundred banks with the same removable seats, service level, acceptance rate and willingness to switch is the expensive part of that multiplication. A national market-share figure requires evidence on the frequency of those conditions and the price of the bids that actually win.

To count one win I would want the expiring order, a credible cleanup quote, a competing offer where available, the replacement invoices and the acceptance log for the same case mix. I would follow the contract into its second year. The migration charge should disappear, while a discount granted for the pilot might expire. If the original suite collects more in actions than it lost on seats, it has successfully changed the unit on its invoice. If the lab earns a recurring case fee and the bank keeps the saving after paying for exceptions, the predicted transfer has a customer, an amount and a date. Those are the entries worth adding up.

Sources and reading notes

  1. 16 · Salesforce Agentforce pricing

    Pricing units, credits and seat alternatives. Public list price is different from negotiated unit price.

  2. 17 · Snowflake Cortex evaluation guide

    Distinct AI and warehouse meters, geography-specific example and usage history. Do not generalise effective pricing.

  3. 18 · Databricks agent platform documentation

    Unity Catalog governance, runtime and tools. Product evidence. Unlisted Databricks financials require attributed company disclosures.

  4. 20 · Brynjolfsson, Li and Raymond, QJE 2025

    Published version, staggered introduction, 5,172 support agents, +15% issues resolved per hour. Use this version consistently.

  5. 26 · Futurum, enterprise applications market, H1 2025 edition

    Table 2, April 2025 forecast vintage. 2026 forecasts $323.3bn SaaS and $91.8bn on-premises enterprise applications. Excludes many infrastructure and middleware categories.

  6. 29 · Salesforce FY27 Q2 earnings

    Quarter to July 2026. $10.8bn subscription and support includes $440m Informatica. Separate acquisition contribution from organic change.

  7. 34 · Zylo 2026 SaaS Management Index

    Instrumented customer estate. For a renewal, distinguish entitlements, assignment, recent activity, workflow necessity and cancellability.

  8. 38 · Flexera's own three-year software renewal

    First-party account of a $46m mixed software and cloud agreement. $1m hard SaaS savings, $1.5m other hard savings and $4.5m cost avoidance over three years. No matched invoices disclosed.

  9. 39 · Fin outcome billing rules

    17 September 2026. Distinguishes confirmed or assumed resolution and configured procedure handoff. Base plan, included resolutions and incremental unit price matter.

  10. 40 · Salesforce completes its acquisition of Fin

    Closing announcement dated 10 September 2026. Buying an outcome-based service can still pay the incumbent group.

  11. 41 · Salesforce and Anthropic announce Claudeforce

    26 August 2026 product and partnership announcement. Salesforce in Claude and Claude inside Salesforce illustrate alternative locations for orchestration. Commercial splits are undisclosed.

  12. 42 · Salesforce Agent API setup

    External client app and authorised identity for calling Agentforce. Specific access depends on configuration.

  13. 43 · Zylo's buyer guide to subscription management

    Zylo's interpretation of the 2026 index reports 54% of licences used and estimates $19.8m yearly unused spend for a typical large organisation. Telemetry and estimated exposure, not audited cancellable cash.