PLG (product-led growth) motion

Product-led growth is a motion where the product itself performs the work usually done by marketing and sales teams: attracting users, demonstrating value, and moving them to purchase. It is not a philosophy. It is an operational choice with hard constraints. When those constraints are met, PLG is the lowest CAC motion available. When they are violated, it is a catastrophe.

What PLG actually is

PLG is a motion, not a product feature. A motion is the orchestrated set of touchpoints that moves a prospect from awareness to decision and then expansion. In a sales-led motion, salespeople are the primary touchpoints. In a PLG motion, the product is.

Here is the full customer journey in a PLG motion:

Discover: A prospect finds the product. Usually through organic search, word-of-mouth, or community channels. No sales team, no ads, no outbound prospecting. The discovery is pull-driven, not push-driven.

Signup: Frictionless signup. No sales call required. No qualification meeting. No contract negotiation. The prospect creates an account, sometimes with just an email address. The onboarding is self-serve.

Aha moment: Within minutes to a few hours, the user experiences the core value. They see a real result from the product. This is not aspirational value (what the product could do). This is concrete value (what it does right now, for their real problem, in their real context). The aha moment is when the user thinks: “Oh, this actually works. I see why I need it.”

Activation: The user configures the product for their use case, invites collaborators, connects it to their workflows. Activation is the transition from “trying the product” to “using the product for real work.”

Expansion and upgrade: As the user or their team uses the product more, they hit usage-based billing tiers, need additional seats, or want advanced features. Revenue expands through usage growth, not annual contract negotiations. Expansion is automatic, driven by the customer’s own success with the product.

At scale: The product becomes sticky because switching costs are high (data, integrations, team workflows), and the customer is expanding into new use cases. Churn is driven by product obsolescence or a competitor, not by organizational decisions to “reduce spend.”

The core constraint: time-to-value

PLG is not viable above a certain threshold of time-to-value (TTV). TTV is the duration between signing up for a product and experiencing the core value.

PLG threshold: TTV must be under 1-2 hours. More precisely, the aha moment should come in the first session for many users, and certainly within a few hours of starting.

Why? Because the conversion funnel for free trials is steep. Here are typical benchmark conversion rates for PLG products:

• Free signup to aha moment: 50-70% of signups experience the aha moment within the first session.
• Aha moment to paid upgrade: 5-15% of users who see the aha moment upgrade to paid in the first 30 days. (This varies wildly by use case and pricing model.)
• Overall free-to-paid conversion: 2-8% for most PLG businesses, with high performers at 10-15%.

Every day of delay before the aha moment cuts conversion by 30-50%. Here is why:

• Users sign up with intent to evaluate. That intent decays by the hour.
• Most free users do not check back. If you do not capture them in the first session, you do not capture them at all.
• If aha moment requires configuration, setup, or learning, users abandon before they reach it.

This is not theoretical. It is the defining constraint of the PLG motion. Products that violate it—where TTV is measured in days or weeks—convert at 0.1-0.5% from free to paid. That is not PLG. That is a broken sales motion pretending to be product-led.

Diagnostic rule: If your free-to-paid conversion is below 2%, your TTV is too long. The fix is not better marketing. The fix is a faster path to core value.

When PLG works: the diagnostic matrix

PLG works only when specific conditions align. Here is the decision matrix:

When you see four or more green checkmarks (PLG works) in that matrix, you have a PLG-viable motion. When you see four or more red checkmarks (PLG fails), you have a sales-led motion. When you are in the middle, you are in a hybrid zone—and that requires intentional hybrid design, not prayer.

The asymmetry: engineer buyer vs manager buyer

One of the most dangerous mistakes in PLG positioning is treating all end-users as the same buyer. They are not.

PLG works best for engineer buyers (individual contributors with purchasing authority). A software engineer discovers a tool, starts using it, and—if the company has a distributed IT culture—can often add it to the stack without asking permission. An engineer at an infrastructure company can spin up a monitoring tool, connect it to their AWS infrastructure, and show value to their team within a day. If the tool is good, the manager sees the engineer using it, likes the results, and the product naturally expands to the team.

