Guides
How to do it by hand.
Each of these is a thing Vesqo does, written out as a thing you can do yourself with the tools' APIs and thirty lines of code: the joins, the baselines, the arithmetic, the caveats. Vesqo comes in at the end, for when you would rather not run the script every Monday.
-
Connect Sentry errors to Stripe revenue
Put the user on every Sentry event, read who an issue hit from Sentry's API, find them in Stripe, and sum the MRR behind the error. Ruby and curl, with the caveats.
-
How to connect product analytics to revenue
Group analytics by company, name the one event that means the product worked, pull each account's activity and join it to what they pay. Then the two comparisons that turn it into a churn warning and a conversion alarm.
-
How to identify the paying customers affected by errors
One account per customer across Sentry, PostHog, Stripe, support and the CRM: pick a key, propagate it, join by company domain where you cannot, and keep the overrides. With the SDK calls.
-
How to measure the revenue impact of a production incident
Three numbers, not one: MRR exposed, revenue blocked and revenue lost. How to fix the window, find who was affected, and compare against the right baseline, with a worked example.
-
How to prioritize bugs by customer value
Event count is the wrong order. A score from the paying customers behind each issue, their MRR, the payments it blocked and the support it caused, and how to compute it weekly and put it in the tracker.
See what it finds in a workspace with a bad afternoon in it.
The demo is Farol Jobs, a made-up job board with a bad release in it, every screen open. Ask it anything. Then connect your own.