When does PLG break and need a sales overlay in 2027?

What a sales overlay actually is and why the threshold matters

A sales overlay is not "adding a sales team." It is a layered set of human interventions placed on top of a working product-led motion, each layer justified by a specific signal and each one heavier and less reversible than the last. There are three, and they are meant to be built in order.

Sales-assist is the lightest. Reps own no motion — they own intervention. The product still runs acquisition, activation, conversion, and default expansion. A sales-assist rep steps in only at friction points: a self-serve deal stalled in the buying flow, a trial account that hit a wall, a prospect who clicked "contact sales" because of a procurement question, a customer stuck on billing terms while trying to upgrade from a $15K plan to a $70K enterprise arrangement. The rep is a closer and an unblocker, not a hunter. You can run this layer with one or two people, no comp-plan rebuild, no org restructure. That is why it goes first: it is cheap, low-risk, and reversible.

Sales-led expansion is the second layer, and it is the one most PLG companies under-invest in even though it usually holds the fastest ROI. Here a human — an Account Manager or Expansion AE — owns the relationship and growth of accounts the product already converted to paid. They map the org, find which other teams could use the product, locate the budget owner, run deliberate expansion plays, and treat the renewal as a conversation rather than a default. CAC is effectively zero because the customer is already acquired. This layer is what moves NRR from a stuck 110% to 125-135%, and compounded across an installed base that delta frequently outweighs the entire new-logo motion.

The full enterprise overlay is the heaviest: a separate team selling top-down into accounts PLG cannot reach at all, or where the footprint is a small shadow-IT pocket and the real deal is a company-wide multi-year agreement negotiated with a VP or C-level buyer who has never personally opened the product. It carries its own AEs, SDR support, sales engineering, deal desk, enterprise packaging, and genuine outbound. Cycles run 3-9 months; ACVs run $75K-$500K+. This is sales-led growth operating inside a PLG company.

Why the threshold matters more than the label: PLG's financial advantage is low CAC and fast payback, often 6-14 months. Every overlay layer trades some of that away for ACV ceiling relief and forecastability. Add a layer the signals do not justify and you have converted a capital-efficient company into a capital-intensive one before the revenue arrived. Add it too late and you have handed a segment to a competitor who will use it to fund a move back down into your core.

The honest mental model: PLG breaks when the marginal dollar of growth becomes meaningfully more expensive to acquire through the product than it would be through a human. Every signal below is a proxy measurement of that crossover.

How to read the seven signals before the numbers turn

PLG rarely fails loudly. It decays, and by the time decay reaches the quarterly numbers you have usually left two to four quarters of enterprise revenue uncaptured. Count these signals rather than feeling them. Three or more firing simultaneously for two consecutive quarters is the decision threshold; two is a watch-list. At least one of the three should be a demand signal rather than an internal one.

Signal 1 — Enterprise inbound exceeds roughly 10% of signups. When more than one in ten new accounts is enterprise-shaped — over 500 employees, asking about SSO and procurement, clicking "contact sales" on the pricing page instead of "start free" — you have a structural demand stream self-serve cannot serve. At 3-5% you can reasonably ignore it. At 10%+ you are losing money every week.

Signal 2 — Self-serve accounts hitting expansion ceilings. Look for accounts sitting at 80%+ of a plan's seat or usage limit that have not upgraded in 60+ days. The product has done its job; a human now has to do theirs.

Signal 3 — Competitors winning deals you should win on product merit. When win/loss interviews cite "they had a team that walked us through implementation and security" rather than "their product was better," you are bringing a self-serve motion to a sales fight.

Signal 4 — Usage-rich accounts that never convert. Free or trial accounts with deep feature adoption, multiple active users, and months of sustained engagement that stay unpaid are the cleanest qualification signal available. A human conversation closes a meaningful fraction of them.

Signal 5 — Security and procurement questions with no owner. SOC 2 and ISO 27001 requests, penetration test results, custom DPAs, vendor security reviews, SAML configuration, data residency, redlined MSAs. When these arrive weekly and route to support or a founder's inbox, each one is a stalled deal.

