The product-led growth mistake most SaaS companies make

PLG became the dominant growth framework of the 2020s because Slack, Figma, Notion, and Calendly made it look easy. It is not easy, and it is not universally applicable. Most B2B SaaS companies that have adopted PLG are running a free tier without a conversion engine — and calling the support tickets that result a growth strategy.

What PLG actually requires

Product-led growth is a go-to-market strategy in which the product itself is the primary driver of acquisition, activation, and expansion. The key word is "primary." PLG doesn't mean no sales team — it means the product does the job that a sales team would otherwise do, up to the point where the deal size justifies human involvement.

For this to work, three structural conditions need to be present simultaneously.

First, the product must deliver meaningful, standalone value to a single user before any team or collaboration feature is required. Figma passes this test — you can design a complete document alone and get significant value. Most project management tools fail it — a project management tool with one user is a worse to-do list. If your product's core value proposition requires more than one person or significant data setup before it becomes useful, PLG will produce a high churn free tier, not a conversion engine.

Second, setup friction must be low enough that a non-technical user can reach the activation event — the moment of first real value — without assistance and in under thirty minutes. This is not a design preference, it is a structural requirement. PLG works because the product replaces the sales call. If a user needs a 45-minute onboarding call to understand how to set up the tool, they need a sales call. You haven't replaced the sales call with the product — you've just removed it and introduced abandonment instead.

Third, and most commonly missing: there must be a clear, natural upgrade trigger. This is the moment where the free-tier user hits a wall that only upgrading solves, and the wall is one they want to solve rather than one that feels like a penalty. Usage-capped premium features, such as a limited number of AI generations, can be a genuine upgrade trigger — users who hit the limit are already convinced of the value and want more of it. A seat limit on a product that most users use alone is not a natural upgrade trigger — it is a tax on people who want to add colleagues.

The free-tier support burden trap

When a product is adopted as PLG without these conditions being met, the outcome is predictable. Free tier signup rates look good — you've removed the primary friction of the purchase decision. Activation rates are low — the setup is too complex without assistance. The free tier generates support tickets at the same rate as paid users, without the revenue to support it. Conversion rates from free to paid are below 2%, and the product team cannot identify a clear intervention because the upgrade trigger is unclear.

Consider a hypothetical B2B data integration platform that adopts PLG with a free tier of 1,000-row limits and no data source restrictions. Free signups jump from 200 a month to 1,800. This looks like success. Support ticket volume climbs even faster. Run illustrative numbers: at 1.4% free-to-paid conversion within 90 days and a USD 4,800 ACV, those 1,800 signups produce about 25 new customers a month. If supporting the free users costs more than the revenue those customers bring in, the free tier is cash-flow negative — whatever the board calls it.

The structural problem: data integration is not a single-user product. You need credentials from multiple systems, permissions from IT, alignment with a data team, and a specific use case to connect. None of these can be resolved in thirty minutes by a non-technical user. The activation event — first successful data sync — requires setup complexity that the sales-assisted motion resolves in a 45-minute implementation call. PLG removes that call and introduces abandonment instead.

The products where PLG is structurally sound

PLG works consistently when the product is designed from the first line of code for it. The canonical examples share structural features beyond the brand recognition: Calendly delivers full value to one person (schedule your own meetings), has zero setup complexity (connect your calendar, share a link), and has a natural upgrade trigger (you want multiple event types or team scheduling). The product architecture and the PLG motion are inseparable.

Loom is another clean example. A single video recorded and shared delivers immediate value. The viewer does not need a Loom account. The upgrade trigger is precise: you have hit the video limit and you are already convinced of the value because you've used it. The free tier is not a reduced version of the product — it is the complete value proposition with a natural volume ceiling that converts engaged users.

