Mehul Fanawala Interview
“The moment a founder stops trying to close and starts trying to solve, the customer starts selling themselves on the solution.”
Q1. Your work spans sales, marketing, and customer success. How did your career evolve into revenue operations?
I didn’t set out to build a career in revenue operations—it’s something I grew into over time.
My background has always been rooted in sales and customer success. I’ve been directly involved in closing deals, onboarding customers, managing renewals, and stepping in when expectations weren’t met. Over time, I realised that most revenue-related challenges weren’t due to a single team failing, but rather a lack of alignment between teams.
This became even clearer when I started working closely with my co-founder, Manasi, who comes from a strong marketing background. Marketing, sales, and customer success were all doing their jobs, but they weren’t speaking the same language.
Revenue operations became the bridge. It allowed us to view the entire customer journey as one unified system rather than three disconnected functions. That shift—from thinking in terms of “my team” to “the revenue system”—ultimately shaped my work and led me into RevOps.
Q2. You often say founders should stop selling and start solving. What does that look like in a real sales call?
When founders focus on selling, conversations tend to revolve around pitching features and proving how impressive the product or service is. But when they focus on solving, the entire dynamic of the call changes.
In practice, it means talking less and listening more. Founders start asking questions like, “What breaks if this doesn’t get fixed?” or “What have you already tried that didn’t work?” Instead of jumping straight into a demo, they aim to understand the true cost and depth of the problem.
I’ve seen deals move faster when founders are transparent enough to say, “This might not be our problem to solve,” or “You may not need us yet.” That kind of honesty builds trust instantly.
The moment founders shift from trying to close a deal to genuinely trying to solve a problem, customers begin to convince themselves of the solution.
Q3. After auditing many SaaS teams, what is the most common revenue leak founders ignore?
The most common—and often overlooked—revenue leak is the gap between what gets sold and what actually gets delivered.
Sales teams often close deals based on excitement, urgency, or pressure to hit targets. Meanwhile, onboarding and customer success inherit customers with very different expectations. This misalignment isn’t intentional, but it significantly impacts retention, expansion, and referrals.
Founders tend to track leads, conversions, and revenue closely. However, they often overlook expectation alignment. When that breaks, churn appears months later and feels sudden—even though the warning signs were present from day one.
This gap between promise and reality is one of the most expensive leaks I see, and it’s almost always preventable.
Q4. Many startups chase growth quickly. Where do you see speed hurting revenue more than helping it?
Speed becomes harmful when it’s applied to acquisition without strengthening the foundation first.
Many startups rush to scale marketing and sales before they’ve fully figured out onboarding, activation, and value delivery. On the surface, growth looks impressive—but underneath, churn quietly accelerates.
I’ve seen teams celebrate rapid pipeline growth while customer success teams are firefighting and product teams are overwhelmed. In such cases, revenue doesn’t compound—it leaks.
The right approach is to earn the right to grow. When retention, handoffs, and customer outcomes are stable, speed becomes an advantage. Before that, it only masks underlying issues.
Q5. If a SaaS team’s pipeline looks healthy but revenue is stagnant, where should they investigate first?
The first place to investigate is the gap between pipeline and closed revenue.
A healthy-looking pipeline can often mask deeper issues—such as poor qualification, deals stagnating in specific stages, or prospects entering the funnel without a genuine buying intent. On paper, the pipeline looks strong, but in reality, it’s fragile.
I’d also closely examine what happens after the demo stage, as that’s often where momentum is lost. If follow-ups slow down, decision-makers disengage, or next steps aren’t clearly defined, revenue stalls despite a strong influx of leads.
When revenue is stuck, it’s rarely a pipeline volume issue—it’s almost always a problem of conversion and execution within the pipeline.
Q6. What advice do you strongly disagree with in today’s SaaS or startup culture?
I strongly disagree with the idea that founders should “always be selling.”
Founders should absolutely stay close to their customers—but constant selling often leads to short-term wins at the cost of long-term clarity. I’ve seen founders close deals that later result in churn, increased support burden, and team burnout.
The most effective founders step in not just to close deals, but to understand patterns. They pay attention to recurring objections, confusion points, and friction across the funnel—and then work to fix the system so the team can perform better independently.
Selling may sustain revenue today, but solving ensures it continues to grow in the future.
Q7. Fun one: If you had to ban one SaaS metric from founder dashboards, which one would it be and why?
I’d ban total pipeline value.
It often creates a false sense of progress. A large pipeline may feel reassuring, but it doesn’t indicate how much of it is genuinely qualified or likely to convert. I’ve seen teams become complacent because their pipeline appears “healthy,” even as revenue remains stagnant.
If founders focused more on metrics like stage-to-stage conversion rates, time to close, and how many deals reach activation, decision-making would become far more precise.
Pipeline is a hope metric. Revenue quality is a reality metric.
Bio:
Mehul Fanawala is a revenue operations specialist with a strong foundation in sales and customer success. With hands-on experience across the entire customer lifecycle—from closing deals to onboarding and retention—he focuses on aligning marketing, sales, and customer success into a unified revenue system. As a co-founder, Mehul works closely at the intersection of strategy and execution, helping SaaS teams identify revenue leaks, improve conversion, and build sustainable growth systems.
Interviewed by: Abhishek Rath
Edited by: Shantanu Singh
0 Comments