11 min left 0%

plg vs sales-led: choosing your b2b growth motion

There are companies and products which are business driven — sales decides what to be built, operations decide what to build. And then there are companies like BrowserStack or Postman or CleverTap — they are product driven businesses. The products exist. And that is driving the business.
Talvinder Singh, from a product talk at IIM Trichy

Every B2B startup in India eventually faces a version of this meeting: the CEO opens with “we need to grow faster,” and two camps form immediately. One camp says “let the product sell itself — remove friction, improve onboarding, let users upgrade on their own.” The other says “hire ten more AEs, build an outbound machine, and close enterprise deals.” Both camps are wrong in the way they frame the argument, because they treat PLG and sales-led as philosophies instead of what they actually are: engineering decisions about how money and people flow through your company.

Product-led growth and sales-led growth are not mindsets. They are GTM architectures. They have different cost structures, different team shapes, different failure timelines, and different metrics. Picking the wrong one does not mean you grow slowly. It means you burn cash building an engine that does not match your product, your buyer, or your market.

The architecture choice you cannot defer

Most B2B companies in India defer this decision. They start with founder-led sales, sign a few design partners, and then grow by adding more salespeople as revenue comes in. That works until it does not. Around Series A or B, someone asks: why does it cost us 40% of the contract value to acquire each customer?

That is the moment the growth motion question becomes urgent. And by then, the company has already built its org chart, its incentive structure, its pricing, and its onboarding flow around whichever motion it fell into accidentally.

Here is what actually differs:

DimensionProduct-Led GrowthSales-Led Growth
How users find youSelf-serve signup, freemium, word of mouthOutbound sales, events, partnerships
Who decides to buyThe end user adopts first, then pulls in the buyerThe buyer is sold first, then pushes it to users
Cost structureHigh upfront product investment, low marginal cost per userLow upfront product investment, high marginal cost per deal
Team shapeGrowth engineers, product designers, data analystsAEs, SDRs, solution engineers, customer success
Time to first revenueSlow (months of free usage before conversion)Fast (deals close in weeks to months)
Key metricFree-to-paid conversion rate, PQL rate, time-to-valuePipeline value, win rate, average deal size, CAC payback
Failure modeMillions of free users, nobody convertsHigh CAC, high churn, salespeople selling what the product cannot deliver
Where it breaksACV too low to justify enterprise expectationsProduct too complex for self-serve, too much hand-holding needed

The failure modes matter more than the success stories. PLG fails silently — you accumulate users who love the free tier and never convert, while your cloud costs climb. Sales-led fails loudly — you burn through AEs who cannot hit quota because the product does not match what they are promising.

Product-led growth in India: what actually works

PLG has become a central focus for Indian B2B startups. This is not an afterthought. Founders are realising it. VCs are realising it. And they are looking for PMs who can execute PLG — not just talk about it.

But PLG in India looks different from PLG in San Francisco, and the differences matter.

Postman is the clearest Indian PLG success. Abhinav Asthana built something developers wanted to use individually. No sales team called CTOs to pitch API testing tools. Developers downloaded Postman because it solved a daily annoyance, told other developers about it, and over time entire engineering teams were using it. By the time Postman’s sales team showed up at an enterprise, 200 developers inside that company were already on the free plan. That is textbook PLG: individual adoption creates organisational demand.

Freshworks started sales-led and layered PLG on top. Freshdesk’s free tier brought in small businesses who could not afford Zendesk. As those businesses grew, they upgraded. Freshworks did not choose PLG as a philosophy. They chose it as a cost-efficient acquisition channel for the SME segment, while keeping a sales team for mid-market and enterprise. Two motions, two segments, deliberately separated.

Razorpay is an interesting case. Payments is inherently PLG for developers — sign up, get API keys, integrate, start processing payments. But enterprise deals (large merchants, banks, financial institutions) required a sales team to handle compliance, custom pricing, and integration support. Razorpay did not try to make one motion work for both. They let self-serve handle the long tail and built a dedicated enterprise team for high-ACV clients.

