Expansion Signal Prompts: Spotting Upsell Moments in Usage Data

Most upsell opportunities die quietly inside a spreadsheet nobody opens. Your customers generate usage data every single day — logins climbing, seats filling, API calls spiking, features being touched for the first time. Buried in that data are accounts ready to expand right now, and accounts that will buy from a competitor if nobody calls them this week. The problem isn't a lack of data. It's that turning a raw CSV export into a prioritized shortlist of expansion conversations takes hours most CSMs don't have.

That's what these prompts are for. Paste in your usage export, run the prompt, and get back a ranked list of accounts with the signal behind each one and a suggested talk track. Copy-paste ready. Steal them.

Why usage data beats every other expansion signal

Volume is the enemy here. A mid-market CSM with 60 accounts can't eyeball weekly exports for every one of them. AI can scan all 60 in minutes and hand you the five that matter, with evidence. That's the entire premise of this post: replace the weekly "scan the spreadsheet and guess" ritual with three prompts that do it systematically.

Prompt 1: The Expansion Shortlist

This is the workhorse. It takes a usage export and returns a ranked list of expansion candidates with the reasoning attached.

Role: You are a customer success operations analyst specializing in expansion revenue.

Context: Below is a usage data export covering [TIME PERIOD] for our customer accounts. Each row is one account. Columns: [LIST YOUR COLUMNS, e.g., Account Name, ARR, Seats Licensed, Seats Active, DAU, MAU, API Calls, Key Features Used, Support Tickets, Days Since Onboarded].

Task: Identify the top 10 accounts most likely to expand (buy more seats, upgrade tiers, or add products). For each account, provide: (1) the account name and current ARR, (2) an expansion likelihood score from 1–10, (3) the 2–3 specific signals that earned the score, (4) the most likely expansion motion (seat expansion, tier upgrade, cross-sell), and (5) one sentence describing the opening line for the CSM's outreach. Rank the list by score, highest first. Ignore accounts onboarded in the last 30 days — they're still ramping.

Constraints: Base every claim on the data provided. If a signal is ambiguous, say so rather than inventing context. Do not recommend outreach for accounts with unresolved critical support tickets — flag those separately.

Data: [PASTE CSV HERE]

Three things make this prompt work better than a generic "analyze this data" ask. First, it defines the columns so the model doesn't misread your export. Second, it forces a score plus evidence format, which kills vague answers. Third, the constraint about critical support tickets prevents the classic blunder of pitching an upsell to an account that's furious about an outage.

Tactical note: If your export is too large for one paste, split it by segment and run the prompt per segment. You get cleaner rankings when you're not comparing a 5,000-seat enterprise against a 12-seat startup on the same scale.

Prompt 2: The Feature-Gap Detector

Seat expansion is the obvious motion. The quieter one is feature adoption: accounts paying for capabilities they don't use yet — or worse, accounts that clearly need a tier they haven't bought. This prompt finds the mismatch between what an account does and what it pays for.

Role: You are a product adoption specialist for a B2B SaaS company.

Context: Our pricing has [TIER COUNT] tiers: [TIER NAME] includes [FEATURES], [NEXT TIER] adds [FEATURES], etc. Below is per-account feature usage for [TIME PERIOD].

Task: Find accounts showing "tier pressure" — usage patterns that indicate they'd get real value from a higher tier or an add-on product they don't have. For each match: (1) account name, (2) current tier, (3) the specific usage behavior creating tier pressure (e.g., "hitting the 10k automation-run cap 4 weeks running"), (4) the recommended tier or add-on, (5) the estimated value of the upgrade in the customer's own terms (time saved, limit removed, capability unlocked — not our ARR), and (6) a one-line talk track the CSM can use that frames the upgrade as solving the customer's problem, not selling them something.

Constraints: Only flag accounts where the usage evidence is strong — at least 3 of the last 4 weeks showing the pattern. Skip accounts in their first 60 days. Frame every recommendation from the customer's perspective; no internal sales language.

Data: [PASTE CSV HERE]

The key line is (6): the talk track framed from the customer's perspective. "Your team ran into the automation ceiling four weeks in a row — here's how the next tier removes it" beats "you're hitting your automation cap" because it solves a problem instead of pitching a product.

Prompt 3: The Timing Trigger

Even a perfect expansion candidate fails if you call at the wrong moment. This prompt scores timing — which accounts are in a window right now where an expansion conversation will land.

Role: You are a customer success strategist focused on expansion timing.

Context: Below is account-level data: [Account Name, Renewal Date, Last QBR Date, Recent Usage Trend (up/flat/down), Recent Champion Changes, Open Support Tickets, Last CSM Touchpoint].

Task: Score each account's expansion timing right now on a 1–10 scale. Consider: proximity to renewal (90–120 days out is ideal — close enough to matter, far enough to not feel pressured), recency of QBR or business review (fresh alignment helps), usage momentum, champion stability, and support health. For the top 10, give: (1) the timing score and what drives it, (2) the single best reason to have the conversation this month, and (3) any timing risk that argues for waiting (e.g., "renewal is 30 days out — fold this into the renewal negotiation instead of running a separate motion").

Constraints: Be explicit about timing risks. A "9" with a champion who just left is a trap, not an opportunity — flag it as one.

Data: [PASTE CSV HERE]

This is the prompt most teams skip, and it's the one that prevents the most damage. Bad timing doesn't just lose the upsell — it burns trust. Run the timing check before outreach and your shortlist becomes "accounts that should expand and will take the meeting."

The weekly workflow: 30 minutes, every Monday

Prompts are only useful if they become a habit. Here's the operating cadence that makes these stick:

1. Monday 9:00 — Export. Pull the standard usage export. Same columns, same format, every week. Consistency is what makes the prompts reliable; if the column order changes, the model's interpretation drifts.
2. Monday 9:10 — Run Prompt 1. Get the expansion shortlist. Pick your top 5.
3. Monday 9:15 — Run Prompt 2 on the top 5. Check for tier pressure you can lead with.
4. Monday 9:20 — Run Prompt 3 on the top 5. Kill any with timing risks. What survives is your outreach list for the week.
5. Monday 9:30 — Assign. Each surviving account gets an owner, a talk track (from the prompt output), and a deadline for first touch. Log it in the CRM so the shortlist is visible, not just a chat transcript.

Thirty minutes. Five qualified expansion conversations queued with evidence and talk tracks. Compare that to the old way: an hour of spreadsheet squinting, a gut-feel list, and outreach that starts with "just checking in."

What to watch out for

Don't automate the outreach itself. These prompts produce the shortlist and the talk track — the CSM still makes the call, in their own words. The moment expansion outreach becomes fully automated email sequences, response rates crater and customers smell the automation. AI finds the moment; the human has the conversation.

Track hit rate. Keep a simple log: accounts flagged, accounts that expanded within 90 days. After a quarter you'll know whether your prompts are calibrated. If the hit rate is under 20%, tighten the constraints (raise the minimum usage pattern from 3-of-4 weeks to 4-of-4, add a minimum ARR threshold). Prompts are instruments — tune them.

The bottom line

Your usage data already knows which accounts are ready to grow. These three prompts — the expansion shortlist, the feature-gap detector, and the timing trigger — turn that data into a weekly pipeline of qualified, well-timed expansion conversations. Thirty minutes on a Monday replaces hours of guesswork, and every outreach starts with evidence instead of a hunch.

Tomorrow: Office Hours That Work — a repeatable flow for running 1:many sessions that customers actually show up to.