Launch HN: Skope (YC S25) – Outcome-based pricing for software products

Post by benjsm » Fri, Aug 22, 2025, 2:08 AM UTC

hermitcrab wrote: post #40

benjsm wrote: post #38

Earlier quoted context omitted.

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…

'gaming' as in 'game the system, take advantage of' .

Post by benjsm » Fri, Aug 22, 2025, 5:56 AM UTC

artathred wrote: post #42

> depend on every single customer reporting each outcome quickly and accurately. Why would the end customer have to report this? The company should be determining this and in very specific scenarios, ask the customer to approve the outcome. It’s very easy to game though if you’re relying on end-customers to always self report, just look at all the people getting refunds on Uber Eats because the food wasn’t the “right…

Post by mushufasa » Sat, Aug 23, 2025, 3:07 AM UTC

benjsm wrote: post #6

mushufasa wrote: post #4

This sounds really great in concept. I don't see detail here. As someone who would be interested in using this, can you clearly explain how you will measure and track the outcomes? That's the key detail that matters. Relying on customers to self-report is not sufficient, and an automated self-report-system is not a true improvement.

Thank you! To define the outcomes, it will be up to our customer and their users to state precisely what an outcome is and how it will appear. Once we have that information, we sync into their systems of record and act as that verification layer. It’s not an automated self-report-system, because they don’t have to report anything. As the work gets completed successfully (ie, a meeting booked or a customer support tic…