Best match

Most recent

Acquire

Agreement

Reach

Inc., dba Medicx Health ("Medicx”), a leading healthcare consumer-focused omnichannel marketing and analytics company. The transaction purchase price is $95 million, and certain members of ...

OptimizeRx Announces Agreement to Acquire Medicx Health for $95 million to Expand its Omnichannel Reach to Consumers

Yahoo Finance

Stock

Software as a Service

If you want to skip our overview of the SaaS industry, then take a look at the 5 Best SaaS Stocks To Buy Now. The dot com era of the 1990s focused on the consumer side of the […]

14 Best SaaS Stocks To Buy Now

Vision

AI vision can substantially enhance the functionality, efficiency, and user experience of applications, software, and websites, particularly in the Software as a Service (SaaS) model. For users ...

How to add AI vision to your apps, SaaS, sites and projects

Geeky Gadgets

Business Wire

Security on the Mass Rapid Transit

Founded by three French American experts in data protection and AI, Zygon comes out of stealth mode to release an automated solution to manage companies’ security posture at the scale of SaaS.

Zygon raises $3M in seed funding to create security solutions for the SaaS era

Fujitsu

Fujitsu will develop SaaS analytics services for pharmaceutical companies and medical institutions using anonymized electronic medical record data. Aiming to improve the efficiency of the drug development process and improve the quality of medical care ...

Fujitsu and TOPPAN Holdings collaborate to expand medical big data business

Appalachian State University

Analytics

App analytics tools are essential in providing key metrics, allowing us to understand what areas of our app need improvement to further enhance user acquisition. It is no surprise then that app marketers are increasingly investing in data analytics ...

Top App Analytics Tools (2023)

Uber

Leucine

Leucine, a B2B SaaS start-up has raised $7 million Series A funding round led by Ecolab Inc. and joined by Pravega Ventures, Axilor Ventures, Techstars, and angel investors. The funding will ...

SaaS start-up Leucine raises $7 million Series A funding

Business Line

LEEDS, England, Oct. 17, 2023 — A new report published today by Panintelligence, a provider of SaaS analytics software, indicates the extent of the AI rush in the SaaS (Software-as-a-Service) industry and warns that up to two-thirds of SaaS companies ...

Two-thirds of SaaS AI Projects Could Be Undermined by Bad Data, Report Warns

datanami.com

This report is meant to emulate the process that Steve Makinen and other members of the VSiN Analytics team undergo when handicapping each day’s MLB board. The following systems and qualifying plays are from the weekly update series on handicapping MLB ...

VSiN Analytics MLB Report for Tuesday, October 17

vsin.com

United States National Security Agency

Signature

NSA has released Elitewolf, a repository of intrusion detection signatures and analytics for OT environments. The National Security Agency has published a repository of tools to help critical infrastructure entities hunt for malicious activity in ICS and ...

NSA Publishes ICS/OT Intrusion Detection Signatures and Analytics

SecurityWeek

Get the most recent info and news about ChartMogul on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

ChartMogul is an analytics platform to help you run your subscription business. You get a complete overview of your global subscriber base; MRR, ARPU, ASP, churn and LTV are presented in a beautiful and easy to use dashboard. Our mission is to build powerful and secure cloud software for subscription businesses of all sizes, with a strong emphasis on good design and ease of use.

ChartMogul

How to Move Infrastructure From Classic VMs to Containers Orchestrated By Kubernetes

Alternative Pricing: Letting Go of Bad-Fit Customers is For the Best

Why Does a 'Good Customer Churn Rate' Matter?

Learn how Nick Franklin has taken ChartMogul from $0 to millions in ARR by helping other SaaS businesses understand their recurring revenue analytics. Davis Baer : What’s your background, and what are you working on? : My name is Nick Franklin, I’m the founder and CEO of a SaaS startup called . ChartMogul makes software to help subscription businesses measure, understand and grow their recurring revenues. We plug directly into our customers’ subscription billing systems (e.g., Stripe, Recurly, PayPal, iTunes Connect, etc) and automatically calculate things like monthly recurring revenue (MRR), churn rate, average revenue per customer, and even GAAP revenues. Users can then segment their metrics to uncover further insights and make data-informed decisions. Nick Franklin ChartMogul ChartMogul is used by over 2,000 businesses, including many top SaaS brands such as Typeform, Pipedrive and Calendly, as well as many consumer subscription services like LingoKids, brainHQ and BKOOL. Today our ARR is in the single-digit millions, so we’re on the journey towards $10M ARR. Over half our team (of 34 people) is involved in product and engineering, so we’re still very much R&D focussed with quite a lean sales and marketing operation. Our second largest team is customer success. Prior to launching ChartMogul I spent five years at Zendesk, where I joined as the 9th person on the team and was responsible for the EMEA and then Asia markets. What motivated you to get started with your company? Prior to joining Zendesk I was working at another software company in the product team, and product is really where my heart has always been. I’d also always had an ambition to try and start a company. So while I spent 5 years on the commercial side at Zendesk, the pull to get back to building product and also to try my hand at founding something was always there. I saw the need for a solution like ChartMogul while working at Zendesk. We had built some custom dashboards to track our MRR using one of the early SaaS BI tools, but it was quite a poor user experience and I couldn’t quickly find answers to simple questions, e.g., if I wanted to see what the average revenue per customer was in Hong Kong vs Singapore, it wasn’t possible without writing some custom SQL. But despite these shortfalls it was still quite useful (and also addictive) to keep checking these dashboards, I was checking them a couple times per day, my boss was checking them…so I saw there could be something very useful and engaging there. Once the initial idea was there I didn’t really spend time on additional validation — my personality is to trust my gut and see if people will use what we make. It’s probably a useful trait while things are getting started, though at our stage I now try to be more methodical with decision making. I also had little to no expertise in data and analytics, but did have nearly seven years experience working at cloud software companies. I was working at Zendesk in Asia (we’d just finished opening an office in Manila), when I left my job and moved to Berlin (more about here). I had some savings and used some of these to finance the initial beta development of ChartMogul until we took on our first seed round, which was $600K, led by . that decision Point Nine Capital I didn’t really have an alternative idea, I had dreamed of doing something for consumers as I thought this was cooler, but in the end my experience in B2B SaaS led me to take a path that I had more confidence would be successful. What went into building the initial product? It look us around six months to build our first beta version. The initial development was done by 2–3 engineers I found via UpWork + myself, and our creative director led on the design side. I initially went part time at Zendesk in order to have time to dedicate to ChartMogul, but I quickly realized I really needed to be all in to have any chance of success, so being part time only lasted around three months. We spent between $50K and $100K getting to initial beta release, with the majority of that money going towards engineering costs. While I understand our tech stack and can code Ruby and JavaScript, professional engineers run circles around me, so this was a necessary expense to get to market in time with a robust product. The initial product was a Ruby on Rails app, on top of a Postgres database, with a single page JavaScript application build using Backbone+Marionette for the frontend. We also used D3.js for the charting visualizations. We always tried to buy vs. build, so used a tonne of SaaS and developer tools to speed up our time-to-market, from SendGrid, to Stripe and New Relic. How have you attracted users and grown your company? Through my time at Zendesk I was lucky to have a connection to at Point Nine Capital. He was kind enough to invite me to their annual SaaS Founders Meetup in late 2014, where I met a bunch of other SaaS founders, had some of them take look at what we were building, and made connections that I could later use when we had something more robust for them to try out. Christoph Janz In the weeks following the meetup I remember Rodrigo (now a Partner at Point Nine) was introducing me to companies in their portfolio like Typeform, who are still a client today. We were extremely lucky to have Point Nine’s support, even before I raised the subject of fundraising with them. We did a sort of official “beta launch” on stage at the very first Product Hunt meetup in Berlin, which was towards the end of 2014. This also led to us being featured on Product Hunt the next day, and that got us a tonne of signups, some of whom are still customers today. I also met Ed Shelley at that meetup, who became our first post-funding hire in Berlin, and is still with ChartMogul today. We’ve tried a bit of everything to attract users: Product Hunt, Quora, creating content and syndicating it, paid advertising, social media, co-marketing with our integration partners. For us building strong relationships with our integration partners (Stripe, PayPal/Braintree, Recurly, etc) and collaborating with them, as well as focussing on producing quality content have both been really huge, especially in the early days. We’ve also invested in building our brand and recently went through . our first re-brand Of course there isn’t really a replacement for really nailing your product, as word of mouth always will be the number one growth driver for us. What’s your business model, and how have you grown your revenue? To date we’ve always been a pure SaaS company, 100% of our revenues are from selling software subscriptions. Most of of our revenues come from our core subscription analytics product, but we also have a second product which is billed as a paid add-on called Revenue Recognition. We’ll likely one day offer some paid services along with our SaaS offerings, but I think we’re some ways off from this, in order to remain focused we’ll probably be pure SaaS in terms of revenues for some time. One of the advantages of our product is that you can combine revenue data from different sources and consolidate everything in one system. Because of wanting to test this benefit, we knowingly took the decision to create a bit of overcomplexity in our own payment stack. So we use a combination of Stripe, Braintree and Recurly to bill our customers, which does require a bit more maintenance than a normal SaaS startup would have to deal with at our stage (normally you’d want to start with just a single billing system), but it allowed us to build knowledge internally about how different systems work, and also dogfood ChartMogul’s ability to aggregate payment data from different payment systems. While we’ve experimented with outbound in the past, we’ve not found it to be an effective channel for us, so today all our leads come inbound in the form of a free trial signup, or demo request. We then have our sales team, which is a small team of four people, work to try and convert these inbound signups into paying customers. There are really only four high-level metrics to look at in terms of what drives revenue growth: Number of leads, conversion rate from lead to paying customer, average deal size and churn rate. Positively impacting revenue growth for us has really just been a never ending effort to make incremental improvements to these four metrics, e.g., create some great content to try and get more leads, refine our product to improve conversion rate, chip away at the reasons customers cancel, tweak pricing or focus on the needs of larger opportunities to increase deal size. Our focus recently has really been on reducing the reasons customer’s cancel, as we feel reducing churn is the thing that will have the biggest impact at the scale we’re at now. Churn was something that kind of crept up on us, we had almost no churn in our first few months, so naturally we focussed on expansion vs. retention. But in reality we have some churn like every SaaS business, and in every B2B SaaS business retention becomes the biggest growth driver in a way, so it’s worth focussing on churn really from day one, perhaps even before you actually have any meaningful churn data to look at. What are your goals for the future? Our mission is to help businesses grow faster using their revenue data, and we’re still only scratching the surface of what is possible here. So we have a very ambitious product roadmap. Our long-term ambition is to build an iconic SaaS company whose products are used (and loved) by hundreds of thousand of people around the world every day…so we’ve a long way to go before we realize this vision for ChartMogul. In terms of accomplishing these goals, I think the biggest challenge comes down to people. Will we be able to attract the people we need to accomplish these goals, can we get everyone aligned and working together well and will we be able to retain our people? Past a certain size (and we’re certainly past that size at 34 people) every problem is really a people problem. With the right people, in the right market, with the right incentives, all working together well, there’s very little that cannot be accomplished. What are the biggest challenges you’ve faced and obstacles you’ve overcome? If you had to start over, what would you do differently? I’ve made countless mistakes, be it a hire that didn’t work out, a product decision that wasn’t right, not focussing my attention where it was really needed, micro managing (or under managing), etc. I feel like being a first-time founder & CEO of a startup is like the ultimate education. I used to think something along the lines of… “yeah in big companies they always say ‘people are the number one asset’ but we’re a startup, our shiny new product is our number one asset”, and that’s completely wrong, everything that’s produced by the company is just a reflection of the quality and health of the team. So if I was to start over I would put far more focus on building a really solid foundation and culture earlier on. Jason Lemkin says it best, your job as CEO is to just to hire the best team you can possibly hire with the resources you have and then just support them. It sounds simple, but really hard to do in reality. Moguls talking with ChartMogul customers. Have you found anything particularly helpful or advantageous? I think doubling down on content from day one was really a good decision for us, it’s a long-term investment but it really pays off to start making that investment early. The job of founder/CEO has forced me to adapt and grow up a lot as a person. Being accountable to 30+ employees, thousands of customers, and our investors, is a job with a lot of responsibility that I’m not sure there’s any shortcut to getting good at. I’ve found being honest with myself and the people around me about what I do and don’t know, and making a commitment to constant improvement is the best approach. Four years ago when we were getting started I think I wanted to appear a bit like the invincible founder who knew what he was doing (“We’re crushing it!“), and therefore was reluctant or show any weakness or ask for help from others. But in reality everyone is winging it to some extent (and few are truly “crushing it”) and asking for help actually shows strength and not weakness…so this is something I’ve learnt over time. There are also a tonne of great books that have helped me, and are both invaluable. I’m not a very fast reader so audiobooks are really helpful for me here. The Hard Thing about Hard Things High Output Management I’ve also found exercise to be really beneficial. I began going to the gym regularly around the same time as we started the company and I think this has really helped me with general wellbeing and managing the stresses of the job. What’s your advice for entrepreneurs who are just starting out? If you are still on the fence about starting a company, my number one piece of advice is to just get started. It’s not original, but it’s true! Don’t wait. You can always get another job or figure out some backup plan if it doesn’t work out. Often fear — fear of failure, loss of status and income at a good job — is the thing holding people back from getting started. I know it was for me! Making decisions (or worse, avoiding decisions) influenced by fear is never good. I love the saying “Hard choices, easy life. Easy choices, hard life.” One book I wish I’d read before getting started is . It talks in depth about the concept of category creation, with the general thesis being that most founders spend their time on building a company and a product, but rarely do they consciously define and build their category at the same time. Play Bigger When I meet SaaS founders who are just starting out, the thing that seems to regularly separate the ones who do really well vs. the ones who don’t do so well is this: When the product they’re building seems to be solving some seemingly small but well-defined problem, and just focusses on solving this problem, then they tend to always do well. When I see products that are trying to do many different things for different people at the early stages then this is usually a sign things are unlikely to go well. I guess “focus on doing one thing really well”, is tired advice but I’ve seen it play out quite a few times. Where can we go to learn more? You can find me on twitter at , and you can find out more about ChartMogul over at . I’ll be very happy to answer any questions in the comments below. https://twitter.com/nick_franklin chartmogul.com This interview is brought to you by , a tool to schedule and automatically repeat your posts on Facebook, Instagram, Twitter, Pinterest, LinkedIn, and Google My Business OneUp

Founder Interviews: Nick Franklin of ChartMogul

This blog post is about how retired its last pieces of infrastructure on DigitalOcean, marking its migration to AWS as complete. ChartMogul The journey was not your regular AWS migration as it involved moving our infrastructure from classic VMs to containers orchestrated by Kubernetes. In a series of articles, we will share our experiences about: Our journey to AWS EKS (Kubernetes managed service). Some of the most critical roadblocks we encountered. Our current stack and tooling. Our infrastructure plans going forward, hoping they can be helpful to the entire community. Life With DigitalOcean Since our inception in 2014 and up to mid-2021, our entire infrastructure has run on DigitalOcean droplets (self-managed cloud virtual machines). We needed a cloud provider to get us off the ground quickly, reliably, and cost-effectively. DigitalOcean made a lot of sense and was a great choice. We are where we are because of them. That choice gave us the freedom to focus on product building without worrying about scalability and infrastructure complexity – aspects that typically kick in at a later stage. Every aspect of our infrastructure was provisioned, configured, and managed in-house. We used configuration management and Infrastructure as Code tools (Saltstack and Terraform) to manage things. We kept growing over the years, and by 2019 we found ourselves looking at a fleet of somewhere around 50 machines in constant need of management, software updates, security patches, and so on. And with new projects in our pipeline, we expected our compute power needs to double by the end of 2020. Why Move and Why Now? As great of a choice DigitalOcean was, our organic growth was pushing the boundaries of our setup over the years. We faced challenges with multiple areas, some fixable and preventable, some not. Various Failures Ad-hoc unannounced maintenance windows that suddenly broke production. Hardware failures on several occasions, affecting our primary – replica database setup (e.g., droplets entering a ”live migration state to other hardware machines” without notice, meaning 1-2 hours of downtime for that droplet.) Unexplained networking issues with latency between our machines that DigitalOcean’s support team never cleared out (this was critical for our Postgres read-replicas lag, Redis instances, and HA in general). AMS2 Region Deprecation Our DigitalOcean region (AMS2) was announced as “soon to be retired”, meaning limited support. We could not secure additional resources on-demand, and executing simple tasks usually meant long planning and wasted resources. Simple things such as upgrading a Postgres version and provisioning a new machine to perform a task were becoming impossible to do. Limited Hardware Choices Being in the subscription analytics space means data-intensive operations, large volumes, and the ability to often scale accordingly. Modern machines with more extensive hardware resources were only available in other regions. Network performance degradation was a frequent occurrence, and we soon realized that migrating to a different region was our best bet. Lack of Modern Cloud Features and Managed Services The volume of operational work to maintain our infrastructure to keep up with the growth rate (and deal with tech debt simultaneously) increased. We had to take a hard look at our setup and understand whether moving into a different DigitalOcean region or a new cloud provider was the best choice. Should We Stay or Should We Go? We started looking into the benefits of staying with DigitalOcean and simply moving to a new region – a more leisurely, quicker, cheaper, less painful option. But at the same time, we treated this move as an opportunity to modernize parts of our stack in service of expected user growth and an increased rate of progress. By the end of our assessment, we realized that specific must-have requirements would be hard to achieve by staying and simply switching regions. The most important ones were: Flexibility in auto-scaling compute resources. Managed databases. Provisioning of resources based on temporary usage. Low(er) latency. Service interoperability. Container-based infrastructure with Kubernetes orchestration. This list of requirements along with the challenges listed in the previous section tipped the scale in favor of switching providers. Why AWS? Choosing a new cloud provider to power ChartMogul infrastructure was a long journey. We researched the market and discovered many tradeoffs and advantages a new provider could bring to the table. Our options were Amazon Web Services (AWS), Google Cloud (GCP), and Azure. Ultimately, we decided to go with AWS. We list some of the main reasons below. Team Expertise We were already using some AWS services in production (e.g., S3 for storing incremental Postgres backups). More importantly, a few of our engineers had prior professional experience using various AWS services extensively in production systems. Scalability We can ramp AWS instances up or down at the push of a button. We can instantly provision resources like RDS databases and compute resources temporarily. We can iterate through experiments and proof of concepts quickly. The flexibility and scalability of Kubernetes node pools backed up by EC2 auto-scaling are hard to beat. Data Security and Compliance Data security has always been top of mind. Over the years, AWS security capabilities have grown substantially. The number of new services AWS developed around data security covers most of our needs in the container/Kubernetes space. They play nicely with well-established services such as private VPC isolation, fine-grain control of policies, and IAM roles. Compliance-wise, we plan to become SOC II certified asap, and we found AWS to be an advantage that can help fast-track that journey. compliance programs Managed Services Postgres is at the heart of what we do at ChartMogul, and we’ve typically spent a lot of time actively managing our database fleet of machines to support our growth. High availability and reliability of databases were becoming growing concerns, so we decided to evaluate multiple offers from major cloud providers with managed PostgreSQL. AWS RDS was the clear winner. Managed Kubernetes was another major factor to consider, and this was head to head with Google Cloud (GCP). Google’s managed Kubernetes (GKE) felt better than what AWS had at the time, but comparing RDS to CloudSQL wasn’t close feature-wise. Nowadays it seems that AWS is catching up with EKS however; We benefit from great RDS features such as snapshots flexibility, backup durability (with SLA), read replicas for Postgres, painless upgrades, dedicated IOPS, Cloudwatch metrics, Performance Insights, and the list goes on. The Insane Number of AWS Services At the time of writing, AWS offers over 200 services. Most of them give you the ability to get instant access to managed services from so many areas like compute, databases, data analytics, data warehousing, serverless, and storage. Our engineering teams can now leverage top-notch integrations to solve core problems quickly and prioritize buy vs. build where it makes sense. Disaster Recovery AWS cloud is an essential part of our Disaster Recovery plan. That’s because instances are easy to spin up, we can promote RDS read-replicas to primary at the click of a button, snapshots are a breeze, we can host in multiple regions, and we have a top-notch integration with our IaC tool of choice. AWS Credits We secured $100k worth of credits through the AWS Startup program. We were able to plan, test, and complete our migration without considerable expenses. Migration to AWS Our migration from DigitalOcean to AWS was a ten-month-long journey. The entire effort was backed up by volunteers from all of our engineering teams and driven by a DevOps engineer, a backend engineer, and our head of engineering. Some things involved trial & error. We tried multiple ways of: Moving data from Postgres to RDS with near-zero downtime. Moving our app and services from VM-based architecture to containerized ones in Kubernetes. Fundamentally changing the way we deploy. A perfect plan was in place, and everything looked good to go on paper, but we learned the hard way that things will not always go to plan. At times, our near-zero downtime migration goal was at serious risk, and back to the drawing board we went. Perseverance, drive, and fantastic team effort helped us overcome the challenges we faced. Careful planning did wonders too; Given our capacity, we established early on that breaking down the actual migration into three stages (or days) would work best. Week Prior D-Day Start Postgres replication from DigitalOcean to RDS instances. Review our AWS future production infrastructure. Configuration of secrets (AWS Parameter Store). Ensure CI/CD pipelines are ready to deploy to our new Kubernetes clusters. The Day Before D-Day Prepare our AWS temp webhook recorder infrastructure (losing events during our migration was not an option). Move some data in advance (e.g., DigitalOcean Spaces to S3). Update all Parameter Store secrets to production values. Prepare DNS changes. Set all Kubernetes deployments to zero pods to prevent services from accessing production data during migration. D-day: Flicking the switch Redirect all webhooks to AWS temporary recorder. Stop all the services on DigitalOcean. Wait for Postgres replication to catch up on the latest updates. Compare DigitalOcean and RDS Postgres data (to ensure integrity and replication catch up). Drop the subscription from RDS to Postgres running in DigitalOcean. Create RDS read replicas. Update our Parameter Store secrets with new RDS endpoints and secrets. Deploy to Kubernetes and restart PgBouncer to load new configurations. Switch DNS records for to AWS. app.chartmogul.com At this point, we were running our production workload on the shiny new infrastructure! We finished the whole thing in 10 hours (we initially estimated 8 hours – not too bad). Challenges With AWS The biggest struggle was with the DMS service (AWS managed service to move databases into RDS). It was not as easy to use as advertised. In our case with Postgres, it was not helpful. Eventually, we developed a custom way of moving data into AWS. We also came to the hard realization that moving databases with zero downtime to AWS with webhook support is complicated. We developed a custom approach to support this setup. More on these custom approaches in future articles. Future Articles in the Series Look out for future articles documenting our migration journey from DigitalOcean to AWS. We will touch on topics such as: Why we chose Kubernetes to power ChartMogul. How we migrated PostgreSQL to RDS. How we migrated our Rails app to Kubernetes. How we set up an IPSEC tunnel to AWS VPC.

Cómo mover la infraestructura de máquinas virtuales clásicas a contenedores orquestados por Kubernetes

Comment déplacer l'infrastructure des machines virtuelles classiques vers des conteneurs orchestrés par Kubernetes

कुबेरनेट्स द्वारा ऑर्केस्ट्रेटेड कंटेनरों में बुनियादी ढाँचे को क्लासिक वीएम से कैसे स्थानांतरित करें

クラシック VM から Kubernetes によってオーケストレーションされたコンテナにインフラストラクチャを移行する方法

Como mover a infraestrutura de VMs clássicas para contêineres orquestrados pelo Kubernetes

Cách di chuyển cơ sở hạ tầng từ máy ảo cổ điển sang vùng chứa do Kubernetes tổ chức

如何将基础架构从经典 VM 迁移到由 Kubernetes 编排的容器

lost a large number of legacy customers when migrating them to a new pricing model, however, the highly engaged `good fit` customers enabled ChartMogul’s continued growth. ChartMogul Early Pricing Experiments ChartMogul’s pricing model was customer-based at the company’s inception. The price you paid for using CharMogul was dependent on the number of customers your business served. Even in the early years of ChartMogul, we encountered several challenges with customer-based pricing: We frequently couldn’t close deals without discounting. We encountered a lot of friction with the entry-level pricing. Paying customers that were growing into higher pricing tiers would reach out regularly to ask for discounts. Ultimately, we ended up with many customers having discounts and all sorts of individual agreements and a large number of plans. There was a fundamental lack of a price to value alignment. ChartMogul’s pricing page in 2017 The Decision to Move Away From Customer-Based Pricing In the summer of 2018, we conducted extensive research into alternative pricing models. The research concluded with a clear recommendation: revenue-based pricing would result in a better price to value alignment. The decision to migrate from customer-based pricing to was just a first step. revenue-based pricing We decided that after the release of revenue-based pricing to new customers, we would also migrate all legacy customers to the new pricing. To understand the impact of the new pricing on our current recurring revenue, we mapped the whole customer base to MRR bands. We did this by creating ranges in $10K MRR increments such as $10-20K MRR, $20-30K MRR, and so forth. This showed us the customer count in each band and what the total amount paid would be. ChartMogul’s pricing page in 2022** Before Migrating Our First Customer While preparing for the pricing migration, we determined that the account management team would take the lead on the project since we anticipated that re-selling and additional onboarding would be necessary to migrate some of these accounts successfully. We divided our customer base into groups, segmented by price and plan. Later, we prepared customizable messaging templates that reflected our company values like integrity and empathy. An Iterative, Empathetic Pricing Migration Process The migration process started out with the oldest legacy plans and the lowest paying accounts in them. We worked through migrations in batches and set a quarterly goal for the account management team. The batching helped us to tweak our messaging as we went along. We found that showing strong empathy in our communication and allowing the customer to be heard really helped to get the buy-in. In many cases, we were asking for a lot of extra money so we aimed to always identify opportunities to deliver more value and expand the usage of ChartMogul. Some discussions took several weeks of back and forth and occasionally involved the product and engineering teams. What surprised us most was that many customers accepted the new pricing with little to no resistance. Challenges Encountered A number of customers had strong emotional responses. Getting them to agree to the new pricing was a journey that required patience from both sides which at times resulted in several weeks of back and forth. When a conversation wasn’t going anywhere, myself or our CEO would get involved to help work towards a win-win solution. Some founders and executives responded better when talking to someone they perceived as an equal. In some cases, the price increases were extreme where a customer would move from paying something like $300 to paying $2500. We decided to be flexible when working with these types of high-value accounts. We developed a system we called gradual pricing alignment. Instead of asking a customer to pay the full amount right away, we would roll out the increase in increments over a more extended period of time. Letting Go of Bad-Fit Customers We determined during the pricing migration that some customers were simply not the right fit. Looking closer at these accounts, we found that we had been trying to keep some customers happy for years at great expense to our business. These accounts were leftovers from the early time of ChartMogul, when our positioning wasn’t that clear yet, which attracted all types of customers. Some had become bad fit customers over time. The gap between what ChartMogul could do for them and what they wanted to use our product for had grown significantly since signing up. When a customer had such a limited usage profile and no interest in expanding it, there was often no pathway to get the buy-in to our new pricing. 44.7% Account Retention is Not the End of the World To understand the result of the migration, let’s dive into one customer segment and look at ChartMogu’s Pro Plan customers that migrated to the new Scale or Volume Plans. In that customer segment, we lost 178 accounts. From 322 subscribers in September 2018, we went to 144 in February 2020. Account retention was 44.7%. ** Chart: Migrating from Pro Plan to Scale or Volume Plans – Subscribers At first glance, this was a huge loss for the business. However, looking at MRR in that same segment tells a different story. We went from $57,640 to $85,838 and attained almost 148.9% MRR retention. ** Chart: Migrating from Pro Plan to Scale or Volume Plans – MRR Moreover, these accounts expanded further since we completed the pricing migration in Q1/2020. Our Takeaways From the Pricing Migration All in all, the project took 1.5 years to complete. We consider the pricing migration a big success for several reasons. The remaining customers were primarily highly engaged, good-fit users that took full advantage of the platform. This made it easier for our success team to manage those customers. We saw our support volume relative to our customer number decrease. The pricing migration also helped our positioning. We learned that B2B SaaS was our sweet spot which impacted our product roadmap and marketing strategy. We gained a better understanding of our pricing power. Value-based pricing reduced friction for our sales team to convert leads to paying subscribers and our account managers to retain customers. My favorite part of the pricing migration was all the engaging conversations we had with our customers. These helped us build better, value-based relationships with them. Our team learned a ton about where our customers are realizing the most value. We gained a better understanding of our customers’ future needs which will empower our company to prepare for the future to grow alongside their changing needs.

Customer churn rate, also known as logo churn rate is a key indicator of the health of your SaaS business. At a high level, the gives you the rate at which your customers are canceling their subscriptions. customer churn rate A high customer churn rate can be deadly for your business. In this post, we analyze, anonymized and aggregated data from to find out what is a good target customer churn rate for a SaaS subscription business. ChartMogul We also discuss why it is important to track customer churn rate and the underlying reasons behind a high customer churn rate. Monthly Customer Churn Rate by ARPA & MRR Bands The chart below shows the median Customer churn by a companies average revenue per account (ARPA) per month. As a reminder, ARPA is the average revenue per account i.e. average MRR across all your customers. It is also known as ARPU or APRC. You can find your ARPA within your . ChartMogul Dashboard As you’ll notice, the customer churn rate for the median company varies by the ARPA band you are in. For companies with ARPA per month in the range of $0-10, the median monthly customer churn rate is 6.8%. It decreases to 1.9% as your ARPA per month increases to >$500. In addition, to the median, the chart below also shows the 25th and 75th percentiles of the customer churn rate. The trend remains the same. For companies with lower ARPA, the customer churn rate is higher while for companies with higher ARPA the customer churn rate is lower. The best companies should target a customer churn rate of <2% per month. This goes down to <1% as your ARPA increases. Below is the data for monthly customer churn rate split by monthly recurring revenue (MRR) band. As you’ll notice, the monthly Customer churn rate of a median company is higher in the initial stages of the business (6.8% for <$10k MRR, 4.6% for those with MRR b/w $10-50k). As more companies find product-market fit and hone into their customer category the churn reduces. Down to about 3.5% per month. Although it then stabilizes at that level and doesn’t reduce even when a company grows. The chart below also shows you the 25th and 75th percentiles of the customer churn rate by MRR band. The best companies should target a monthly churn rate <2%. Calculation Methodology. Monthly Customer churn rate is calculated as the ratio of the number of customers who churned in the month (excluding any customers who both joined & churned in the same month) / Total number of customers at the start of the month. We calculate the aggregates over a 3 month period (Nov ‘21, Dec ‘21 & Jan ‘22). We use the for all companies for easier comparability. standard B2B churn formula Why Should You Care About Customer Churn Rate? Customer Churn Rate is helpful because it gives you: Quick feedback — compared to other cohort-based metrics such as Net or Gross dollar/customer retention, churn gives you immediate feedback. You can run tests on your platform and then see feedback in a few days or months. Easy to measure — the formula for customer churn rate is straightforward and easy to measure. Also, it is relatively hard to game this metric. If your customer churn rate is high that means that i) You’ll not be able to compound your user base and hence your revenue, and ii) The money you just spent to acquire your customers i.e. the customer acquisition cost (CAC) goes down the drain sooner. Churn is deadly. A monthly churn rate of 5% corresponds to an annual churn rate of 46%. That means you’ll lose close to half your existing customers in the next year if you don’t contain your churn. Here is a helpful table that helps you look at yearly churn corresponding to a particular monthly churn number. The formula we use to get the annual churn rate from monthly churn rate is the following: Annual Churn Rate = (1- (1-Monthly Churn Rate)12) Why Do You Lose Customers, Anyway? Customers leave you primarily because they don’t see value in your product. The underlying reason as to why they don’t see the value could be threefold: They haven’t been onboarded well: They can’t get to the ‘Aha’ moment where they get to see the magic of your product. Your product is too complex to understand or they are not sure of what job your product accomplishes. Support docs are not easy to understand. Customers are searching for an answer and they just can’t get it. When trying out a new product what you don’t have is time/patience. Price doesn’t correlate with value — even if some of your customers see the value in your product, they can get more value for the same price elsewhere. Hence they churn. Wrong customer segment — Maybe they weren’t the right customer segment who should be using your product in the first place. Your marketing strategy needs to change in this case. And probably you’ll need to too. fire some of your customers Unrelated to your product value, there is also some Involuntary churn that happens. This is because of card expiry, declined payments, etc. Customers also leave because they get acquired, and their new home no longer uses your product. Consider digging deeper to get the real reason behind the churn. A way to do this is to talk to your customers. Find out why they churned? Was it because of your or was it because your product was missing a key feature. And then test your hypotheses (eg. features, pricing, plan). Repeat. pricing