Signal 6 — An ACV ceiling baked into self-serve pricing. When your top self-serve tier caps around $12K/year and you keep meeting prospects who would pay $60K-$150K for the same product with enterprise controls and a relationship, the pricing architecture itself is capping ACV.

Signal 7 — Board pressure for committable revenue. Self-serve revenue is probabilistic, forecast from cohort behavior. Enterprise revenue is committable — a rep calls a number against a pipeline. Approaching a raise, this is a legitimate business signal, not vanity. It becomes a problem only when it is the *only* signal firing.

Underneath the seven sit four symptoms worth naming separately, because they show up before any signal crosses a threshold. Self-serve ARR decelerating to 4-6% quarter-over-quarter growth while signups and activation stay healthy means the funnel is saturated at the deal sizes it can close, not broken. Large accounts churning from lack of attention — in a $15M-$40M ARR PLG business the top 5-10% of accounts typically produce 40-60% of revenue, and those accounts have procurement cycles and multiple champions, so a renewal is a decision rather than a default. Expansion stalling inside accounts that should obviously grow: a 600-person company with 45 paid seats, three connected integrations, deep feature adoption, and no expansion in three quarters. And the NRR plateau, the most quantitative of them all — healthy PLG climbs toward 120-135% as cohorts mature, and flattening at 105-115% despite a good product almost always means the self-serve-shaped expansion is exhausted and what remains requires a human.

The step-by-step process for layering the overlay

The sequence below is deliberate. Each step de-risks the next, and skipping ahead is the most reliably expensive mistake in this entire domain.

Step 1 — Run the cohort analysis before anything else. Pull every account that expanded or converted to enterprise in the last 12-18 months. Look at what those accounts were doing 30-90 days *before* the expansion event. Reverse-engineer the pattern. A Product Qualified Lead definition is a regression, not a guess, and it must exist before the first hire — otherwise the first rep spends three months guessing which accounts to work.

Step 2 — Ship a v1 PQL score. The PQL is the mechanism that lets a sales overlay strengthen PLG rather than cannibalize it. An MQL expressed interest; an SQL got qualified by a rep; a PQL has demonstrated value-aligned behavior inside the product. It carries near-zero acquisition cost because the product already acquired and activated the account, and it converts at 25-40% in well-run orgs versus 1-5% for an MQL, because it is grounded in revealed behavior rather than stated intent. Crucially, it also resolves the political tension: reps are not cold-calling and not poaching free users, they are reaching accounts the product itself flagged as ready.

Step 3 — Build the handoff, not just the score. When an account crosses the threshold, fire an event into the CRM carrying context: which behaviors triggered it, account size and industry, current plan, who the active users are, and the suggested play (convert trial, expand seats, upsell to enterprise tier). A rep should open that record and know within ninety seconds why the account is on their list and what to say. The handoff that fails hands over a name and a number; the rep re-discovers what the product already knew and the efficiency advantage evaporates.

Step 4 — Hire one individual contributor, not a VP. Give them the PQL queue and the inbound. Have them establish the empirical facts: PQL conversion rate, deal size, cycle length, which plays work. They are writing the playbook the team will later run.

Step 5 — Wire the trigger design in both directions. User-initiated triggers are the buttons and forms — "Contact sales," "Get a custom quote," "Request enterprise access." Keep them visible but never blocking the self-serve path, low-friction (a short form, not a twelve-field interrogation), and fast, because a PLG buyer who clicks expects a response in hours, not days. System-initiated triggers are the more sophisticated half: the product detects a threshold crossing and proactively routes — hitting a seat or usage ceiling, a burst of team invites especially to senior titles, an SSO integration connected, sustained heavy API usage, multiple users from the same large company signing up independently, or a security-related support ticket. The discipline is that the trigger routes, not blocks.

Step 6 — Graduate deliberately. If sales-assist reps convert PQLs at 30%+ on deals larger than self-serve, the model is proven and you can build the expansion layer with the comp and org changes that layer requires. If they struggle, you learned it cheaply, with one or two salaries at risk instead of a department.

