From PLG to PLG+SLG – How Lucid Scaled to 70M+ Users

Lucid’s rise to 70M+ users did not happen because the company picked a side in the endless SaaS cage match of product-led growth versus sales-led growth. It happened because Lucid understood something many software companies learn a little too late: these motions are not enemies. They are phases, layers, and, when handled well, a very profitable tag team.

Long before “PLG” became the kind of term people say in board meetings while nodding thoughtfully at spreadsheets, Lucid was already building a cloud-native product that users could adopt quickly, share easily, and expand organically. The company made diagramming collaborative, web-based, and dramatically easier to access than older desktop tools. That gave it the broad distribution engine every PLG company dreams about: a product that could spread inside teams without requiring a ceremonial sales call, three demos, and someone from procurement asking questions that sound like riddles.

But Lucid did not stop at self-serve. As usage deepened inside companies, the company added a sales-led layer to serve complex buyers, support larger deployments, and unlock enterprise expansion. In other words, Lucid did not abandon PLG. It taught sales how to work with it.

Lucid’s first growth engine was not sales. It was usability.

Lucid was founded in 2010 to fill a gap in cloud-based visual collaboration. That timing mattered. Teams were already living in the browser more often, but diagramming still felt stuck in an older era. Lucidchart entered the market with a product that was easier to try, easier to share, and easier to use across distributed teams. That sounds obvious now, but “obvious” is usually what success looks like after the hard part is over.

The early logic behind Lucid’s product-led growth was simple: get broad distribution, collect rapid feedback, and improve the product fast. A self-serve, freemium model let the company put the product in front of thousands, then millions, of users without waiting for a large outbound sales machine. That decision also created an enormous learning advantage. The more people used the product, the faster the team could see where activation worked, where it broke, and where delight turned into habit.

This was not PLG as a slogan. It was PLG as operating discipline. Lucid optimized for adoption, not just awareness. It let users discover value early, collaborate with others, and naturally invite teammates into the experience. That matters because the best product-led growth does not merely get one person hooked. It creates a reason for groups to work inside the product together.

Why Lucid’s PLG model worked so well

Lucid had several structural advantages that made product-led growth especially powerful.

1. The product solved a cross-functional problem.

Lucidchart was not trapped inside one tiny job title. Engineers used it for architecture diagrams. IT teams used it for network maps. product managers used it for workflows. operations teams used it for process documentation. That breadth widened the top of the funnel without making the product feel vague.

2. Collaboration created built-in distribution.

Visual work is rarely a solo sport for long. Once one person creates a diagram, someone else needs to review it, edit it, approve it, or present it. That gave Lucid natural sharing loops. A product that moves through teams has a much better chance of turning one user into an account.

3. Integrations made Lucid easier to keep.

Lucid connected with ecosystems where work already happened, including Google Workspace, Atlassian tools, Microsoft apps, and Slack. That reduced friction and made Lucid feel less like “another tool” and more like a visual layer inside existing workflows.

4. Pricing stayed simple enough to preserve momentum.

One of the hidden superpowers of strong PLG companies is that the buying motion feels light. If users need a map, a translator, and emotional support to understand pricing, the self-serve engine starts coughing dramatically. Lucid kept its plans legible and its entry points accessible, which helped the product keep moving through teams.

The result was serious scale. Lucid’s earlier growth story includes 10M+ users in its freemium era, 15M users by 2018, and more than 20M users by 2020. By the time the company’s more recent PLG-to-PLG+SLG evolution was discussed publicly, Lucid was being framed around the 70M+ user milestone. Since then, the company’s own site has moved that headline number higher. The point is not the vanity metric. The point is that Lucid built enormous user density before trying to force every outcome through a traditional enterprise sales funnel.

The real pivot was not from product to sales. It was from users to accounts.

Many SaaS companies treat the move into enterprise as a dramatic identity crisis. Suddenly the team starts speaking in enterprise jargon, wearing more blazers, and acting like the product should apologize for having ever been easy to use. Lucid’s evolution was smarter than that.

Instead of replacing PLG with a sales-led model, Lucid layered sales on top of usage. That is the key distinction. The company already had grassroots champions inside organizations. It already had product adoption. It already had proof that teams found value. Sales was introduced not to create demand from scratch, but to capture, expand, and support demand that product usage had already surfaced.

That is why Lucid’s story is better described as PLG+SLG, or more precisely, PLG with a product-led sales layer. The front door remained self-serve. The enterprise muscle showed up when complexity, scale, security, procurement, or organizational rollout demanded more help.