Tring Tring. You just received a notification from ChartMogul. A new customer signed up. Oh yes! Your monthly recurring revenue (MRR) just shot up. Tring Tring. Another notification. A customer just canceled. Oh no! Your MRR went down. Tring Tring. A customer just upgraded their plan from basic to premium. Yes! MRR goes up again. You get the point. Your monthly recurring revenue (MRR) moves every day. It’s because of all the underlying dynamics of customers joining, upgrading, canceling, or downgrading. Understanding and being on top of all these MRR movements can sometimes get confusing. To simplify this a bit, you can think that your MRR movements only have two components: MRR Added — i.e. the revenue that your business added in a particular period MRR Lost — i.e. the revenue that your business lost Below is a screenshot of the MRR movements chart in ChartMogul. The blue bars show the MRR added while the pink ones show the MRR lost. If your goal is to grow your business, you need to add more MRR than you lose. So the blue bars need to add up to more than the pink ones. Understanding MRR Movements Let’s dive deeper into how your SaaS business adds or loses MRR. And how those changes are categorized in SaaS as MRR movements. You can add MRR to your business by: Attracting new customers — in SaaS jargon, this is called a New Business MRR When existing customers pay more — this is called Expansion MRR Re-attracting ex-customers — Reactivation MRR And, you can lose MRR when your: Customers cancel — Churn MRR Existing customers start paying less — Contraction MRR So that’s how you lose or add MRR to your business. Now that you have a basic understanding of MRR movements, let’s look at these metrics for an average startup. Benchmarking MRR Movements by MRR Bands MRR Added Benchmarks As we discussed above, MRR added is made up of three components: New Business, Expansion & Reactivation We analyzed, aggregated and anonymized data from ChartMogul to find out how MRR movements split up across these three sub-components. The chart below shows new business MRR as a percentage of MRR added. As you would expect, new business makes up the largest component of MRR added for most businesses. Specifically, for startups with MRR <$10k, new business MRR makes up for 77.7% of their MRR added. As businesses grow, the proportion of revenue generated from new business decreases. It goes down to almost half (50.7%) for startups with MRR >$1m. This is because as SaaS businesses grow, they focus their energy on increasing revenue from their existing customers. Hence, the proportion of expansion revenue as a percentage of total MRR added increases. As you’ll notice in the chart below, startups with >$1m in MRR, generate 36.1% of MRR added from expansion activities. This is the classic “land and expand” strategy that many SaaS businesses employ. The third component of MRR added is reactivation. This component remains roughly stable throughout business growth, contributing to 9-13% of MRR added. MRR Lost Benchmarks Now, let’s move on to MRR lost. As a reminder, MRR lost can be grouped into two components: Churn and Contraction. The chart below shows Churn MRR as a percentage of total MRR lost. Churn makes up for the bulk of the MRR lost — roughly 70-80%. Here too, as the business grows, contraction MRR as a percentage of MRR lost increases in proportion. Although, it does eventually stabilize around that 30% range. Benchmarking MRR Movements by ARPA Bands In the section above, we looked at MRR movements by the MRR band. In this section, we look at MRR movements by bands of average revenue per account (ARPA) per month. As a reminder, ARPA is the average revenue per account, i.e. average MRR across all your customers. It is also known as ARPU or APRC. You can find your ARPA in . ChartMogul Why look at MRR movements by ARPA band? Well, at a given ARPA value. The way you sell, the way you service, and the way you retain all depend on your ARPA. everything is sort of the same MRR Added Benchmarks by ARPA Bands The chart below shows new business MRR as a percentage of MRR added across bands of ARPA per month. As you’ll notice, here too, new business MRR makes up the largest share of MRR added. Although, at higher ARPA, this proportion does get smaller. This is because, at a higher ARPA, expansion starts to contribute more to the MRR added. For example, companies with ARPA per month of >$500 or annual contracts over $6k get 43.7% of their revenue through expansion. For companies with an ARPA of less than $10, it’s only 7.9%. The reactivation proportion of MRR also depends on your ARPA. At a higher ARPA, your reactivation MRR decreases. One reason for this could be that at a higher ARPA, . And because of that informed decision, fewer come back. fewer customers take the knee-jerk reaction of churning MRR Lost Benchmarks by ARPA Bands As for MRR lost, Churn is the largest contributor. Although, for startups with ARPA >$500, churn contributes to only a little more than half of the revenue lost. The rest is contraction MRR. If your business is in a higher ARPA band, retaining existing customers and making sure they are using your product becomes of key importance. Calculation Methodology. We used anonymized and aggregated data from ChartMogul’s platform to carry out this analysis. We categorized companies into MRR & ARPA bands and then calculated aggregates over 3 months (Dec ‘21, Jan ‘22 & Feb ‘22). Three Questions You Should Ask Yourself Now that you understand the basics of MRR movements, there are three questions that you should ask yourself: Do you understand the dynamics of MRR movements for your particular business? For example, do you know how much of your MRR added comes from new business vs expansion or reactivation? Do you have an expansion loop built-in within your product? As businesses grow, one of the key drivers for their growth is expansion revenue. Does your pricing strategy take this into account? Do you have a strategy in place to contain contraction? Contraction can be as high as 45% of all MRR lost at higher ARPA’s. Having a strategy in place to contain that could help you grow faster. As is wisely said, MRR Saved = MRR Gained :)

