Read how an account actually uses you.
“This account says they love us, but is anyone actually using the product?”
Turns raw usage into per-capability adoption tiers, a 12-week trend on each, power-user IDs, and a ghost-active flag.
What this skill does
Reads how an account actually uses your product and gives a plain read: which capabilities they have adopted, whether each one is rising or fading, and who the power users are. It turns "how are they using us?" into a product-engagement score you can act on, and it flags the accounts that look active on the surface but create no real value underneath.
Inputs
- Works today with: a usage export by account, with a row per account and columns for each capability's activity count and a last-active date. Paste it or upload a CSV.
- More powerful connected to a product-analytics tool: it reads events automatically, at your chosen account grain, across the whole base.
- Sharper with a CRM: cross-references usage to the account record and its fit score.
- Sharper with a longer history: a full trend window instead of a single snapshot.
How it works
- 1Adoption tier per capability
Every capability gets exactly one tier: POWER, ESTABLISHED, EMERGING, DORMANT, UNTOUCHED, NEVER-ADOPTED. Power means heavy, recent, repeated use. Untouched means they had it and stopped. Never-adopted means they never started. The Untouched and Never-adopted rows are the onboarding gap, the consultative outreach list.
- 2Trend per capability
Over TREND_WINDOW weeks, each capability is RISING, FLAT, DECLINING, or COLLAPSED. A high tier with a declining trend is an early quiet-quitting signal, worth more than the raw count.
- 3Power-user identification
Surface the individual users whose activity clears POWER_THRESHOLD, with which capabilities each one leans on. These are your expansion anchors and your reference candidates.
- 4Ghost-active check
When an account looks alive on the baseline "any activity" signal but every real capability is zero, flag it. This is the classic blind spot: seats are technically active (someone logs in) but no value is being created. Must show the per-capability zeros that prove it.
- 5Fit-score cross-check
If you carry an account fit score, compare it to what usage actually shows. When the fit score sits at the floor but adoption is clearly real, call it a false negative and promote the account. When the score is high but usage is a ghost, flag the mismatch the other way. The usage is the ground truth.
Output format
PRODUCT ENGAGEMENT · acme.com · 12-week window
Capability Adoption Trend Last active
Core action Power Rising today
Automation Established Flat yesterday
Templates Emerging Rising 3d ago
AI assist Dormant Declining 18d ago
Advanced module Untouched - -
Integrations Never-adopt - -
_active baseline Power Rising today
NOT ghost-active: 4 of 6 capabilities show real activity
Fit-score check: score 28 looks low, but adoption is real -> false negative, promote
Weekly actives: 351 latest · 339 four-week avg (Rising)
New users (14d): 8 signups · 5 active within 7d · 3 still untouched
Story: Power on the core action with rising template use. The gap is the
advanced module and integrations. 3 new users have not activated yet, that is
the onboarding conversation.
Tips
- No GHOST-ACTIVE verdict without showing the per-capability zeros that prove it.
- Every "not adopted" surfaces capability by capability, named, never "low usage."
- Trend is over the full window, never a single week. Small samples lie.
- Never report a number the export does not contain. A missing column is a prompt, not a guess.
Get a structured account read straight from your CRM.
A sixty-second summary, a multi-source activity audit, a qualification-vs-stage gap check, and an 8-state deal-risk verdict.
Ship the analysis: the CRM update, the post, the email.
Takes a read's output and drafts what goes out, draft-first and fully logged, ready to paste or write directly when connected.