Step 7 — Score the right behaviors. The categories that predict expansion are consistent across PLG companies. *Seats and users added* is the most universally predictive — an account growing from 3 to 12 active users in 60 days is on a trajectory; weight velocity, not just count, because momentum predicts better than absolute size. *Feature depth and breadth* — accounts touching three, four, five distinct feature areas have woven the product into a workflow. *API usage* — sustained, growing call volume across multiple distinct endpoints with a production key generated means the product is embedded in the customer's own systems. *Team invites*, especially invites crossing departments or going to senior titles, are a leading indicator of company-wide spread; score volume, acceptance rate, and the org-distance of invitees. *Integrations connected* — SSO provider, data warehouse, CRM, Slack — each one raises switching costs and is trivially easy to instrument.

Layer firmographic fit as a multiplier, not an additive term: a 2,000-employee company crossing the behavioral threshold is a different opportunity than a 15-person company crossing the same one. Output a number *plus a tier* — PQL-Enterprise, PQL-Expansion, PQL-Convert — so routing logic knows which layer and which play the account belongs to. Re-fit the model every two quarters against fresh closed-won and closed-lost data; as the product and ICP drift, so do the predictive behaviors, and a stale model quietly sends reps to the wrong accounts.

Costs, timelines, and typical ranges

The most common financial error is treating the first rep's salary as the cost of the overlay. The real cost runs three to five times that, and a meaningful share of it must be spent *before* the first hire.

The first AE, fully loaded. Base plus on-target variable is the visible part. Add benefits and payroll overhead, then ramp — a rep on a brand-new motion is commonly 3-6 months from full productivity and you pay full freight the entire time — then the management and coaching time to onboard them. A first AE at a $120K-$160K base with matching variable realistically costs $250K-$350K all-in in year one once ramp and overhead are counted.

Sales tooling. A CRM configured for this motion (or a real reconfiguration of the one you have), a sales engagement layer, call recording and conversation intelligence, scheduling, and a deal desk process. Budget roughly $15K-$50K/year early, scaling with headcount.

PQL infrastructure. This is the line most companies forget and it is foundational: product analytics instrumentation, the data pipeline from product events into the CRM, the scoring model itself, and the RevOps time to build and maintain it. Between tooling and the engineering/analytics time consumed, $30K-$150K+ in year one depending on build versus buy. The important property: this cost exists whether or not the overlay works. It is the price of admission, and partially building it before the first hire is what makes that hire productive on day 30 rather than day 120.

Payback timeline. Be honest that the first layer is net cost-negative for two to four quarters. You pay for the rep, the tooling, the infrastructure, and the ramp before converted-PQL revenue catches up. A well-sequenced sales-assist or sales-led expansion layer typically reaches payback in 9-15 months *if* a real PQL engine feeds it. A full enterprise overlay built without that engine can take 24-36 months or never pay back at all — because it is then generating 100% of its own pipeline from cold outbound at true sales-led CAC, which is exactly the cost structure PLG existed to avoid.

Deal cycle and ACV ranges by layer. Sales-assist deals look like accelerated self-serve: days to a few weeks, ACVs in the same band as the top self-serve tier through roughly 3-5x it. Sales-led expansion runs on the renewal and usage calendar — weeks to a couple of months, with the payoff measured in net expansion ARR rather than logo count. The enterprise overlay is 3-9 month cycles at $75K-$500K+ ACV, with a security review, procurement, legal, and executive alignment in the path.

Readiness thresholds. The revenue proxy for "the PLG engine is real and self-sustaining" is typically $2M-$5M ARR, growing efficiently, with a payback period that proves the unit economics. It is a range rather than a number because it depends on ACV and inbound mix: a company at $2.5M ARR with 15% enterprise inbound is more ready than one at $6M ARR with 2%. Below that band you do not have an engine for sales to overlay — you have a product looking for a motion.

Enterprise-readiness prerequisites, which have their own timeline. Before the heaviest layer can win anything, the product and company need SSO/SAML, SCIM provisioning, audit logs, role-based access control, SOC 2 and ideally ISO 27001, a real DPA, custom contract capability, an SLA, and a matching support tier. SOC 2 alone is a multi-month exercise. Building the enterprise team before this exists produces a team that loses every deal at the security review and burns out in two quarters.

