From Free Users to Enterprise Contracts: The Product-Led Sales Playbook

Elena Verna defines product-led growth as the product's ability to self-serve activate, engage, and convert usage into monetization. That monetization can be direct revenue or indirect growth through virality or user-generated content. But direct self-serve monetization has a cap of around $10,000 because credit cards get flagged or declined and prosumers are often unwilling to put more on a card. Product-led sales attaches a salesperson to close a much larger contract, often $15,000, $20,000, or $100,000, for an enterprise-level solution.

PLG began with an individual use case: a person has a job to be done and solves it inside the product. PLS assumes a migration from that individual use case to an enterprise-level solution. With Amplitude, an individual wants data at their fingertips to make better product decisions, while a company wants self-servability of data, democratization of data, and a data-driven culture. Products are good at showing users what they can do, but bad at communicating enterprise-level value; sales can tell that story and increase perceived value.

Elena says the right sales motion depends on the end user's motivation, ability, and permission inside the organization. If a user is highly motivated, has the ability to solve the problem, and has permission or forgiveness from the organization, the escalator can be organic. Often, however, users lack permission to make enterprise-level decisions, need stakeholders and a committee, or cannot drive a company-wide integration. In the Amplitude example, dropping an SDK into one product area is different from convincing the entire product organization to adopt Amplitude across every interaction. Sales can bridge those friction points by attracting the right decision-makers, identifying the champion, and helping form the buying committee, while marketing educates users on how to sell internally.

Miro and Figma illustrate the ladder. An individual comes to Miro for a workshop or brainwriting board, then Miro becomes a team collaboration tool; the enterprise-level problem is increased innovation and productivity across the organization. Miro cannot clearly show that org-wide productivity increase in-product, but sales can sell the story. With Figma, an individual designer wants better feedback capture, a team collaborates more openly, and the enterprise value is better-fitting designs, faster turnaround, and better product performance. Elena argues that product development has become lazy about showcasing enterprise value and relies too much on sales to tell that story.

PLS usually starts with organic demand from the user base. Users contact support or message people at the company saying they want to purchase the product for their whole company. Elena warns that companies should not hire salespeople until they feel that pool of demand, because if nobody is asking to purchase, an SDR cannot simply manufacture a purchase. But organic demand dries up quickly if it relies only on champions and enterprise buyers who are already inside the user base. Product qualification can show that a meaningful sales conversation could occur based on usage signals, but the buyer is often missing.

Elena states that 90% of product-led sales is converting usage into an opportunity by finding a decision-maker outside the existing user base. Marketing and sales are crucial for connecting that decision-maker to the usage and then driving an opportunity through the sales funnel to closed-won. End users are not the same as enterprise buyers, so organic demand from hand-raisers plateaus and cannot carry the whole motion.

Product-led sales means going upmarket, with contract values above the sales floor. Elena puts the traditional sales floor at around $15,000, which usually means aiming for $100,000-$200,000 contracts and selling to mid-market or enterprise segments rather than small startups. Companies that sell to contractors, freelancers, or startups may be better staying self-serve because those personas do not want to talk to sales, are more price-sensitive, and prefer to do everything on their own. Adding sales changes the go-to-market motion whether the company likes it or not.

There are two paths into PLS. A product-led growth company adds PLS to move upmarket from individual use cases to company-level value. A top-down sales organization adds PLS either because customers need to see value through usage before signing, or because it is moving downmarket and its fixed cost of sale no longer scales. In the sales-led case, PLS helps automate parts of selling and remove humans from the process where possible. Elena also says every sales-led company should add product-assisted tactics, and ideally pressure product to own monetization components, even if it does not become full PLG.

Elena argues that product should own self-serve revenue targets when there is self-serve revenue, often through a growth product team rather than every core product manager. For PLS, product may not own a revenue target, but it should own the pipeline created by product and the product-qualified account threshold that triggers sales engagement. PQA is an account-level signal based on volume, velocity, feature breadth, and behavior that says now is the time for sales to engage. That threshold is different from activation and core engagement.

PQA is an aggregate account-level metric across a logo, team, or workspace, depending on what best predicts sales readiness. A PQL, by contrast, exists only when there is a person in the account who can actually buy. In smaller segments, the user may equal the buyer, but upmarket the end user is often many steps away from the buyer. Forcing sales against a high-usage PQA with no PQL creates a bad user journey and cold outbound that users ignore, so marketing may need to bring an MQL and connect that lead to the usage.

Elena describes three lead-attribution buckets: usage with a PQL already inside, usage with no buyer where marketing brings the lead, and a top-down lead with no usage at all. These channels have different conversion rates, playbooks, and sales enablement needs. Companies need to distinguish them rather than funnel every lead through the same process.

A new product signup is not an MQL in the traditional sense. In top-down sales, an MQL is already considering an enterprise-level offering; in PLS, a new user is usually trying to complete an individual job and is far earlier in the consideration journey. Reaching out ten minutes after signup to ask about budget and readiness to buy is a mismatch. Sales can add value only when it meets the user at the right point in that journey.

