Skip to main content
Whitepaper20 pages · September 2026

Buying Applied-AI Research: A CFO's Field Guide to Pricing, Phasing, and De-Risking an R&D Engagement

A fixed-price line item for an applied-AI research phase looks, to a finance leader, like a single number to approve or reject. It is neither single nor a number you should read on its own terms. This whitepaper reads the commercial anatomy of a multi-year subsurface computer-vision programme built for a mid-sized Middle East carbonate operator and reframes it as the questions a CFO should put to any applied-AI R&D vendor. Six levers set the price. First, effort-obligation contracting, because the deliverable is a metric nobody can warrant at signing, so paying for a guaranteed result is paying for a payout the vendor cannot honestly price. Second, milestone-tranche payments gated to phase boundaries, which convert an open-ended bet into a sequence of small, cancellable ones: on this programme the year-one agreement was paid in five tranches, each released at a phase boundary, so the buyer's real exposure at any gate was only what was sunk. Third, a contingency for requirement change, a bounded line on the face of the contract that absorbs scope drift without reopening the price. Fourth, owned-versus-rented compute, the choice that decides whether the largest recurring cost is fixed or floating, which through the 2022 energy shock meant the difference between a rental market climbing without a ceiling and a single bounded contingency for twelve months. Fifth, academic-rate arbitrage, the single largest lever, where routing delivery through a university partner lowered the day rate at every seniority band and came with a whole-phase commitment discount, so the buyer paid less for the same seniority of work. Sixth, per-head training economics, which price capability transfer into the mandays so the operator ends up owning what it paid to build. We assemble one worked phase from these levers and argue that a disciplined price is engineered from the six, while a lump-sum quote hides which of them the buyer is, or is not, getting. We describe the structure of each lever and withhold the amounts, rates and percentages, which are commercial terms between the parties. The mechanics of each lever were treated at length in earlier chapters of this programme; here they are the columns of a single buyer scorecard.

Tarry SinghTannistha Maitiby Tarry Singh and Tannistha Maiti
In this whitepaper18 min
  • IThe lump sum is a category error
  • IILever two, made concrete: exposure is only what is sunk
  • IIILever three: a contingency that is a line, not a surprise
  • IVLever four: whether the biggest recurring cost is fixed or floating
  • VLever five: the arbitrage that is the largest single lever
  • VILever six: paying for capability you keep
  • VIIAssembling one worked phase from the six levers
  • + 5 more sections
Download PDF

A finance leader who is handed a single fixed-price line for an applied-AI research engagement has been handed a summary of a decision, not the decision. The number is real. It can be defensible or hopeful, disciplined or lazy, and from the outside the two look identical. What separates them is not the digit at the bottom but the structure above it: how the work is contracted, how the money is phased, what absorbs the surprises, where the compute sits, which rate card the people are billed on, and whether the price buys the operator its own future capability or rents it forever. Read the line alone and you cannot tell. Read the six levers behind it and you can.

We write this from a specific engagement rather than a template. Over roughly three years we built and ran a subsurface computer-vision programme for a mid-sized Middle East carbonate operator: detection models for fractures and bedding planes in a fractured carbonate reservoir, and the compute-heavy training a research-grade programme consumes over years. This paper is about the other envelope, the commercial one, and it is written for the person who has to approve the spend and later answer for it. The programme's own workbooks, cost memos and signed agreements are the source for every lever described here. The client's identity and its wells are withheld, and so are the amounts, day rates, percentages and tranche sizes, which are commercial terms between the parties. What we give instead is the structure: how each lever worked, in what order it was applied, and what a buyer should ask about it.

The claim is simple and it is the spine of everything below. A CFO should price an applied-AI R&D engagement on six levers, not on a single lump sum. The six are effort-obligation contracting, milestone-tranche payments gated to phase boundaries, a contingency for requirement change, owned-versus-rented compute, academic-rate arbitrage, and per-head training economics. Five of them are questions you put to the vendor before you sign. All six are things a lump-sum quote can quietly get wrong while still footing to a plausible total.

The lump sum is a category error

Start with why the instinct to buy a fixed outcome for a fixed price fails on this kind of work specifically. In a conventional procurement, a fixed price is a discipline: it forces the vendor to absorb its own estimation risk, and it gives the buyer a clean number. That logic holds when the deliverable is knowable at signing. An applied-AI research deliverable is not. The thing being bought is a metric, a detection accuracy or a throughput, whose value nobody can commit to before the labelled data arrives and the experiments run.