The metrics that gate the spend. Watch five together. *Self-serve conversion rate* — healthy and stable means sales is an addition; declining means fix the funnel first, because otherwise you are papering over an activation problem with expensive humans. *Time-to-value* — short and consistent is the foundation, and lengthening TTV is a readiness red flag because a PQL only means something if accounts reliably reach value. *Net revenue retention* — the master metric, and its plateau is the single most reliable trigger for the expansion layer. *Enterprise inbound percentage* — tells you whether sales-appropriate demand is self-sustaining. *Usage-without-payment cohort size* — evidence the product creates value the motion fails to capture; if that cohort is small, the overlay has little to harvest. Both conditions must be true: healthy engine *and* genuine uncaptured demand. A healthy engine with nothing uncaptured means stay pure. An unhealthy engine with apparent demand means fix the product, because that demand is an artifact of a leaky funnel.

Where teams get it wrong

Five archetypal failures account for most of the damage, and each has a recognizable early tell.

The premature VP of Sales. A company at $3M ARR with strong PLG metrics but one or two signals hires a senior VP from a sales-led background. The VP does exactly what they were hired to do and builds a team in their own image — AEs with quotas, SDRs doing outbound, a traditional pipeline. With no PQL engine to feed it, that team generates cold pipeline at sales-led CAC, the unit economics blow out, and the board that wanted predictable revenue now owns an expensive cost center. The correct move was one IC and a scoring model. The pattern is hiring the *leader* and the *structure* before proving the *motion*.

The free-tier war. A commissioned sales team arrives without incentives aligned to the PQL. Reps rationally see the free tier as unmonetized inventory and lobby — successfully — to gate features behind "contact sales" and shrink the free tier. This failure is uniquely insidious because it is self-reinforcing: gating creates more contact-sales volume, which makes sales look productive, which justifies more hiring, which creates more pressure to gate, all while top-of-funnel conversion quietly erodes. By the time leadership notices, both the product and customer expectations have changed and the engine is hard to rebuild.

The PQL-less enterprise team. A company skips sales-assist and expansion and builds the heaviest layer first because enterprise logos are exciting. With no scoring engine, the team cold-prospects, ignores the warm product footprint, and competes against true sales-led companies on their terms and at their CAC — while thousands of unharvested in-product footprints sit untouched. The pattern is throwing away the one structural advantage a PLG company has when it enters enterprise sales.

The attribution civil war. Without a pre-agreed model, marketing, growth, and sales spend every QBR fighting over credit for PQL-sourced revenue. Reps refuse to work PQLs they cannot claim fully; growth resents sales "stealing" product-driven wins. The org turns zero-sum precisely where it needed to compound.

The founder's vanity enterprise pivot. After a competitor announces a big logo or after a hard board meeting, a founder decides the company is "going enterprise" and redirects roadmap, hiring, and their own time toward a handful of large prospects while the PLG engine — still 90% of revenue — is neglected. A few marquee deals close slowly and unprofitably; the self-serve motion decays from inattention.

Beyond the archetypes, three design mistakes recur.

Comp that makes reps fight the queue. The tension is unavoidable: how do you pay a rep for revenue the product substantially generated? Paying full commission on every PQL overpays and makes your most efficient revenue your most expensive. Paying nothing on product-sourced revenue means no good rep joins, and the ones who do chase the few cold deals they can claim. What works: a lower rate on PQL-sourced revenue than rep-sourced — for example 6-8% on a converted PQL versus 12-15% on a cold-sourced deal — which honestly reflects that the rep closed it and handled procurement while the product generated the demand. Comp the expansion AE on net expansion ARR with renewal as a gate, so they are not paid at all if the base churns. Comp the enterprise overlay closer to a traditional plan because that motion genuinely is rep-driven, with a modest haircut where a meaningful product footprint pre-existed. The governing principle: tune the rates until a rep working the PQL queue diligently *out-earns* a rep chasing cold deals. If cold is more lucrative, you have built a sales team that fights your PLG motion. Keep year-one quotas realistic on any new layer — a mature quota on an unproven model guarantees turnover that resets your learning to zero.

