Then Stripe should provide the metric as an API and precalculate it. (They already have as it powers their dashboards, it's just inaccessible via API access.)
It's extremely frustrating that external metrics dashboards report MRR as significantly higher than it actually is.
It makes me distrust and dislike Stripe that such a core figure is absent in their API. There should be zero excuse for not providing it. It's a ridiculous omission.
I've spent too much time trying to solve this and it disappoints me.
If you think it’s easier to calculate MRR with Lago than with data derived from Sigma or the reporting data exports, I suggest showing how it’s done in each case and explaining why Lago’s schema makes it easier.
Arguing that it’s harder on Stripe because if you’re DoorDash you would have to pay a lot of money for Sigma is not honest.
Disclaimer: the example (for the sake of the article) is relatively simple, as it's our first article on this topic, but we're willing to go much deeper, so feedback/inputs are welcome.
The article is correct that calculating MRR is difficult and requires access to your billing data.
I am very skeptical that working with data provided by Lago makes it any easier than working with the data you can get from Sigma or from data pipeline exports.
I don’t have a lot of love for Stripe by any means, but this is poorly argued.