Worship Online / APPLICATION MAINTENANCE + REVENUE PROTECTION
Reduce account sharing. Protect subscription revenue
We implemented an on-premises solution to combat account sharing.
THE EXISTING PRODUCT
Solved the issue with account sharing by users
Added Multi-factor Authentication (MFA) to the project in a risk-free way for the business. That increased daily signups by roughly 30%. The revenue has stopped descending 5% monthly and recovered. That also has improved security.
Improve the existing product where the business is losing value. We installed and configured Metabase for data analysis, then used it to measure the results of targeted MFA and session limits while keeping the subscription application in place.
THE BUSINESS CHALLENGE
Stop account sharing
We tackled declining revenue by combating widespread account sharing with Multi-factor Authentication (MFA) and login session limits. Through data analysis and monitoring, severe account sharers were targeted, leading to a 30% increase in daily signups and a 400% reduction in average login sessions per user. Revenue stabilized, preventing 5% monthly losses. The login session limit of three sessions per account enhanced security and accountability.
The revenue was slowly descending. It was clear that this happened because the users shared their accounts because of the many logins they used to make daily.
THE WORK WE DELIVERED
Improve the product. Keep the business moving
- 01
Set up Metabase and introduce targeted MFA
We collected the necessary data to determine who shares their accounts and how severely. Then, we defined indicators showing the situation dynamics and started measuring and monitoring them. We installed and configured Metabase ourselves as the analytics tool for this work. We used it to analyze account-sharing patterns, define measurable indicators, and track the results of our changes over time, taking ownership of the data analysis as well as the application changes. The users who shared their accounts severely and for sure got Multi-factor Authentication (MFA) enabled, which we also implemented. That increased daily signups by roughly 30%. The average login session per user decreased from 6 to 1.5, or by 400%. Revenue has stopped declining.
- 02
Limit sessions and measure the results
Later, we implemented a login session limit so that one account could have a maximum of 3 simultaneous login sessions. That was possible only after we built the infrastructure around the measurement system. We continued using Metabase to measure changes in login activity, signups, and revenue after introducing MFA and session limits.
VALUE FOR THE BUSINESS
Prevent Account Sharing: the results
Daily signups increased by 30%, login sessions per user decreased by 400%, and revenue stopped declining. Our solution prevented 5% monthly revenue losses.
We tracked and measured the results with the Metabase analytics setup we installed and configured. Ongoing data analysis helped us assess the effect of the account-sharing controls and monitor login activity, signups, and subscription revenue.
THE ENGINEERING DETAILS
More about the work
WE TAKE OWNERSHIP OF EXISTING RUBY ON RAILS APPLICATIONS
Need to stabilize revenue and improve your existing app?
Need someone to take over your Rails app? We maintain, stabilize and improve existing Rails applications, from production issues and upgrades to new features and infrastructure. Keep your product moving without unnecessary rewrites or rebuilding your engineering team.
Discuss your Rails app Explore existing Rails app takeover