Nick Mehta: Why Category Creation Is a Last Resort

Category creation sounds like a growth strategy. Nick Mehta ran Gainsight for 13 years, built the customer success category from scratch, and his opening advice to founders who want to do the same thing is: make sure you actually have to. The Gartner magic quadrant he envisioned at Gainsight's founding took ten years to appear. Most founders don't have ten years, and most categories don't need to be invented.

This episode of Recall Sessions, a Village Global Podcast series hosted by Somrat Nigogi, follows Gainsight's earliest years: the meetup above a bar in Mountain View that drew 75 people and eventually became a 6,000-person conference, and the thirteen years Mehta spent doing sales calls alongside everyone else.

Listen to the full episode on Apple Podcasts, Spotify, YouTube, or wherever you listen to podcasts.

For insights from across the Village Global Network straight to your feed, follow us on X, LinkedIn, YouTube, Instagram, and TikTok.

Key Insights

Category creation is a last resort

Mehta's name is so bound up with the customer success category that founders might assume he'd recommend the following his category-creation playbook. He doesn't. His first question to any founder considering category creation: have you exhausted every other option?

The framework he offers has three tiers. Redefine an existing category first. If that's not possible, merge two existing ones. Databricks did this. Palo Alto Networks did this. Category creation is what Mehta calls "in case of emergency, break glass." The costs are real: years of market education, slow sales cycles, and a Gartner magic quadrant that might not exist for a decade.

He uses Snowflake as the corrective. An investor described it to him as "data warehousing, next generation," and Mehta thought it sounded boring. It was a $100B company. "Turns out that's a pretty good category." The more specific the existing frame you can attach to, the faster the market understands what you're selling. Boring categories with clear buyers close faster than exciting ones that require explanation.

A $2 million TAM is not a death sentence if you're building the category

When Gainsight launched in 2013, roughly 1,000 customer success managers existed worldwide. At a few thousand dollars per seat, the math produced a TAM that would end most investor conversations before they started: $2 million. Mehta knew it. "He went in anyway. The TAM measured a market that didn't exist yet at scale.

The premise was structural. SaaS's subscription model created a problem nobody had formally named: customers who signed contracts still needed to stay, expand, and renew. Someone had to own that relationship, and nobody did yet. Whoever built the professional community around this emerging role would define the software category that served it. Mehta bet on the role growing. Ten years later, 300,000 CSMs were working in the field.

The lesson Mehta draws is about what a TAM calculation actually measures. A market analysis in 2013 could only count the CSMs who existed in 2013. It had no mechanism for projecting a role that SaaS's growth dynamics would force into existence. The TAM was right about the present. It was structurally blind to the future Gainsight was trying to build.

Humans buy software for human reasons

Gainsight's most commercially successful salesperson, Adam Wicks, closed the company's largest land deal: $6 million per year at SAP. He beat quota every year Mehta ran the company. What separated Wicks from everyone else had nothing to do with product knowledge or process mastery. He was genuinely curious about what individual people at large companies were afraid of: getting promoted, not getting fired, managing teams they'd just inherited.

"Humans buy software for their human needs and then they justify it to their business," Mehta says. The ROI case is real, but it comes second. First comes understanding what a specific VP is worried about this quarter. The business case is the rationalization the buyer writes after the emotional decision is already made.

Wicks opened conversations with what he'd seen other people in that role struggling with: a shared frustration, a peer connection he could make, a perspective on something the buyer was already dealing with. He asked for nothing. He offered something concrete. The product entered the conversation only after the buyer had decided Wicks already understood their world. Mehta frames the principle simply: understand what a specific person cares about as a human before you explain what your software does.

Build on a platform you don't own to earn trust you can't buy

Gainsight originally built on force.com, Salesforce's application development platform. The technical objections were obvious: platform dependency, royalty payments, migration risk if the relationship changes. Mehta's counterargument was concrete. Workday was among Gainsight's first handful of enterprise customers. "There's no way we get Workday without force.com. They've told us: the only reason we got it is because we're on force."

