Log in
See a Demo

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

By /

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.

Facebook Twitter Youtube

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

5 Steps to Navigate Buying Groups in 2025: A RevOps Guide

5 Steps to Navigate Buying Groups in 2025: A RevOps Guide RevOps 10 min In today’s business environment, B2B buying is never just one person. According to Forrester Research, more than half of global business buyers purchase in complex buying scenarios that include more people, more departments, and generally higher price points. And this buying group can be made up of 7 to 20 people! Unlocking the power of buying groups is a crucial aspect of the B2B landscape. This blog is a synopsis of our conversation with revenue operations leader, Nandini Karkare. She is currently the SVP of RevOps at Zywave. Nandini suggests strategic steps to navigate through the realms of Revenue Operations and helps uncover the strategies, insights, and best practices that constitute a comprehensive guide to mastering the dynamics of buying groups. Read on to get actionable tips on how you can navigate buying groups in 2025 (and beyond). And implement the learnings to create a winning GTM motion. Here are the 5 steps Nandini recommends: 1. Decode Your Buying Groups The buying groups typically consist of members from departments and they all contribute different aspects. It is critical to understand the scope of decision-making including the people who play the most significant roles in making the call. Gartner’s report on B2B Buying highlights that 77% of B2B purchases involve a buying group of four or more people. PS: The key stakeholder can turn out someone altogether different from who you had building a relationship with all along. a. Capturing Buying Group Members   Effective buying group management means considering not just decision-makers but influential stakeholders across departments. Misidentifying key players or focusing solely on the main contact risks derailing the sale. (i) How can you map the entire buying group efficiently? Leverage internal and external data to identify the key players Segment the Group by Role and Influence (ii) Not everyone in the buying group holds equal power or influence. Segment them into categories: Decision-makers (who give the final heads-up) Influencers (who sway the decision) Users (who use the product and provide feedback) Budget owners b. The Role Transition Within a Buying Group   Moving the focus from a buying group to a renewal or expansion committee includes knowing precisely who remains in the relationship, as well as who becomes more active as an account grows. (i) New roles may emerge in a Buying Group Technical or operational leaders may become more influential post sale, since they are now using the product. (ii) The focus shifts from buying to renewal The interaction should be more about the return on investment (ROI) of the product placed on the market, ongoing value delivery, and ongoing needs. (iii) Alignment between the buying groups and renewal committee Leveraging the same enthusiasm and relationships generated at the first-buying stage helps in anchoring the transitions and preventing any drop-offs in engagement. Related Resource: Navigate Enterprise Buying Committees: Strategies for Driving Alignment c. Understand the Personal and Collective Priorities of a Buying Group As per McKinsey & Company, B2B buying decisions increasingly require engagement across departments, with 60% of purchasing committees including members from outside traditional procurement, like IT and HR. (i)Alignment Between C-Suite and Technical Teams Decisions aren’t Made in a Vacuum Collaboration between C-suite and technical teams ensures a holistic approach to solving customer problems, creating stronger, more sustainable relationships Their cross departmental collaboration can help with: (ii) Alignment on Strategic Goals C suite executives need technical assistance to translate their strategic vision to reality that also aligns with company-wide objectives. (iii) Technical Validation These insights guide the C-suite in making informed decisions that fit technical infrastructure and future-proofing. (iv) Cross-functional Communication Bridging the gap between these two groups involves continuous, open communication, ensuring that technical evaluations don’t delay business goals but instead support them cohesively.   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

Scroll to Top

Just one more step