Senior Product Manager, PLG

1 week ago

Edmonton AB, Edmonton Census Division, AB; Alberta, Canada Themis Solutions Inc. Full-time €137,500 - €186,100

Clio is the global leader in legal AI technology, empowering legal professionals and law firms of every size to work smarter, faster, and more securely. We are transforming the legal experience for all by bettering the lives of legal professionals while increasing access to justice.

Summary: We are currently seeking a Senior Product Manager, PLG to join our Product Led Growth team.

This role is open to remote applicants across the U.S. and Canada, with the exception of Quebec.

We are a remote-first team with hub offices in Burnaby, Calgary, and Toronto. If you are local to one of those hubs you will be expected in office a minimum of two days per week on our Anchor Days.

What your team does:

Clio's PLG team runs two live growth motions at once: helping existing customers discover and adopt more of Clio through Clio Explorer and the unified nav, and bringing net-new prospects into Clio through a self‑serve Freemium tier of Clio Work. Both motions increasingly depend on the same underlying machinery, account and license infrastructure, usage caps and trial systems, PQL signal routing, and the CBS platform that powers all of it.

This role owns that shared foundation. You will build the PLG platform that lets our Monetization PM and our Onboarding & Activation PM move fast and experiment freely, instead of each rebuilding the same account‑state logic, cap‑tuning system, or signal pipeline from scratch. This is not a role that competes with theirs for territory. It is the layer underneath both of them.

Who you are:

  • You think in systems, not features
  • You have owned a platform or infrastructure layer before, not just a customer‑facing feature, and can describe a specific bottleneck you found (a manual process, an inconsistent data model, an undefined handoff) and what you built to remove it.
  • You instinctively ask "what capability, once built, lets five other teams move faster" rather than "what should we ship this quarter."
  • Instrument before you optimize; you have defined metrics from scratch across more than one team's motion, and made them consistent, rather than inheriting a dashboard someone else built for a single product.
  • You are comfortable with cohort analysis and funnel metrics, and you know the difference between a metric that's actually causal and one that just moves together with the outcome you care about.
  • Basic SQL proficiency is expected, not aspirational.
  • You can work across teams without owning their roadmaps. This role spans Monetization, Onboarding/Activation, CBS, Engineering, and RevOps. You will not control any of their roadmaps. Getting shared infrastructure built and adopted requires influence, not authority. You can give a specific example of shipping a cross‑team outcome without direct control over the teams involved.
  • You’ve built for internal teams before, not just external customers. Sales, BDR pods, and CS ops teams are among your users here, the same rigor you'd apply to a customer‑facing surface applies to their tooling. You understand that a fix to a manual back‑office process (an account merge, a signal handoff) is often worth more than a customer‑facing feature.
  • You ship things. Consistent track record of shipping end‑to‑end in B2B SaaS: spec, build, launch, measure, iterate.
  • You do not wait for perfect data or a fully settled number. You are comfortable setting a threshold before evidence exists and revising it once it does.

What you'll work on:

The PLG Core Foundation

  • Own the account and license model, trial and freemium infrastructure, and usage‑cap tuning systems that power both PLG motions.
  • Partner with CBS on the billing and account architecture, license mobility, request‑access flows, account merge and reconciliation, that both motions run on top of, and that currently bottlenecks at scale.
  • Build a single, consistent measurement layer (activation rate, cap‑hit rate, conversion rate, cost‑to‑serve) so Monetization and Onboarding/Activation are working from the same numbers, defined the same way, regardless of which motion generated them.

Enabling the Motion‑Level PMs

  • Build the trial‑unlock surfaces, contextual upsell infrastructure, and PQL/signal‑routing systems that the Monetization PM and Onboarding & Activation PM build their initiatives on top of. Treat their roadmap needs as your primary input.