PLG to Enterprise GTM: Playbook for Experimentation, Signal Discipline and AI

PLG to Enterprise GTM: RevOps Playbook for Experimentation, Signal Discipline, and AI That Actually Works

A conversation with Stephanie Couzin.

Executive Summary

Lucid’s GTM evolution is not a “PLG vs Sales” story. It’s an operating model story. In this episode, Stephanie Couzin (VP, GTM Strategy & Ops at Lucid) breaks down how modern revenue teams can scale experimentation, build enterprise sales muscle, and adopt AI without turning their tech stack into a Frankenmonster.

Readers will learn:

  • PLG → Enterprise is a signal shift: you move from optimizing for users to optimizing for accounts, buying committees, and expansion readiness.

  • Experimentation only works if comp risk is managed: GTM tests touch variable pay, so pilots must be designed as true win-wins.

  • Psychological safety is a growth lever: teams ship better ideas faster when people can speak up, fail fast, and share learnings without fear.

  • Data is the cost of entry for GTM testing: if upper-funnel metrics and activity data are messy, your “experiments” turn into opinions.

  • Standardize AI or suffer whack-a-mole: pick a core AI platform to reduce tool sprawl and enable repeatable adoption.

  • Agentic vs Copilot AI are different games: agentic is replacement (parity + cost savings), copilot is augmentation (productivity + more customer time).

  • Start with the use case, not the tool: the fastest path to value is defining the workflow problem first, then deciding buy/build.

  • One priority beats twelve “priorities”: focus drives execution, and execution is the only feature that matters.

The Hidden Shift: From “Users” to “Accounts”

Early Lucid was deeply product-led, built on a mature self-serve engine.

Then came the layering:

  • Sales motion

  • Segmentation

  • Enterprise complexity

  • Multi-threaded post-sales workflows

Stephanie describes it as moving from user-centric growth to account-centric expansion.

PLG gives you usage.
Enterprise GTM demands orchestration.

The real challenge isn’t adding sales reps.
It’s building the infrastructure to know when, where, and why sales engagement should happen.

Experimentation Built Lucid’s Sales Muscle

Stephanie points to Lucid’s early experimentation with a Product Qualified Motion.

Most PLG companies start with lead scoring at the user level.

Lucid evolved it further:

  • Not just which user is engaged

  • But what is the account telling us?

  • And who should we reach out to now?

That shift is everything.

“Where that really evolved over time was identifying at the account level, what are the signals we need to outreach at the right time with the right messaging.” — Stephanie Couzin

That’s the marriage of:

  • First-party product signals

  • Third-party intent and context

  • Segment-aware targeting

  • Persona-aware outreach

Stephanie calls it the “special sauce” of modern lead scoring.

The Account Expansion Checklist (Lucid’s Internal Recipe)

Stephanie hints at what many GTM teams lack: an internal definition of “ready.”

Lucid has an internal checklist:

“A set of account signals where we say: this account is locked and ready to expand.”

If the checklist isn’t met, Lucid doesn’t stop.

They reverse-engineer value:

  • You use Slack?

  • You use documentation tools?

  • You have workflows Lucid integrates into?

Then Lucid doesn’t sell harder.

They sell smarter: “This is how you get more value.”

Cross-Functional Alignment: Experimentation Without Chaos

Testing in GTM is not like testing in product.

Because in revenue… someone’s commission is always involved.

Stephanie puts it bluntly:

“Testing something new will impact someone’s variable compensation.” — Stephanie Couzin

So experimentation requires designing for buy-in.

Lucid ran a coverage pilot by:

  • Using lower-risk accounts

  • Making rep trades fair

  • Ensuring nobody felt punished for participating

A GTM experiment only works if it’s a win-win. Otherwise reps sandbag, ignore, or resist.

And your “pilot” becomes theater.

Psychological Safety Is the Real GTM Scaling Lever

Stephanie goes deep here, referencing Google’s Project Aristotle – Google studied what makes teams high-performing.

The #1 factor wasn’t IQ.
It wasn’t experience.
It wasn’t process.

It was:

psychological safety.

“They could speak up without fear of consequence. They felt freedom to fail fast.” — Stephanie Couzin

Stephanie teaches this internally at Lucid.

And she’s clear:

This isn’t about politeness.
It’s about intentional leadership.

