product-analyst
Track user metrics and provide data-driven insights for product decisions. Use when measuring product health, analyzing user behavior, conducting cohort analysis, or optimizing key metrics. Covers acquisition, engagement, retention, revenue metrics, and data-driven decision making.
What this skill does
# Product Analyst
Measure user behavior and product health to inform data-driven decisions.
## Core Principle
**What gets measured gets improved.** Define the right metrics, track them relentlessly, and act on insights quickly.
## North Star Metric
**The ONE metric that best captures value delivered to users.**
Your North Star should:
- ✅ Represent real customer value
- ✅ Correlate with revenue
- ✅ Be measurable frequently (daily/weekly)
- ✅ Rally the entire team around one goal
**Examples by Product Type**:
```yaml
Communication:
Slack: Messages Sent (weekly active)
Zoom: Weekly Meeting Minutes
Discord: Active Servers
Marketplace:
Airbnb: Nights Booked
Uber: Completed Rides
Etsy: Gross Merchandise Value (GMV)
Media/Content:
Spotify: Time Listening
Netflix: Hours Watched
Medium: Total Time Reading
SaaS/B2B:
Asana: Weekly Active Teams
Notion: Collaborative Documents
Salesforce: Deals Closed (CRM value)
Social:
Facebook: Daily Active Users (DAU)
Instagram: Posts Shared
Twitter: Tweets per User
```
**How to choose your North Star**:
1. What action represents core value?
2. If users do this more, do they get more value?
3. Does this predict revenue?
4. Can the entire team influence it?
## Key Metrics by Category
### Acquisition Metrics
**Goal**: Get users into the product
```yaml
Traffic Sources:
- Organic Search: SEO traffic
- Paid Ads: Google Ads, Facebook Ads
- Referral: Word of mouth, links
- Direct: Typed URL, bookmarked
- Social: Twitter, LinkedIn posts
Key Metrics:
- Unique Visitors: Total website visitors
- Sign-ups: Users who created account
- Conversion Rate: Visitors → Sign-ups
- Cost Per Acquisition (CPA): Ad spend / sign-ups
- Source Quality: Which sources convert best?
Targets:
- Visitor → Sign-up: 2-5% (good), 5-10% (excellent)
- CPA: < $50 (B2C), < $200 (B2B), depends on LTV
```
### Activation Metrics
**Goal**: Get users to "aha moment"
```yaml
Activation Definition:
- User completes onboarding
- User takes first core action
- User experiences product value
Examples:
Slack: Sent 2,000 messages (team is active)
Dropbox: Added file to folder
Twitter: Followed 30 accounts
Airbnb: Completed first booking
Key Metrics:
- Activation Rate: Sign-ups → Activated
- Time to Activation: How long to aha moment?
- Onboarding Completion: % who finish setup
Targets:
- Activation Rate: >40% (good), >60% (excellent)
- Time to Activation: <24 hours (ideal)
```
### Engagement Metrics
**Goal**: Keep users coming back
```yaml
Key Metrics:
- Daily Active Users (DAU)
- Weekly Active Users (WAU)
- Monthly Active Users (MAU)
- DAU/MAU Ratio (Stickiness): How often users return
- Session Frequency: Times per week user logs in
- Session Duration: Time spent per visit
- Feature Adoption: % using each feature
DAU/MAU Stickiness:
Excellent: >40% (Facebook, Slack)
Good: 20-40% (most SaaS)
Needs Work: <20%
Session Frequency Targets:
B2C Social: 5-7 times per week
B2B Tools: 3-5 times per week
E-commerce: 1-2 times per week
```
### Retention Metrics
**Goal**: Prevent churn
```yaml
Cohort Retention:
- Day 1: % still active 1 day after sign-up
- Day 7: % still active 7 days after
- Day 30: % still active 30 days after
Good Retention Curves:
Consumer B2C:
- D1: 60-80%
- D7: 40-60%
- D30: 30-50%
- Flattening curve (good!)
Enterprise B2B:
- D1: 80-90%
- D7: 70-80%
- D30: 60-70%
- Very flat curve
Bad Retention:
- D1: 40%
- D7: 10%
- D30: 2%
- Steep drop-off = product-market fit issue
Churn Rate:
- Monthly Churn: % users who stop using each month
- Target: <5% (consumer), <1% (enterprise)
- Churn = Revenue Leak
Net Retention:
- (Starting Users + New - Churned) / Starting Users
- Target: >100% (growth despite churn)
```
### Revenue Metrics
**Goal**: Monetize effectively
```yaml
Key Metrics:
- MRR (Monthly Recurring Revenue): Predictable monthly income
- ARR (Annual Recurring Revenue): MRR × 12
- ARPU (Average Revenue Per User): Revenue / # users
- LTV (Lifetime Value): Total revenue from user over lifetime
- CAC (Customer Acquisition Cost): Sales + marketing / new customers
- LTV:CAC Ratio: Must be > 3:1
- Payback Period: Months to recover CAC
Calculations:
LTV = ARPU × Average Lifetime (months)
Average Lifetime = 1 / Churn Rate
Example:
ARPU: $50/month
Churn: 5% per month
Average Lifetime: 1 / 0.05 = 20 months
LTV: $50 × 20 = $1,000
CAC: $300
LTV:CAC = $1,000 / $300 = 3.3:1 (Good!)
Targets:
- LTV:CAC: >3:1 (minimum), >4:1 (healthy)
- Payback Period: <12 months
- MRR Growth: >10% month-over-month (early stage)
```
### Satisfaction Metrics
**Goal**: Keep customers happy
```yaml
NPS (Net Promoter Score):
Question: "How likely are you to recommend us?" (0-10)
- Promoters: 9-10
- Passives: 7-8
- Detractors: 0-6
NPS = % Promoters - % Detractors
Benchmarks:
Excellent: >50
Good: 30-50
Needs Work: <30
CSAT (Customer Satisfaction):
Question: "How satisfied are you?" (1-5)
Target: >4.0 average
CES (Customer Effort Score):
Question: "How easy was it to [task]?" (1-7)
Target: <3.0 (low effort)
```
## Segmentation
**Don't treat all users the same.** Different cohorts behave differently.
```yaml
Segment by Engagement:
Power Users (Top 10%):
- Use daily
- High engagement
- Understand product deeply
→ Interview them for feature ideas
Casual Users (Middle 60%):
- Use occasionally
- Basic feature adoption
→ What prevents them from power usage?
At-Risk Users (Bottom 20%):
- Haven't logged in 7+ days
- Low engagement
→ Re-engagement campaign
Churned Users:
- No activity 30+ days
→ Exit survey, understand why
Segment by Acquisition Source:
- Organic vs Paid
- Which source has best retention?
- Which source has best LTV?
Segment by Plan:
- Free vs Paid
- Starter vs Pro vs Enterprise
- Which tier has best retention?
Segment by Cohort (Sign-up Date):
- Week 1 users vs Week 2 users
- Did product changes improve metrics?
```
## Funnel Analysis
**Track conversion at each stage:**
```yaml
Sign-up Funnel Example:
1. Land on homepage: 10,000 users (100%)
2. Click "Sign Up": 2,000 users (20%)
3. Fill sign-up form: 1,200 users (12%)
4. Verify email: 800 users (8%)
5. Complete onboarding: 400 users (4%)
Analysis:
Biggest drop-off: Homepage → Sign Up (80% lost)
Fix: Clarify value prop, add social proof, improve CTA
Second drop-off: Form → Email verify (33% lost)
Fix: Simplify form, reduce friction
Optimize biggest drop-offs first for max impact.
```
## Cohort Analysis
**Compare user groups over time:**
```yaml
Example: Retention by Sign-up Week
Week 1 Cohort (Jan 1-7):
100 users signed up
- D1: 80 active (80%)
- D7: 40 active (40%)
- D30: 20 active (20%)
Week 2 Cohort (Jan 8-14):
120 users signed up
- D1: 102 active (85%) ← +5% improvement!
- D7: 60 active (50%) ← +10% improvement!
- D30: 36 active (30%) ← +10% improvement!
Insight: Onboarding changes in Week 2 improved retention!
Action: Roll out Week 2 changes to all users.
```
## A/B Testing
**Test hypotheses systematically:**
```yaml
1. Form Hypothesis: 'Adding social proof to homepage will increase sign-ups by 10%'
2. Design Experiment:
- Control: Current homepage
- Treatment: Homepage + customer testimonials
- Split: 50/50 traffic
- Primary Metric: Sign-up rate
- Duration: 2 weeks or 1,000 visitors per variant
3. Run Test:
- Don't peek early (wait for significance)
- Monitor for bugs/issues
4. Analyze Results:
Control: 1,000 visitors → 20 sign-ups (2.0%)
Treatment: 1,000 visitors → 25 sign-ups (2.5%)
Lift: +25% relative
P-value: 0.04 (significant at p<0.05)
Decision: WIN - Ship it!
5. Document Learning: 'Social proof increases sign-ups by 25%. Apply to all hRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.