TL;DR — Product-led growth is a channel strategy. It describes how customers find and adopt your product — but so does direct sales, so does partner, so does outbound. It does not describe how you capture revenue from that adoption. In our work with PLG companies, we consistently see the two conflated — and the result is strong user growth with weak monetization. The licensing, packaging, and pricing decisions don’t disappear because your acquisition is product-led. They just go unowned. Somebody needs to own the value metric decision, the packaging model, and the pricing governance — whether your GTM is product-led, sales-led, or both.
“We’re a PLG company.” We hear this from customers regularly. It means different things to different people — some mean they have a free tier, some mean self-serve signup, some mean the product team drives growth metrics, some mean all three. The label has become so broad that it communicates almost nothing about how the company actually monetizes.
What it consistently does communicate: the company’s identity is built around the product driving adoption. And that’s fine — it’s a valid channel strategy. The problem starts when PLG becomes the answer to the monetization question too. When the same framework that governs acquisition is assumed to govern revenue capture, the monetization architecture goes unbuilt.
PLG Is a Channel Strategy, Not a Revenue Architecture
Product-led growth started as a description of self-serve acquisition — the product sells itself, users convert without a sales conversation. By 2020 it had become synonymous with freemium + viral loops. By 2023, “pure PLG” was declared dead and “product-led sales” emerged as the hybrid. By 2025, PLG means something different at every company that claims it.
What hasn’t changed: PLG describes how customers arrive. It does not describe:
- What value metric the price attaches to — the licensing decision
- What capabilities go in which edition — the packaging model
- What price points hold up under deal pressure — the pricing architecture
- Who governs discounting and deal terms — the operational infrastructure
These are the trifecta decisions. They exist regardless of whether your acquisition is product-led, sales-led, partner-led, or some combination. A product-led company still needs someone to own them. The channel strategy doesn’t solve them by default — it just makes it easier to assume they’ll solve themselves.
There’s a prior problem before any of that: the capital efficiency argument for PLG — that self-serve acquisition lets you grow without burning money on sales — is scale-dependent. OPEXEngine benchmarking data shows that the efficiency benefits of PLG motions don’t materialize until companies reach meaningful scale. Earlier-stage software companies that skip direct sales in favor of self-serve acquisition often lose something they can’t buy back: the market intelligence that direct selling provides. What buyers actually value. What they’ll pay for. Where the packaging boundaries should sit. Direct sales isn’t just a revenue tactic — it’s how you learn to build a monetization architecture that PLG can later amplify. PLG scales a model that already works. It doesn’t build one from scratch. This is especially true for complex products — where buying decisions involve multiple stakeholders, configuration, and discovery — because the sales conversation is the mechanism by which you learn what customers actually value and what they won’t pay for. Self-serve can’t replicate that feedback loop.
As Lauren Kelley, former CEO of OPEXEngine (now Bain), puts it: “All costs of PLG — like marketing and website costs of free product distribution and support — should be included in CAC, in the same way that marketing and sales expense associated with direct sales to new customers defines CAC. And CAC expense and CAC benchmarks should be one factor in an optimal pricing strategy.” The capital efficiency narrative falls apart when you account for the full cost of acquiring and serving free users — and when you recognize that CAC benchmarks should inform pricing architecture, not exist in a separate conversation from it.
What Breaks When Nobody Owns PLG Pricing
Freemium as a default, not a decision
PLG companies we work with almost always start with a free tier because “that’s what PLG companies do.” The free tier isn’t evaluated as a packaging decision — it’s treated as a prerequisite of the growth model. Nobody asks: is free the right entry point for our product? Would a free trial convert better? Is the free-to-paid boundary in the right place?
The result is a free tier that captures users but doesn’t create a natural path to paid. The capabilities in the free tier are either too generous (users never need to upgrade) or too restrictive (users churn before experiencing enough value to justify paying). This is a packaging architecture problem, not an adoption problem — but PLG companies diagnose it as adoption and invest in more product-led growth tactics when the fix is restructuring what’s free and what’s paid.
Volume in the packaging instead of the licensing
PLG companies routinely build volume into their edition structure rather than their licensing model. The free tier allows 3 users. The next edition allows 10. The next allows 50. The volume thresholds live in the packaging when they should live in the licensing.
This conflation shuts down expansion revenue. When a customer needs 15 seats, they’re stuck between the 10-seat edition and the 50-seat edition. They either overpay for capabilities they don’t need (the 50-seat edition comes with features they’ll never use) or they negotiate a custom deal that takes weeks. The sales team spends its energy navigating between packaging boundaries instead of selling.
The fix: the licensing model handles volume (I need more units of the same metric) and the packaging model handles capability (I need more features). When separated, expansion is frictionless — “I need 15 more seats at the same edition” — and upsell is a separate conversation about capability.
No pricing owner
In a typical PLG org structure, the product team owns the growth model — acquisition, activation, engagement metrics. Finance owns the revenue targets. Sales (if it exists) owns deal closure. Nobody owns the monetization architecture.
The recommendation from PLG advisors is a cross-functional “PLG team” organized by outcome, tracking “Product Driven Revenue” as a North Star metric. The North Star is product-engagement-based — something every function can influence. This sounds collaborative. What it produces is distributed accountability with no architectural owner.
When every function influences the pricing metric but nobody owns the licensing decision, the packaging structure, or the discount governance, you get: – Ad-hoc discounting on enterprise deals with no consistent framework – Pricing changes driven by product engagement data without modeling revenue impact – A free tier that persists unchanged because nobody has the authority (or the data) to restructure it – Edition boundaries that haven’t been revisited since launch because “the pricing works” — meaning it hasn’t visibly broken, not that it’s capturing value
What we see in our engagements with PLG companies: almost none of them come to us with underlying monetization architecture. PLG encourages a do-it-yourself approach to pricing under the guise of simplicity — the self-serve model extends to the monetization decisions themselves, as if packaging and pricing are as easy to self-serve as the product. They aren’t. Pricing is an executive team function. CEOs who delegate it — or let it distribute across a cross-functional team with no single owner — are handing the decisions that most directly affect revenue capture, deal quality, and company valuation to the people with the least visibility into the full business model. Pricing can make or break a company. Treating it as a byproduct of the growth motion is how it breaks.
The upmarket wall
Some PLG companies do generate significant enterprise revenue — self-serve adoption can pull in large customers, especially in horizontal tools where individuals bring products into organizations. The question isn’t whether a PLG company can reach enterprise customers. It’s whether the pricing architecture was designed for them or just survived to them.
The difference shows up in deal economics. Enterprise procurement needs predictable annual costs. The PLG pricing page shows monthly per-seat rates. Enterprise buyers need custom SLAs and compliance terms. The PLG packaging has one enterprise edition with a “Contact Sales” button. Enterprise deal desk needs discount governance. The PLG company has no deal desk — and no governance framework for the custom deals that start arriving. Companies that “survive” to enterprise revenue this way rarely know how much they left on the table: compressed deal sizes, elongated sales cycles, discounts granted without a framework, and expansion revenue that stalled because the packaging wasn’t designed for it.
The fix isn’t “add an enterprise tier.” It’s designing the monetization architecture to serve multiple customer groups — self-serve individual users, mid-market teams, and enterprise organizations — each with the channel strategy that fits. PLG handles the first group. Product-led sales handles the second. Direct sales handles the third. But all three need to share a coherent licensing model, packaging structure, and pricing governance.
The Trifecta Still Applies
PLG doesn’t exempt a company from the licensing, packaging, and pricing decisions. It changes who makes them and what data informs them — but the decisions still need to be made deliberately.
Licensing in PLG: The value metric still has to map to how customers extract value. PLG companies have an advantage here — they have usage data that most companies don’t. Peer-reviewed research on subscription markets demonstrates that usage patterns reveal willingness to pay without requiring price experimentation. The data is already in your system. Use it to build a value-based pricing strategy rather than defaulting to what other PLG companies have chosen. Usage-based pricing is often the right answer for PLG products — but it isn’t automatically correct because your acquisition is product-led. Pairing PLG with usage-based pricing without deliberate value metric selection conflates the acquisition motion with the monetization strategy again, just with a different metric. And a usage-based metric without packaging guardrails and enterprise pricing governance creates its own failure modes: unpredictable revenue, customers who optimize usage to minimize bills rather than expand, and enterprise procurement that anchors negotiations to the self-serve rate.
Packaging in PLG: The edition structure has to create a natural upgrade path from free → individual paid → team → enterprise. Each boundary should be a packaging decision based on which capabilities different customer groups need — not a volume gate that forces customers into editions based on headcount. Freemium is a packaging decision, not a PLG requirement. Some PLG products work better with a free trial. Some work better with a low-cost entry tier. The right answer depends on where the value realization happens in the product experience.
Pricing governance in PLG: Even product-led companies close enterprise deals. When they do, someone needs to own the discount framework. Discount distributions in B2B software routinely span wide ranges off list — a pattern we’ve seen across datasets going back decades. PLG companies that add enterprise sales without governance find themselves in that range faster than traditional companies — because the self-serve pricing becomes an anchor that procurement uses to negotiate the enterprise deal down.
What Continuous Monetization Looks Like in PLG
Continuous monetization — the discipline of continually optimizing licensing, packaging, and pricing — is actually easier in PLG companies because the usage data exists. The challenge is that PLG teams typically connect usage data to product decisions, not monetization decisions.
The shift: the same product analytics that tell you which features drive activation should also tell you which features belong in which edition, which value metric correlates most strongly with expansion revenue, and where the free-to-paid boundary should sit. This isn’t a separate “pricing project” — it’s reading the data you already collect through the lens of monetization architecture rather than growth metrics.
When the PLG team monitors engagement and the monetization architecture monitors revenue capture from that engagement, the two compound. When they’re disconnected — when adoption goes up but revenue per customer stays flat — the channel is working and the monetization isn’t.
One clarification on what continuous monetization is not: it isn’t freewheeling experimentation. Treating pricing as a variable to A/B test — changing price points, packaging boundaries, or value metrics without a clear hypothesis about what you’re changing and why — confuses correlation with causation. You might find a number that converts better without understanding what drove the change, which means you can’t replicate it, can’t defend it under deal pressure, and can’t build on it. Controlled experiments have a place in monetization: isolating one variable, forming a hypothesis, and measuring against a clear outcome. That’s how you learn. Constant tinkering in the absence of architectural grounding is how you accumulate noise. Continuous monetization is disciplined optimization of a sound architecture — refining the value metric, adjusting edition boundaries, updating governance as the market evolves — not a substitute for building the architecture in the first place.
The discipline has a downstream consequence most PLG companies don’t consider until they’re in an acquisition conversation: asset transfer value. Buyers underwrite the pipeline, the roadmap, and the revenue quality — not just the headline ARR. A sales pipeline full of heavily discounted custom deals, negotiated without a governance framework, gets muted in the valuation multiple because the buyer can’t model what those deals are worth at renewal. A product roadmap full of capabilities has transferable value only if there’s a documented track record of how each change affected customer demand. Freewheeling experimentation — confusing correlation with causation — means you can’t demonstrate that track record, and the buyer can’t underwrite what the roadmap is worth.
The companies that get full multiple on both pipeline and roadmap treated monetization as an architecture from the start: governed discounting, deliberate packaging decisions, controlled experiments with clear hypotheses. That discipline is what makes the asset transferable. It’s also what makes the revenue defensible — because when a buyer stress-tests the pipeline, there’s a framework behind every deal, not just a collection of one-off negotiations.
Pricing is not a growth lever. It’s the architecture that determines how much of your growth you actually capture — and how much of that captured value survives due diligence. The architecture question is upstream of all of it: what value metric, what edition structure, who governs deals. Get those right, and the lever metaphor becomes irrelevant.
If your PLG company has strong adoption and weak monetization — or if enterprise deals are taking longer than they should because the pricing architecture wasn’t designed for that buyer — the growth motion isn’t the problem. The monetization architecture is. See how SPP approaches monetization for PLG companies or talk to a pricing expert about what your usage data reveals.