Practical mechanisms Lucid uses:

  • Weekly project show-and-tells

  • “Smart Fridays” where reps share plays

  • Normalizing learnings over perfection

The GTM Psychological Safety Loop

Safe to speak → More ideas → Faster experiments → Better learning → Higher trust → Stronger execution

Data Discipline: The Unsexy Requirement for GTM Experiments

Stephanie delivers one of the hardest truths in RevOps:

Lower funnel data is solid.

Upper funnel data is… suspicious

“As you move further up funnel… fewer eyes are on those metrics.” — Stephanie Couzin

Testing requires:

  • Full-funnel accuracy

  • Integrated activity capture

  • Shared KPI definitions

  • Governance (tagging, segmentation discipline)

AI in GTM: Standardize or Suffer

Stephanie’s AI governance advice is refreshingly simple:

“Standardize on something. Otherwise you’re in whack-a-mole.”

Lucid standardized on Google Gemini.

Not because it solves every revenue use case.

But because:

  • It reduces fragmentation

  • It sparks shared experimentation

  • It creates repeatable workflows

  • It prevents reps from duct-taping random tools together

The goal is not AI everywhere. The goal is AI that fits into systems.

The Most Important GTM AI Rule: Start With Use Cases, Not Tools

Stephanie nails this:

“What use case are you trying to solve, not what tool do you want?”

Because shiny object syndrome is real. Most orgs buy AI like toddlers choosing cereal:

“Ooh, the box is shiny.”

Lucid forces the opposite:

Define workflow pain first.
Then evaluate tooling.

AI Use Case Intake Form

  1. What GTM workflow breaks today?

  2. What manual effort exists?

  3. What does “better” look like?

  4. Is this assistive or agentic?

  5. Can current stack solve 80% already?

  6. What data sensitivity is involved?

  7. What adoption friction will occur?

Agentic AI vs Copilot AI: Stop Confusing the Two

Agentic AI

  • Replaces human work

  • Measured in cost savings

  • Goal is parity (“do no harm”)

Copilot / Assistive AI

  • Enhances workflows

  • Measured in productivity and customer time

  • Harder to quantify, but more transformative

“Most AI we adopt for revenue teams is assistive. It makes teams more productive.”

That’s where the real gains are:

  • Better prep

  • Faster follow-up

  • Less manual CRM work

  • More customer-facing time

The GTM Takeaway

Stephanie Couzin’s playbook isn’t about trends.

It’s about fundamentals:

  • Experimentation with fairness

  • Signals that map from user to account

  • Data discipline across the funnel

  • Psychological safety as execution fuel

  • AI adoption that starts with workflows, not vendors

  • Standardization over chaos

Lucid’s GTM evolution shows what modern revenue teams need:

Not more tools.
Not more noise.

Better systems.
Better learning.
Better alignment.

And maybe fewer tabs open.

Want to hear more stories from revenue leaders? Subscribe to The Revenue Lounge podcast to never miss an episode!

More Resources

Top 15 Guided Selling Tools for 2025