PLG fails for manager buyers (leaders with budget but limited tool autonomy). A manager discovers a tool, sees potential, but cannot unilaterally deploy it. They need to assess it against other options, evaluate ROI, get security/IT approval, add it to their budget forecast. The tool’s ability to deliver aha moments to individual contributors does not matter if the manager buying it has no way to evaluate those aha moments against organizational constraints.

Here is the contrast:

The mistake is positioning a tool as “for engineers” when you are actually trying to sell to engineering managers or CTOs. Your aha moment is: “I can fix this performance issue in 30 seconds.” Their buying criteria is: “Can we standardize on this across 50 teams, maintain it for 5 years, and will the vendor still exist?”

Diagnostic: If your free-to-paid conversion is strong for individual engineers (10%+) but weak for manager buyers (1-2%), you have an asymmetry. Your product has PLG motion for one buyer type but not the other. Either segment the product and motion explicitly, or accept that you need sales for manager buyers.

Where founders force PLG and lose

PLG is alluring to founders because it is cheap (low CAC) and scales quickly (exponential viral growth if the product is good). This is seductive. Founders often try to force PLG into markets where it cannot work, burning months and cash trying to solve a motion problem with product changes.

Here are the most common founder mistakes:

Mistake 1: Forcing PLG when the buyer is procurement

The pattern: You build a compliance or infrastructure tool. The product is great. Engineers love it. They use it on day 1. But the buyer is the CISO, the CFO, or the legal team. These people do not use the product. They approve the spend.

You launch a free tier hoping engineers will sign up and convince the procurement committee to buy. Thousands sign up. Conversion to paid: 0.2%. You blame product. You add features. Still 0.2%. You have diagnosed the problem backwards.

The problem is not that the product lacks features. The problem is that the aha moment for an engineer (“This tool detected an anomaly”) is not the aha moment for a CISO (“This tool reduces our risk to <1%”). You are trying to sell to two different buyers with one motion.

The fix: Segment explicitly. Keep the engineer-focused PLG motion for awareness and activation. Layer a sales motion on top for the procurement committee. Train your sales team to speak the CISO’s language: risk reduction, compliance, audit-readiness. The free tier becomes a proof point that engineers are already using the tool—not the primary conversion lever.

Founder mistake: Trying to make the free tier convince the CISO. It will not. A CISO needs a security assessment, reference calls, compliance documentation, and a three-month pilot. They do not need to “try” the product.

Mistake 2: Forcing PLG with high TTV

The pattern: You build a complex workflow tool. Onboarding requires data import, custom field setup, and training. TTV is 2-3 weeks. You launch a free tier. Ten thousand users sign up. After 30 days, 50 users have completed onboarding. Of those, 5 convert to paid.

You conclude: “Our free trial is not compelling enough. Let me redesign the onboarding.” You hire a designer, rebuild the UX. Now TTV is 1.5 weeks. Maybe 2-3% of signups complete it. Still 0.1% free-to-paid conversion.

You have misdiagnosed. The problem is not the UX. The problem is that TTV > 1 week is incompatible with a PLG motion. Most users do not have a contiguous 1-2 week window where they are evaluating your product. They sign up, get busy, come back two weeks later, do not remember why they signed up, and churn.

The fix: Separate the motion. For users with simple use cases (clear path to aha in hours), keep the PLG motion. For users with complex setups (TTV > 1 week), switch to a sales motion: 30-minute onboarding calls, hands-on setup, dedicated implementation. Or redesign the product so the aha moment comes in 30 minutes with a simplified version, and expansion/customization is the paid motion.

Founder mistake: Trying to optimize UX when the constraint is structural. No UX redesign accelerates a 3-week data migration. If data migration is required, you need a sales team or a pre-built connector strategy.

Mistake 3: Forcing PLG when the problem is not painful enough

The pattern: You build a nice-to-have tool. It would be useful if teams adopted it. But it is not urgent. It is not solving a daily pain point. Users sign up because they are curious, try it for 15 minutes, and churn because they do not have an active use case.

Free-to-paid conversion: 0.5%. You blame the onboarding. But the onboarding is fine. The problem is that the user does not have a reason to upgrade. The tool is not worth $10/month if they use it once per quarter.

