400 years of litterature across the world has warned us about this impending doom, yet we are racing headlong into it.
Launch HN: Skope (YC S25) – Outcome-based pricing for software products
31–40 of 46 posts
Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#32There has to be a translation layer the customer 1) can understand, and 2) agrees with.
Most companies settle for a consumption-based proxy to value and outcomes.
Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#33Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#34Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#35I'd suggest making your developer documentation public. A huge part of understanding whether I need this or not is reading how to build in your outcome-based pricing integration into my product.
Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#36Great concept, and love the approach of solving your own problem. There is a wide gulf between consuming something (tokens, emails sent, etc) and outcomes. There has to be a translation layer the customer 1) can understand, and 2) agrees with. Most companies settle for a consumption-based proxy to value and outcomes.
Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#37Isn't this essentially the unity price model that's getting laughed out of the market?
Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#38Earlier quoted context omitted.
Thanks! Definitely see where you’re coming from. Software startups with really good products are generating massive amounts of business value for their customers right now. Subscriptions and usage models really constrain them in how much they can capture of that. Incentives are also constantly misaligned, especially with usage as buyers will always try to minimize usage as much as possible. Charging on outcomes chang…
This whole area sound so incredibly ripe for gaming. >Tickets closed without being escalated to humans are usually what’s defined as an outcome. So I can make bank with a bot that replies to every query with "** you! Ticket closed." ? >cost savings for a dental clinic How can you software possibly know that?
Not quite, because the buyer and seller would never agree to that being a real outcome. It would have to meet certain requirements/thresholds for customer satisfaction. That’s where we come in to verify that those contract terms are actually met as it happens.
There are a ton of ways to calculate cost savings depending on what it’s built for. Voice agents that handle booking and outbound calls, supplier sourcing agents that only buy the best priced items, etc. It’s then possible to translate those things into a monetary figure, relative to the business.
Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#39Re: Launch HN: Skope (YC S25) – Outcome-based pricing for software products
#40Earlier quoted context omitted.
This whole area sound so incredibly ripe for gaming. >Tickets closed without being escalated to humans are usually what’s defined as an outcome. So I can make bank with a bot that replies to every query with "** you! Ticket closed." ? >cost savings for a dental clinic How can you software possibly know that?
Thank you - would love to hear more about the gaming use case. Not quite, because the buyer and seller would never agree to that being a real outcome. It would have to meet certain requirements/thresholds for customer satisfaction. That’s where we come in to verify that those contract terms are actually met as it happens. There are a ton of ways to calculate cost savings depending on what it’s built for. Voice agents…