Linear is instructive for B2B specifically. Issue tracking has been a PLG-hostile category — most issue trackers (Jira being the canonical example) require significant configuration before they're useful, are inherently team products, and have unclear individual-user value. Linear succeeded with PLG by making the single-user experience — fast, keyboard-driven, beautiful — the product's primary differentiator. One developer using Linear is a markedly better experience than one developer using Jira. That individual value is the foundation on which the team growth loop is built.

The hybrid motion that most B2B companies actually need

For most B2B SaaS products — particularly those in categories that require integration, configuration, or multi-stakeholder buy-in — the right answer is not PLG or sales-led growth. It is a product-assisted sales motion: the product creates intent and demonstrates value, and a human converts that intent into a purchase.

This is not a failure to implement PLG. It is a correct reading of your product's structure. The practical implementation looks like this: a free trial (time-gated at fourteen or thirty days, not a permanent free tier) with an assisted onboarding track. Users who complete onboarding and reach the activation event within the trial period are flagged for sales outreach — not a cold sales call, but a call to an already-activated user who has experienced the product's value and is approaching the end of their trial.

This motion can convert activated trial users at many times the rate of free-tier-to-paid conversion in a true PLG model. The economics are structurally better for complex B2B products because the sales cost is applied only to already-activated users rather than being eliminated and replaced with support costs.

HubSpot ran this motion for years before adding PLG elements to its lower-tier products. Salesforce built its business on a sales-led motion. Both are among the most successful SaaS companies in history. The growth motion needs to match the product's structure and the buyer's journey, not the prevailing framework in the industry press.

Diagnosing whether PLG is working

If you have already launched a PLG motion and want to know whether it is functioning as a conversion engine or a support burden, there are four diagnostic metrics that tell the truth quickly.

Free-to-paid conversion at 90 days. Below 2% for an individual-use product or below 5% for a team product is a signal that the upgrade trigger is unclear or absent. Between 2-5% for individual and 5-10% for team suggests a working trigger with room for optimisation. Above these thresholds consistently is evidence of a functioning PLG engine.

Time-to-activation for free users. If the median free user takes more than 48 hours to reach the activation event, the setup friction is too high for PLG to work without assistance. PLG activation needs to happen in the first session or the abandonment rate will absorb the signal.

Support cost per free user. If your free-user support cost per account is within 50% of your paid-user support cost per account, you are subsidising free users at roughly the same rate you are serving paying customers. This is the support burden trap in a single number.

Upgrade trigger clarity. Qualitatively: can you name a single moment in the product that converts free users to paid at a disproportionately high rate? If you cannot, or if the answer is "different things for different users," you don't have a trigger — you have users who upgrade despite the absence of one.

• 01
  Test single-user value before building the free tier. Can one user, alone, without assistance, get clear value from your product in under thirty minutes? If the answer is no, PLG will generate signups and abandon them. Solve this product problem before adopting the go-to-market motion.
• 02
  Design the upgrade trigger before the pricing tiers. The upgrade trigger is the feature or limit that a genuinely engaged free user will want to unlock. Design this first — it should feel like removing a ceiling, not like lifting a penalty. Then build your pricing tiers around it.
• 03
  Track support cost per free user from day one. If free-user support cost is within 50% of paid-user support cost, the free tier is cash-flow negative. This is not a marketing cost — it is a structural problem with your PLG model that will not improve as you scale.
• 04
  Consider a time-gated trial over a permanent free tier. For products with setup complexity or multi-stakeholder buy-in, a fourteen-day full-access trial with an assisted onboarding track converts better than a permanent free tier with feature limitations. The trial creates urgency. The assistance resolves the setup friction that PLG alone cannot overcome.
• 05
  If your ACV is above USD 10,000, PLG is unlikely to be your primary motion. At that ACV, the buyer's journey involves multiple stakeholders, procurement processes, and security reviews. No free tier experience replaces that process. PLG can generate intent and qualified leads, but a sales team closes the deal. Build the product experience to generate intent, not to replace the sale.

Frequently asked questions.