Top 15 Guided Selling Tools for 2025 RevOps 10 min Imagine that you are planning to build a new house but are unsure where to start. You have a basic idea of what you want but are not an expert in home construction or design. In such a situation, you would need a skilled architect who understands your needs, preferences, and budget and then guides you through designing your dream home. The architect would help you make informed decisions about your new home’s design, materials, and features. Similarly, a guided selling tool uses customer data and sales expertise to help customers navigate the purchasing process and make informed decisions. It can provide personalized recommendations based on the customer’s needs and preferences, answer questions, and offer advice to help them choose the right product or service. What is Guided Selling? Guided selling is a strategy involving a structured approach to lead potential customers through the sales process. It is the process of analyzing current sales, historical sales, and customer data to help sales reps provide tailored product recommendations to customers and increase the likelihood of conversion.  Let’s say you are shopping for a new laptop. You visit a website that offers guided selling, and you’re prompted to answer a series of questions. The questions might include things like: What will you primarily use the laptop for? Do you need a large screen or a lightweight design? How important is battery life to you? What is your budget? Based on your responses, the website would then recommend a few different laptops that meet your needs. It might provide detailed information about each laptop, such as the processor, RAM, and storage capacity, as well as customer reviews and ratings. The website might offer additional guidance, such as recommending accessories or providing information on warranties and support. Throughout the process, the focus is on helping you make an informed decision based on your unique needs and preferences. Guided selling can be particularly effective for complex or high-value products or services where customers may require more personalized guidance and support to make informed purchasing decisions. By providing a more consultative sales approach, guided selling also helps to establish long-term customer relationships. How Does Guided Selling Work in B2B SaaS In B2B SaaS, guided selling typically involves a sales representative or a customer success manager who guides the customer. The process usually begins with the customer expressing their needs and goals and the guide using that information to suggest relevant products or services. The guide may use various tools, such as a software demo, to help the customer understand the features and benefits of each option. In addition, guided selling often involves providing educational resources to the customer to help them better understand the product or service and how it can help them achieve their goals. This may include case studies, white papers, or other content that provides valuable insights into the benefits and use cases of the product. Let’s have a look at the guided selling process in detail: The Process of Guided Selling Tools The guided selling process is a customer-centric approach to sales that involves guiding potential customers through the buying process by providing personalized recommendations, advice, and support. The following are the general steps involved in a typical guided selling process: 1. Gathering customer information The first step of the process involves collecting data on the customer’s needs, preferences, budget, and any other relevant information that can help the sales process. 2. Identifying customer pain points In this stage, the sales team uses the information gathered in the previous stage to identify the customer’s pain points or areas of concern.This is typically done through a series of questions or a needs assessment. 3. Providing product recommendations Based on the customer information and pain points identified, the sales team provides recommendations on the products or services that best meet the customer’s needs. 4. Presenting solutions At this stage, the sales team presents the recommended products or services to the customer and explains how they address the customer’s pain points. The sales representative provides information about the recommended products or services, including their features, benefits, and pricing. 5. Handling objections If the customer has any objections or concerns, the sales team addresses them and provides additional information or alternative solutions as needed.  6. Closing the sale Once the customer is satisfied with the recommended product or service, the sales team closes the sale by facilitating the purchase process. 7. Follow-up and customer support After the sale is complete, the sales team provides follow-up support to ensure the customer is satisfied with their purchase and offers any additional assistance or support as needed.   Examples of Guided Selling Tools in Businesses Here are some examples of techniques of guided selling tools:  1. Automate sales playbook To ensure consistent performance, sales playbooks should be automated. Guided selling relies on a solid foundation of methodologies, blueprints, and plays that facilitate the sales process. It’s important to choose a solution that simplifies the playbook for sellers, allowing them to follow the plan and consistently advance deals easily. 2. Identify specific needs In some situations, customers may need a clearer idea of what they are looking for when they visit your website. In such cases, a brief questionnaire can be used to determine and guide their specific requirements. For instance, if you run an online clothing store, you could ask customers questions about their preferred fit and fabric to steer them toward products that best match their preferences. This approach can increase the likelihood of a purchase by helping customers make informed decisions based on their needs. 3. Real-time response For a guided selling software to be effective, it needs to be adaptable and flexible, able to react to changing circumstances in real time. At a fundamental level, ensuring that sales representatives remain attentive to communication and other sales activities can reduce the time it takes to close deals and result in higher revenue velocity. In other cases,

A 30-60-90 Day Guide for First-Time Directors of Revenue Operations