Elena recommends starting with top-down intuition about which account signals correlate with sales excitement, hand-raisers, or sales form submits. Feed sales accounts that fit that model, but do not send every user to sales, because low close rates will make sales disregard the channel. The next step is to compare hand-raisers with non-hand-raisers through a simple regression or histogram analysis and build the first PQA model from the strongest predictors. Sales should be involved early, and PQA definitions should evolve through regular feedback rituals.

Do not buy a PLS platform before understanding the data. Elena warns that data can tell lies and that buying a platform will not bridge the gap to understanding what actually matters. She prefers to start manually with analytics and sales intuition, then automate once there is data-sales fit. Amplitude and Mixpanel offer regression or correlation tools, but Elena says she often starts manually because the analyst needs to understand whether the data is correct and whether variables are actually predictive.

The most important PQA signals include network effects inside the company, volume thresholds, and velocity. Elena describes creating both pull and push mechanisms so new signups from an existing company join the existing account instead of creating rogue individual accounts. Seven users in a company is a common magic number, similar to seven friends on Facebook or seven connections on LinkedIn. Volume thresholds vary by product: events sent for Amplitude, boards for Miro, revisions for Figma. Velocity changes in users, events, or storage are powerful timing signals, and behavioral signals such as an admin switch or a visit to terms of use or privacy pages can indicate an enterprise evaluation.

Channel saturation matters. If sales floods email or in-app notifications, users become blind to the channel even when the timing is right. PQA is about the right time to engage, and accounts move in and out of PQA, so sales should sunset outreach if it does not connect and wait for the next PQA moment. The product should be accountable for getting more accounts to reach that threshold.

Elena approaches systems as an evolution, not a revolution. If sales is heavily embedded in Salesforce, do not force a switch to another tool; embed the PLS data into Salesforce instead. Early on, use Google Sheets, Looker or Tableau dashboards, Amplitude reports, Salesforce widgets, and ETL pipes through HubSpot or Marketo. Deliver prototypes in spreadsheets and automate only after validating that the motion has business value.

The people needed are product managers who can get accounts to PQA, salespeople who understand usage-rich PQAs and can find a buyer, marketing to educate users and enterprise buyers, and analytics to dig for correlation and test causation. If starting from PLG, Elena suggests doing the first sales yourself, founder-led style, before hiring. If starting from sales-led growth, run a pilot with an AE or SDR separated from the top-down quota. PLS that starts in PLG may begin with a blended SDR/AE role and specialize later. Notion did not hire its first salesperson until past $10 million ARR, and Miro waited until roughly $5-$7 million ARR, closing through support and customer success.

The internal collaboration model is the most important part. In traditional sales, marketing creates pipeline, sales sells, and product engages the paid user for retention. In PLS, product acquires and activates the customer and product creates pipeline for sales. That means product and sales must collaborate closely, and product must take accountability for pipeline. Trying to do PLS inside marketing is a recipe for failure within six months. Product leadership should be accountable for revenue targets while product people own KPIs such as free-to-paid conversion, package mix, and PQA or PQL creation. At Miro, the head of growth product had a self-serve revenue target and shared a pipeline-creation goal with marketing.

For self-serve revenue, Elena says the key inputs are free-to-paid or trial-to-paid conversion, package mix, average revenue per user, and first- and second-term retention. The biggest lever is monetization awareness: in a freemium product, roughly 75% of customers may not be aware of what is being sold. Products can improve awareness through feature walls, usage walls, trials, and consistent paid triggers; Slack saw gains from showing message limits, and SurveyMonkey improved conversion by making paid triggers visually consistent and ensuring users saw at least three of them, applying the advertising rule of three. After awareness, optimize checkout and pricing friction, and only then consider changing the monetization model.

For PLS, product should own a PQA target rather than a direct revenue target. Elena frames it as a conversion rate: how many active teams in the ideal customer profile segment reach the PQA threshold this month. That PQA goal becomes another product goal alongside activation and engagement, and it gives sales predictable pipeline instead of forcing sales back into a premature top-down motion.

The common pitfalls are treating PLS as a traditional top-down process, failing to hold product accountable, leaving marketing out, and waiting too long to improve data and efficacy. Sales interaction must add value rather than disrupt the user journey, and companies need to profile users at signup so they know whether buyers are in the user base. Elena recommends three to four onboarding screens asking about company size, department, seniority, and use case; users who drop off during profiling were likely low-intent anyway. Benchmarks: across Netlify, Miro, and Amplitude, it took 12+ months of usage before sales contracts could be created sustainably, with occasional high-intent exceptions. Freemium conversion is usually around 5%, trial conversion closer to 10-15%, and contract values rise as the motion moves upmarket.

Looking ahead, Elena wonders whether AI will automate parts of sales conversations through chat, email, or even Zoom, with AI selling in a deeply personalized way. That would not be pure product-led growth because the product is not selling entirely by itself, but it could become an AI sales layer that surfaces personalized answers faster than humans or content systems. She calls it simply "AI sales" and is curious how it will evolve.