When a vendor agrees to build something for one enterprise customer, such as a nightly export in the file layout that customer’s payroll system reads, the cost that matters shows up later. At renewal the customer can decline to sign, and it is likely to treat the export as something the base price already covers.
The vendor could be building either of two things, and they age differently over a multi-year term. One is a capability: a configurable export whose field mapping and file layout are documented settings any customer can use, maintained with the rest of the product. The other is a promise to keep one customer’s file working with one payroll system, which means rework whenever that payroll vendor changes its format, on a schedule the vendor does not set.
The objection is that bespoke work is where products come from, and Sierra’s design-partner program is evidence for it. Logan Randolph told First Round Review in 2025 that Sierra’s distinguishing features began as partner requests. Partners first reviewed conversations in exported CSV files and wrote comments back into them; when SiriusXM wanted a fuller view, Sierra built Agent Studio, now a main part of the product.
Randolph also described the filter: build a request when it serves the core problem the partnership exists to solve. Requests that passed became product. That is the classification I am asking for, made before the work starts and written into the contract. Work that ships as documented configuration renews with the subscription at the standard price, and the customer is entitled to whatever the settings produce. Work built for one customer outside that test, to win or keep the deal, is the promise. The interview does not say how Sierra handled its narrowest builds at renewal, and that is the case this piece is about.
For the promise, I would write into the original contract that it renews as its own priced line with a named owner on the vendor’s side, and that the vendor can retire it on a notice period the customer accepted at signing. The customer then knows what it pays for, and the vendor is not negotiating the export’s future at the one moment the customer can walk away.
When the product team cannot say which of the two it is building, pricing it as the promise is the reversible choice. A priced line can later fold into the standard product in an easy conversation; a price added to something the customer has used for a full term starts a hard one.