Support tickets became a growth signal, not just a service queue.

One of the smartest parts of Lucid’s early evolution is almost comically unglamorous: support interactions became a discovery engine for sales opportunities. When users submitted tickets showing buying intent, asked about integrations, or came from organizations with meaningful free-user density, Lucid saw those moments for what they were: signals.

That meant the company did not need to invent an artificial enterprise motion. It could observe where product usage was already clustering and then respond. Sometimes the path was as simple as helping a happy user introduce the team to an admin or IT buyer. That is not flashy. It is just effective. And effective, unlike flashy, usually pays the bills.

This approach also reveals a larger truth about scaling from PLG to sales: the best enterprise opportunities often come from behavior, not branding. A company can call itself “enterprise-ready” all day long. If nobody inside large organizations is already using the product, that label is just a costume.

Lucid made enterprise feel like an extension of the product, not a betrayal of it

As Lucid moved upmarket, it had to serve more complicated buying requirements. Enterprise customers needed stronger administration, governance, compliance, and security controls. They also needed a smoother path for onboarding larger groups of users, managing access, and maintaining trust at scale.

Lucid responded by building the kinds of features enterprise buyers actually care about when the contract gets serious: domain control, verification, SAML, two-factor authentication, admin visibility, uptime commitments, and more advanced governance capabilities. Later, Enterprise Shield added deeper data governance and content control functionality for customers with stricter compliance requirements.

This is where many PLG companies wobble. They either over-customize for every buyer request and become operational spaghetti, or they refuse to support enterprise needs and leave money on the table. Lucid’s middle path was more disciplined. It listened for recurring patterns, built where the opportunity was durable, and avoided turning the roadmap into a museum of one-off demands.

That strategy matters because enterprise success in a product-led company should not mean building a second, unrelated company in the basement. The sales-assisted motion has to strengthen the core product, not drag it off into a swamp of custom exceptions.

Lucidspark raised the ceiling on who Lucid could serve

If Lucidchart gave Lucid a strong PLG base, Lucidspark helped widen the category. Built rapidly in 2020 and launched publicly that October, Lucidspark expanded Lucid from structured diagramming into digital whiteboarding and collaborative ideation. In less than a year, it had already reached more than a million customers.

That product expansion was strategically huge. It let Lucid capture earlier stages of teamwork: brainstorming, workshops, planning, alignment, and decision-making. Suddenly Lucid was not just the place teams documented what they had already figured out. It was also the place where they figured things out in the first place.

That shift matters in growth terms because it increases both frequency and breadth of use. A product used only for documentation can be valuable. A platform used for ideation, planning, visualization, and execution has many more opportunities to spread across departments. It also creates more reasons for executives to standardize on the platform instead of tolerating a pile of disconnected tools.

In plain English: Lucidspark did not just add a feature set. It added more entry points into the account.

The suite strategy turned usage into standardization

Lucid’s next smart move was packaging. Rather than selling separate islands of value forever, Lucid brought Lucidchart and Lucidspark together in the Lucid Visual Collaboration Suite. Then it pushed further with ideas like universal canvas, which connected ideation and documentation more tightly across workflows.

This was more than a product packaging trick. It was a go-to-market advantage. In PLG, simplicity helps people start. In sales-led expansion, broader platform value helps larger organizations standardize. Lucid’s suite strategy gave the company a way to speak to both motions at once.

A single user could still start free or small. But once an organization wanted better alignment, fewer silos, stronger governance, and faster movement from idea to execution, Lucid had a more compelling enterprise story. It was no longer just “buy more seats for a diagramming tool.” It became “standardize how teams think, plan, document, and move work forward.” That is a much bigger budget conversation.

International expansion was part of the growth playbook, not an afterthought

Lucid’s scale story also includes serious international thinking. By 2018, the company was already serving users across more than 180 countries and operating in multiple languages. It also opened an Amsterdam headquarters to support EMEA growth. More recently, leaders speaking about the company’s PLG-plus-sales motion have described international expansion as a major milestone, with a meaningful share of revenue coming from EMEA.

The lesson here is that international expansion in a PLG company is not just “translate the homepage and hope for the best.” Lucid’s public commentary around this phase points to a more disciplined model: keep pricing simple, shorten the path to value for non-English users, increase proximity to customers, respect local compliance realities, and build feedback loops that work regionally.

