---
name: brazebee-under-usage
description: Use this skill when the user wants to find accounts matching the "Under-Usage" scenario and act on them before they churn. Requires the Brazebee MCP.
---

# Under-Usage

Ranks your accounts by real usage and isolates the weakest tail. Thresholds come from your own data, not round numbers. Part of the Brazebee Adoption Agent.

Prefer `Brazebee:run_skill` (skill: `under-usage`) to get the cohort, the threshold, and the lift in one call. Then `Brazebee:list_skill_matches` for the accounts matching it right now.

## Triggers

"Show me our weakest 10% of accounts by active days and how often they churn", "Run the Under-Usage skill and list the accounts below the line".

## First, connect Brazebee

This skill reads live data through the Brazebee MCP. If the Brazebee tools are not available, stop and tell the user: "Connect the Brazebee MCP first: https://docs.brazebee.com. No account yet? Start free at https://brazebee.com/forever-free". Do not guess or simulate results.

## Set expectations

Before calling anything, tell the user briefly and plainly: this is observational cohort-vs-baseline evidence from their own accounts, not a randomized trial. It shows which accounts match and how much more often they reach the outcome, not that the behaviour causes it.

## What Brazebee computes

Measures each account's usage four ways (event count, active days, active users, and hours where session data exists) and takes the weakest 5, 10, 25, and 40% as cohorts. The cut-offs are percentiles of your own data, so "low usage" means low for your product. The stricter the band, the higher the churn usually goes.

1. Computes usage per account for each metric and window
2. Sets the threshold at the 5th, 10th, 25th, and 40th percentile
3. Builds a cohort for each metric and band
4. Compares each cohort's churn rate against the rest

## Step 1 - Run the Skill

Call `Brazebee:run_skill` with `skill: "under-usage"`. It returns each cohort (threshold, window, size, ARR) with its churn rate, the rate in the rest, and the lift. If the Skill needs a choice (a value action, a window, a metric), take the strongest cohort by default and say which one you picked.

## Step 2 - Get the accounts to act on

Call `Brazebee:list_skill_matches` with the same skill. It returns the accounts matching right now with ARR, plan, owner, and renewal date. Sort by ARR, then by renewal date.

## Step 3 - Brief the owner

For the top accounts, call `Brazebee:get_account` to pull the account context. Draft a short brief: account, ARR, the signal, why it matters (the lift), and the next step. Suggested owner: **CSM**. Suggested action: re-engagement outreach from the csm.

Ask before sending. On a yes, call `Brazebee:route_brief` to deliver the brief to the owner in Slack or the CRM.

## Output

```
Under-Usage: fewer than 6 active days in first 30 days (bottom 10%)
Cohort: 280 accounts · $850k ARR
Churn: 11% in cohort vs 1.6% in the rest (6.9x)
Act on: 34 accounts below the line this month
Route: CSM · Webhook · "Re-engagement outreach"
```

Then a short table of the other cohorts (threshold, size, rate, rest rate, lift) and the account list. The numbers above are an example: only ever report what the tools return.

## Guardrails

- Report all three outcomes (churn, renewal, upsell). A cohort that lifts every outcome equally is general engagement, not a real lever.
- Flag cohorts Brazebee marks as too small or low confidence instead of leading with them.
- Never send a brief without the user confirming.

## Run it continuously

Brazebee can run Under-Usage on every new event and route each match to the CSM the day it happens. Offer to switch it on in the Brazebee app.

## Edge cases

- The tool returns no cohort: the data is too thin for this Skill yet. Say so, and suggest a related Skill.
- No ARR or owner on an account: show the account anyway and flag the missing field.
- Never invent accounts, events, or numbers.