The pattern across all three: PLG works in India when the end user can experience value alone, without needing a manager’s approval or a procurement process. The moment you need someone with a budget to say yes before the product can be used, you are in sales-led territory regardless of what your pitch deck says.

// scene:

Series B board meeting at a B2B SaaS startup in Bangalore. The CEO is presenting the growth plan.

CEO: “We have 40,000 free users and 400 paying customers. Our PLG motion is working. We want to double down — hire a growth team, improve onboarding, and increase free-to-paid conversion from 1% to 3%.”

Board Member: “What is the average contract value of those 400 paying customers?”

CEO: “About 2 lakh per year.”

Board Member: “So your entire paying base generates 8 crore ARR. To hit 50 crore, you need either 2,500 customers at 2 lakh or 100 customers at 50 lakh. Which path are you choosing?”

VP Product: “The 2,500 path is PLG. The 100 path is enterprise sales. We cannot do both with this team.”

Board Member: “You can do both. But not at the same time, and not with the same product experience. Pick which one funds the next 18 months.”

The startup chose the enterprise path. Their PLG motion became a lead generation channel for the sales team — not the primary revenue driver. This is not a failure of PLG. It is a recognition that the math demanded a different motion at that scale.

// tension:

PLG and sales-led both work. The question is which one matches your revenue math right now.

Sales-led is not dead: when it is the right call

The PLG hype cycle has convinced a generation of PMs that sales-led is an inferior model. It is not. For many Indian B2B companies, sales-led is not just the right call — it is the only viable path.

Darwinbox sells HR software to large Indian enterprises. An HRMS touches payroll, compliance, attendance, performance reviews — functions where a wrong configuration has legal consequences. No CHRO at a 10,000-person company is going to let an HR manager self-serve their way into a new HRMS. The buying process involves security reviews, compliance checks, data migration planning, and executive sign-off. This is a sales-led product by nature, not by choice.

Zoho runs a dual model but its enterprise motion is heavily sales-led. When Zoho sells to a mid-size manufacturing company in Coimbatore, that company does not have a “growth team” evaluating SaaS tools. The owner wants someone to visit, demonstrate the product, understand their specific workflow, and promise support in their language. Zoho’s sales-assisted approach — regional offices, local language support, on-site implementation — is a competitive moat that a pure PLG company cannot replicate in India’s SME market.

Vyapar targets India’s small business and retail segment for accounting. The users are shopkeepers, small manufacturers, traders. Many of them are adopting software for the first time. Vyapar’s growth comes from a mix of self-serve (app store downloads) and a large on-ground sales and support team that onboards users who have never used accounting software before. Calling this “PLG” would be misleading. The product is simple enough for self-serve, but the market requires assisted adoption.

Sales-led is the right choice when:

  • The buyer and the user are different people with different incentive structures
  • Implementation requires configuration, data migration, or integration work
  • The ACV justifies the cost of a human sales process (generally above 5-10 lakh annually in India)
  • The market does not self-educate about your product category
  • Compliance or security requirements mandate a formal evaluation process

If three or more of these are true for your product, build a sales-led motion and do not apologise for it.

The hybrid trap: why most companies botch the transition

Here is where companies actually die. Not by choosing PLG or sales-led, but by trying to bolt one onto the other without changing anything else.

The most common version: a PLG company hits a revenue ceiling and decides to add enterprise sales. The board loves this. “We have 50,000 free users — just hire salespeople to convert the big accounts.” It sounds logical. It is a trap.

The PLG product was designed for individual users. The onboarding assumes one person. The pricing is per-seat. The product has no admin console, no SSO, no role-based permissions, no audit logs. The enterprise buyer needs all of these before signing a contract, and building them takes 6-12 months.

Meanwhile, the salespeople you hired are sitting idle. They cannot sell what does not exist yet. They start selling what they wish the product could do. Prospects get demos of “upcoming features.” Three months later, the sales team is frustrated, the product team is underwater on enterprise feature requests, and the free users — who were generating all the word-of-mouth growth — are seeing slower feature development for the product they actually use.

