Back
Profitable Ruby Gem
Profitable Ruby Gem
#profitable
Calculate the MRR, ARR, churn, LTV, ARPU, total revenue & estimated valuation of your pay-powered Rails SaaS app, and display them in a simple dashboard.
Update Gemspec #profitable
Pass 500 downloads in RubyGems #profitable
Get retweeted by @excid3, creator of the pay gem and one of my Ruby heroes #profitable
Version bump 0.2.3, write changelog #profitable
Improve accuracy of `time_to_next_mrr_milestone` by converting the monthly growth rate to a daily growth rate and then calculating the number of days instead of the number of months #profitable
Fix `time_to_next_mrr_milestone` using a growth rate as a 100% percentage, not as a 0.00 float #profitable
Draft new release + version bump (v0.2.2) #profitable
Add syntactic sugar so we can also write `estimated_valuation(multiple: 3)` (h/t @marckohlbrugge) #profitable
Add more MRR milestones (more in the beginning for dopamine release, more spaced as we move up) – and include the famous $83,333 MRR milestone too ($1M ARR) #profitable
Try to fix churned MRR miscalculation (h/t @marckohlbrugge) #profitable
Fix APRC miscalculation due to `total_customers` miscounting customers that didn't actually pay any charges (h/t @marckohlbrugge) #profitable
Release new 0.2.1 version for @pretzelhands, who's not even a Ruby dev but made a point about syntactic sugar and I'm a syntactic sugar maximalist #profitable
Version bump, update README and CHANGELOG with new methods #profitable
Add syntactic sugar for estimated_valuation(at: "3x") – now also supporting Numeric-only inputs like estimated_valuation(3) to avoid writing 3 extra characters (h/t @pretzelhands) #profitable
Merge pull request #1 from marckohlbrugge/patch-1 #profitable
Launch on X x.com/rameerez/status/1829923… #profitable
Version fix #profitable
Version fix #profitable
Version bump; production ready; getting ready for launch #profitable
Remove recurring VS non-recurring revenue in dashboard and show only total revenue in period because queries are slow and the calculation might not be accurate anyways #profitable