That playbook fits Lucid’s larger strategy. Product-led growth can open doors globally, but sustained international revenue usually requires more than passive availability. It requires localization, operational support, and, eventually, people on the ground who understand how software is purchased and adopted in each market.

What Lucid’s growth story teaches SaaS companies

Lucid’s journey offers several lessons that are worth stealing, preferably without getting caught.

First, sequence matters. Lucid did not rush to build a large sales organization before the product had broad adoption. It let product usage create leverage first.

Second, signals beat guesswork. The company used real user behavior, support interactions, account density, and integration interest to identify where sales could help.

Third, cross-functional alignment is non-negotiable. In Lucid’s more recent framing of PLG+SLG, tight coordination between product, marketing, sales, and operations is a recurring theme. Once you have both self-serve and sales-assisted motions, blurred ownership can become a tax on growth.

Fourth, enterprise does not have to kill simplicity. Lucid kept coming back to simple pricing and fast paths to value even as it added enterprise features. That is a big deal. Complexity may impress internal stakeholders, but it often terrifies actual buyers and slows adoption.

Fifth, platform breadth can amplify both PLG and SLG. More use cases mean more entry points for users and more standardization potential for organizations. Lucidspark, the suite strategy, and later platform expansion all helped Lucid sell a bigger story without losing the original product-led foundation.

Final takeaway: Lucid did not choose between PLG and sales. It choreographed them.

The most important thing about Lucid’s story is not that it scaled to 70M+ users. Plenty of people can wave around a big user number like it is a magic amulet. The important thing is how Lucid built the machine behind that number.

It started with a product people could adopt without friction. It created habits through collaboration. It expanded through integrations and team use cases. It watched for buying signals instead of forcing a premature enterprise playbook. Then it added sales, customer success, security, governance, localization, and platform breadth in a way that respected the product-led core.

That is what real PLG+SLG looks like. Not product versus sales. Not marketing versus product. Not the annual corporate ritual of inventing new acronyms and pretending that counts as strategy. Just a company that understood when to let the product lead, when to let sales assist, and how to make both motions stronger together.

Lucid scaled because it solved the right problem in the right order. First: get users. Then: understand accounts. Then: earn the right to standardize. That is not the loudest growth story in SaaS. It is just one of the smartest.

Extended experience-based lessons from the move from PLG to PLG+SLG

If you have ever worked inside a SaaS company trying to move from pure PLG to a PLG-plus-sales model, Lucid’s story will feel familiar in all the right ways. The transition rarely feels like a grand strategic masterpiece while you are living it. It feels messier. Product teams worry that sales will overpromise. Sales teams worry that product is moving too slowly. Marketing tries to explain the company in a way that makes sense to both a solo user on a free plan and a procurement committee with seventeen opinions and one shared spreadsheet. The miracle is not that tension exists. The miracle is when a company turns that tension into coordination.

That is why Lucid’s example is so useful for operators. It suggests that the healthiest version of PLG+SLG is not one where sales barges in and “saves” the business. It is one where sales learns to read product behavior, product learns which enterprise needs are durable, and customer-facing teams become translators between usage and revenue. In practice, that usually means small moments matter more than giant strategic declarations. A support ticket with buying intent matters. A cluster of active users inside one domain matters. A security question from a serious admin matters. These are not background noises. They are the plot.

There is also an emotional lesson here for founders and growth leaders. Many teams are afraid that adding a sales layer means betraying the original product-led promise. But that fear can become its own form of rigidity. Users do not care whether you win an internal philosophy debate. They care whether the product helps them do real work and whether the company can support them as usage grows. If a self-serve motion gets a team started and a sales-assisted motion helps the broader organization standardize, users are not offended. They are relieved.

The inverse is also true. Sales cannot become an excuse for product laziness. The fastest way to ruin a strong PLG motion is to let every hard problem default to “have an AE explain it.” That is how simple products become confusing products with nicer slide decks. Lucid’s growth story works because the company kept returning to user value, simplicity, and product experience even while it built out enterprise readiness. That balance is hard. It requires judgment. It requires saying no. And yes, it occasionally requires disappointing someone who really wanted a custom feature yesterday.

For modern SaaS teams, that may be the clearest lesson of all: the path from PLG to PLG+SLG is not a costume change. It is an operating upgrade. The companies that do it well are not the ones that abandon their product instincts. They are the ones that scale those instincts into a broader commercial system.

SEO Tags