posthog-features-drive-revenue

name

posthog-features-drive-revenue

description

Rank a PostHog user's product features by the revenue of the customers who use them (joins Stripe MRR/invoices to feature-usage events) and save it as a reusable PostHog insight. Use this whenever someone asks which features their highest-revenue or best customers use most, wants revenue-weighted feature adoption, wants to tie existing feature usage to MRR/ARR, or wants to decide which features to invest in based on paying customers. Triggers on phrasings like 'which features drive revenue', 'what do our best customers use', 'revenue by feature', 'connect Stripe revenue to feature usage', or 'which features should we double down on'. Boundary: this ranks EXISTING features by adopter revenue, it is not a before/after test. For whether a specific rollout, experiment, or feature flag moved revenue use posthog-feature-revenue-impact; for revenue by acquisition channel or ad spend use posthog-acquisition-channels-retention. It sets up the Stripe warehouse source if needed and builds the insight end-to-end.

Which features drive revenue?

Question: Which product features do our highest-revenue customers use most? For: Product & PMM · Difficulty: Beginner · Shape: one SQL/HogQL query Data sources: PostHog events (feature usage per account) + Stripe (MRR & invoices per customer)

What this produces

A saved PostHog insight — a table of features ranked by the revenue of the accounts that use them — so the user can see which features their paying customers actually rely on, and spot high-revenue accounts that haven't adopted a top feature yet.

Workflow

First read references/posthog-workflow.md and follow it for the shared setup: confirm the PostHog MCP is connected, make sure the Stripe source exists (set it up via the secure connect-link flow if not), and learn this project's real schema. Everything below is the question-specific part.

1. Identify the pieces in this project

• Feature usage events. Use to find the events that represent meaningful feature use (not pageviews). Confirm with the user which events count as "features" — every product defines this differently.