GROWTH WITH ALEX
PLGPublished November 18, 2026·10 min read

PLG Activation Guide: 16 Nudges That Move Users to Value, and How to Define a PQL

How to define activation, build the 16 in-product nudges that move new users to their first win, score product-qualified leads (PQLs) with a simple point model, and automate alerts and handoffs — with rollout order, metrics and common mistakes.

By Alexandre Contador, Fractional CGO & GTM Advisor

Person holding a smartphone showing an app
Photo by Terrillo Walls on Unsplash

Product-led growth lives or dies in the gap between signup and first real value. Acquisition can fill the top of the funnel indefinitely; if users don't reach their first win, they leave, and no amount of traffic fixes that.

This guide gives you a practical system: how to define activation, 16 in-product and lifecycle nudges to move users toward it (with when to show each, what to say and how to measure it), how to define and score product-qualified leads (PQLs) and how to automate the handoff to sales. It builds on the free "16 PLG Nudges" checklist and the PLG Workflows and Automations download.

Why activation is the lever

Buyers increasingly want to evaluate on their own. Gartner's June 2025 survey reported that 61% of B2B buyers prefer a rep-free buying experience, and later coverage of a follow-up survey put the figure higher. For products that can be tried, the first session is the sales call.

That makes activation the highest-leverage metric in a PLG business: it determines whether acquisition spend turns into retained users, and it is the foundation for everything downstream — conversion, expansion and referral.

Person holding a smartphone with an app open
The first session is the sales call: every screen should move the user toward one real result. · Photo by Terrillo Walls on Unsplash

Step 1: Define your activation event

Before adding any nudge:

  1. Write the activation event in one line. It's the action that predicts a user will stick. Example: "created a project and invited one teammate in the first 7 days".
  2. Track it as an event in your product analytics.
  3. Validate it with data. Query signups from the last 90 days, flag who hit the action within 7 days, then compare day-30 retention between those who did and didn't. Report the action with the strongest lift and the median time to reach it.
  4. Pick the metric for each nudge before you ship it.

A prompt to run the diagnosis with Claude Code and your product database:

Query signups from the last 90 days. For each, flag whether they hit [action] within 7 days. Compare retention at day 30 between those who did and didn't. Report the action with the strongest lift and the median time to reach it.

If you're not sure your activation definition is right, test two or three candidates. The best one is usually a value action ("connected real data"), not an easy-to-track setup action ("created an account"). The ultimate guide to PLG covers common ways teams pick the wrong moment.

The 16 nudges

The nudges cluster into four groups. Within each, the format is when → what → how to measure.

Group 1: Setup nudges (get the user started)

#NudgeWhenWhatMeasure
01Checklist → setupFirst session, after signup3–5 steps ending in the activation event, with 1–2 already ticked% of new users completing the list in 7 days
02Empty state → first winAny page with no data yetOne sentence on what the page does plus one button to create the first thingFirst-object-created rate
03Tooltip → next stepRight after a user finishes a stepPoint at the single next action, nothing elseClick-through vs. users who never saw it
04Progress → finishSetup is half done and the user goes quietA percentage bar and "2 steps to your first [result]"Setup completion rate
07Template → quick startCreating something newThree templates for the most common jobsTime to first object, template vs. blank
08Sample data → ahaBefore real data is connectedA working dashboard with clearly labelled sample data% who connect real data after seeing the sample

Group 2: Momentum nudges (get a second step and a second user)

#NudgeWhenWhatMeasure
06Invite → teamAfter the first win, not before"Work is faster with your team" plus invite by email or link% of accounts with 2+ active users
11Success moment → shareRight after the first real resultCelebrate it, then offer to share with the teamShares and invites from that screen
13Re-engagement email → come back2–3 days of no activity during onboarding"You're 2 steps away" plus a deep link to the exact stepReturn rate within 48 hours of the email
14In-app survey → insightRight after setup is doneOne question ("How easy was setup?"), scored 1–5Response rate and low scores you follow up

Group 3: Money nudges (turn value into revenue)

#NudgeWhenWhatMeasure
05Usage meter → upgradeA user passes 80% of a plan limitShow the meter and the plan that removes the limitUpgrade rate from users who saw the meter
09Trial countdown → decide3 days and 1 day before trial endsDays left plus what they keep if they pick a planTrial-to-paid rate
12Locked feature → previewA free user opens a paid featureA blurred preview of the result and "Preview Pro"Upgrade starts from the locked screen
16Seat limit → expandA team hits its seat limit"5 of 5 seats used" plus add a seat in one clickSeat expansion revenue

Group 4: Habit nudges (build the routine)

#NudgeWhenWhatMeasure
10Feature spotlight → discoverOnce the core habit existsOne new feature, one sentence, one buttonAdoption of that feature within 14 days
15Streak → habitThe product has a natural daily or weekly rhythmA streak counter and a reason to return tomorrowWeek-2 and week-4 retention

Rules that apply to every nudge

  • One idea per nudge. Point at the single next action.
  • Timing beats copy. A mediocre message at the right moment beats a clever one at the wrong time.
  • Off switch always. Dismiss once, never show again.
  • Respect the first session. Don't ask for team invites before the user has had a win.
  • Measure against users who didn't see it, not against last month.

The rollout order

Ship in this sequence; resist the urge to batch.

WindowNudgesWhy
Weeks 1–201 Checklist + 02 Empty statesThey lift activation for almost every product
Weeks 3–403 Tooltips + 13 Re-engagement emailCatch users who stall
Month 205 Usage meter, 09 Trial countdown, 12 Locked preview, 16 Seat limitThe money nudges, once activation is healthy
Month 311 Success moment, 15 Streak, 10 SpotlightHabit and discovery