On this programme the point was not hypothetical. Detection accuracy rose as labelled wells arrived, and the level it would reach was unknowable when the contract was signed. A result guarantee written at kickoff would have committed the provider to a bar the work only cleared near the very end, and would have paid perverse incentives the whole way there: it rewards safe, unfalsifiable claims over honest experiments, because an honest experiment can fail and a vague one cannot be caught failing. The correct contractual object is therefore an effort obligation, explicitly "not responsible for achieving a specific result," which prices the work rather than the outcome. That is lever one, and the full clause-by-clause reading of how such a contract is papered, effort obligation, phase-capped liability, the data-timeliness clause, and the foreground-IP split, lives in our earlier chapters on contracting an AI R&D engagement and is a pointer here, not a re-derivation.

There is a subtler failure too, and finance leaders feel it after signing rather than before. A lump sum collapses the internal structure of the price into a single figure, and a figure cannot be audited. When the programme is a year in and someone on the board asks why the number was what it was, a lump sum has no answer beyond "that is what they quoted." A price built from named levers has an answer for every line: this much was people, at this rate card, discounted this much for the whole-phase commitment; this much was a bounded contingency; this much was compute, carved out and owned rather than rented. The difference is not cosmetic. It is the difference between a spend you can defend under scrutiny and one you can only apologise for.

The lump sum's second structural failure is that it hides the phasing. A single number paid on a single schedule gives the buyer no cancellation optionality, which on genuinely uncertain research is the most valuable thing the buyer can hold. That is lever two, and it deserves the first instrument.

Lever two, made concrete: exposure is only what is sunk

The signed year-one service agreement on this programme was not payable as one sum. It was paid in five tranches, each released at a phase boundary, from a mobilisation tranche at signing to a final tranche at handover. Each gate was a real decision point, with provider phase-exit ramps after the early phases. The structure is not administrative housekeeping. It is the risk-management instrument.

FIVE TRANCHES, GATED TO PHASE BOUNDARIES60%of the approved total still cancellable at this gateYour exposure is what is already sunk, not the approved totalClick a gate to stand there: the staircase shows committed vs remaining.CUMULATIVE SHARE OF APPROVED TOTAL0%25%50%75%100%20%At signing20%Phase 1 pt 220%Phase 220%Phase 3 pt 120%Phase 3 pt 2WHERE THE MONEY STANDSapproved total100%committed / sunk40%tranche in flight20%STILL CANCELLABLE60%of the total, not yet owedVS A SINGLE LUMP SUMA lump-sum contract commits thewhole total on day one.Gates keep 60% cancellable here.PHASE-GATE STEPPERclick a step, or use arrow keys, to stand ata different phase boundarystanding atPhase 1 pt 2 · Dataset deliveredillustrative: five equal tranches as shares of the approved total · phase labels follow the programme · gate spacing is even for legibility
Paying an applied-AI research programme as milestone-tranches gated to phase boundaries turns an open-ended bet into a sequence of small, cancellable ones. This staircase plots five phase-gated tranches cumulatively, as shares of the approved total, from a mobilisation tranche at signing to a final tranche at handover. Click a gate to stand there and read the split: the committed and sunk portion in teal, and the remaining tranches that a lump-sum contract would already have committed but a gated one leaves cancellable. The orange marker is the only element that argues: the cancellable remainder at the chosen gate, which shrinks gate by gate but, until the last gate, is money the CFO does not yet owe. The five tranches and their phase labels follow the programme's signed year-one agreement; its tranche amounts are commercial terms and are withheld, so the tranches are drawn as equal illustrative shares, and the gates are spaced evenly for legibility.

The staircase above is the CFO's view of that structure, drawn with five equal illustrative tranches so that the shape, not the contract, carries the argument. Stand at any gate and the total resolves into three parts: what is already committed and sunk, the tranche currently in flight, and the remainder that is still cancellable. A lump-sum contract commits the whole approved total on day one. The gated contract, at every point before the last gate, leaves the rest of the total un-owed and walk-away-able, and early in the programme that is most of it. That cancellable remainder is the entire argument for phasing, and it is why the milestone schedule, not the rate card, is the thing a treasurer should read first.