A 30-60-90 Day Guide for First-Time Directors of Revenue Operations RevOps 10 min Starting a new job as a Director of Revenue Operations is an exciting opportunity to make a significant impact on a company’s revenue growth. To ensure success in this role, it’s essential to have a strategic plan that guides your actions during the crucial first three months. Here’s a 30-60-90 day plan that will help you strategically manage revenue operations and drive sustainable growth. We recently spoke to Hassan Irshad, Director of RevOps at FEVTutor. He shared his approach to this powerful framework, demonstrating how each phase (30, 60, and 90 days) builds strategically upon the last to deliver alignment, trust, and sustained improvement. By breaking down complex goals into achievable milestones, the 30-60-90 day approach empowers RevOps leaders to initiate meaningful change without overwhelming teams. For all the RevOps leaders, it’s a way to approach change with purpose, driving measurable impact and laying the groundwork for long-term success.  The 30-60–90 day framework must be an indispensable tool and here is how you can implement progressive, sustainable growth strategies from day one. First 30 days for a Director of Revenue Operations The purpose should be to gather insights and understand the organization, especially the needs and challenges of different teams. 1. Goals for first 30 days:   i. Meet Key Stakeholders Meet with cross departmental teams like Finance, HR, and Sales to understand their goals, challenges, and priorities. ii. Document Everything Create a “lay of the land” document summarizing findings on different team goals, challenges, and processes.   iii. Understand the Product Take product demos, listen to sales calls, and use tools that show how the product is sold. This helps in understanding the customer needs better. iv. Dive into Your CRM Understand your CRM (whether Salesforce or HubSpot) to assess how the data is organized. This is to check whether it’s easy to use, and identify immediate improvements. The CRM should be the central source of truth, with other tools supporting it. The data should be unified with easier adoption for the teams. v. Build Trust Internally Establish trust within your teams by listening carefully, asking questions about how RevOps can help, and addressing quick fixes to show you’re there to help. Having this trust shows them that you’re here to support their success. Quick wins, such as small fixes that make people’s jobs easier, helps in establishing credibility early. 2. Establish Clear KPIs   i. Understanding Team KPIs It is important to ask you stakeholders about the KPIs that matter to understand their goals and what their expectations are. ii. Aligning KPIs Across Teams Different departments oftentimes work in silos. RevOps should strive to align these departments and check if these KPIs match the overall business objectives. Gaps must be closed if their KPIs don’t align. iii. Setting RevOps KPIs As you approach the end of the first 30 days, start establishing RevOps-specific KPIs that match company goals, which may involve metrics like revenue increase, conversion rates, or improvements in overall efficiency. 3. Tech Stack Audit Deep dive into the existing tools that your company is using. Identify all redundancies, and find opportunities to streamline the entire tech stack. i. Map Out Tools Compile a list of all tools used by teams, noting their purpose and how they work with the CRM. ii. Evaluate Use and Cost Determine if tools are actively used or if there are duplicates. Look for cost-saving opportunities by consolidating tools when possible. https://www.youtube.com/watch?v=sVDJ9KI1tGw&t=869s Next 30 days – Alignment and Control The next 30 days marks a shift from discovery to alignment. The goals should be to create cohesion between departments (e.g., Sales, Marketing) and laying down effective controls. The improvements need to be implemented without overwhelming the teams. This phase combines further exploration with actionable improvements with the primary task being bringing the teams into sync.   1. Ways to bring your teams together i. Encouraging cross-team collaboration by addressing silos and ensuring all teams work toward shared quarterly or company-wide goals. ii. By creating alignment, you help teams see RevOps as a support system rather than an enforcer. This keeps communication channels open and creates buy-in. iii. Based on your findings, introduce controls wherever needed to improve workflow. Example: If close dates aren’t being recorded properly, this could skew reports. Meet with sales, identify the root cause (e.g., manual data entry that is taking too much of a reps’ time), and provide solutions or tools to make their tasks easier. Ensure that controls are practical and developed with the trust built in the first 30 days. Foster internal consensus within teams so that these improvements are adopted seamlessly. 2. Navigate Organizational Politics (i) Barrier Removal Larger organizations may have internal politics or ingrained processes that resist change. Find an internal “sponsor” who trusts and supports RevOps initiatives and can authorize actions to navigate any resistance. (ii) Trust and Consistency As you implement changes, make sure your efforts consistently demonstrate how RevOps can make work easier and more efficient for everyone. 3. Evolving the Tech Stack (i) Assessing Tech Needs If tools aren’t fully integrated (e.g., a tool not writing data back to the CRM), identify their gaps and consider evolving the tech stack. (ii) Holistic View Use insights from the discovery and alignment phases to start envisioning necessary tech improvements that align with company goals. Beginning of the 90-Day Phase: Vision and Execution This phase, described as “Vision and Execution,” involves shaping and executing a strategy based on insights gathered from the discovery and alignment phases. a. Roadmap Creation Create a roadmap covering the next two quarters, focusing on long-term, high-impact changes that align with business goals. Use learnings based on stakeholder needs, organizational goals, and the findings from the first 60 days i. Set Priorities Collaborate with end users (Sales, Marketing, Customer Success) to understand their pressing needs and align the roadmap with these needs. ii. Strategic Execution Prioritize initiatives that will have immediate revenue impact or

Scroll to Top
Upcoming Webinar

How To Build Autonomous GTM Agents that Revenue Teams Actually Trust

A panel on autonomous GTM: what works, what breaks, and what trust actually requires.

Just one more step