Outcome Based

this guide explains how to implement outcome based pricing instead of charging for underlying activity (api calls, tokens, etc ), you charge for a business outcome the scenario you are building an ai powered customer support platform instead of billing for api calls llm tokens you charge customers based on support tickets successfully resolved pricing model $2 00 per support ticket resolved customers are charged based on results, not underlying usage core concept system activity (calls, tokens, etc ) → produces an outcome → meter the outcome → bill the customer the key shift you are metering the result , not the individual steps that produce it step 1 define the outcome start by identifying the business event you want to charge for in this example support tickets resolved this becomes your meter step 2 create the meter where to configure go to meters click create meter configure label tickets resolved meter type count no dimensions required each time a ticket is resolved, you will send meter value = 1 step 3 create a pricing plan where to configure go to pricing create a new pricing plan configure name support outcome plan billing period monthly step 4 add a usage based rate where to configure add a usage based rate configure meter tickets resolved rate model per unit rate $2 00 step 5 assign the plan to a customer where to configure go to customers assign the pricing plan to a customer once assigned, all metered outcomes will be billed step 6 sending usage (conceptual) each time your system resolves a support ticket send a meter event with value = 1 if 50 tickets are resolved total usage = 50 example outcome if a customer resolves 120 tickets in a month billing calculation 120 tickets × $2 00 = $240 why outcome based pricing this model aligns pricing directly with value delivered instead of charging for system activity you charge for what the customer actually cares about important distinction outcome based billing does not replace tracking underlying usage you should still track api calls llm tokens other system activity these are useful for cost tracking optimization internal visibility for internal cost tracking and attribution, see workloads docid\ xtorhvsoi2aok1bzpwfdu