Hybrid PLG/SLG OKR patterns for product-sourced growth, handoff logic, and attribution framing. Use when designing PLG or hybrid-motion KRs, benchmarking PQL funnels, or deciding when product demand should stay self-serve versus become sales-assisted.
From opspal-okrsnpx claudepluginhub revpalsfdc/opspal-commercial --plugin opspal-okrsThis skill is limited to using the following tools:
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Designs, audits, and improves analytics tracking systems using Signal Quality Index for reliable, decision-ready data in marketing, product, and growth.
Enforces A/B test setup with gates for hypothesis locking, metrics definition, sample size calculation, assumptions checks, and execution readiness before implementation.
Use these as planning priors, not as substitutes for org baselines:
| Metric | Planning Reference |
|---|---|
| Visitor -> Signup | ~6% P50 |
| Free -> Paid | ~5% |
| Trial -> Paid | ~17% |
| Activation Rate | 20-40% |
| Expansion ARR | 40-50% of new ARR when model supports it |
Treat the funnel as a sequence with ownership transitions:
visitor -> signup -> activated -> PQL -> pipeline -> paid -> expansion
For each stage, name:
Escalate from self-serve to sales-assisted or sales-led when one or more of these become true:
Do not hand off based on vibe or logo size alone. The handoff must name the actual trigger.
Every opportunity or expansion event gets one primary source:
product_sourcedsales_assistedsales_sourcedTrack assists separately, but do not add assist value on top of sourced ARR totals.
X% to Y%X% to Y%X% to Y%X% to Y% of total pipelineX% to Y%40-50% of new ARR where the model supports it../../opspal-core/config/revops-kpi-definitions.json../../opspal-core/agents/product-analytics-bridge.mdskills/okr-methodology-framework/SKILL.md