Guide

GTM choice shows up in the roadmap. "Done" means different surfaces depending on whether a user can get value alone or a committee must buy.

If you are PLG-first, prioritize: signup and activation friction, empty states and templates, team invite, self-serve billing, and instrumentation for funnels and PQLs.

If you are sales-led or moving upmarket, prioritize: roles, SSO/SAML, SCIM, audit logs, SOC 2 and DPA artifacts, sandboxes for SEs, quote-to-cash, and SLAs that survive procurement.

Hybrids need both — and a clear entitlement story so self-serve users are not blocked from the aha while enterprise buyers get the controls they require. Gating SSO behind enterprise is normal; gating the core canvas behind a demo call is usually a GTM smell for a PLG product.

Case sketches

CompanyMotion patternWhy it fits
SlackPLG → enterprise salesBottom-up teams; high willingness to expand; IT eventually needs controls
FigmaStrong PLG + upmarket salesMultiplayer design; file sharing is distribution; orgs consolidate seats
DatadogProduct-led adoption by engineers + sales for large accountsDevelopers feel value in hours; enterprise needs contracts and scale
SnowflakePrimarily sales-led / sales-assistedHigh ACV, data gravity, security and architecture conversations

None of these are "pure." The useful question is where demand originates and where humans add leverage.

Metrics by motion

MotionMetrics that matterVanity traps
PLGActivation rate, free-to-paid, self-serve revenue, invites, time-to-valueRaw signups, demo requests
Sales-ledWin rate, cycle length, ACV, pipeline coverageWebsite traffic alone
HybridPQL volume/quality, PQL→close, self-serve vs sales mix, NRRCounting all signups as sales leads

Tie engineering OKRs to the row you are actually in. A "ship growth" quarter that only moves signups in a sales-led enterprise product is theater.

As an engineer: PLG means checkout and onboarding are the critical launch surface. Sales-led means demo stability, admin tooling and audit logs unblock revenue as much as the flashy feature. Hybrid means build PQL events with the same care as payment webhooks, and expose usage context in the CRM so humans do not call blind.

Common mistakes

  • SSO before activation is solved — runway burns. Ignore audit logs when five Fortune 500 trials are blocked — also malpractice. Sequence with actual deal blockers.
  • OKRs on the wrong row. Signups in a sales-led motion; demo requests in a PLG motion.
  • Gating the aha behind a call in a product that was supposed to be self-serve.

Check yourself

Should this product be PLG? Answer with ACV, buyer complexity, time-to-value, and whether usage creates distribution — then propose a hybrid if the answer is "both over time."

Sales-led enterprise product. Is "more signups" a good quarterly OKR? No. Win rate, cycle length, ACV and pipeline coverage match the motion. Signups are vanity here.

Key takeaways

  • Roadmaps must match motion: activation and billing for PLG; SSO, audit and SE tooling for enterprise.
  • Hybrids need entitlements that keep the aha free and put controls on the paid/enterprise rungs.
  • Measure the row you are in. Copying another company's GTM without looking at ACV and time-to-value is a common failure.

Further learning

Lenny's NewsletterDeeply researched product, growth, and career advice for product leaders, founders, and ambitious builders. Click to read Lenny's Newsletter, a Substack publication with millions of subscribers.lennysnewsletter.com

Next: GTM failure modes.