Blurred org boundaries. The clean line is that growth owns the funnel up to the PQL; sales owns everything from the PQL forward. Growth — product managers, growth engineers, lifecycle marketing, product marketing — owns acquisition, onboarding, activation, the self-serve conversion and expansion paths, the pricing page, in-product upgrade flows, and the PQL model itself, measured on signups, activation rate, self-serve conversion, and PQL volume. Sales owns PQL conversion, expansion of PLG-acquired accounts, and the enterprise overlay, measured on PQL conversion rate, net expansion ARR, and enterprise bookings. Four hard rules: do not put sales in charge of the free tier or self-serve pricing; do not let sales prospect the active free-user base unsupervised; keep Customer Success as its own function under its own leader, neither folded into sales (it becomes a revenue function and stops protecting retention) nor into support (it stops being proactive); and have one revenue leader accountable for the seam, because the most common hybrid failure is two leaders optimizing two halves and nobody owning the middle. RevOps is the connective tissue — it owns the data pipeline from product analytics into the CRM, the attribution model, the routing logic, and the account segmentation that decides which customers get a human CSM versus digital CS. Without it, growth and sales argue about definitions instead of compounding.

No attribution rules agreed in advance. Use three mutually exclusive categories plus one overlay tag. Product-sourced: the account self-served to paid with no human — full credit to growth. Sales-sourced: a rep generated the opportunity with no meaningful product footprint — full credit to sales. Sales-converted (PQL-sourced): the product generated the PQL and a rep converted or expanded it — reported explicitly as *shared*, never claimed whole by either side. Sales-influenced is a tag layered on product-sourced or PQL-sourced deals a rep helped, used to understand contribution and never double-counted into revenue. Decide the rules before the quarter, compute them from product and CRM events rather than arguing them in a spreadsheet, and report the shared category proudly — a healthy hybrid *wants* a large sales-converted number.

The wrong first hire. The instinct is a proven enterprise rep with a big logo on their resume. That is usually wrong, because their entire instinct is built for a motion you are not running. The right first hire is PLG-native, consultative, and product-fluent: comfortable diagnosing a situation and pointing a customer to a *smaller* tier when that is right, because in a PLG motion trust compounds and pushy closing torches it; able to actually use the product and hold a credible technical conversation without a sales engineer; energized rather than insulted by a warm PQL queue; and collaborative with product and growth, feeding friction back rather than treating those teams as adversaries. Explicitly not a cold-outbound hunter — a hunter dropped into a PQL-conversion role gets bored, goes rogue prospecting, and resents the comp plan. Look for someone who *chose* PLG, often from another PLG company one stage ahead, or from sales engineering or senior CS. The first hire sets the cultural template for the whole revenue org.

Decision framework: which layer, and when to hold

Both errors are real, and the discipline exists because avoiding one instinct pushes you into the other. Pure-PLG-purist culture pushes good operators toward "too late"; logo envy and board pressure push them toward "too early."

Too early is asymmetrically worse because it is harder to reverse. It crushes the unit economics that made PLG work — blended CAC balloons, payback stretches from months to years, and the efficient-growth story breaks. It starts the free-tier war described above. And it distracts the founder, who gets pulled into being the de facto enterprise closer, spending their highest-leverage time on a handful of slow deals while the engine generating the overwhelming majority of revenue runs unattended. You cannot easily un-hire a team, un-change a comp culture, un-gate a free tier, or un-distract a founder. Waiting one extra quarter costs a quarter of enterprise revenue; moving one quarter early can cost the engine.

Too late is permanent in a different way. Enterprise demand does not wait — a 3,000-person company with a real initiative and no door in your funnel buys something else, and once a competitor lands that account top-down you are locked out for years. Whales churn from neglect: the largest accounts have the most stakeholders and the most competitive attention, and running them through the same automated lifecycle as a 5-seat account loses them at renewal, which in a power-law base can erase a quarter of net new growth. Worst, the competitor who built the enterprise motion you delayed uses that revenue and those reference logos to fund a move back *down* into your mid-market core. And an NRR stuck at 108% because you never built sales-led expansion is a valuation ceiling on the metric investors weight most heavily.

