Girish Mathrubootham on Freshworks Pricing, Products and Scaling

Girish Mathrubootham looks for founders who understand a problem deeply, show craftsmanship and can hire strong teams. The Freshworks founder discusses product, pricing and company building with Harry Stebbings, drawing on his own operating and investment experience.

Mathrubootham recalls being a restless student who did not try hard to fit in. He spent roughly a decade building products before Freshworks, having discovered product management after a manager challenged him to change roles.

A broken television shipped from Austin to Chennai helped inspire Freshworks. After months of unsuccessful insurance claims, he posted on an online forum; he says the shipping company apologized and paid soon afterward. He saw social platforms shifting some power toward customers.

Having built on-premises support desks, he began researching online customer complaints and conceived a fresh help desk. He founded the company in 2010; the story is his account of the inspiration, not evidence that every public complaint produces the same outcome.

Before the product was ready, a Hacker News post attracted hundreds of signups. He asked the six-person team to reduce scope and release an early version, then describes a beta and early customer growth: 100 customers in 100 days and 200 in 200 days, according to his recollection.

He initially sent the alpha to small groups because he feared servers would crash. Rather than call the first release embarrassing, he says it did a basic job at a price small customers could afford. The early plan prices he recalls were $9, $19 and $29 per agent per month.

Freshworks first attracted small businesses and institutions with limited budgets. Mathrubootham believes starting low and adding features for larger customers works better than moving down from enterprise; this is his strong generalization from experience, not a proven rule for every software company.

The company deliberately sold globally from the beginning; he recalls seven customers across four continents and a first customer in Australia. He says Indian customers often expected more customized service, while selling standard software internationally offered a larger market. His comparison is a personal business experience, not a description of all customers.

To make low prices workable, the company used search optimization, advertising, transparent pricing and self-service signup rather than expensive sales for every customer. The product was intended to be intuitive enough that a small buyer could try and purchase it without a long implementation or contract negotiation.

He expects search to evolve as users ask generative AI systems for answers, and says Freshworks is researching how its products are represented in those systems. His expectations about referral behavior are forward-looking and partly based on personal observation.

Pricing depends on the customer, problem and market entry, he says. Freshdesk entered a crowded help-desk market with design, usability and a low price, then expanded its offerings. He says some customers now pay over $1 million annually while others begin at much smaller amounts; these are company-reported examples.

Inbound sales can bring an individual team from a large company as easily as a small business. He recalls SolarCity beginning with a 25-seat deal and later having 13 teams, over 1,000 licenses and nearly $1 million in annual payments across separate invoices. This is his company-specific recollection.

He says packaging helps serve both small and larger customers: keep the core experience simple while placing features such as audit logs and sandboxes in enterprise plans. The difficulty is preserving a consumer-like interface without ignoring advanced requirements.

Moving upmarket is hard, he agrees. He reports more than 67,000 Freshworks customers, over 2,000 paying more than $50,000 annually, and roughly 87% of revenue from customers paying over $5,000. These figures are his account at the time, not independently audited in the interview.

Stebbings asks why retain small customers. Mathrubootham says the long tail supplies future growth: some larger accounts began with small payments or adopted several products. The strategy still requires marketing and sales to find customers with suitable economics.

His advice is to develop a second product while the first is working: product leaders should plan revenue several years ahead, because building, launching and achieving momentum take time. This is his operating rule, not a universal schedule.

He clarifies that Freshworks layered a second go-to-market motion onto its inbound business, focusing initially on companies of roughly 500–5,000 employees rather than abandoning small customers. He says managing both motions is difficult but also gives the company multiple product and customer segments.

The trade-offs show up in product and pricing. Enterprise teams may tolerate implementation partners, while self-service users need intuitive workflows; sales teams may prefer negotiated high prices while online buyers need transparent pricing. Freshworks chose to keep prices public, he says.

Hiring leaders who understand both motions is also difficult. Mathrubootham says specialists in one approach can neglect the other, so the task is to assemble complementary leadership rather than assume a single playbook covers both.

