skip to content

A multi-year commitment was signed weeks before a re-platforming halved the fleet it covered - what are your realistic options now?

level: principalimportance: should knowfreq 36%

answer

  1. the term keeps billing regardless
  2. ask what the instrument covers
  3. flexible spend floats, fixed shape strands
  4. exchange and resale are not universal
  5. ladder terms against roadmap confidence

basics

~20 s

Start by asking what the instrument is expressed in: a commitment tied to a machine shape strands, one expressed as spend per hour can often be consumed by other workloads. Then look for exchange, resale or renegotiation routes, and sequence the migration against the term.

solid answer

~50 s

The first question is not what to do, it is what was signed. If the commitment is expressed as an amount of spend per hour that any matching usage draws down, the cheapest fix is usually to point other steady workloads at it, so the replacement architecture or a neighbouring service consumes what the retired fleet no longer does. If it is tied to a specific machine shape, that route narrows sharply. Some providers offer an exchange into a different shape and some a resale route for certain instruments - neither is universal and neither is free, so I would establish which exist before promising anything. Failing those, the term is sunk: I would sequence the migration so the retirement lands near term end, and fold the remainder into the next negotiation rather than treating it as a reason to freeze the architecture. The durable fix is governance - ladder terms against how far the roadmap is credible, and keep a deliberately uncommitted band.

go deeper

for a junior

The key fact to hold is that a term commitment keeps billing for the committed level until the term ends, even if the workload it was bought for no longer exists.

for a middle

Be able to explain why a commitment tied to a specific machine shape strands when the fleet changes, while one expressed as consumption per hour can often be drawn down by other workloads.

for a senior

Work the routes in order - redirect consumption, exchange, resale, renegotiate, accept - and refuse the sunk-cost argument that the remaining term justifies delaying a migration.

for a principal

Own the policy: how much of the bill may be non-cancellable, laddered across which terms, gated on a stated roadmap horizon, and reviewed on a cadence rather than at renewal.

## Establish what was actually bought A "commitment" is not one thing, and the recovery options differ so much by instrument that answering before you know which one you hold is guesswork. The axis that matters most: - **Tied to a shape.** The commitment covers a particular machine profile, size or family, in a particular place. Usage only draws it down if it matches. When the covered fleet goes away, nothing consumes it. - **Expressed as spend or usage per hour.** The commitment covers an amount of consumption, and any qualifying usage anywhere in the account or organisation draws it down. The replacement architecture may consume it without anybody doing anything. Providers differ on which forms they sell, on how wide the matching rules are, and on whether unused commitment in one part of an organisation can be consumed by another. Find out before you plan. ## The recovery routes, in the order worth trying 1. **Redirect consumption.** If the instrument is flexible, look for other steady workloads that could move onto the covered shape or draw down the covered spend - a neighbouring service, a batch tier currently on metered capacity, the replacement platform itself. This is the only route that is usually available immediately and usually costs nothing. 2. **Exchange.** Some platforms let a commitment be exchanged into a different shape, typically with conditions on term length and total value. Where it exists it is the cleanest fix for a shape-tied instrument; it is not universal. 3. **Resale or transfer.** Some providers run a route for reselling or transferring certain instruments. It applies only to some instruments, usually at a discount to what you paid, and it should never be assumed as part of the original purchase decision. 4. **Renegotiation.** Where the relationship is large enough that terms are negotiated rather than clicked, a stranded commitment can sometimes be rolled into a larger or longer arrangement. This trades a known loss for a bigger promise, so it is a decision to take deliberately rather than as a rescue. 5. **Accept it and sequence around it.** If none of the above applies, the term is sunk cost. The correct response is to schedule the migration so that the covered fleet's retirement lands as close as possible to term end, and to keep the remainder visible in planning so nobody rediscovers it as a surprise at renewal. ## The decision that is actually being tested The trap in this scenario is the sunk-cost one: **a remaining commitment is not a reason to keep running the old architecture.** The money is spent either way. The only comparison that matters is the cost of continuing to run the old fleet against the cost of running the new one, with the commitment excluded from both sides because it bills regardless. Where the covered shape can still be used productively, using it is a genuine saving; where using it means delaying a migration that pays for itself, the commitment has simply become a fixed cost and should be treated as one. ## What changes next time The durable fix is not a better negotiation, it is a policy about how much of the bill may be non-cancellable: - **Match term to confidence horizon.** Sign the longest term only for capacity whose existence is credible over that whole term. Discount depth is the wrong axis to choose a term on. - **Ladder, do not step.** Cover the confident part long, a further slice short, and leave a deliberately uncommitted band on metered capacity. The band is what absorbs a roadmap change. - **Prefer the flexible instrument** where the provider sells one and the price difference is small, because it survives a change of shape. - **Put a roadmap gate on the purchase.** A commitment decision should require an explicit statement from whoever owns the covered workload that no change is planned inside the term - in writing, at the time. - **Review at a fixed cadence**, not only at renewal, so a divergence between the covered shape and the running fleet is found in the quarter it starts rather than at the end. ## Saying it at the right altitude At a lead level the interviewer is listening for risk framing rather than a trick. The honest summary is that a term commitment converts a variable cost into a fixed one in exchange for a discount, that the discount is payment for the risk you took, and that the organisation's job is to decide how much fixed cost it wants and to keep that decision synchronised with the roadmap. A stranded commitment is what that risk looks like when it lands, and it is recoverable only partially, only on some platforms, and never reliably.

  • The team argues the remaining term is a reason to postpone the re-platforming. Is it?
    No. The committed amount is billed whether or not the old fleet runs, so it is sunk and belongs on neither side of the comparison. Compare the cost of running the old architecture against the new one with the commitment excluded. It becomes relevant again only if the covered shape can host the new workload, which is a saving rather than a reason to delay.
  • What single governance change most reduces the chance of this recurring?
    Tying term length to a stated confidence horizon for the covered workload, with the owner signing that nothing is planned inside the term. Most stranded commitments are not bad arithmetic - the break-even was right - but a term chosen from the discount curve rather than from how far ahead the roadmap was credible.
  • How does the flexible form of the instrument change the exposure?
    It narrows it without removing it. A commitment expressed as consumption per hour can be drawn down by other qualifying workloads, so a change of machine shape or of service does not necessarily strand it. It still binds total spend for the whole term, so an organisation that genuinely shrinks is exposed either way.

saying these in an interview costs you the question

  • Assuming any commitment can be sold back or cancelled
  • Believing an unused commitment stops billing once the workload is gone
  • Treating the remaining term as a reason to freeze the architecture
  • Assuming the commitment automatically follows the replacement workload
  • Choosing term length from the discount depth rather than the roadmap