The fix: Redefine your ICP. Who is the user that sees this problem every day? Or add a trigger-based motion: do not try to convert cold signups to paid. Instead, identify users who have achieved a specific milestone (connected 10 integrations, created 5 workflows, invited 3 team members) and target upgrade messaging to them. Or shift from a PLG motion to a use-case-specific sales motion where you target companies whose specific workflow maps to your tool’s strength.

Founder mistake: Assuming that a free trial can convert low-urgency use cases. It cannot. PLG works for painful problems with obvious value. It fails for nice-to-haves no matter how good the UX is.

Mistake 4: Forcing PLG in a consensus-buy market

The pattern: You build a tool for enterprise teams. It is great. Individual contributors adopt it and request it from their managers. But the manager says: “I need to evaluate this against our other options. I need security docs, compliance verification, and a meeting with your team.” The user has no authority to override that.

You see high adoption in the product but 0.1% free-to-paid conversion because the user cannot unilaterally buy. The company is paying for thousands of free users and zero revenue. You have built an acquisition machine with no monetization.

The fix: At high company sizes (>500 employees) and in regulated industries, the buyer is rarely a single person. You need to layer in a sales motion. Target the manager or the person with the budget. Do not rely on bottom-up adoption alone. Or partition the product: self-serve for individual use, sales-negotiated contracts for team deployment.

Founder mistake: Assuming that if an individual loves the product, the organization will buy it. Organizations buy on different criteria than individuals.

Mistake 5: Forcing PLG when pricing is too high

The pattern: You charge $500/month for an individual developer tool. Developers adopt it and love it. But when asked to upgrade from the free tier to paid, they push back. “I cannot expense $500/month on my own authority.” The developer loves the tool but cannot justify the cost alone.

Or you charge $5k/month. Your free tier gets thousands of signups. Conversion to paid: 0.1%. Your pricing is higher than the entire budget of a small team.

The fix: Offer a lower-priced individual tier ($10-50/month) where a single person can buy with a corporate card. Monetize expansion from there. Or shift to a sales motion for higher price points. Or implement usage-based billing where users start small ($5/month) and expand as they use more.

Founder mistake: Assuming a free tier can justify a high price point. It cannot. A free-to-paid conversion usually requires that the paid tier be affordable enough that the individual user can approve it without asking. Above ~$100/month, you need organizational approval, and organizational approval requires organizational evaluation, which requires sales.

The metrics that signal motion-market fit vs misfit

Here is how to read your metrics to diagnose whether PLG is working or broken:

Metrics that signal PLG is working

Metrics that signal PLG is failing

The PLG rules: what actually works

These are the rules that separate PLG motion success from failure. They are not guidelines. They are thresholds.

Rule 1: Time-to-value must be under 2 hours, ideally under 30 minutes.

If a user needs to configure data, set up integrations, or complete onboarding calls before seeing value, it is not PLG. It is a broken sales motion. PLG requires that the aha moment come in the first session, usually within the first 10-15 minutes.

Rule 2: The buyer must be the user.

If the person using the product is not the person approving the purchase, PLG fails. Layer sales on top for the approver, but do not expect the free tier to convince someone who does not use the product.

Rule 3: Free-to-paid conversion < 2% means redesign, not optimization.

Most founders try to squeeze conversion improvements through UX tweaks (nicer onboarding, better copy, stronger CTAs). If conversion is below 2%, the constraint is structural, not tactical. Usually, it is TTV. Fix TTV first.

Rule 4: Expansion must be product-driven, not negotiated.

In a sales-led motion, expansion is negotiated annually. “What features do you want to add? What is the new price?” In a PLG motion, expansion is automatic. Users upgrade because they are hitting usage limits or discovering new use cases. If you are manually approving expansion deals, it is sales-led, not product-led.

Rule 5: Churn must be <10% monthly (<70% annual).

PLG only works if customers stick around long enough to expand. If you have high churn, the problem is PMF (the product is not delivering value) or buyer mismatch (you are converting the wrong type of customer). PLG does not lower churn. It only lowers CAC.

Rule 6: NRR must be >100%, ideally >120%.

