The problem
An error tracker reports 340 events and 12 users. A founder needs a different number: how much money is behind those 12 users, and did any of them try to pay while it was broken? Getting it means exporting user ids from Sentry, matching them by hand against Stripe customers, and looking up each subscription. By the time the sum is known, the meeting it was for is over.
Without that number, every incident is either an emergency or nothing, decided by volume. A bug that hits a hundred free users outranks one that hits the two customers paying half the MRR.
What Vesqo does
Vesqo joins the users an error hit (Sentry, when the SDK tags events with the user) to the companies that pay (Stripe), by email domain. Every signal about an incident then carries the paying customers in it and the sum of their MRR, and the payments that failed in the same window are read from Stripe directly.
The signal ranks by that money, in the app and in the morning brief. A regression that hit €798 a month sits above one that hit nobody who pays, whatever the event counts say.
After the fix, ask: which of those customers came back, whose payment went through, who has not been active since. The answer comes with names and links.
Example
Questions it answers
- How much MRR is behind the customers affected by this incident?
- Which payments failed during the outage, and have they gone through since?
- What do the users on this Sentry issue pay us?
- Which incident this month hit the most revenue?