Blog

When to use PLG and when not to: a decision framework for B2B SaaS

Person at a crossroads making a strategic decision

PLG has become one of the most discussed GTM strategies in B2B SaaS. The success stories — Slack, Notion, Figma, Calendly — are compelling. But the companies that made PLG work share specific structural characteristics that are not present in every B2B product. Adopting a PLG motion without those characteristics does not accelerate growth; it creates a complicated free tier that nobody converts from. This article gives you a five-dimension framework to evaluate whether PLG is right for your specific situation.

Why PLG fails when it should not

The most common failure mode is adopting PLG as a trend rather than as a structural fit. A B2B company launches a free tier, onboards thousands of users, and sees almost no conversion to paid. The free users consume support, generate noise in the data, and require ongoing infrastructure investment — without producing revenue.

This happens not because PLG is broken, but because the product does not have the structural properties that make PLG work. PLG is a motion that amplifies what is already good about your product's user experience. If the product does not deliver quick individual value, does not have natural viral mechanics, and does not create urgency to upgrade, a free tier will produce free users — not paying customers.

The five-dimension PLG decision framework

Evaluate your situation honestly against these five dimensions. The more dimensions you score positively, the stronger the structural fit for PLG.

Dimension 1: Time-to-value

The central question: can a new user experience meaningful value within a single session, without a sales call, demo, or extensive configuration?

Strong PLG fit: A user signs up, connects their calendar or uploads a file or invites a teammate, and within minutes understands why the product is useful. The aha moment is self-evident and arrives early. Calendly, Loom, and Notion all deliver value in the first session.

Weak PLG fit: The product requires a data migration, an IT integration, organizational configuration, or days of setup before a user can experience its value. ERP systems, complex financial tools, and custom-built enterprise platforms typically fall here. Not because they are bad products, but because the value is not accessible without significant setup work.

The practical test: take a new user who has never seen your product and measure the time from signup to their first moment of "this actually helps me." If that window is under 10 minutes, PLG is viable. If it is hours or days, your activation problem will undermine any PLG motion you build.

Dimension 2: Individual value vs. organizational value

The central question: does the product deliver value to an individual user independently, or does its value require organizational-level adoption?

Strong PLG fit: The product is immediately useful to a single person. A designer using Figma, an individual writing in Notion, a developer running queries in Retool — each gets value without needing their colleagues to use it first. The organizational value comes later, when collaboration features add network effects.

Weak PLG fit: The value of the product is exclusively or primarily organizational. An HRIS system without employee data has no value for the individual HR manager testing it. A procurement platform with no supplier catalog is useless to the procurement officer in a trial. Products where the value lives at the organizational level — in aggregated data, in process integration, in company-wide workflows — are fundamentally harder to PLG.

The nuance: some products can be redesigned to deliver individual value first, then organizational value at scale. This is a product strategy decision, not a fixed constraint. But it requires deliberate architectural choices, not just a free tier on top of an existing product.

Dimension 3: Annual Contract Value (ACV)

The central question: is your typical ACV low enough that users will self-serve their way to a paid plan, or high enough that you need sales involvement to justify the purchase?

Strong PLG fit: ACV below €5,000 per year. At this price point, buyers are willing to put a credit card into a checkout form without a sales conversation. The purchase decision is within an individual's authority. Procurement processes and legal reviews are not required.

Hybrid PLG+SLG fit: ACV between €5,000 and €50,000. Users self-serve to explore and validate the product, but the purchase decision often requires finance approval or a brief sales conversation. PLG generates the interest and product validation; sales closes the deal. This is the "product-qualified sales" motion and is where most successful mid-market PLG companies operate.

Weak PLG fit: ACV above €50,000. At this level, procurement processes, legal reviews, security assessments, and multi-stakeholder sign-off are standard. A free tier still has value — it lets champions validate the product internally before a sales conversation — but the conversion path is always going to involve sales. PLG is a supporting motion, not the primary one.

Dimension 4: Adoption friction

