signals-scout-customer-analytics-billing-and-usage

Detects per-account product usage and MRR shifts masked by flat account totals.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-customer-analytics-billing-and-usage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signals-scout-customer-analytics-billing-and-usage
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-customer-analytics-billing-and-usage
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-customer-analytics-billing-and-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Account-level monitoring only sees aggregate engagement, so it misses when one product inside an account quietly drops or spikes while the account total stays flat. This Skill finds those masked per-product moves in billing and usage data so account managers can act before churn or surprise invoices.

Core Features & Use Cases

  • Masked divergence scoring: Compares each staked account's per-product weekly usage against a same-weekday trailing 4-week baseline, flagging moves over 30% while the account total holds.
  • MRR-weighted severity: Weights every finding by the product's share of account MRR from invoice line items, suppressing drops on products under 5% of the bill.
  • Spike triage and context sweep: Distinguishes real adoption from instrumentation loops using daily billing series, then sweeps account notes, notebooks, and Slack summaries for planned explanations before filing.
  • Use Case: An account's feature flag usage drops 30% while replay growth keeps the total flat; the Skill confirms the move, finds no planned migration, and files a report routed to the active account manager.

Quick Start

Ask the Signals agent to run the product-mix scout and report any staked account where one product's usage or forecasted MRR moved over 30% while the account total stayed flat.

Frequently Asked Questions about signals-scout-customer-analytics-billing-and-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect product usage drops hidden by flat account totals?

Score each account's per-product weekly usage against a same-weekday trailing 4-week baseline and flag moves over 30% while other products hold within 10%. The flat account total is what makes the shift invisible to aggregate monitoring.

How does the scout distinguish real adoption from an instrumentation loop?

Real adoption ramps gradually across days and follows weekday rhythms, often lifting related products. An instrumentation loop is a step function that pins at a new level, runs flat through weekends, and moves one product alone.

What data sources does the billing and usage scout require?

It requires system.accounts joined to three billing materialized views keyed on organization_id: billing_usage_by_org_date, billing_invoice_line_items_by_org, and billing_invoices_by_org. Without a verified account-to-billing join it closes out empty.

When does the scout skip reporting a usage drop?

It skips drops on products under 5% of account MRR, moves matching seasonal patterns, accounts with no active manager or CRM link, shifts a human already touched in the last 7 days, and fleet-wide moves indicating a capture problem.

Who receives the reports the scout files?

Reports are routed to users holding an active account-manager relationship on the account, resolved via system.account_relationships joined to posthog_user. The account_owner property is never used since it names the customer's internal champion.