Two properties of the tranche design are worth naming because a buyer can specify them. The first is that the gates fall on phase boundaries rather than on the calendar. A tranche released simply because three months passed rewards elapsed time; a tranche released because a phase deliverable landed rewards progress, and it gives the buyer a genuine decision at each gate rather than a rubber stamp. The second is the exit ramp. On this programme the provider could leave cleanly after an early phase on short notice, and the buyer held a short termination notice of its own. Exit ramps sound like they protect only the vendor, but they protect the buyer more: a vendor that is contractually free to walk after a completed phase has no incentive to pad a struggling programme along to keep billing, because it is not trapped. How these gates map onto the phases is treated in our anatomy of the twenty-month engagement's phases, milestones and gates. Here the five tranches are simply the columns that make lever two legible, and the lesson for the scorecard is narrow: a buyer should be able to point at any moment in the programme and say exactly how much of the approved total is still theirs to cancel.

Lever three: a contingency that is a line, not a surprise

Research changes shape as it runs. Requirements drift, a well arrives in an unusable format, a promising approach dies and a second has to be stood up. A disciplined price does not pretend this will not happen; it prices a bounded amount for it, on the face of the contract, so that the drift is absorbed without anyone reopening the number.

On the worked Phase-3 build, that line was a small percentage contingency carried on top of the discounted role stack. It is small by design. A contingency large enough to swallow any conceivable change is just a slush fund that erodes the discipline of the fixed price; one too small is theatre. A small, named percentage on a research phase is the vendor saying, on paper, "this much surprise is priced in, and beyond it we talk." The earlier phases of the same programme carried a larger contingency on their commercial engine, which tells the buyer something useful: the contingency percentage is itself a negotiable dial, and a vendor that can articulate why it chose one percentage for one phase and a different one for another is a vendor that has actually thought about the risk it is pricing rather than padding a round number.

When Phase-2 compute on the same programme ran materially over plan, at more than twice its planned GPU-hours, the overrun did not detonate the contract. It was carried through the contract's own change mechanism as an additional request rather than an emergency renegotiation, precisely because the structure anticipated that research consumes compute unpredictably. This is the part buyers most often get wrong. They treat a contingency as a sign of vendor weakness, a hedge against the vendor's own bad estimate, and negotiate it toward zero. It is the opposite. A named contingency plus a written change mechanism is what keeps a genuine surprise from becoming a contract crisis, because the paper already says what happens. The contingency line and the change mechanism are two sides of the same discipline: the price is fixed, and the way it is allowed to move is written down in advance, so that movement is a procedure rather than a fight.

Lever four: whether the biggest recurring cost is fixed or floating

Compute is usually the largest recurring cost in a multi-year AI programme, and the decision to own it or rent it is made first, on day one, when the programme's risk is least understood. Framed as a finance question it looks like capex versus opex, and renting almost always wins the first meeting because it defers the capital and preserves the option to walk. Framed as a risk question it looks different, because renting pins your largest recurring cost to a market you do not control.

We made the owning choice in 2020, through a multi-year hardware partnership that put the cards on our own books and a local data-centre deal that gave full cost visibility. Nobody forecast a war. But when the 2022 energy shock arrived, the consequences were measurable and asymmetric. The market for DGX and high-performance-compute hosting moved from about 12,000 to 15,000 US dollars a month before the shock to past 20,000 after it; energy prices rose roughly 400% and electricity about 394%. A programme renting its compute would have watched its single largest line climb without a ceiling for the duration. The programme we ran absorbed the shock differently: one bounded, transparent contingency line across a twelve-month window, and that was the whole of the shock's effect on its infrastructure cost. The full board-grade reconstruction of that decision, the three-way public-cloud, private-cloud and on-premise cost model behind it, is a pointer to our hardware-moat chapter. For the CFO scorecard the lever reduces to one question: is the largest recurring cost of this programme fixed the day I sign, or is it floating on a market I cannot bound?

Lever five: the arbitrage that is the largest single lever

Of the six, the one that moves the price most is the least visible on the invoice: which rate card the mandays are billed at. On this programme, delivery routed through a university partnership, which unlocked academic day rates below the open-market commercial ones across every seniority band, and lowered the buyer's cost for the same seniority of work.