How to Take a Hold of Your MRR Movements

Over the last six months, we built and refined a dedicated outbound sales strategy. The result? A swath of data and learning, but, ultimately, the decision to pull the plug. This is the story of our most comprehensive attempt at outbound which was quick to remind us that 1) every business is different and 2) sometimes dedicated planning and grit still result in failure. ChartMogul is a product-led business. We spend most of our waking hours thinking about how to build a reliable, beautiful product that helps subscription businesses grow faster using their customer and billing data. This mentality extends, of course, to our marketing strategy, which is why folks still print out and read . our cheat sheets our weekly roundup It also extends to our customer acquisition and sales strategy. More than 90% of our leads come through our 14-day trial. Then, it’s our job to help those businesses get set up, evaluate our product, and ultimately, make a purchase decision. We’ve grown sustainably for six years in this way. Enter: the allure of an outbound sales motion. In a recent completed in Q2 of 2016, less than 20 percent of mid-size B2B companies relied on solely inbound or outbound strategies; 84 percent of respondents used some mix of both. Act-On and Demand Metric study We know who our prospective buyers are, what is important to them, and how to engage them — after all, we’ve been working with SaaS founders and operators consistently for some time. And importantly, our retention rate for these customers is high. What would it mean for our business if we could crack outbound sales? If we could reliably generate new opportunities and onboard right-fit customers? Could introducing a new sales motion accelerate our ability to hit our next few revenue targets? Our outbound sales strategy We set a plan to find out. To properly test outbound, we knew that we needed the following: Hungry salespeople trained on and devoted to outbound efforts Appropriate process and tooling Target accounts and reliable contact information Personalized, on-brand messaging that illustrates how and why we’re the right subscription analytics partner. We hired two SDRs (Leo and Verena), trained them on our value proposition, outreach style, and strategy. We consumed the latest and greatest prospecting content from sales leaders like and . We even took Winning by Design’s 4-week course on prospecting. Becc Holland Josh Braun We decided to focus our efforts exclusively on our best-fit customers: B2B SaaS. We curated a list of these businesses and researched their pricing and billing strategies. Notion housed a dedicated outbound sales playbook, complete with best practices, templates, and creative ideas. Thomas, our senior sales lead in EMEA, that automatically sourced contact details for qualified prospects at those businesses. built an impressive process and toolset Before we started, we mapped out the success criteria for measuring outbound — we required consistency, strong sales qualification, and larger opportunities (±2x ASP because many ChartMogul customers pay $100-$250/month). Our SDR team strived to contact 40 new accounts/week with highly personalized 1-1 messaging. What worked with our strategy So, how did it go? The energy invested in personalization proved fruitful. Prospects were receptive. Our email outreach yielded meetings, and we were able to create qualified opportunities. We coupled email outreach with social, and Twitter proved a hearty avenue for conversations with SaaS founders. Many SDR teams strive to book meetings, and while that was a top priority for us, we also encouraged prospects to trial our product. This is because many of our buyers prefer to evaluate the capabilities of our product without sales assistance — and ‘being aligned’ with prospects is a core value of our sales culture. We know that trial users with imported data convert to paying customers at a high rate, so getting prospects to try the product is half the job. We were hoping that an outbound strategy can help us add even more fuel to our . product-led motion Through effort and determination, we managed to get new users on the product, reactivate old trials, book discovery calls, create opportunities, and win new customers. Importantly we did this in a way that was true to ourselves without burning our brand. What didn’t work so well… Unfortunately, we weren’t able to win enough customers to consider the program a success. In just under six months, we were able to: Set 39 total meetings set from an average of 1,650 emails sent/month (~10K emails sent total) Create 13 deals (which is less than 1 deals created/month/SDR) Convert 7 new customers (which is less than 1 sales/month/SDR) at a win rate of 54% and ASP = 1.5x You can see that the funnel breaks down from outreach to meetings booked. To counteract this, we increased the volume of outreach after several weeks. Still, we were unable to get enough consistent meetings to ensure the program’s success. I have a few hypotheses why the program didn’t work as we were hoping it would… though it’s most likely a combination of all of the following: B2B SaaS founders are the recipients of lots of outbound, so it’s perhaps a less effective strategy than it was five years ago Our messaging and timing was weak The order/sequencing of our outreach was lacking Prospects on our target list are satisfied with their current state Our segmentation was too broad What’s next? Continuing the program could mean winning a new large customer here and there, but the allure of outbound promises consistency. And we must employ sustainable strategies that give us energy and keep us focused. This is, of course, a bit frustrating, but our dedicated attempt was comprehensive enough to learn that outbound sales is not a viable GTM strategy given current inputs. And maybe that’s true for you too. We hear a lot about the importance of focus for product teams, but rarely for commercial teams. Sales and marketing teams are all too often pursuing a quick win or growth hack instead of sustainable growth via select channels. It’s essential to keep an eye on your limited resources and use them in the best way possible. For now, we’ve decided to retire these efforts and turn our focus on opportunities with potential for viral results. Stay tuned!