Large enterprises run procurement processes that take months and involve security reviews, legal sign-off, and IT approval. A startup selling a net-new product has to clear all of those gates from scratch. A plugin to a platform an enterprise has already approved inherits that trust. Gainsight didn't have to earn Workday's trust as a vendor; it arrived pre-authenticated as a Salesforce extension.

Platform risk is real and Mehta doesn't dismiss it. Four or five years in, Gainsight built its own native platform and migrated every customer off force.com. Someone told him it couldn't be done. They treated it as a challenge and did it. But not every company can execute a migration of that complexity, and the window to attempt it has a lifespan. The framework Mehta offers: if you believe you can eventually escape the platform dependency, build on it to get started. If you're genuinely uncertain whether you can escape, think harder before committing. The platform accelerates trust. It doesn't free you from needing a plan for what comes after.

Check the org chart for threats, ignore the marketing

Around 2017, Salesforce announced at Dreamforce that they were "the customer success platform." It was on billboards. It was on the website. Gainsight's phone lit up with nervous customers wondering if they'd just watched their vendor get killed by a competitor with unlimited resources.

Mehta's diagnostic for assessing the actual threat: ignore the announcement entirely. Look at the internal org. "Is there a GM or senior person in the platform company who would wake up and think this is really important for them to solve? If there is, you've got a problem." An announcement without someone whose career depends on executing it is marketing. An announcement with a dedicated senior owner is a threat.

At Salesforce, Gainsight sat in the seam between Sales Cloud and Service Cloud. Neither team owned it. Nobody's promotion was tied to winning the customer success market. The competitive threat was real enough to create short-term sales drag. Some customers waited eighteen months to see what Salesforce would actually ship, but Salesforce moved to its next message two years later. Mehta also had a more vivid education in how Salesforce developed their competitive feature set. He demoed the full Gainsight product to someone he understood to be a Salesforce partner at Dreamforce. The next year, that person appeared on a Dreamforce stage presenting a Salesforce-built replica.

The diagnostic applies today to any founder watching foundation model companies expand into adjacent markets. Find the org chart. Find the person whose career the expansion is riding on. If the ownership is diffuse, spread across multiple teams, folded into everyone's job a little and no one's job entirely, the threat is mostly noise.

Thirteen years of founder-led sales wasn't a failure to delegate

The standard arc of founder-led sales has a familiar shape: do it yourself until you understand the pattern, write the playbook, hire the team, hand it off. Mehta ran Gainsight for 13 years. He was still doing sales calls on his last day.

He did hire salespeople early. Most of them struggled to replicate what he was doing, and the reason was structural rather than personal: the category was too undefined, the buyer too uncertain about what they were purchasing, and the sales conversation too dependent on a founder-level conviction about why customer success as a discipline mattered. The standard salespeople could sell software. They could not sell a belief system. Mehta could.

The conventional frame treats sustained founder involvement in sales as a handoff problem, as evidence that the founder didn't build a scalable process. Mehta's 13-year run suggests a different reading. A founder's depth of conviction about why a category exists is a sales asset with a long lifespan. At Gainsight, it didn't become obsolete as the company grew. The category was still being explained and justified at scale, and the person who believed in it first was still the most persuasive person to explain it.

About the Guest

Nick Mehta was CEO of Gainsight from 2013 to 2025, leading the company from pre-revenue to a $1.1 billion acquisition by Vista Equity Partners and building customer success into a recognized enterprise software category. Before Gainsight, he grew LiveOffice to $25 million in ARR and sold it to Symantec. He has co-authored two books on customer success, was named EY Entrepreneur of the Year for Northern California, and serves on the boards of F5 and PubMatic.

About the Host

Somrat Niyogi is the founder and GP of Recall Capital and a Village Global Network Investor, writing first-checks at the pre-seed and seed stage into B2 SaaS companies. He previously served as General Manager and Head of Business Development at Gusto, with earlier operator roles at Clari, Miso, Stitch, and Salesforce. Together, Village Global and Somrat back early-stage founders across AI, fintech, and B2B SaaS.