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

Re:Launch HN: Skope (YC S25) – Outcome-based pricing for sof... by benjsm on Thursday August 21, 2025 @12:07PM (#44974453)

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 ticket closed) we will see it, verify it and bill it in realtime.

Would love to chat as well ([email protected]) if you have any questions specific to your use case. May be able to give a better answer, as the nuance really varies by use case.

[ Parent | on HN ]

Re:Launch HN: Skope (YC S25) – Outcome-based pricing for sof... by AznHisoka on Thursday August 21, 2025 @03:06PM (#44976770)

>> we will see it, verify it and bill it in realtime.

How do you verify that work got completed?

[ Parent | on HN ]

Re:Launch HN: Skope (YC S25) – Outcome-based pricing for sof... by mushufasa on Friday August 22, 2025 @11:07PM (#44992743)

"we sync into their systems of record and act as that verification layer"

As long as those 'systems of record' are controlled by the customer, then that is self reporting. If they don't enter a sale into their CRM or tag it differently there's nothing you can do.

The industries where I have seen pay-for-outcomes work are industries where there are regulated legal controls or strong third parties. For example, a lot of financial services have commission payments that are based on the actual invested assets as measured by the bank/custodian, that then get paid out to salespeople or partnerships.

[ Parent | on HN ]