SynapticThe Next Computing Bill
Chapter 09 · Interactive edition

The database collects its toll

A bank can buy a cheaper answer and still run up its warehouse bill. Follow one approved question all the way to the meter.

The bank has issued two receipts for the same payment. One says Friday. The other says Monday. A customer wants to know which date counted towards her bill. A model can give a perfectly sensible account of weekends, settlement windows and posting delays. Someone at the bank still has to establish which rule applied to this payment, what the ledger contained on Friday evening and whether the adjustment made on Monday changed the answer. The customer has already supplied the bank with everything it needs. The bank has put those things in different places.

Suppose an outside company offers to deliver the answer and its supporting entries to a case officer for ninety cents. Its sales director might reasonably see a route into an established data platform’s business. I would ask her to bring a second person to the meeting, the engineer who can tell us how many times the warehouse started while her agent was doing the work. The platform can lose the customer’s first click and still get paid for almost everything that happens afterwards. In a contract priced by consumption, an enthusiastic competitor can be an excellent customer.

Three numbers a buyer could recognise

In its 2025 update, Gartner forecast $161 billion in worldwide database management system spending for 2026. That category covers a great deal of work unrelated to our question, including databases that record sales as they happen. Some of the work our agent needs, such as maintaining a business glossary or correcting an old payment rule, can sit in a services contract outside that market. I use the forecast to locate an established budget. Applying a prospective percentage loss to it would require evidence about the jobs buyers actually move. 28

Snowflake’s filing offers a more precise view of one company. It earned $1.491861 billion in product revenue in the three months to July 31, 2026. Its professional services and other revenue brought the quarter’s total to $1.546793 billion. Holding product sales at the July quarter’s pace for four quarters gives $5.97 billion. An investor wanting the trailing four actual quarters can add the four rounded quarterly figures in the same filing and obtain about $5.21 billion. Growth accounts for the difference. Choosing between those numbers changes the apparent size of the business by roughly three quarters of a billion dollars without changing one customer order. 31 51

Databricks said on August 13 that it had crossed a $7 billion revenue run rate. In that announcement it also reported more than a thousand customers consuming its products at annual rates above $1 million, including more than a hundred above $10 million. A reader can take from this something more concrete than a valuation. There are individual accounts in which changing how a fraction of the work gets done can matter to both parties. Databricks supplies thresholds at a particular time. Snowflake supplies recognised sales over a fiscal period. Precise relative market shares would require comparable numerators and a common market definition. 32

The Snowflake filing also puts a name to the party beneath the platform. Third-party cloud infrastructure, including resources used for inference, represented about 75 per cent of its $434.4 million cost of product revenue that quarter. The denominator is the cost of delivering the product. The share of the buyer’s dollar going upstream will differ. When a platform customer and a cloud operator both announce a new AI contract, it is worth checking whether there was only one buyer at the start of the chain. The same inference run can appear in the platform’s revenue and the infrastructure supplier’s sales. 51

A saving the engineers already found

A good outside bid should have to beat what a competent data team can do for itself. Zendesk engineers Neilson Zanotti and Anatoly Mikhaylov published an instructive example. They copied three of their largest data models, cloned the production workflows and ran them in parallel against different warehouse configurations. Each configuration processed the same input. The engineers reported a reduction of over 80 per cent in credit costs from sizing the warehouses appropriately and described bringing additional work onto Snowflake with the capacity they had freed. The comparison concerns particular workloads and configurations. The engineers gave no company-wide before-and-after cash invoice. 52

There are two buyers an AI sales team could meet at that company. The first owns a set of costly jobs and can document what it took to reduce their consumption. The second owns an unmet demand for analysis and can use the headroom immediately. The first buyer’s evidence establishes a saving on the work tested. The second buyer can cause total consumption to rise in the same month. It would be quite a trick to sell an AI service against the former’s supposed waste while leaving the latter’s order out of the budget.

Back at the bank, a plausible source of waste is a daily job that reconstructs the payment calendar independently for each department. Another is the analyst who reruns the same extract because a case officer cannot see when the first one was made. Remove the redundant job and publish a dated extract. Those improvements deserve a price of their own in the tender. Some repeated reads will survive. The Monday officer may need both Friday’s official position and the later corrected record. Combining them into one current view can shorten the query log while making it impossible to establish what the bank told its customer.

What the officer is allowed to know

