Outcome-Based Pricing
Pricing where the customer pays for a measurable outcome, not for transactions or usage; for example a fee per resolved support ticket. It gives the tightest alignment with customer value, but the vendor absorbs the cost variability.
AI and GrowthTerm 65 / 81
In practice
Bessemer spells out the conditions: be confident in your AI's performance, be able to absorb cost variance, and have an outcome that is unambiguous and measurable. A hard case can consume far more compute than expected; the fee stays fixed while the cost moves. Pricing before you define the outcome means writing a contract that invites disputes (our reading). Poyar describes a shift toward charging for the work delivered by software and AI agents; do not read that as "everyone is moving to outcome-based".