Outbound Sales Strategy and Why We Decided Against It

Pricing localization is a strategy where you present the price of your SaaS differently depending on where the customer lives. You may also hear it referred to as multi-currency pricing or localized pricing. If I asked you how much a house cost, could you give me an answer? The answer is likely no because there’s no such thing as a universal price, even for an identical house. You’ve heard it before—location, location, location. A similar property has a different price tag in Toronto, Paris, São Paulo, Cairo, Seoul, and Bangalore. The same could also be true for your SaaS business. In our , we detail the importance of SaaS pricing and how to get it right for your audience. We also shared that revisiting your monetization strategy is an essential part of growing your business. While some companies might want to stick with the rates that work right now, there may come the point where you can’t rely on growing your market share at the same rate as your company’s early days. B2B SaaS Pricing Masterclass One way your pricing can change as your company evolves is by using multi-currency pricing. Here’s what you need to know about SaaS pricing localization. What is pricing localization? Pricing localization is a strategy where you present the price of your SaaS differently depending on where the customer lives. You may also hear it referred to as multi-currency pricing or localized pricing. Even the simplest pricing localization method requires new workflows and considerations, so it’s understandable if you’re apprehensive about jumping in feet first. Here are some of the benefits of SaaS pricing localization that can make the transition worthwhile: Potential customers may feel more comfortable when they browse your pricing page and see their local currency Optimizing pricing for different countries could help you grow your market share in a region Experimenting with localized pricing lets you find the ideal strategy for each country and increase revenue 2 types of pricing localization Not all pricing localization strategies are created equally. There are two to choose from, and they each come with their benefits and challenges. Change your display currency The first and most straightforward type of pricing localization is where you only change the currency shown. This localization strategy is also called “cosmetic” localization. When you use this strategy, customers avoid any sticker shock at checkout or after payment since they see the price they’ll pay upfront. Having local pricing also makes it easier for potential customers to imagine the cost in their budget without mental math for the exchange rate. For example, shows pricing in local currency for select countries. The America pricing page has plans starting at $99 while French browsers see prices from €99. In this scenario, the pricing strategy is the same, and the only variable is the currency that customers see and use. Hotjar The benefit of cosmetic pricing localization is how simple it is to implement. There’s no need to adjust your pricing strategy or tiers—simply update the currency based on the person’s location. This pricing localization strategy works best when the exchange rate and cost of living between the base currency and display currency are similar. Change your product cost The second type of SaaS pricing localization is more strategic than a simple cosmetic change in currency. Instead, you can customize your pricing based on your customer’s cost of living and purchasing power and have “true” localization. A country or region with a higher cost of living or exchange rate closer to your home currency has a similar or identical price to home. A country with a lower cost of living or buying power pays a proportionally smaller price. Netflix uses a true pricing localization strategy to the fullest extent, with special pricing for . Monthly pricing varies by location and is either displayed in local currency or USD. If you ever wondered what Netflix costs in Japan, Afghanistan, Swaziland, you can . many of the 190 countries it serves browse pricing here Wondering how SaaS companies come up with these local prices? While we don’t have the inside scoop on Netflix’s exact pricing strategy, you can use the . Yes, that’s the real name. The Economist compares the price of a Big Mac across the world using the same base currency, like USD. You can to compare pricing using your base currency. Big Mac Index use this tool Here’s an example. Imagine your entry-level plan is $10 a month USD, and you want to localize to Russia. If you use the proportion for the current Big Mac Index ($5.67 in the US vs. $2.20 in Russia), you would divide your base price by 2.5 (the Big Mac ratio) for a Russia-localized price of $4 a month USD. While customizing your SaaS pricing based on the cost of living is more work than changing the display currency, it could be the way to go for some regions. If you want to expand to markets with very different economics than your own (whether they have more or less purchasing power), true pricing localization makes you a more accessible option. Pricing localization may even give you a competitive advantage if you’re the only option doing it. Though it might be hard to quantify, it’s also possible that customizing a sales page to a person’s location could feel more personal. How to decide when to use localized pricing for your SaaS If you’ve read this far, chances are you’re curious about trying SaaS pricing localization on for size. Here are a few questions to ask yourself to see if it’s time to experiment with multi-currency pricing. If pricing plays a critical role in your positioning Before you start changing your pricing, you need to think about your customers in each region. For subscription apps like Headspace, a global audience is part of their growth ambition. , former Product Marketing Lead at Headspace and how it aligns with their goals of bringing mental health to the world. Cristina Poindexter talked about price localization strategies Her recommendation is to begin your pricing localization discussions with positioning. Talking about whether you want to be a premium product or mass-market solution upfront makes every other pricing localization decision easier. If you want to hear more about Headspace’s experience with pricing localization, . this discussion in partnership with Google Play is worth watching If you’re at a stage where you want to appeal to as many SMBs as possible, then a competitively low price could be ideal. In that case, true pricing localization that makes your cost attainable in your target countries could be the way to go. On the other hand, there can be such a thing as a “too low” price for enterprise customers if it makes them feel that you can’t handle their scale. If a higher price is essential for positioning, a less complicated cosmetic localization strategy offers easier customization. It’s also worth noting that it’s easier to lower existing prices than raise them, so experimenting with higher prices is worth exploring. If you have (or want) a global audience Until you have a solid pricing strategy at home, you likely don’t need to sweat the small details of global pricing localization. Earlier stage companies that focus on capturing more of their existing potential TAM (total addressable market) in one country or region can skip pricing localization for now. If you want to grow in a specific country or notice more and more customers from a region, then you can consider localized pricing. When in May of 2021, , founder of , commented on how the change would benefit global creators. Stephen shared that, “the hope [with localized pricing] would be that this ultimately makes it possible for MORE creators to make revenue on Twitch and more fans supporting their fav creators.” Twitch announced localized pricing Stephen Ellis Pipeline If conversion rates are much lower for a country or region Maybe you’re here because you’ve realized that as hard as you’re trying to break into a new market, you just aren’t gaining the traction you’d like to see. It’s possible that pricing could be to blame, particularly if it’s a country with a vastly different cost of living. Pricing alone isn’t necessarily the culprit, but something to experiment with. Trying price localization could also help if you want to grow in a region where you’re nearing the ceiling of the total addressable market. Rather than adding new customers at the same rate as you used to, you could try customizing pricing to reach your revenue goals. ChartMogul can help you understand your customers and where they are hailing from and answer questions like: Which regions or countries have the highest Average Revenue Per Account? Where is churn most prominent? What to expect when you take on multi-currency pricing Your wheels are turning now, and you think you want to pitch the idea of pricing localization to your team. The only problem? It’s going to be a team effort. Implementing a new and variable pricing strategy comes with many moving parts, and everyone has a role. Your marketing team needs to manage positioning Questions about the impact of pricing on your positioning will likely go to the marketing team. They’ll need to research the market you want to enter (or optimize) and understand how pricing affects decisions. Questions for your marketing team to explore: How are competitors pricing their tiers in the country? What do buyers in this country look for in a SaaS? Does our messaging need to change alongside the pricing update? Your product team needs to customize displays by location If your website is currently the same wherever you access it, some updates to the pricing page are necessary. The simplest route would be creating a guide where people can browse pricing by country . To make it seamless, though, you’ll probably want your pricing page to update based on a person’s location. , as Netflix has Questions for your product team to explore: How many versions of the pricing page will we need? How will we update pricing based on location? Does pricing localization also impact other steps in the checkout and billing process? Your finance team needs to manage multi-currency invoices Unsurprisingly, your finance team will probably have the most adjustments to handle when switching to localized pricing. While you’ll still manage your accounting in your home currency, things like invoices and typical payments will vary between customers. Questions for your finance team to explore: How will we manage multi-currency invoices, contracts, revenues, and payments? What tools will help us manage conversions between currencies? Are there any tax or accounting implications to managing multiple currencies and countries? Your sales team needs to monitor fluctuating MRR In ChartMogul, you can set your primary currency, whether it is EUR, USD, or the currency where your business is headquartered. When ChartMogul comes across an invoice that is billed in a different currency, it will automatically convert the MRR amount to your account’s primary currency. Your ‘Primary currency’ is the currency in which your revenue is reported in your ChartMogul account. We found that this is the most common and useful way in order to track subscription metics. If your global customers pay different amounts, our projections and reporting will vary. Even if you go the simpler route of “cosmetic” localization, you still need to manage exchange rates. This means that metrics like your MRR will fluctuate, even if there aren’t actual changes in accounts. Questions for your sales team to explore: How will we adjust reporting and analysis to account for exchange rate fluctuations? Do we need separate goals and benchmarks for each region? How do we expect pricing to impact close rates? ChartMogul helps you manage global subscriptions You can’t manage what you don’t measure, but luckily for your teams, ChartMogul makes it easy to monitor global subscriptions. Our subscription analytics platform helps you measure, understand, and grow your recurring revenue. There are also features to help you manage exchange rates, so you have an accurate view of MRR and change your base currency at any time.