The central question: can a user get started with the product without IT involvement, data migration, compliance review, or company-level procurement?

Strong PLG fit: A user can sign up with a work email, get through onboarding with zero IT involvement, and immediately start using the product. No VPN, no IT ticket, no security questionnaire, no procurement form. Slack, Notion, Figma, Zoom — all can be started by a single employee without organizational approval.

Weak PLG fit: The product requires IT-managed SSO, company-wide data integration, custom security configuration, or formal procurement approval before a user can try it meaningfully. Enterprise security tools, deeply integrated data platforms, and products that process sensitive organizational data typically face this barrier.

This dimension is partially within your control: product teams can make deliberate choices to reduce onboarding friction and defer compliance requirements until the enterprise upgrade. But there are structural limits — some products cannot responsibly be deployed without organizational oversight, regardless of how much you simplify the onboarding.

Dimension 5: Viral or expansion mechanics

The central question: does using the product naturally bring other users into it, either through sharing, collaboration, or organizational expansion?

Strong PLG fit: The product has built-in sharing or collaboration mechanics that create new user acquisition as a side effect of usage. Figma links, Loom videos, Notion pages, Calendly booking links — each of these creates a touchpoint with a non-user who then enters the product's acquisition funnel.

Moderate PLG fit: The product does not have viral mechanics, but individual adoption naturally expands to teams. A developer uses a tool, demonstrates its value to colleagues, and the team adopts it. Bottom-up expansion without virality still works, but it requires more deliberate outreach to champions and does not create the compounding acquisition loops that make pure virality so powerful.

Weak PLG fit: The product is fundamentally single-player. It delivers individual value but creates no natural reason to share, collaborate, or expand. Analytics tools used by a single analyst, personal productivity tools, or specialized utilities used by one role in an organization are examples. PLG can still work, but retention and expansion require more deliberate nurturing rather than structural momentum.

Scoring your PLG fit

Run your product through the five dimensions and assess honestly:

  • 4-5 strong fits: PLG should be your primary GTM motion. Invest aggressively in self-serve onboarding, activation optimization, and product analytics.
  • 2-3 strong fits: PLG works best as a hybrid motion. Use PLG for top-of-funnel validation and product-qualified lead generation, then overlay with sales for conversion and expansion.
  • 0-1 strong fits: Do not force PLG. A free tier that does not convert is not a PLG motion — it is a cost center. Focus on SLG or MLG where your product characteristics actually support the motion.

The hybrid case: PLG as a sales assist motion

Many B2B companies that cannot run a pure PLG motion can still benefit from PLG elements as a sales assist. The logic: let prospects experience the product through a free trial or limited free tier before the sales conversation, so that when sales engages, the prospect has already validated the product's value.

This changes the nature of the sales conversation dramatically. Instead of explaining what the product does and why it matters, sales is having a conversation about implementation, expansion, and commercial terms with someone who already knows the product works for them. Demo-to-close rates are higher, sales cycles are shorter, and objection handling shifts from "does this work?" to "how do we deploy this organization-wide?"

For a detailed framework on running this combined motion, see the article on combining PLG and enterprise sales.

The PLG alternative: when to lead with SLG

If your product scores poorly on the PLG fit dimensions, a well-executed SLG motion will outperform a forced PLG motion. SLG makes sense when:

  • Your ACV is consistently above €20,000 and buying decisions involve 4+ stakeholders
  • Your product requires IT integration or organizational data before it delivers meaningful value
  • Your target buyers are senior executives who do not self-evaluate software — they delegate that to their teams
  • Your market is concentrated enough that a focused outbound motion with tight ICP targeting will reach a high percentage of potential buyers

SLG is not an inferior motion. It is the right motion when the structural conditions favor it. The mistake is choosing between PLG and SLG based on what is fashionable rather than what fits your product and market. For an assessment of which motion fits your specific situation, the GTM Scan helps you evaluate your current GTM architecture against your product and market characteristics.