Follow the question through five layers. The bank retains a versioned copy of the ledger. A permission check determines which entries the officer may inspect. Retrieval brings back the payment, the posting history and the dated policy. A model composes an explanation. The bank keeps a record of the sources used, the decision and the reviewer. In one arrangement the platform supplies the whole service. In another the outside company organises the search and prepares the answer, while the bank continues paying the platform that holds the records. Select either arrangement in the cutaway and inspect what each party supplies.

Exhibit 22 / Governed query model

The governed query

Trace the answer to a disputed posting date from the bank’s records to an auditable decision. Select a layer to inspect its owner and meter. Refuse permission to see which stages still run.

Governed query sectionExternal orchestration
ArchivePermissionRetrievalGenerationAudit
Retrieval · warehouse creditData platform

Authorised. The bank can accept the answer after reviewing its evidence.

Inspect a layer
Retrieval

Bring back dated evidence. A fully eligible cache hit avoids this warehouse wake.

$3.90 per credit on a one-credit/hour warehouse. Each cold start pays at least one minute.
Read the five meters
External route · assumed billing units
StageSupplied byBilling basis
ArchiveData platformCorpus per month
PermissionData platformSubmitted request
RetrievalData platformWarehouse credit
GenerationAI supplierAccepted answer
AuditData platformSubmitted request
Figure 22. A single request, read from the archive upwards. The native offer bundles all five stages. The external bid leaves the warehouse, access control and evidence trail with the platform. The route is an illustration of capabilities described by both vendors. Prices in the model are stipulated bank terms. Snowflake evaluation · Databricks authorisation

The permission check comes before reuse. Yesterday’s senior officer had access to two accounts. Today’s officer has access to one. Both can type exactly the same question. Databricks documents an option for an application to act on behalf of its user. The user’s existing Unity Catalog permissions apply within the scopes granted to the application. The company separately describes how an agent can call tools and retain traces for inspection. These mechanisms give the buyer something to test with the actual roles in its bank. An application running solely under its own service identity can have a different entitlement from the employee at the keyboard. 18 53

Snowflake’s rules for reusing a stored query result illustrate the same point from another direction. Privileges, unchanged underlying data, query text and configuration can all affect eligibility. A reusable database result also differs from a previously generated letter to the customer. The figures here count a cache hit when all the evidence for an attempt can be reused under the current permissions and freshness rules. The agent still prepares a response and the reviewer still decides what to accept. Revoking access stops a retrieval. An audit entry can record that the system refused the request. There is no payable accepted answer on that file. 54

A supplier engineer might object that a good agent can find another way to answer. That is precisely what the bank has to test. Snowflake published a synthetic lending evaluation in which eight of forty correct baseline answers took an unexpected tool path. In a separate run, evaluating forty questions at on-demand prices came to about twelve dollars, including both judges and warehouse work. The example uses an Enterprise account on AWS in Dublin. It tells us how the authors priced a particular evaluation and why they examined the route to an answer. No customer reached a bank decision for thirty cents on the strength of that experiment. 17

A bid for nine thousand answers

Give our illustrative bank ten thousand authorised questions a month. The buyer accepts nine thousand after a thirty-day reopening window. The other thousand go to its existing exception desk under either contract. The bids stipulate the same mix of cases, the same escalation time and the same evidence and acceptance standard. One buyer payment covers the service even if an accepted case needed two attempts. Both suppliers have already qualified at this renewal. First-time installation, unchanged bank salaries and the cost of the common exception desk sit outside the comparison. A buyer changing any of those terms should reopen the prices too.

The current platform bill for this work is $12,600 a month. The platform offers a new all-inclusive price of $10,350, equivalent to $1.15 for each accepted case at the stated volume. The outside company quotes ninety cents for the answer. A director comparing the two quotes might conclude that the newcomer saves a quarter on every case. That quarter has to pay for a considerable amount of work. Under the split contract, the bank still pays the platform $900 a month to retain the records and another $300 for authorisation and the audit trail. These are assumed commercial terms. The two vendors in the reporting above have offered this hypothetical bank no such tariff.

Now turn to the warehouse. Assume one question in ten needs one fresh attempt. That produces eleven thousand retrieval attempts across the month. Half can reuse all the evidence they need. Each of the remaining 5,500 wakes a dedicated warehouse, makes six consecutive twenty-second queries, then suspends it. Under the illustrative one-credit-an-hour configuration at $3.90 per credit, two minutes cost thirteen cents. The month’s bill for the warehouse comes to $715. The rate uses the Dublin platform-credit example in Snowflake’s guide. The figures use its documented minimum of sixty seconds per provisioning and subsequent billing by the second. The duration, isolation of workloads and immediate suspension are our assumptions. 17 55