ACADEMIC VS COMMERCIAL RATE CARDS · THE BIGGEST LEVER100of 250 mandays in the widest-gap bandsThe academic card sits below the commercial one, and the gap widens with seniorityDrag the seniority mix: the more senior the work, the more the rate card matters.GAP RANKMANDAYS AT THIS MIXJunior51Researcher50Sr researcher50Head / senior50Principal500255075100gap rank: 1 narrowest, 5 widest (order, not size)two senior bandsWHERE THE RATE CARD MATTERS MOSTmandays in the two senior bands100mandays in the three junior bands150IN THE WIDEST-GAP BANDS40%of the phase’s mandaysThe rate-card choice saves the buyer most when seniormandays dominate, because the top-band gap is the widest.ASK THE VENDORWhich rate card is each band billed on,and who, structurally, bills at that card?SENIORITY-MIX LEVERdrag the share of the 250 mandays that sitsin the two most senior bands10%30%50%70%80%40%from the project archive: the gap order by band and the 250-manday total · rates withheld · the per-band split you drag is illustrative
The single largest lever in an applied-AI research price is which rate card the mandays are billed at. This ladder lists five seniority bands, from junior to principal, and ranks the gap between the academic (offered) and the commercial (open-market) day rate at each one: the academic card sits below the commercial one at every band, and the gap widens with seniority. Drag the seniority-mix lever to shift a 250-manday phase toward the senior bands and watch how many mandays land where the rate-card choice matters most, because the top-band gap is where routing through an academic partner saves the buyer the most. The orange running figure is the only element that argues: the mandays billed in the two widest-gap bands at the chosen mix. The band order of the gap and the 250-manday total are from the project archive; the rates themselves are commercial terms and are withheld, so the gap is shown as a rank rather than a size, and the per-band manday distribution the reader drags is an illustrative allocation, not the exact staffing split.

The ladder above states the arbitrage plainly. The academic card sits below the commercial one at every band, and the gap between them widens with seniority, which is why the saving to the buyer grows as the work skews senior. This is not a discount a vendor grants out of goodwill. It is a structural feature of routing an R&D engagement through an academic partner, and it is available to the buyer only if the engagement is set up that way from the start. A CFO who does not ask which rate card is in force is leaving the single largest lever unexamined. The arbitrage also carries a real obligation the buyer should want: academic routing typically comes with a local training and capability mandate, which on this programme meant in-country capability building was a first-class deliverable, not a footnote, and it connects directly to lever six.

Lever six: paying for capability you keep

The last lever asks whether the price buys the operator its own future capability or merely rents an outcome. On a well-structured applied-AI engagement, the mandays are not just labour; they are the mechanism by which the vendor's people train the client's people. This programme's year-two agreement was built around exactly that: a series of live technology-transfer sessions, online and onsite, hands-on work with the client's own models, and an MLOps track, so that the operator ended the engagement able to run its own AI rather than dependent on the vendor to run it. A meaningful share of that agreement was capability transfer rather than model-building. Per-head training economics price that transfer into the day rates rather than bolting it on as a separate consulting line.

The distinction the CFO should hold is between two ways to spend the same money. One buys an outcome the vendor delivers and keeps the expertise to reproduce. The other buys the outcome and the operator's ability to reproduce it without the vendor next time. The second is more expensive per unit of immediate output and far cheaper over the life of the capability, because it ends the dependency. The programme's academic routing reinforced this, since a university partnership carries a training and localisation mandate as a matter of course, which on this engagement made in-country capability building a first-class deliverable rather than a courtesy. And the capability the operator built was theirs to keep: the foreground-IP split handed the operator the majority of what was created, a structure treated in full in our chapter on the research-services agreement. The relevant question for the CFO is therefore not only what the mandays produce, but what the organisation can still do the day the vendor's people leave.

That is the whole scorecard. Effort obligation makes the price honest. Milestone tranches make it cancellable. The contingency makes it durable against change. Owned compute makes it stable against macro shock. Academic arbitrage makes it economical for the buyer. Per-head training makes it a purchase of capability rather than a rental of output. Now assemble them.

Assembling one worked phase from the six levers

Take the Phase-3 build and reconstruct its fixed price the way the workbook does, lever by lever. Five roles were planned across 250 mandays at academic day rates and summed to a role stack. A whole-phase commitment discount came off that stack as its own line. A bounded contingency was added on the discounted base. Phase-3 infrastructure was carved out and priced on its own. The disciplined fixed price is the sum of those lines, and every one of them has a lever behind it.

