The Chargebee success story does not start with a lightbulb moment. It does not start with a problem encountered in the shower or an insight that arrived during a carpool. It starts with a spreadsheet.
In 2004, Rajaraman Santhanam sent a document to his college friend Krish Subramanian. It was not a business plan or a product vision. It was a savings plan. It included instructions for saving between 20% and 30% of your salary every month, reducing your lifestyle systematically, and accumulating enough capital to eventually start something without being at the mercy of investors from day one.
Krish read the spreadsheet and made a decision. He sat down with his wife and told her that if he did not try this, he would regret it for the rest of his life. She backed him fully. They began cutting back on everything. Neither of them wanted to launch a startup and then find themselves making hard short-term decisions because the runway had run out.
For seven years, they saved.
The patience embedded in that origin story explains almost everything about how Chargebee was eventually built: the willingness to spend five years finding product-market fit before the growth hockey stick appeared, the resistance to raising money before the company needed it, the culture of listening to customers obsessively because word of mouth was the only marketing budget available, and the product quality that came from competing on service rather than spending.
Most startup success stories are about speed. This one is about the discipline to go slow in order to eventually go fast.
The Team Was the Idea
By 2009, Krish had built a genuine career. He had worked at MatexNet, TCS, and Cognizant, leading engineering teams, understanding how global software companies were built and scaled. When Cognizant offered him the chance to take a US account and build a team there, an opportunity that could have defined the next five to seven years of his professional life, he said no.
He went back to India and started looking for a problem to build a company around.
What happened next was unusual even by startup standards. The founding team came together before the idea did. Krish and Rajaraman reconnected, motivated by their years-old savings plan and a shared desire to build something. Rajaraman, who had spent nearly a decade at Zoho, one of India’s most influential SaaS companies, brought his former roommate Thiyagarajan Thiyagu into the conversation. Thiyagu was on sabbatical from Zoho. Then Rajaraman and Thiyagu convinced their mentor at Zoho, Saravanan KP, who had spent 12 years there as a technical architect, to join as well.
By May 2011, all four had quit their jobs. They were building full time. In a drawing room in one of the co-founders’ houses in Chennai. With no product and no idea what they were going to build.
This is the opposite of how the conventional startup story goes. You are supposed to have the insight first, then recruit the team to execute it. Chargebee assembled the people first and then looked for the problem.
Krish has described his framework explicitly: he did not care which problem they chose as long as they chose something that could scale. He was not looking for the one right idea. He was looking for a team capable of executing on whatever idea they picked.
This philosophy, that the quality of the people matters more than the quality of the initial idea, is something that Krish has returned to repeatedly in public conversations. It is also something that the Chargebee story validates quite directly. The company they ended up building looks almost nothing like the early experiments they considered. What carried them through the pivots and the slow years was not the original product thesis but the combination of engineering depth, customer empathy, and interpersonal trust that existed between four people who had known each other for years before they started.
The Problem They Chose
KPS and Rajaraman came up with three ideas. They chose billing.
The reasoning was blunt and correct: everyone needs to get paid. More specifically, the founders had been watching the subscription economy begin its ascent, and they noticed that the software infrastructure supporting it was genuinely terrible.
In 2011, if you were building a SaaS company and wanted to charge customers on a monthly or annual basis, you faced an unpleasant set of options. You could build your own billing system from scratch, which required significant engineering resources and ongoing maintenance that most startups could not afford. You could use enterprise billing tools that were built for much larger companies and required months of implementation. Or you could patch something together with a payment gateway, manually managing all the complexity around subscription renewals, plan upgrades, downgrades, proration, trial periods, dunning, tax compliance across geographies, and revenue recognition.
None of these options were good. Every SaaS startup was effectively rebuilding the same billing infrastructure from scratch, making the same mistakes, and distracting engineers from building the actual product. Chargebee was going to be the infrastructure that let a startup handle all of that without building anything themselves.
The insight was not original in the abstract. The execution was what mattered. And the execution started in a drawing room in Chennai with four engineers who understood deeply, from years of working inside Indian SaaS companies, what good software looked like and what the real experience of building billing infrastructure felt like.
Freshworks, which was simultaneously being built by Girish Mathrubootham in Chennai at the same time, became one of Chargebee’s first customers. Girish and Krish had bonded over coffee and South Indian food before either company had meaningful revenue. The Freshworks connection was not incidental. The founding circle of Chennai SaaS, the companies that came out of Zoho’s orbit, that were building global software products from India, that understood both the technical and the customer-facing requirements of subscription businesses, became Chargebee’s earliest and most important reference customers.
Five Years Before Product-Market Fit
Krish has divided Chargebee’s history into two distinct phases. The first five years were about finding product-market fit. The second five years were about scaling what they found, growing at roughly 100% annually once the product clicked.
The first phase was harder and longer than most companies would have survived. The early customers were small SaaS startups and ecommerce companies that needed billing automation but often had limited budgets and very specific requirements. Chargebee was competing against better-funded global incumbents, primarily Zuora and Recurly, while operating from Chennai and trying to win the trust of US and European companies who had no particular reason to trust an Indian startup for something as critical as billing.
The trust-building strategy was simple and required a lot of person-hours: obsessive responsiveness. If a customer had a question, Chargebee answered it fast. If they had a problem, Chargebee fixed it fast. If they needed a specific feature or integration, Chargebee built it and told them when it was ready. The quality of the support and the speed of the iteration cycle became the product differentiators that marketing dollars could not buy.
Rajaraman’s framing of the competitive strategy was direct: “We couldn’t out-market others. We had to out-listen and out-serve. That’s what helped us win those crucial first 100 customers.”
Those first 100 customers became advocates. They told other founders at startup events and in Slack communities and on Hacker News that Chargebee was the billing infrastructure that actually worked and actually had support that answered you. The word-of-mouth growth that followed was the direct result of having served those early customers so well that they felt a personal stake in the company’s success.
By January 2013, Chargebee had its first customers. By 2019, Accel invested in the company’s first significant outside round, an $18 million Series B. Between those two dates was seven years of bootstrapping, frugal operation on the savings the founders had accumulated, and product iteration driven entirely by customer feedback rather than investor mandates.
Why Bootstrapping Was a Strategic Choice
Chargebee’s seven years of bootstrapping before taking significant outside capital is unusual for a company that eventually raised $470 million and reached a $3.5 billion valuation. It was not accidental.
The savings plan that Rajaraman had shared with Krish in 2004, the frugality they had practiced through the years before founding the company, gave the founders enough runway to wait for the right moment to raise money rather than raising it out of desperation. When you are not running out of cash, you can afford to say no to investors whose timelines or portfolio conflicts make them a bad fit. You can afford to wait for the customers who will become real advocates rather than taking any revenue you can get. You can afford to build the product the right way rather than shipping something undercooked because a fundraising timeline demands it.
The culture that Chargebee built during those bootstrapped years was also specific. Without a marketing budget, the only acquisition channel was customers telling other customers. Without investor pressure to show fast top-line growth, the only metric that actually mattered was whether customers were genuinely delighted. These constraints produced habits that persisted even after the company was well-funded: a bias toward serving customers over acquiring them, a product philosophy that prioritized depth and reliability over breadth and speed, and an engineering culture that took pride in the craft of what they were building.
Krish has described the Insight Partners relationship, which began with the company’s first US-focused institutional round in 2019, as transformative in a specific way. Insight pushed Chargebee to think carefully about which customers were actually their best customers, not the loudest or the most demanding, but the ones whose needs matched what Chargebee was built to solve. That analysis shaped the product roadmap for the following years. Building products for the best customers rather than the most vocal ones is a discipline that most companies learn too late, if they learn it at all.
The Product That Became a Platform
The original Chargebee product was a subscription billing tool. You connected it to a payment gateway, configured your pricing plans, and it handled the recurring charge cycles, upgrade and downgrade logic, trial management, and invoice generation that would otherwise require months of in-house engineering.
This product was genuinely excellent at what it did. But billing, as the founders discovered over years of listening to customers, was only one layer of a much larger problem. The companies using Chargebee to handle their billing were also struggling with revenue recognition, which is the accounting process of determining when and how to record revenue from multi-year contracts, prepaid plans, and complex subscription arrangements. They were struggling with customer retention, specifically with the process of identifying customers who were about to churn and doing something about it before they cancelled. They were struggling with revenue analytics, with understanding which pricing models, which customer segments, and which acquisition channels were actually generating sustainable recurring revenue.
Chargebee’s response to this was to expand the platform through both organic product development and strategic acquisition.
RevLock, acquired in late 2021, added automated revenue recognition that helped Chargebee’s customers comply with ASC 606 and IFRS 15, the accounting standards that govern how SaaS companies recognize revenue. This is genuinely complex stuff that finance teams at growing companies spend enormous amounts of time managing manually. Automating it within the same platform that handled billing made the combined product significantly stickier and significantly more valuable.
Brightback, acquired in January 2022, added intelligent churn prevention. When a customer tried to cancel their subscription, Brightback’s system could identify the reason and present a targeted intervention: a discount, a pause option, a downgrade path, a personal outreach from the account team. This turned the cancellation flow from a one-click exit into a managed process that materially improved retention for the companies using it.
The combination of billing, revenue recognition, and churn prevention created what Chargebee called a “revenue operations platform” rather than a billing tool. The transition from billing company to revenue operations platform is the same strategic move that Salesforce made from CRM to business software, or that HubSpot made from marketing automation to an integrated business platform. You start by solving one urgent problem exceptionally well. Then you use that customer trust and distribution as the foundation for expanding into the adjacent problems that your existing customers also have.
The bimodal go-to-market that Chargebee operated was a natural extension of this platform ambition. On one end, early-stage startups could use the free tier to get subscription billing running quickly, without procurement cycles or implementation timelines. As those startups grew, they encountered more complex requirements: multi-currency support, regional tax compliance, sophisticated dunning workflows, enterprise reporting. Chargebee was already there, already understood, already trusted, with features ready for each stage of growth. The land-and-expand motion was built into the product architecture.
From Chennai to Global Infrastructure
Building a global software company from Chennai in 2011 required overcoming a specific kind of friction that Silicon Valley founders do not typically face. US and European customers in the early 2010s were not accustomed to trusting critical billing infrastructure to a company based in India. The perception was not that Indian engineers were less capable, but that a startup without a physical presence, without US-based support, and without the social proof of notable US investors or US-based customers was a risk they did not need to take when they could use a company they had heard of.
Chargebee’s response to this was characteristically operational rather than marketing-driven. They made the support experience so good that the location of the support team became irrelevant. They built compliance infrastructure, SOC 2 certification, PCI compliance, GDPR compliance, the trust signals that enterprise buyers required, before enterprise buyers made it a formal requirement. They accrued reference customers systematically, prioritizing logos that would carry weight in the conversations they needed to have.
When Freshworks went public in 2021, it was meaningful for Chargebee in a specific way. Freshworks was a proof point that a global SaaS company built from Chennai could achieve the scale and the credibility required for enterprise customers anywhere in the world. The Chennai SaaS ecosystem that included Freshworks, Zoho, and Chargebee among its most prominent companies had collectively demonstrated something that investors and customers could now take seriously: India was not just an outsourcing destination but a genuine source of product-led software innovation.
Chargebee’s customer base by the time of its 2022 Series H reflected this trajectory. Over 4,000 subscription businesses in 60+ countries. Okta, Freshworks, Calendly, Study.com, Goop, Pret a Manger on the customer roster. Revenue growing at rates that allowed the company to double its valuation from $1.4 billion to $3.5 billion in nine months.
The Revenue Numbers and the Discipline Behind Them
Chargebee’s revenue trajectory tells the story of those two phases Krish described. $24 million in 2020. $33.7 million in 2021. $115.4 million in 2022, a 3x jump driven by the pandemic acceleration of subscription business adoption and the platform expansion. $124.4 million in 2023. $202.6 million in 2024.
The pandemic was meaningful for Chargebee for the same reason it was meaningful for Zoom, DocuSign, and every other tool that enabled remote and digital business. Companies that had been planning to move their business models toward subscription were suddenly forced to move faster. Companies that had been relying on in-person sales and delivery had to find digital distribution immediately. All of them needed billing infrastructure, and Chargebee was positioned to absorb that demand because the platform had been built patiently for exactly this kind of customer.
The 2022 jump from $33.7 million to $115.4 million is the number that most observers point to as the inflection. It was real. But it is worth situating it correctly. The infrastructure that allowed Chargebee to absorb that growth without breaking was built during the years of slower growth that preceded it. The engineering depth, the support culture, the compliance certifications, the product breadth that came from the RevLock and Brightback acquisitions: all of it was in place before the pandemic created the demand spike that filled it.
The layoffs of late 2022 and 2023, which affected approximately 142 and then 100-120 employees respectively, reflected the same discipline that had defined the company’s approach to everything else. When it became clear that the pandemic-driven growth spike had overstated the sustainable baseline, and that the company had hired ahead of demand that did not materialize, Krish made the adjustment. The CEO described it as responding to market shifts and refocusing on core strengths. It was the same deliberate, patient approach applied to contraction that had been applied to growth.
Building Out of India, Thinking Like a Global Company from Day One
One of the things Chargebee got right that many Indian software companies of its generation got wrong was the global positioning from the beginning.
Rajaraman spent nearly a decade at Zoho, and Zoho’s influence on how Chargebee thought about building software for a global market is visible throughout the company’s history. Zoho had demonstrated that an Indian software company could build world-class products for US and European enterprise customers without relocating to the US and without abandoning the cost advantages and engineering talent depth available in India.
Chargebee built on that template. The engineering and product teams remained in Chennai. But the go-to-market, the customer success infrastructure, and eventually the executive team were built globally. The San Francisco address on the incorporation documents was not a vanity headquarters but a functional presence in the market that mattered most for the company’s early growth.
The willingness to invest in compliance certifications early, before customers demanded them, was another expression of global ambition. SOC 2, PCI DSS, ISO 27001, GDPR: each certification was expensive and time-consuming to obtain. Each one also removed an objection from the enterprise evaluation process and signaled a level of infrastructure maturity that smaller competitors often deferred until customers forced the issue. By the time enterprise buyers were asking about compliance, Chargebee already had the answers.
What the Chargebee Story Is Really About
Krish Subramanian received a savings plan spreadsheet in 2004 and took it seriously enough to reorganize his financial life around it. Seven years later he and three co-founders built a company that would grow to $202 million in annual revenue and a $3.5 billion valuation.
The connection between those two things is not coincidental. The discipline of saving 20-30% of a salary to fund an eventual startup is the same discipline as spending five years finding product-market fit without capitulating to investor pressure for faster growth. It is the same discipline as choosing to serve your best customers rather than your loudest ones. It is the same discipline as investing in compliance infrastructure years before customers require it. It is the same discipline as making acquisitions to expand the platform rather than bloating headcount to pump short-term metrics.
Chargebee is what a subscription economy should produce: a company that practices what it sells. The platform exists to help other companies build durable recurring revenue businesses. The company itself was built on the same principles. Patience, repeatability, customer trust, and revenue that compounds over time rather than spiking on hype and collapsing when the hype fades.
The founders could not out-market Zuora. They could not out-spend Recurly or the Stripe Billing teams. What they could do was out-serve every customer they touched, build the trust one company at a time, and let the product quality and the customer advocacy do the work that other companies delegated to marketing budgets.
It took five years to find product-market fit. The five years after that were 100% growth annually. The patience was the prerequisite for the acceleration.
A savings spreadsheet sent between college friends in 2004. A drawing room in Chennai. Four engineers who cared more about building the right team than finding the right idea. And a billing product so good that 18,000 subscription businesses in 60 countries now trust it with their revenue.
Leave a Reply