Keep a log of what you shipped and what moved. Tie it into your 90-day GTM sprint experiment backlog. For the tools to run it, see the $0 → $1M ARR tech stack: PostHog for events, Customer.io for behaviour-based email, Userflow for in-app checklists and GrowthBook for experiments.

Step 2: Define and score PQLs

A PQL (product-qualified lead) is a user whose behaviour signals they're likely to pay. It's the bridge between self-serve and sales: instead of "this person downloaded a PDF", you know "this team invited five colleagues and hit their usage limit".

A starter point model

SignalPoints
Hit activation3
Invited 2+ teammates3
Used a paid feature during trial3
Hit a usage limit4
Visited pricing 2+ times2
Company size in your ICP2
Business email domain1
Example PQL scoring weights (threshold: 8+ points = PQL)
Hit usage limit4 pts
Hit activation3 pts
Invited 2+ teammates3 pts
Used a paid feature in trial3 pts
Visited pricing 2+ times2 pts
Company size in ICP2 pts
Business email domain1 pts

Source: Growth with Alex — PLG Workflows and Automations (starter weights; tune to your data)

PQL = 8+ points to start. These weights are a starting hypothesis, not a law: tune them against real conversions.

Calibrate with your own data

Export users with a flag for who converted and ask Claude to fit a simple model:

Using this export of users and who converted, fit a simple scoring model. Show which behaviours predict conversion. Suggest thresholds for PQL and a ranked list of current free users above the threshold.

Then check, at least quarterly:

  • Which attributes actually correlate with becoming an opportunity?
  • Is the PQL-to-paid rate high enough to justify a salesperson's time?
  • Are some signals (for example, a single pricing visit) creating false positives?

Don't score too early

Add a time filter: require a minimum number of days since activation (for example seven) before PQL scoring switches on. First-week excitement looks like PQL behaviour but usually isn't — users poke around, then drift.

Account-level vs. user-level PQLs

For team products, score the account as well as the user: a single power user at a 3-person company may matter less than five moderate users at a 200-person target. Use firmographic fit (ICP) as a multiplier, not just a few points.

Step 3: Automate the conversion workflows

Four workflows turn signals into revenue without a human watching dashboards:

Workflow A — Activation nudges (email + in-app)

  • Signed up, hasn't done [action] after 24h → email with a one-step guide.
  • Did action 1 but not action 2 → in-app tooltip.
  • Stuck for 3 days → offer a short call or a template.

Workflow B — PQL alert

  • Trigger: user crosses 8 points.
  • Actions: create a CRM task, send a Slack alert and enrich the account.
  • Message: a personal note referencing what they did, not a generic upsell.

Workflow C — Upgrade prompts

  • In-product when a limit is hit.
  • By email when a paid feature is tried.
  • Trial-ending sequence at days 7, 12 and 14 with a value recap.

Workflow D — Checkout friction audit

Walk the path from pricing to payment in a browser (with Claude if you like), list every click and field, then remove half.

A typical tool chain: product analytics → automation tool → CRM property update (PQL score and top signals) → enrichment → Slack alert to the assigned rep with the username, company, score and recent actions. For agent-driven versions of these automations and the guardrails they need, see agentic GTM workflows.

Metrics that matter

MetricWhy it matters
Activation rateQuality of entry into the product
Time to first valueSpeed of onboarding
Free-to-paid conversionFunnel health
PQL-to-paidAccuracy of your scoring model
Net revenue retentionExpansion success (see expansion guide)
Logo and revenue churnOverall health

Model your growth impact with the free SaaS growth rate calculator, and watch the metrics founders should track.

Diagnosing a stalled activation funnel

If nudges aren't moving activation, work through these in order:

  1. Wrong activation event. Compare retention for candidate actions; pick the strongest predictor.
  2. Wrong users. If positioning attracts the wrong signups, activation falls regardless of UX. Revisit your ICP.
  3. Too much setup before value. Offer sample data, templates and shorter signup.
  4. Nudges at the wrong time. Check the event sequence; show the invite prompt after the first win.
  5. No instrumentation. If you can't see step-by-step drop-off, fix tracking before redesigning.

Common mistakes

  • Shipping five nudges at once, then not knowing which worked.
  • Nudging before a win, especially asking for invites too early.
  • No off switch, which trains users to ignore everything.
  • Scoring on vanity events like page views.
  • Handing sales every PQL without a threshold review, which burns trust.
  • Ignoring qualitative signals. Watch session recordings and read support chats for why users stall.

Next steps

Frequently asked questions

Activation is the first moment a new user gets real value from your product — the action that best predicts they will stick. A typical example is "created a project and invited a teammate within 7 days". Define it from retention data, not intuition, and track it as an event.

A product-qualified lead is a user or account whose product behaviour signals they are likely to pay — for example activating, inviting teammates, using a paid feature in trial, hitting a usage limit or visiting pricing repeatedly. PQLs let sales and success reach out with context instead of a generic pitch.

One at a time. Pick one nudge, measure it for two weeks, then add the next. Shipping many at once makes it impossible to know which one moved activation, and risks overwhelming new users.

They can if they interrupt or repeat. Every nudge needs an off switch (dismiss once, never show again), should appear at a relevant moment, and should point at the single next action rather than a tour of features.

It depends on your product, audience and definition, so compare against your own baseline rather than a generic benchmark. The aim is to improve the share of new users who reach your activation event, and to shorten the time it takes.

Want a second opinion on your GTM?

30 minutes, no pitch — just a direct conversation.

Book a Strategy Call