THE CFO BUYER SCORECARD · SIX LEVERS, NOT ONE LUMP6/6seams a buyer can inspect · assembledFlip a discipline off to watch its seam vanish into a lazy quoteEach lever is read off one real Phase-3 workbook; its figures are commercial terms, withheld here.1Academic-rate arbitrageCan delivery route through a university partner?partner card, every bandnames the rate card2Bulk discountWhat does committing the whole phase buy me?shown as its own linewhat commitment buys3Requirement-change contingencyWhat absorbs scope drift without reopening the price?bounded, on the facesurprise priced in4Owned vs rented computeIs the largest recurring cost fixed or floating?carved out, priced alonecost fixed, not floating5Effort-obligation contractingAm I buying an outcome the science cannot promise?priced as effort, not resultmakes the price honest6Per-head training economicsDoes the price transfer capability to my own people?250 mandays, 5 named rolescapability priced into the mandaysTHE PRICE, ASSEMBLEDMandays at a named rate cardvisibleCommitment discount, own linevisibleChange contingency, boundedvisibleCompute, carved outvisiblePriced as effort, not resultvisibleCapability transfer in mandaysvisibleFIXED PRICEan assembled artefactevery seam visible to the buyerENGINEERED VS A LAZY LUMP QUOTEdisciplined: one seam per leverlazy lump: one block, no seamsWHY LEVER 4 IS RISK, NOT CAPEXHosting market: USD 12-15K -> 20K+/mo in 2022.Owned hardware (locked 2020) carried it as onebounded contingency line for twelve months.Schematic: the bar counts levers, not money · amounts, rates and percentages withheld · hosting band is a market rate
A finance leader's scorecard for pricing an applied-AI R&D engagement. Six levers assemble one worked Phase-3 fixed price: a 250-manday, five-role stack billed at a named academic rate card, a whole-phase commitment discount shown as its own line, a bounded requirement-change contingency on the discounted base, a compute package carved out and priced on its own, an effort basis rather than a guaranteed result, and capability transfer built into the mandays. Toggle any lever off and its seam disappears into the price, which drifts toward the lazy lump a quote-first vendor would carry: a number that still foots but can no longer be audited. The orange count is the only element that argues: how many seams of the price a buyer can still inspect. The levers and the order in which the price is assembled are from the project archive; the amounts, day rates and percentages are commercial terms between the parties and are withheld, so the bar is schematic, one equal segment per lever rather than money. The hosting-market band in the compute card (12 to 15 thousand US dollars a month before the 2022 shock, past 20 thousand after it) is a third-party market rate, not the programme's cost.

The scorecard above is the argument in one object. Every lever is a card, and the panel on the right shows which lines of the price a buyer can still inspect as you engage or disengage each discipline. Turn the arbitrage lever off and the buyer no longer knows which rate card the mandays are billed at. Turn the discount off and the commitment reduction disappears into the rates. Turn the compute carve-out off and the infrastructure vanishes from a line the buyer should have been shown. With every lever engaged, the price is fully assembled and every seam is visible. Flip them off and it drifts toward the lazy lump a quote-first vendor would carry, a number that foots to something plausible while hiding which disciplines the buyer is actually getting. The two structural levers, effort obligation and per-head training, add no amount of their own; what disappears when they are switched off is not a line of arithmetic but the kind of number the price is, which is the point the whole paper is making. A fixed price is not a quantity to accept or reject. It is an artefact you can take apart, and the six levers are the seams.

The arithmetic of the discount deserves an explicit statement, because it is where a buyer most often mistakes a headline for a saving. Write the role stack as S, the commitment discount as d, the contingency rate as c and the carved-out infrastructure as I. The discounted price is the stack net of its bulk reduction:

The discounted role stack
Sd=S×(1−d)S_d = S \times (1 - d)

and the contingency is a bounded percentage of that discounted base, not of the pre-discount sticker:

The bounded change contingency
C=c×SdC = c \times S_d

so the fixed price assembles as the discounted stack, plus its contingency, plus the infrastructure carved out beside it:

The assembled fixed price
P=Sd+C+I=S (1−d) (1+c)+IP = S_d + C + I = S\,(1 - d)\,(1 + c) + I

The order matters. A vendor who applies the contingency to the pre-discount number, or who folds infrastructure silently into the manday rate instead of carving it out, produces a total that looks like the same kind of thing but is not built the same way. Reading the price as an assembled artefact is the only way to catch that.

The same money, read through two counterparties

There is one more view a finance leader should insist on, because it exposes whether the commercial structure is real or presentational. The lines above are how the work was priced. The programme was also funded, and the funding view was split across two counterparties: the operator-facing delivery firm and the university partner each carried a share of the budget, on the same phased basis as the price. The academic rate card and the training mandate are not floating claims; they are the direct consequence of a real counterparty in the structure whose economics differ from a commercial vendor's.