The reverse trap is less common but equally destructive. A sales-led company decides to add a self-serve tier. They strip features from the enterprise product, slap a free plan on the website, and wait for signups. The free product is confusing because it was designed for guided implementation. The onboarding assumes a solution engineer is walking you through setup. Self-serve users churn within a week. The company concludes “PLG does not work for our market” when the real problem is they shipped a lobotomised version of an enterprise product and called it a free tier.

The companies that successfully run hybrid motions — Freshworks, Razorpay, Atlassian globally — treat them as two distinct product experiences with shared infrastructure underneath. The self-serve product and the enterprise product might share 80% of the codebase, but the remaining 20% — onboarding, pricing, permissions, support — is purpose-built for each motion.

// thread: #product-growth — Three months into adding enterprise sales to a PLG company
Ravi (PM, Growth) Our free-to-paid conversion dropped from 2.1% to 1.4% this quarter. We shipped zero growth experiments because the entire team was building SSO and audit logs for the enterprise pipeline. 😬 4
Priya (PM, Enterprise) Those SSO and audit log features unlocked 3 enterprise deals worth 1.2 crore combined. That is more revenue than the growth team generates in two quarters.
Ravi Sure, but the 40,000 free users who generate the enterprise pipeline in the first place are getting a worse experience. If they stop coming, your pipeline dries up in 6 months.
Neha (VP Product) This is the core tension. We need to staff and fund these as separate tracks. Same codebase, different teams, different metrics, different roadmaps. Ravi owns free-to-paid conversion. Priya owns enterprise pipeline. Both report to me. Neither team borrows engineers from the other without my sign-off.
Ravi Can we get that in writing before next quarter's planning? 🙏 6

How to diagnose your growth motion

The growth motion is not a strategy slide. It is observable in how the company actually works. You can diagnose it by asking five questions:

Who touches the customer first? If the first interaction is with the product (signup, free trial, sandbox), you are PLG. If the first interaction is with a human (sales call, demo, partnership), you are sales-led.

What triggers a purchase decision? In PLG, the user hits a usage limit or needs a team feature and upgrades on their own. In sales-led, a salesperson identifies an opportunity and initiates the commercial conversation.

Where does product feedback come from? In PLG, feedback comes from usage data, support tickets, and community forums. In sales-led, feedback comes from sales calls, RFPs, and customer success reviews.

What happens when a deal is lost? In PLG, you lose a deal when a user finds an alternative and switches — often silently. In sales-led, you lose a deal when a competitor wins the evaluation, the budget gets cut, or the champion leaves the company.

How does the company talk about success? PLG companies celebrate signups, activation rates, and viral coefficients. Sales-led companies celebrate deal sizes, win rates, and pipeline coverage ratios.

If your answers are split — some PLG, some sales-led — you are running a hybrid motion. That is fine, as long as it is intentional. If it is accidental, you are in the trap described above.

// exercise: · 15 min
Diagnose your company's growth motion

Run this diagnostic on your own company or a company you are interviewing at:

  1. Draw the first-touch map. How does a typical customer first interact with your product? Trace the path from “never heard of us” to “signed contract.” Count the human touchpoints vs self-serve touchpoints.

  2. Calculate the ratio. What percentage of revenue comes from self-serve upgrades vs sales-assisted deals? If it is >70% self-serve, you are PLG. If it is >70% sales-assisted, you are sales-led. If it is 40-60%, you are hybrid.

  3. Identify the constraint. Is your growth bottleneck a conversion problem (lots of users, few buyers) or a pipeline problem (few users, but they buy when they find you)? Conversion problems point to PLG optimisation. Pipeline problems point to sales investment.

  4. Check for the hybrid trap. If you are running both motions: do they have separate teams, separate metrics, and separate roadmaps? If the same PM owns both free-to-paid conversion and enterprise pipeline, the motions will cannibalise each other.

  5. State your motion in one sentence. Example: “We are PLG for SMEs with self-serve pricing, and sales-led for enterprises with custom contracts. The PLG funnel feeds the enterprise pipeline.” If you cannot state it this clearly, the company has not decided yet.