The counter-case deserves explicit weight. A sales overlay is the *wrong* move in three situations. If PLG still has runway — self-serve conversion healthy and improving, ARR compounding, few signals firing — the highest-ROI investment remains the funnel. If the real problem is activation rather than coverage, adding reps hides a product problem behind headcount; the tell is a declining self-serve conversion rate or a lengthening time-to-value. And if the only signal firing is board pressure or founder ambition, you are pushing rather than being pulled, which is the archetypal premature-VP setup.

Pricing architecture is the routing mechanism that makes the framework work without a human deciding. Four altitudes, each boundary mapping to a motion boundary. *Free* maximizes top-of-funnel and must deliver a genuine "aha" — a crippled free tier kills the engine — but bounded so that success on it creates a natural reason to pay via a seat cap, usage cap, or value-aligned feature gate. It is a growth instrument, owned by growth, not a sales concession. *Self-serve paid* is the workhorse, credit-card purchasable, capturing SMB and lower-mid-market efficiently across one to three sub-tiers. *Sales-assisted* is where "talk to sales" first appears as an option rather than a requirement — volume pricing, annual contracts, light procurement, a security questionnaire — with a semi-public starting price and a negotiated final number. *Enterprise* is contact-sales with no public price, bundling SSO/SCIM, audit logs, RBAC, SLA, dedicated support, and custom contracts. Place "contact sales" too low and you throttle the funnel while teaching customers the product is "really" sales-led; place it too high or not at all and enterprise demand has no door.

Customer Success sits alongside, not inside, the overlay. CS owns adoption, health, and retention of PLG-acquired accounts post-conversion; sales-led expansion owns growth of those same accounts. Do not merge them: a CSM carrying an expansion quota stops being a trusted advisor and you lose your best retention asset, while an expansion AE responsible for health neglects it because comp says growth. Separate incentives, shared accounts, one shared health definition. Below the relationship threshold, "Customer Success" is the product plus pooled digital CS — in-app guidance, lifecycle messaging, help center, community, reactive support. You should not put a human CSM on a $2K/year account, and RevOps owns the segmentation logic that keeps that line consistent.

What the pattern looks like when it works. Slack spread team-by-team on free and self-serve, building enormous in-org footprints before any rep got involved, then layered an enterprise team whose explicit job was converting existing footprint into a top-down agreement with the central administration and controls IT required — harvesting, not cold prospecting. Figma spread bottoms-up among designers because every shared file was a growth loop, then built enterprise pricing, org-wide plans, admin and security controls, and a team that formalized and expanded rather than convincing from zero. Notion grew for years on viral templates and a generous free tier, then deliberately built enterprise plans, an enterprise sales team, and the SSO/SCIM/audit-log capabilities enterprise buyers require — sequencing after the product engine was unambiguously proven. Datadog runs the mature balanced version: developers adopt bottoms-up with frictionless onboarding, usage grows as customers instrument more infrastructure, and a substantial enterprise organization lands, expands, and drives multi-product adoption on top. Airtable shows both sides — a huge, diffuse self-serve footprint is fertile ground for an enterprise team, but only if that team can identify *which* footprint is convertible, which is precisely the PQL problem.

The strategic question is never "PLG or sales." It is: what is the lightest sales layer the signals justify, and how do I sequence it so it strengthens the PLG engine instead of fighting it?

Related questions

What ARR should we be at before hiring the first salesperson?

Typically $2M-$5M ARR with efficient growth and proven unit economics — but the range flexes with inbound mix. A company at $2.5M ARR with 15% enterprise inbound is readier than one at $6M ARR with 2%. Revenue is the floor; three signals over two quarters is the actual trigger.

Should we hire a VP of Sales or an individual contributor first?

An IC, always. A VP builds a team in their own image before anyone has proven the PQL motion converts, producing cold pipeline at sales-led CAC. One consultative rep working the PQL queue establishes conversion rate, deal size, and cycle length — the facts a VP needs to hire against.

How do we pay reps for revenue the product generated?

Split the commission rate: roughly 6-8% on converted PQLs versus 12-15% on rep-sourced cold deals. Tune until a rep working the queue diligently out-earns one chasing cold deals, so the plan pulls reps toward your efficient revenue rather than against it.