SaaS Pricing Localization: How to Do It the Right Way

To my fellow SaaS bootstrappers still relying on a creaky home-grown metrics system — or worse, not having access to any metrics at all — I recommend you start using to get accurate insights into the health of your product. ChartMogul I’m a ChartMogul customer, and I’m a bootstrapper. I’m the founder of Feature Upvote, a bootstrapped and profitable SaaS. As a cash-strapped bootstrapper, if I spend money on a service, it has to be . I need to choose wisely where I spend my company’s limited funds. Because, as 100% owner of my company, the money I spend is money coming out of my own pocket. essential So why do I spend some of that precious, limited money on ChartMogul? Before ChartMogul: Home-grown Metrics In the early days of my business, I wrote my own system for calculating metrics. I say ‘metrics’, but it was really just the singular ‘metric’ of MRR. I only cared about MRR because I hadn’t yet learned about other important SaaS metrics such as Churn and Lifetime Value. MRR was what many bootstrappers were sharing on Twitter and Indie Hackers. Calculating MRR seemed easy, something I could do with one SQL query and a basic web page. And it was easy — when I had just one price point and a few customers. But as my business got traction, pricing got more complex. There were discount plans, coupons, and refunds. My SQL query to calculate MRR was becoming complex and indecipherable. I also had no way to view history and trends. Knowing MRR alone is not useful if I can’t compare it to MRR from a month, six months, or a year ago. Then I added multiple currencies. That completely broke my home-grown metrics. The data it showed was simply wrong. But I didn’t want to spend time maintaining it. I was in the unpleasant situation of having to make business decisions with little data, and what data I had was wrong. As my fellow bootstrappers will know, you always have too many things to do. It is hard to find the time to maintain an internal system used only by the founder. It is the type of work that always finds itself pushed off the to-do list. Discovering ChartMogul’s free plan I read a blog post from another bootstrapper that featured an attractive chart of their MRR growth over time. This chart was generated by ChartMogul and it was awesome! I wanted one for myself! So I took a look at ChartMogul. I instantly realized this was so much better than what my home-grown solution ever could be. Even better, because my MRR was below $10K, I could use ChartMogul’s free plan. More metrics, attractive charts, and free? How could I use ChartMogul, at least until Feature Upvote grew out of the free tier. not Best of all, unlike my homebuilt system, the data was actually accurate. What I initially learned from ChartMogul ChartMogul has excellent that explain what SaaS metrics are and how I can use them. From them I learned that SaaS metrics are more than just MRR. free resources Even just the way MRR is reported in ChartMogul was eye-opening. It breaks down my MRR growth into “New Business” MRR and “Expansion” MRR. This concept of expansion growth was new to me. I soon learnt that it is important for success in SaaS. Expansion revenue is revenue growth that comes from existing customers when they upgrade to a more expensive plan. If your product doesn’t yet have a pricing model that allows your happy customers to give you more money/month, I highly recommend adjusting your pricing model. I discovered that by accident, I had baked into my pricing model. expansion revenue Another SaaS metric that ChartMogul gave me was , a metric I now watch as closely as MRR. This shows how quickly I’m losing those hard-won customers. In the early days, this churn was way too high for my company to ever be sustainable. I got churn under control, partly by improving my product, support and docs, but mostly by increasing prices. Gross Churn Rate $10K MRR: Time to start paying Happy day! I got a notification from ChartMogul telling me I had hit $10K in MRR. But also a sad day, because now I would no longer be able to use ChartMogul for free. My first impulse was to cancel my ChartMogul account. I was still cash-strapped, with too many competing demands on my limited revenue. Paying money to see some pretty charts each month didn’t seem to be a sensible business decision. And yet, I realized it was much more than pretty charts. I had come to rely on the information that ChartMogul gave me. It had become essential in my decision-making. To save money, I resurrect my home-built SaaS metrics system, and devote some time to make it accurate and show more metrics. But when I estimated how long that would take, it seemed like a silly thing to do, when I could instead pay ChartMogul to keep getting the information they were already providing. could In the faced by SaaS founders, buy was the right decision in this case. age-old conundrum of buy-vs-build Decisions I make using ChartMogul I want to share how spending money on ChartMogul has helped me, financially and psychologically. When to pause Google Ads Last year I started running my first Google Ads campaign. After two months of learning and tweaking, Google Ads started to give me new paying customers. But were they paying enough to justify the ad spend? What I needed to know was my “Customer Lifetime Value” or LTV in ChartMogul. I discovered that it wasn’t high enough based on my cost per acquisition from Google Ads. So I paused the ad campaign until we could improve our LTV. Knowing that I should pause the Google Ads campaign saved me way more than I was paying ChartMogul. From that decision alone, my ChartMogul subscription has been worth it. Once our LTV improved, I restarted my Google Ads campaign, confident that doing so was now worthwhile. How did I increase LTV? By increasing prices, which I’ll tell you about further down. Focus on the long term More than I like, my self-esteem as a bootstrapped founder goes up and down with MRR growth. Month-over-month growth greater than 10%? I’m the champion of champions, I tell myself, a true business visionary! But growth only 1% or 2% this month? What am I doing pretending to be something I’m not? Clearly, I have no business acumen at all and should start checking the job ads. A way I’ve found to deal with the yoyo-ing of my business self-belief is to look at longer-term trends in ChartMogul. One way is to compare metrics year-on-year. ChartMogul does this comparison with many metrics by default. This long term view keeps me relatively calm. Another way is to smooth out the curves by grouping data by quarter. I set the date range to all-time and group data by quarter instead of by month, then view the MRR chart. This quarterly view shows me a smooth and steady increase in MRR. Instead of being blinded by monthly swings, I can see that our long-term progress is good. Effect of a large price rise I have the developer’s mentality, shared by many technical founders, whereby we vastly undervalue our work. For a long time I wasn’t charging enough for Feature Upvote. Slowly and steadily I’ve become willing to experiment with pricing, but every price rise still causes me anxiety. My first price experiments were small and cautious price increases — followed by weeks of closely monitoring the result in ChartMogul. Are people still signing up for paid accounts? How does behavior differ at different pricing levels? Who is churning? I monitor the long-term results of pricing changes via ChartMogul’s “Average Revenue Per Account” or ARPA chart. This is perhaps my favorite view of my business in ChartMogul. Watching the consistent ARPA growth helps steady my nerves as our prices go up. After the initial price increases went well, I started to feel bold, so in late 2020 I abruptly doubled our prices for new customers. (Existing customers remained on the old pricing.) Using ChartMogul’s segments feature, I can compare customers by pricing: one segment for customers on old pricing plans, and one segment for customers on the new much higher plan. Comparing customer segments by price has been a revelation. Customers at the new price point have much lower churn. They have higher LTV, way more than double. SaaS veterans already know this, but I had to learn this myself. Only by seeing the result of a large price increase in my own business did I really understand what happens — increasing prices overwhelmingly leads to better customers, who pay more and churn less. I can conclude that raising prices — despite causing a drop in customer signups — was a very good decision. A vital tool for decision making My product was launched four years ago this month, and I’ve been using ChartMogul for three of those four years. It remains a vital part of my decision making process. I discarded my old home-grown metric system long ago, and it is never coming back. Although I was hesitant at first about paying for ChartMogul, it has helped me earn much more than I pay for it.

ChartMogul

chartmogul.com

126 employees

Since 2014

COMPANY RANKING

ChartMogul

EVERGREEN INDEX #1679

See more notable links about ChartMogul

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #ChartMogul

ChartMogul

ChartMogul

chartmogul.com

126 employees

Since 2014

COMPANY RANKING

ChartMogul

EVERGREEN INDEX #1679

Related CompaniesRank

ChartMogul Story MentionsComplete List

See more notable links about ChartMogul

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #ChartMogul

ChartMogul