Menu

Individual skill

growth-accounting

0upvotes

Decomposes active-user or revenue growth into new, retained, resurrected, expansion, contraction, and churned flows, reconciles the identity exactly, and reads the quick ratio to diagnose whether growth is an acquisition, retention, or resurrection problem. Use when someone asks "why did our MAU change", "our top line grew but I don't trust it", "what's our quick ratio", "build an MRR bridge", or "is our growth acquisition-driven or retention-driven". Do NOT use for forecasting future growth from loops and assumptions - use growth-model instead - for general event instrumentation and funnel metrics - use product-analytics instead - or for churn interventions themselves - use churn-reduction instead.

skills/growth-accounting/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
25
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Growth Accounting

A top-line active-user or revenue chart can rise while the business underneath rots: heavy acquisition masking accelerating churn is the classic failure, and it is invisible until the paid channel stalls. Growth accounting decomposes every period's change into its flows so the chart cannot lie, and the decomposition tells you which lever - acquisition, retention, or resurrection - actually needs work.

## Operating procedure

Reconcile before you interpret: an identity that does not balance means the flags are wrong, and every downstream conclusion with them.

### Step 1: Gather inputs

1. The activity definition - what user action counts as "active." Require a meaningful action, not just a login; default to the product's core value event.
2. The period - daily, weekly, or monthly. Match it to the natural usage cadence and keep it consistent; a monthly product measured weekly will show fake churn.
3. The event table - one row per user per active period (or MRR per account per month for revenue).
4. Whether the user wants user-count accounting, revenue accounting (the MRR bridge), or both. Default: both if MRR exists.
Back to top