Exhibit 23 / Cost sensitivity

How often will the warehouse wake?

The bank receives 10,000 authorised requests and accepts 9,000 answers a month. Price the outside bid at forty combinations of evidence reuse and query count. The platform’s competing offer is $1.15 per accepted answer.

The price of an accepted answer

External route

Select a cell. The first minute of each cold warehouse wake is billable.

USD per accepted answer · queries per uncached attempt across the top
Reused1234681012
100%1.031.031.031.031.031.031.031.03
75%1.051.051.051.061.071.091.101.11
50%1.071.071.071.091.111.141.171.19
25%1.091.091.091.111.151.191.231.27
0%1.111.111.111.141.191.251.301.35
Below the native bidAt or above $1.15

USD · AWS EU Dublin · 20 November 2026. The model uses the guide’s $3.90 platform credit and an assumed one-credit/hour configuration.

6 queries · 50% evidence reuse

Cold warehouse wakes
5,500
Warehouse bill
$715
External route, all in
$10,015
Per accepted answer
$1.1128
Awarded AI revenue
$8,100

The outside bid wins. The bank saves $335 against the $10,350 native renewal.

Trace the cash and the acceptance rule

Each uncached attempt runs all its twenty-second queries in sequence on a newly provisioned warehouse. Every initial request pays one permission fee ($0.02) and one audit fee ($0.01). Retries are included in both fees. The storage bill is $900 per month. The lab asks $0.90 per accepted answer. Below the native price the lab wins, and the platform receives the residual storage, control and compute charges. At a tie the bank retains the incumbent. The $10,350 native bid includes all these functions. A lower quote still has to deliver the same 9,000 accepted answers, escalation time and thirty-day reopening standard. The refused file in Figure 22 falls outside this authorised cohort.

On the proposed external route, the bank pays $8,100 to the lab and $1,915 to the platform. The lab’s fixed delivery expense of $900 and variable costs of $0.60 per accepted answer leave $1,800 before corporate overhead if it wins.

Figure 23. Horizontal movement changes the queries per uncached attempt. Vertical movement changes the share of attempts with fully reusable evidence. Cells show proposed cost; the award uses the unrounded amount. Retries change warehouse activity while accepted output stays fixed. Each row’s first three cells share the same price because they fit within the sixty-second minimum. Billing rule · Regional price example

Add the invoices. The bank pays $8,100 to the lab and $1,915 to the data platform, a total of $10,015. The bank keeps $2,585 compared with its current agreement. It could already have kept $2,250 by accepting the native offer. Winning the argument for this particular lab therefore puts an additional $335 in the buyer’s hands. Of the $8,435 in platform receipts at stake relative to the native renewal, $8,100 changes payee and $335 stays with the customer. A headline about the bank saving $2,585 would give the challenger credit for a concession the incumbent had already put on the table.

The outside supplier needs another calculation before it signs. Suppose its own inference, support and review cost sixty cents for each accepted case, including its spending on attempts that failed, and it carries $900 of fixed monthly delivery cost. The contract yields $1,800 before corporate overhead. The most the lab could charge at buyer indifference in the default workload is $8,435 a month, just under ninety-four cents per accepted case. A competitive fee has to leave something below that ceiling for the bank. A lab with a more expensive remediation desk might find a customer willing to buy at ninety cents and still be wise to decline.

How a cheaper model can enlarge the bill

The first three columns of the heatmap have identical prices in each row. A cold warehouse running one twenty-second query is charged the sixty-second minimum. Three consecutive queries still fit within that first minute. A fourth runs the clock to eighty seconds. Batching enough useful work into an already paid minute can improve the result without another cent of warehouse expenditure. Sending each of those queries to its own cold cluster would give entirely different economics. So would running them on a warm shared warehouse that has paid for the minute anyway. The exhibit exposes the assumption because it can decide the winner.

Choose twelve queries per uncached attempt and leave the cache hit rate at one half. Warehouse spend rises from $715 to $1,430. The platform receives $2,630 on the proposed external route. The buyer would spend $10,730 in total and can accept the platform’s $10,350 renewal instead. A lab hoping to get in by cutting the price of inference now has to take at least $380 out of its quoted fee to reach a tie. In this model the bank keeps the incumbent at a tie, so the lab has to concede a little more to win. The heatmap shows the cost of the proposed route even when the buyer would decline it. A losing proposal earns zero.

