GTM Fundamentals · intermediate · node 6.3
Expansion: PLG at scale
Prerequisites
Product-led growth is the most elegant motion available: no sales team, no CAC, no long cycles. Prospects discover your product, experience value immediately, and pay. It scales from zero to a very precise ceiling, and then it stops. Founders who do not know this ceiling waste months (and millions) trying to force PLG past the point where it works. The result is a motion that no longer moves and a product positioned for individuals in a market that requires committee selling.
Understanding where your product hits the ACV ceiling, building a transitional motion that borrows the best of PLG while introducing sales early enough, and designing the operational handoff is the difference between scaling indefinitely and plateauing.
The ACV ceiling exists because of the buyer committee
PLG works because it removes friction. The buyer signs up, tries the product, experiences value, and buys. There is no salesperson, no demo, no committee. The product is the motion.
This works when the buyer is an individual or a team. But as ACV rises, a critical change happens: the buying committee appears. The buyer is no longer a software engineer deciding on a personal tool. The buyer is now a VP of Engineering deciding on a tool for the entire department. And a VP does not make a decision alone. The CFO cares about cost. The CTO cares about integration. The security officer cares about data governance. Legal cares about the vendor agreement. Compliance cares about audit trails.
The trial is no longer sufficient evidence for this committee. A free trial might convince the engineer that the tool is useful. But it does not convince the CFO that the cost is justified. It does not show the CTO that integration is feasible. It does not prove to the security officer that the tool meets the company’s standards. The trial solves for one person; the committee needs proof on five dimensions.
This is the ACV ceiling. It is not a soft constraint; it is a structural break in how markets work.
Diagnostic: ACV ceiling by product type
The ceiling varies by product complexity and the nature of the buying committee. Certain products can push past $2k ACV on PLG alone. Others hit the ceiling at $500 ACV.
Low-friction B2B consumer tools (Figma, Notion, Slack): $2–3k ACV before ceiling.
These products are individually valuable enough that a single user will advocate for adoption without committee approval. Figma is so obviously useful that the designer pushes procurement to buy. Slack accelerates communication so visibly that the team manager asks to expand. The product sells itself at the team level.
Even here, the ceiling exists. Once you hit $3k ACV, you are selling to multiple departments or larger teams. Now the centralized procurement team gets involved. “Why do we need this if we already have Microsoft Teams?” “Who approved this purchase?” “What is our data residency?” The trial does not answer these questions. The motion stalls.
Mid-market infrastructure and complex B2B ($500–1.5k ACV):
Products like CI/CD tools, security scanners, observability platforms, and data platforms are individually valuable but require integration planning and security review. A developer can start using the tool and finding value. But for the company to commit to it, the security team needs to review it, the infrastructure team needs to integrate it, and the finance team needs to approve the budget.
The free trial might get 50 developers to sign up. It might prove that the tool is useful. But it does not show the infrastructure team that the product integrates with their existing stack. It does not prove to the security team that it meets compliance requirements. The ceiling hits around $1k ACV because the friction above that point is structural, not product-solvable.
High-complexity enterprise tools (enterprise software, security, compliance): $200–500k ACV floor, no PLG.
Some products cannot be self-serve from the start because the complexity is intrinsic. Enterprise security tools, compliance platforms, large-scale data infrastructure, and mission-critical middleware cannot be understood in a free trial. The buyer committee is large, the integration is complex, and the risk is high. These products have no PLG ceiling; they have no PLG at all. They are sales-led from the start.
The rule: The ceiling rises with product simplicity and the magnitude of individual value. The more obvious the value to a single user, the higher the ceiling. The more integration is required, the lower the ceiling.
Founder mistake 1: Forcing PLG past the ceiling
The first mistake is assuming that if PLG is working now, it will keep working at higher ACV. The assumption is usually: “Our PLG motion is moving well. If we optimize it—faster onboarding, more features in the free tier, a more aggressive expansion motion—we can push it higher.”
This is backward. The ceiling is not a result of poor PLG execution. The ceiling is structural. It is where the buying process changes from individual to committee. No amount of optimization on the product side will overcome a structural change in how the market buys.
What happens when you force PLG past the ceiling:
You see a dramatic conversion cliff. Your free-to-paid conversion is 5% at $500 ACV. You optimize, and it rises to 8%. You push harder, and it rises to 9%. But at $1k ACV, it drops to 2%. At $2k ACV, it approaches zero. This is not a tactic problem; it is a market problem. You are selling to committees now, and committees do not sign up for free trials.
Your CAC explodes. To hit the same revenue at a higher ACV with a lower conversion rate, you need to increase your free-tier spending. You spend more on ads, more on content, more on developer relations—anything to drive volume to the free tier. But the conversion rate keeps falling because the barrier is not awareness or product experience; it is structural. You end up with a CAC that exceeds your LTV, and the motion becomes unprofitable.
Your product gets bloated. In an attempt to convert at a higher price point, you add more features to the free tier. You think: “If the customer can see more value upfront, they will buy higher tiers.” But the real problem is not feature coverage; it is committee approval. You end up with a product that is complex for individuals (the original buyer), trying to do too much (solving for the CFO, the CTO, the security officer), and good at nothing (the generalist approach satisfies no one). Your individual users are frustrated because the product is no longer optimized for them. Your committees are unsatisfied because the product does not solve their specific needs.
Your expansion motion stalls. PLG expansion (seat expansion, team expansion, use-case expansion) works when the first buyer advocates internally. But if the first buyer is an engineer and the expansion buyer is a VP, the expansion requires sales navigation. The engineer cannot convince the VP. You need a salesperson. But you have not built sales capability because you assumed PLG would carry you.
The cost of forcing PLG past the ceiling is high: wasted CAC spend, product bloat, and—most critically—a delayed transition to the sales-led motion you actually need.
Founder mistake 2: Not recognizing the ceiling until too late
The second mistake is not seeing the ceiling until you are stuck.
You are growing, your PLG motion is working, revenue is increasing. You reach $2M ARR, and growth starts to slow. You assume it is a tactic problem: “Our onboarding needs work. Our messaging is not clear. We need better marketing.” You spend six months optimizing. Growth improves marginally and then plateaus again. You reach $3M ARR, and you are stuck.
At this point, you realize: the ceiling is structural. You need to transition to sales. But now your product is optimized for individuals, your pricing is designed for self-service, and you have no sales team. Building a sales motion now is a redesign.
Worse, your window to build a sales motion may have closed. Your competitive moat was the speed and elegance of your PLG. But if you are stuck at $3M ARR and a competitor launches with a sales-led motion designed for committees from the start, the competitor will win all the deals above the ceiling. You will own the $500k to $3M segment. The competitor will own the $3M to $50M segment. You will eventually get acquired by the competitor because you did not build the motion to reach higher ACV.
The cost of not recognizing the ceiling is higher than the cost of forcing PLG past it: you build a business that is fundamentally capped at a certain size, and you lose the opportunity to build a sales organization while your product still has momentum.
The diagnostic: Finding your ACV ceiling
To find your actual ACV ceiling (not your theoretical one), use cohort analysis on your conversion and retention metrics.
Step 1: Cohort your customers by initial ARR.
Split your customer base into cohorts: $100–500 ARR, $500–1k ARR, $1k–5k ARR, $5k–10k ARR, $10k+ ARR. For each cohort, measure:
- Free-to-paid conversion rate. What percentage of free users convert to paying customers?
- Time to first purchase. How long from signup to paid?
- Net dollar retention. In year two, how much revenue does this cohort generate per dollar acquired?
Step 2: Look for the conversion cliff.
Your conversion rate will be high in the low-ACV cohorts and drop sharply in the high-ACV cohorts. That cliff is your ceiling. If conversion is 10% at $500 ACV and 2% at $2k ACV, your ceiling is somewhere between $1k and $1.5k.
Step 3: Check unit economics at the ceiling.
At the ceiling, your CAC often exceeds your LTV. If you are spending $5k to acquire a customer with a $5k annual contract value and a 2-year lifetime, your LTV is $10k, and the unit economics are marginally okay. But at $10k ACV with 2% conversion, your CAC might jump to $50k. Now your LTV is $20k, and the economics collapse.
Step 4: Test the sales-led motion below the ceiling.
Before you redesign your motion, test whether a sales motion works at the ceiling. Pick a cohort of inbound leads with $5k+ ACV and manually send them to a salesperson. Measure whether the salesperson can close deals. If the salesperson can, your ceiling is real, and a sales motion will work above it. If the salesperson cannot close either, the problem is not the motion; it is something else (product does not solve the problem, market timing, wrong ICP).
Designing the transitional motion: PLG + Sales hybrid
The transition from PLG to sales does not have to be a hard switch. The best companies build a transitional motion that borrows the best of PLG (frictionless onboarding, product-first proof) while introducing sales exactly where it is needed.
Principle 1: Separate the land from the expand.
In PLG, the land and expand are the same motion: an individual signs up, uses the product, loves it, and buys. In a transitional motion, the land is still individual-driven. A developer signs up, uses the product, finds value. But the expand is committee-driven. The department head needs to evaluate the tool for broader adoption.
Design your product so that individual value is obvious within hours. Then design your sales handoff for when the customer is ready to expand (team seats, custom integrations, enterprise features).
Principle 2: Let the product prove fit; let sales prove feasibility.
The product-led trial proves that the tool is useful for an individual. But it does not prove feasibility for the organization. Sales’ job in the transitional motion is not to convince. The product already did that. Sales’ job is to answer the questions the product trial did not: “How does this integrate with our infrastructure? What is the implementation timeline? What are the security requirements? What is the pricing for 100 seats?”
This is fundamentally different from traditional sales-led. The salesperson is not overcoming objections about whether the product is good (the free trial did that). The salesperson is navigating organizational fit.
Principle 3: Price to signal expansion.
Your free tier is optimized for individual value. Your paid tier should signal expansion. Use tiered pricing that reflects organizational growth: individual plan (1 user, $50/month), team plan (unlimited users, $500/month), enterprise plan (custom).
The price jump between individual and team is critical. It should be steep enough that a department head needs to justify it to their finance partner. That friction is not bad; it is the mechanism that brings sales into the conversation at exactly the right point.
Principle 4: Build a clear hand-off point.
Your product should have a moment where it becomes clear to the user that they need to upgrade from individual to organizational use. This might be when they try to add a second user, when they try to integrate with a enterprise system, or when they exceed a usage limit.
At that moment, instead of forcing them through automated upsell flows, offer a sales conversation. “It looks like your team is ready to grow. Let’s talk about how to scale this securely.” That conversation is when sales takes over.
Real examples: How fast-scaling companies handled the transition
Slack: PLG to sales-led at $1.5k ACV.
Slack’s free tier was generous: unlimited message history (unusual for SaaS), unlimited team members, all integrations available. This meant that a team could get tremendous value without paying. But at some point, the team outgrew the free tier (message history limits), and the team lead needed to justify cost to finance. At that point, Slack introduced a salesperson.
Slack did not force the transition. They did not add artificial limitations to the free tier to drive conversions. They let the product prove value, then introduced sales when the committee appeared. The result: Slack scaled from thousands of free teams to billions in revenue because the sales motion felt like a natural evolution, not a hard sell.
Figma: PLG to sales-led at $2k ACV.
Figma’s free tier lets a team of up to two work on unlimited files. It is genuinely useful. But at some point, the team needs to expand beyond two people. At $2k ACV, Figma introduces an enterprise sales motion: custom pricing, SSO, admin controls, implementation support.
Figma did not assume PLG would scale infinitely. They designed the product and pricing to signal when a transition to sales made sense. The result: Figma scaled to billions in valuation without compromising the elegance of their PLG motion for individuals.
Notion: PLG to sales-led at $1k ACV.
Notion’s free tier is generous. But as teams scale and enterprises want custom branding, audit logs, and dedicated support, Notion introduces a sales team. The PLG motion brought in the early adopters and evangelists. Sales extended the motion to larger organizations.
Rules for scaling through the ACV ceiling
Rule 1: Identify your ACV ceiling before you optimize past it.
Use the diagnostic above. Find where your conversion rate drops sharply. That is your ceiling. Accept it. Do not try to optimize past it; the ceiling is structural.
Rule 2: Start designing for the transition while PLG is still working.
Do not wait until growth stalls. The best time to build a sales organization is when your product has momentum. Design your product, pricing, and customer success to enable a smooth hand-off to sales.
Rule 3: Build sales while PLG still fuels the pipeline.
The sales motion will not work if it has to generate its own pipeline. Leverage your PLG motion: leads that are ready to expand go to sales. Sales’ job is navigation, not conviction. This keeps your CAC manageable while your sales org is immature.
Rule 4: Separate ICP for PLG vs. sales-led.
Your free-tier ICP is “anyone who will get value from the product.” Your sales-led ICP is “organizations where the product will solve a strategic problem.” Do not try to serve both with the same motion.
Rule 5: Measure expansion health separately from acquisition health.
Track free-to-paid separately from paid expansion. Watch for the conversion cliff. The moment you see it, shift resources from optimizing free-tier adoption to building the sales-led motion.
The teaser: What happens when you get the transition right
Companies that navigate the ACV ceiling correctly do not plateau. They reach $5–10M ARR on PLG, then shift into second gear with a sales-led motion that scales to $50–500M. The PLG motion becomes the moat: new customers arrive with product knowledge and conviction, which makes the sales motion more efficient. Sales does not have to sell the product; they sell the organization.
But there is a harder ceiling after that. At $100k+ ACV, the sales motion breaks for a different reason entirely. The deal gets so large, the committee so complex, the implementation so involved, that the motion has to evolve again. What does that look like, and how do founders who navigate it successfully think about it? That is the next ceiling to understand.
Key takeaways
- PLG hits a predictable ACV ceiling. Low-friction products (Figma, Slack) can push it to $2–3k ACV before the committee effect makes product-only trials insufficient. Complex products (security, infrastructure) hit the ceiling at $500–1k ACV.
- The ceiling exists not because PLG is bad but because buying committees require proof that a trial cannot provide: integration planning, security review, implementation roadmap, legal negotiation.
- Founder mistake 1: forcing PLG past the ceiling (faster free tiers, more features in the free product, aggressive expansion motions). This burns cash and delays the inevitable transition.
- Founder mistake 2: not recognizing the ceiling until you are stuck. By the time you hire sales reps, your product positioning is optimized for individuals, and the sales motion is built on a foundation that does not scale.
- The transitional motion borrows from PLG (frictionless onboarding, product-first proof) and adds sales (committee selling, custom implementation). It is not a hard switch; it is a blended motion where PLG fuels sales.
- Design for the transition early: build your product with a clear hand-off point (where sales takes over), design pricing that signals expansion (team seats, enterprise plans), and measure the PLG ceiling using ACV cohort analysis.
Related concepts
How to cite this
@misc{shalvi_gtm_fundamentals_plg_at_scale_2026,
author = {Singh, Shalvi},
title = {Expansion: PLG at scale},
year = {2026},
url = {https://shalvisingh.com/gtm/fundamentals/plg-at-scale},
note = {GTM World Model — GTM Fundamentals}
} Singh, Shalvi. "Expansion: PLG at scale — GTM Fundamentals." shalvisingh.com, 2026. https://shalvisingh.com/gtm/fundamentals/plg-at-scale