Measuring Customer Outcomes, Not Company Adoption, for a Newly Launched API Product

A company is launching a new product for its customers, for example a set of APIs, that simplifies work those customers already do: fewer manual steps and less time per task. The company already knows how to judge its own success and the product's success, using measures such as how many new customers join and how many users are active. What it lacks is a way to tell whether its customers are succeeding with the product. How would you measure customer success for this launch? ```hint Think like the customer's manager Sign-ups and active users show that customers chose the product. Ask instead what a customer's team lead would report upward after switching from the manual process, and which of those numbers you could actually observe. ``` ### Clarifying Questions - Who is the customer we measure: the developers who integrate the APIs, the business that pays for them and owns the workflow, or both? - Which manual workflow does the product replace, and do we already know how many steps and how much time it takes today, or must we establish that baseline? - What data can we see: only our own API logs, or can customers share outcome data from their own systems? - How is the product priced (per call, by subscription or by seat), and should the value customers get be compared with what they pay? ### What a Strong Answer Covers - A definition of customer success kept separate from the company's own adoption and revenue metrics. - Metrics across the customer journey, from integration to depth of use to outcomes such as time and manual steps saved against a baseline. - How each metric would be collected: what comes from product telemetry and what needs customer input. - Leading versus lagging indicators, an account-level view and segmentation. - Pitfalls such as treating raw call volume as success or crediting the product with gains it did not cause. ### Follow-up Questions - One customer's API call volume doubles in a month. Is that good news for the customer, and how would you tell? - How would you turn these metrics into an early warning that a customer account is at risk of leaving? - A large customer says the product saves time but cannot put a number on it. How would you establish the value together?