PLG only makes sense economically if existing customers expand faster than they churn. If NRR < 100%, you are losing revenue from your existing base. You need to fix expansion mechanics or PMF before PLG will be sustainable. (This rule applies to PLG motions that are already at scale; early-stage PLG products may not have NRR signal yet.)

Rule 7: Free-to-paid conversion must be proportional to pricing.

A $10/month product converting at 5% is healthy. A $500/month product converting at 0.5% is not. The higher the price, the more the buyer needs organizational authority, and the more the motion should look like sales-led (longer sales cycle, involvement of approvers, ROI justification). If your free-to-paid conversion is low, you may have a pricing-authority misalignment, not a product problem.

The PLG failure cascade: what happens when the motion breaks

When PLG fails, it fails fast and catastrophically. Here is the cascade:

Stage 1: The early signal. Free signup volume is healthy. You have thousands or tens of thousands of free users per month. But free-to-paid conversion is low (< 1-2%) or stalling.

Misdiagnosis: Most founders blame product. “Our features are not compelling enough. Let me add more.” Or they blame positioning. “Our messaging is not landing. Let me rewrite it.”

Stage 2: Product attempts. You add features, improve onboarding, redesign the signup flow. Free-to-paid conversion remains flat or declines. Meanwhile, you are spending engineering effort on problems that are not the constraint.

Stage 3: Marketing attempts. You assume the product is not reaching the right users. You change targeting, improve ad creative, or shift channels. Signup quality might improve slightly, but conversion stays flat. You are still optimizing the wrong lever.

Stage 4: The realization. After 3-6 months, you realize free signups are not converting. The motion is broken. But you are now months into a dead motion, and capital has been spent.

Stage 5: The scramble. You add a sales team to close the free-to-paid gap. Or you pivot to a different motion. Or you run a “powered by” partnership motion where other companies distribute you. All of these are legitimate—but they are admissions that PLG is not the motion, not last-ditch fixes to save PLG.

The cost: 6 months of wasted product development + engineering opportunity cost + misallocated marketing + demoralized team + months of lost revenue growth.

How to avoid it: Test the motion early. Do not wait for thousands of free signups to prove the motion is broken. Test with 50-100 free signups. Measure: Are 50% reaching the aha moment? Of those, are 5% upgrading in the first month? If the answer to either is no, the motion is broken. Fix it before you invest in scale.

PLG vs SLG: choosing the right motion

PLG and SLG are not better-or-worse. They are optimized for different constraints. Here is how to choose:

Choose PLG when:

• Buyer = user (engineers, designers, individual decision-makers)
• TTV < 2 hours
• Problem is painful enough to solve without external validation
• Buying committee is small (<2 people)
• Price is low enough for individual spend or corporate card ($10-1,000/month)

Choose SLG when:

• Buyer ≠ user (procurement, CFO, CISO approves; team uses)
• TTV > 1 week OR product requires compliance/security validation before use
• Problem is strategic enough to require organizational alignment
• Buying committee is large (>3 people)
• Price is high (>$1,000/month) or deal complexity is high

Choose hybrid (PLS) when:

• You have two buyer types. Example: Datadog has engineers (PLG) and security teams (sales).
• You have two use cases. Example: Slack is PLG for team messaging (self-serve) but sales-led for enterprise compliance.
• Free-to-paid conversion is strong for one segment but weak for another. Separate the motion rather than blending them.

The teaser: from PLG to enterprise

You have just read PLG as a motion. The next layer is: what happens when a PLG company scales and needs to serve large enterprise customers with different buying processes?

The answer is motion transitions—and it is not a simple “hire a sales team.” It is a deliberate architectural choice about which customer segments stick with the PLG motion, which move to a hybrid motion, and which require a full sales-led overlay. Figma did this. Datadog did this. Notion did not (they stayed PLG-pure and that has constrained their enterprise expansion).

The question of how a PLG motion survives or breaks when you scale to enterprise is the subject of the next node.

For now: you have a working diagnostic for whether your market can actually support a PLG motion. If the answer is no, do not try to optimize the motion. Redesign it. Structural failures are not fixed with execution.