Can adding sales actually damage a working PLG motion?

Yes — most often through the free-tier war. Quota-carrying reps with no PQL engine lobby to gate features behind "contact sales," which is self-reinforcing and structurally erodes top-of-funnel conversion before leadership notices. Keep free-tier and self-serve pricing decisions owned by growth.

What if our signals are firing but self-serve conversion is falling?

Fix activation first. Falling self-serve conversion or lengthening time-to-value means the problem is product value delivery, not sales coverage. An overlay added onto an unhealthy engine hides the underlying defect behind headcount and makes it more expensive to diagnose later.

FAQ

Is there a revenue number at which PLG automatically breaks?

No. PLG breaks at a signal threshold, not a revenue number. Two companies at identical ARR can be in completely different positions depending on enterprise inbound share, NRR trajectory, and how much usage-rich demand is sitting uncaptured. Revenue ($2M-$5M ARR) is only a proxy for "the engine is real enough to overlay something onto." The decision rule is three or more of the seven signals firing simultaneously for two consecutive quarters, with at least one being a demand signal rather than an internal one.

What exactly makes a Product Qualified Lead different from an MQL?

An MQL expressed interest — downloaded something, attended a webinar. A PQL demonstrated value-aligned behavior inside the product: it hit the "aha," it is using the thing, and its usage pattern statistically predicts expansion. That grounding in revealed behavior rather than stated intent is why PQLs convert at 25-40% in well-run orgs versus 1-5% for MQLs, and why acquisition cost is effectively zero — the product already did the acquiring.

Which overlay layer should we build first?

Almost always sales-assist, because it is cheap, bounded, and reversible: one or two reps unblocking stalled self-serve deals, with no comp rebuild or org restructure. Its failure mode is scope creep into a full sales motion — reps start prospecting and claiming credit for product-driven conversions. Resist that; graduate on purpose when signals justify it, with the comp and org changes the next layer requires.

Why is building the enterprise team first such a common mistake?

Because it throws away the only structural advantage a PLG company brings to enterprise sales. Without a PQL engine, the enterprise team generates 100% of its pipeline cold, at true sales-led CAC, competing against sales-led companies on their terms — while thousands of in-product footprints sit unharvested. Fed by enterprise PQLs, the same team walks into conversations saying "you have 40 people using this across three departments, let's do it properly."

How do we stop growth and sales from fighting over credit?

Agree the attribution rules before the quarter starts and compute them from product and CRM events rather than arguing them in a spreadsheet. Use product-sourced, sales-sourced, and sales-converted as mutually exclusive categories, with sales-influenced as a non-additive tag. Report sales-converted explicitly as shared and celebrate it — a healthy hybrid wants that number large, because it means both motions are compounding. RevOps owns the model.

What are the prerequisites before a full enterprise overlay can win anything?

SSO/SAML, SCIM provisioning, audit logs, role-based access control, SOC 2 and ideally ISO 27001, a real DPA, custom contract capability, an SLA, and a support tier that matches. These have their own multi-month timelines. A team hired before they exist loses every deal at the security review and burns out within two quarters, and no amount of sales talent compensates for a missing compliance artifact.

Sources

• https://openviewpartners.com/product-led-growth/
• https://www.bvp.com/atlas/state-of-the-cloud-2023
• https://a16z.com/the-product-led-growth-playbook/
• https://www.sequoiacap.com/article/product-led-growth/
• https://hbr.org/2021/09/how-b2b-companies-can-win-with-product-led-growth
• https://slack.com/enterprise
• https://www.notion.com/enterprise
• https://www.figma.com/enterprise/
• https://investors.datadoghq.com/
• https://www.saastr.com/when-to-hire-your-first-sales-rep/

Related on PULSE

• How do you calculate net revenue retention correctly?
• What is a product qualified lead and how do you score one?
• When should a SaaS company hire its first sales rep?
• How do you design commission plans for hybrid PLG and sales teams?
• What does RevOps actually own in a product-led company?
• How do you segment accounts for human CS versus digital CS?