Why should a CFO care about the funding view when the pricing view already foots? Because the two views cross-check each other. A price that is quoted at academic rates but funded entirely through a commercial entity with no academic counterparty is a price claiming a discount it has no structural right to. The two-party split is the evidence that the academic-rate lever was genuine, that a university was actually in the delivery chain and actually bore part of the budget, and that the arbitrage the buyer benefited from reflected a real cost structure rather than a marketing line. When you ask which rate card the people are billed on, the honest follow-up is: and who, structurally, is billing at that card? If the answer is a partner whose economics justify the rate, the discount is durable. If the answer is a commercial vendor simply asserting a lower number, it is a figure that can evaporate at renewal. The two-party reading is how a finance leader tells the two apart.

The questions, as a buyer would actually ask them

The scorecard translates into a short list a CFO can carry into any applied-AI R&D vendor conversation. Each question maps to a lever, and each has a right kind of answer.

  • Is this priced as an effort or as a guaranteed result? On genuine research, "effort" is the honest answer; a vendor promising a specific accuracy at signing is either naive or pricing in a payout you will fund.
  • How is payment phased, and where are the gates? You want tranches tied to phase boundaries with exit ramps, so your exposure at any moment is what is sunk, not the whole total.
  • What absorbs a requirement change without reopening the price? You want a bounded contingency line on the face of the contract, small enough to keep the price disciplined, plus a written change mechanism for anything beyond it.
  • Is the largest recurring cost, compute, fixed or floating? You want to know whether an energy or hosting shock lands on you as an open-ended bill or as a bounded, pre-agreed contingency.
  • Which rate card are the people billed on? An academic or partnership rate card can lower the day rate at every seniority band; if it is available, the engagement should be structured to capture it.
  • Does the price leave my organisation with owned capability? You want per-head training and a majority IP position priced in, so the money buys a capability you keep rather than a dependency you renew.

A vendor who answers all six cleanly is quoting a price you can defend. A vendor who cannot, or who insists the single lump sum is the only sensible unit of purchase, is asking you to approve a summary you are not allowed to inspect.

Where this leaves the finance leader

The temptation with applied AI is to treat the commercial structure as plumbing and the model as the substance. On this programme the opposite was closer to true. The model was uncertain until late; the accuracy curve was genuinely unknowable at signing. What made the programme fundable, survivable and ultimately ownable was the commercial structure: effort obligation instead of an unpriceable warranty, phased tranches instead of a single irreversible commitment, a bounded contingency instead of an open reopening clause, owned compute instead of a floating rental, an academic rate card instead of the open-market one, and per-head training instead of a rented outcome. The worked phase and the year-one agreement are not interesting because of their size. They are interesting because each is an assembled artefact whose seams a buyer can inspect, and inspecting the seams is the whole job.

Price the six levers, not the lump. That is the field guide.

Limitations

This is a synthesis of one programme's commercial record, not a market survey. The levers, the order in which they were applied and the structure of the tranches are taken from the engagement's own workbooks, cost memos and signed agreements: the 250-manday, five-role Phase-3 stack, its commitment discount, its bounded contingency and its carved-out infrastructure; the five phase-gated year-one tranches; the academic and commercial rate cards; and the owned compute through the 2022 shock. The amounts, day rates, discount and contingency percentages and tranche sizes are commercial terms between the parties and are withheld. The hosting-market and energy figures around the 2022 shock are third-party market rates, not the programme's costs. The structure is specific to a subsurface computer-vision engagement routed through a university partnership, and other sectors, currencies and partnership structures will set the levers differently. The instruments are built to show structure without the withheld figures: the tranche staircase uses five equal illustrative tranches with gates drawn at even spacing; the arbitrage ladder ranks the gap between the two rate cards by seniority band rather than sizing it, and the seniority mix a reader drags is illustrative; the scorecard counts the lines a buyer can inspect rather than pricing them. What generalises is the method, reading a fixed price as an assembled artefact and asking the six lever-questions, rather than any specific figure.

References

Determined AI, 2021. Cloud versus on-premise total cost of ownership for deep-learning infrastructure. The public TCO framing referenced in the engagement's own three-way cost comparison behind the owned-versus-rented compute lever. https://www.determined.ai/blog

Intercontinental Exchange (ICE), 2022. European natural-gas and electricity forward benchmarks through the 2022 energy shock. The market source cited in the programme's war-time contingency memo for the roughly 400% energy and 394% electricity moves. https://www.ice.com

Stay ahead

EarthScan insights, in your inbox.

Field-tested research on subsurface and energy-transition AI. About twice a month. No noise.

We use your email only for this newsletter. Unsubscribe anytime Privacy.