// interactive:
Adding Enterprise Sales to Your PLG Motion

You are the PM at a Series B developer tools company in Hyderabad. You have 60,000 free users, 800 paying teams at an average ACV of 1.5 lakh, and 12 crore ARR. The board wants you to reach 50 crore in 18 months. Your VP of Sales (hired two months ago) proposes adding an enterprise tier at 25 lakh ACV and hiring 8 AEs. Your growth team says this will kill the PLG flywheel. The CEO asks you for a recommendation.

You have one week to present a plan. The board meets next Friday. What is your first move?

// learn the judgment

You are PM at a Series B developer tools startup in Bengaluru — think a Postman-like API testing tool. You have 55,000 free users and your PLG flywheel is genuinely working: free-to-paid conversion is at 2.3%, word-of-mouth is strong, and GitHub communities are recommending you organically. Now three enterprise deals have emerged simultaneously — Infosys (1,200 seats), Wipro (800 seats), and HDFC Tech (500 seats). Each deal is worth ₹40-60 lakh annually. To close them, you need SSO, role-based access, and audit logging — none of which exist in the product. Your VP of Sales wants to split the team: two engineers to build enterprise features, leaving four on PLG. Your growth PM says diverting two engineers will kill the PLG experiment momentum just as it's hitting scale.

The call: Do you split the team and pursue both motions in parallel, or do you stay fully PLG and decline the enterprise opportunities for now?

// practice for score

You are PM at a Series B developer tools startup in Bengaluru — think a Postman-like API testing tool. You have 55,000 free users and your PLG flywheel is genuinely working: free-to-paid conversion is at 2.3%, word-of-mouth is strong, and GitHub communities are recommending you organically. Now three enterprise deals have emerged simultaneously — Infosys (1,200 seats), Wipro (800 seats), and HDFC Tech (500 seats). Each deal is worth ₹40-60 lakh annually. To close them, you need SSO, role-based access, and audit logging — none of which exist in the product. Your VP of Sales wants to split the team: two engineers to build enterprise features, leaving four on PLG. Your growth PM says diverting two engineers will kill the PLG experiment momentum just as it's hitting scale.

The call: Do you split the team and pursue both motions in parallel, or do you stay fully PLG and decline the enterprise opportunities for now?

0 chars (min 80)

Career-stage considerations

0-2 years: PLG companies are better for building product intuition because you see the full user journey without a sales team mediating the signal. If you can join a company running a PLG motion early in your career, you will develop a sharper sense of how users adopt and convert than most PMs get in five years at a sales-led org.

3-5 years: Understanding both motions makes you rare. Most PMs know one side deeply and treat the other as a mystery. If you have spent three years in PLG, take a role that exposes you to enterprise sales cycles — or vice versa. The PM who can speak both languages is the one who gets the hybrid-motion design briefs.

5+ years: You will be asked to design the motion, not just operate in it. At this level, the question is not “how do I optimise our PLG funnel” but “should this company be PLG, sales-led, or hybrid — and what organisational changes does that require?” This is a strategic architecture decision, and the people who make it well become VPs and CPOs.

Where to go next

  • Understand pricing mechanics for each motion: Pricing Strategy covers freemium design, willingness-to-pay research, and the India pricing context
  • Build the go-to-market plan: Go-to-Market Strategy covers launch sequencing and channel selection
  • Go back to B2B fundamentals: B2B Product Management covers multi-persona products, enterprise sales alignment, and India B2B dynamics
  • Understand growth PM as a discipline: Growth Product Management covers activation, retention, and experimentation
  • Get the foundation right first: Product-Market Fit covers how to know you have something before you scale it
plg vs sales-led: choosing your b2b growth motion 0%
11 min left