His hiring mistakes included skipping reference checks for candidates referred by investors and overvaluing prestigious resumes. He wishes he had spoken to people who reported to candidates to understand their management style and cultural fit.

Although he prefers to give leaders autonomy, he learned to stay close to major early decisions and how new executives treat their teams. He now treats helping a new management hire succeed as one of his own objectives.

He quotes a colleague’s distinction: principles may transfer between jobs, but playbooks do not necessarily transfer unchanged. His own “which cow, which ditch” analogy tells incoming leaders to identify and solve the most urgent existing problems before prescribing a comprehensive new system.

In 2015, he says, Freshworks hired salespeople faster than product developers while customer requests increased and engineering was occupied with an upgrade. He learned to plan headcount across functions against future revenue and product needs, not just accelerate one part of the organization.

Mathrubootham wanted a multi-product company early. He says he started a marketing product before Freshdesk reached $1 million in revenue but stopped it after investors warned a second product could confuse the market and future fundraising.

He later won board support for Freshservice by framing it as a help desk for employees, adjacent to Freshdesk’s customer support. He recalls approximately $1.5 million in first-year revenue and $6.5 million in the second; these are his figures. He also cites later ARR milestones, which are not reconciled with the video description’s company-wide figure.

Freshconnect was a product that did not work as intended. The team saw customers move from support tickets into Slack for help and tried to bring collaboration into the workflow, but took more than two years to launch. By then customers were standardizing on Slack or Teams, he says.

The company used the same code to integrate with those tools instead of competing directly. He says customer adoption gave a relatively quick signal once the product reached the market; the case illustrates his interpretation of timing and distribution.

His leadership philosophy is to hire people with passion and a learning mindset, create an environment where they can perform and then give them room. He says honest private feedback, genuine relationships and acting on poor hires matter more than empty encouragement.

He rejects the idea that a brilliant individual can ignore the team. As the organization grew, particularly during the pandemic, he found it difficult to maintain culture through successive video meetings. That is his experience, not a controlled comparison of remote and office work.

Mathrubootham says money amplifies a person’s existing character and that, beyond meeting needs, he wants to serve society. He describes employee wealth creation, a software academy for students unable to afford college and FC Madras as examples of impact he values.

Asked how young people find purpose, he says it can be reasonable first to focus on financial security and family responsibilities. He recalls doing so himself before thinking more explicitly about wider purpose; he presents this as a personal perspective.

He believes the coming decade could be important for Indian product companies. He cites growth in SaaSBOOMi participation and increased applications to Together Fund as evidence of momentum. These are his estimates and observations, and he has an institutional interest in the ecosystem.

On liquidity, he points to Walmart’s Flipkart acquisition, Freshworks’ US listing and Indian listings as examples of several possible exit paths. He argues that the old perception of no liquidity is changing, without claiming that every company can achieve an exit.

He says a common misunderstanding is that Indian software companies must first win at home before going global. In his experience many start with international customers, and he wants investors to recognize that model rather than assume the same sequence used in other markets.

He says he had made roughly 60–70 mostly small angel investments before co-founding Together Fund. The fund and SaaSBOOMi are part of his aim to support global product companies from India; he believes an operator network can provide practical help alongside capital.

When evaluating founders, he asks what gives them the right to win, whether their work shows world-class craftsmanship, and whether they can recruit a strong team. He prefers deep familiarity with the problem to choosing an idea solely through abstract scoring.

His angel mistake was sometimes investing to help founders despite lacking conviction. He says several companies wound down and he lost money, though he does not regret trying to help. He reports that one investment, Chargebee, returned his entire angel portfolio and that a $25,000 investment became $3.4 million after a sale; these are his self-reported figures.

In quick fire, he says he is learning poker as a strategy game, identifies accountability as a leadership weakness, and would choose Jeff Bezos for a dinner conversation about building multiple products. He warns founders against underestimating the market and fighting with co-founders, then jokes about watching India play in a World Cup.