Senior Product Manager, Clio

• 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."
• You 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
• Experience building or owning platform/infrastructure capabilities that other product teams build on top of, alongside more customer-facing PLG work
• 6+ years of product management experience in B2B SaaS, with meaningful time in a platform, growth infrastructure, or systems-level role
• Hands-on experience defining shared metrics across more than one team or product line, and instrumentation to track them consistently
• Demonstrated ability to work across multiple product teams without direct authority over their roadmaps
• Strong written communication: a clear platform strategy doc and a concise cross-team update, without a lot of back-and-forth

Desirable

• We are currently seeking a Senior Product Manager, PLG to join our Product Led Growth team
• 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
• 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. If they're blocked on platform capability, that's your backlog
• Instrumentation and Signal
• Turn Clio's own usage data, not just industry benchmarks, into platform priorities. (As one example: internal trial data shows that a customer taking output out of the product predicts conversion far better than any cap-hit metric. The platform should be built to surface signals like that, not just cap thresholds.)
• Build the visibility that lets Product, Data Science, and RevOps see cap-hit, first-value, and conversion data in one place, across both motions
• Cross-Team Coordination
• Partner with CBS on everything that touches billing, licensing, or the account-state model, including the parts that don't feel like "growth" work but block growth work downstream
• Work with RevOps and Sales on how product-qualified signal actually routes to a BDR or AE, and close the gaps where that handoff is manual or undefined
• Translate ambiguous, multi-team priorities, including the post-launch Agentic PLG roadmap, into a platform roadmap other PMs can plan against with confidence