There is another way for an AI company to increase platform revenue. A regional office that once put questions on a list for Friday can now submit them throughout the day. Its staff discover errors before statements go out. A successful pilot spreads to five other offices. Even if the warehouse cost per accepted case falls, the number of accepted cases can rise faster. That is valuable new demand. A financial account that silently treats every new question as a query transferred from an existing workload will exaggerate the old vendor’s loss and understate what its infrastructure helped create.

The incumbent’s best bid

A data platform has a credible route into the customer’s work surface. On November 11, Databricks announced a version of Genie intended to carry out long-running work and bring decisions back to business users. Its materials describe access across sources well beyond the company’s own tables. A buyer can use that announcement to invite an additional bidder. The commercial test is whether the platform can complete the same mixed queue, subject to the same release rules, for less than the outside team. An outside lab answering questions across several competing platforms could still have an advantage with a bank that wants a portable workflow. The price of moving its evidence and its acceptance tests becomes part of that advantage. 57

I would request one month of linked records before accepting either account of the opportunity. For each case, show the submission, authorisation, attempts, query identifiers, evidence version and reopening outcome. Join those to the charges the buyer actually incurred. Snowflake’s per-query attribution view excludes warehouse idle time. Its credit totals cannot by themselves price a warehouse that spent much of a shift waiting for work. Reconcile the warehouse meter to the account invoice, then check the commitment. Credits left unused under a minimum purchase can become capacity for a later job. They turn into a near-term cash saving only if the contract lets the buyer pay less or avoid another purchase. 56

The hardest question at the second renewal is who still knows how to prove an answer. A bank that owns the definitions of posting date and value date, the permission map and a set of difficult cases with agreed outcomes can invite fresh bids for the reasoning work. A bank that let its supplier keep the only working versions of those things can still switch model providers on paper. Its staff will spend the changeover reconstructing the institution’s memory. The prize for the AI company is the right to organise recurring, valuable work. The data company can keep collecting every time that work goes back to the ledger. Which one earns more turns on a fact the buyer can now inspect, how much it paid for an answer it could use.

Sources and reading notes

  1. 17 · Snowflake Cortex evaluation guide

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

  2. 18 · Databricks agent platform documentation

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

  3. 28 · Gartner, worldwide DBMS forecast, 2025 update

    $161bn forecast for 2026 DBMS. Partial proxy for data platforms. Includes cloud databases, excludes some engineering, orchestration and governance.

  4. 31 · Snowflake fiscal 2027 quarterly results

    FY27 Q2 to July 2026, $1.49bn product revenue. Consumption revenue differs from contracted ARR.

  5. 32 · Databricks Q2 announcement, 13 August 2026

    Company-reported run rate above $7bn. Method and audited annual sales are separate questions.

  6. 51 · Snowflake, Form 10-Q for the quarter to 31 July 2026

    Note 3 gives $1,491.861m product revenue. The segment table reports third-party cloud infrastructure expenses at approximately 75% of cost of product revenue in the quarter. Those percentages use different denominators.

  7. 52 · Zendesk engineers on parallel warehouse tests, 25 November 2025

    The authors cloned three large data models and their production workflows. They report more than 80% lower credit costs on right-sized warehouses. Customer-authored on a Snowflake publication. The whole-company invoice and the cost of the newly added workloads are unavailable.

  8. 53 · Databricks Apps, authorisation on AWS

    User authorisation enforces the user’s Unity Catalog permissions within the app’s approved scopes. App authorisation uses its own service principal. Product capability depends on configuration.

  9. 54 · Snowflake, reusing persisted query results

    Conditions include query text, data, role privileges and configuration. Eligibility does not guarantee result reuse. This differs from a cache of a previously generated answer.

  10. 55 · Snowflake, warehouse billing and sizing

    One-minute minimum on provisioning, then per-second billing. One-credit-per-hour X-Small example. The exhibits assume an isolated, immediately suspended warehouse episode. Shared production workloads have different effective costs.

  11. 56 · Snowflake, query attribution history

    Compute attribution per query excludes idle time and other service categories. Reconcile with warehouse metering and the customer contract before claiming cash savings.

  12. 57 · Databricks announces the second generation of Genie, 11 November 2026

    The company describes proactive work and connections across enterprise data sources. Product announcement. Platform usage, customer cash savings and retention are separate measurements.