Usage Bill-Shock Absorber Playbook 2026

Build the benchmark once, refresh it quarterly:

1. Comparison customers: accounts that moved to a bigger plan or a usage commitment after a spike in the last 18 months, and still use it. Aim for 20; with fewer, label it low confidence.
2. How their spike looked: active users against volume, how many of your usual features carried it, and the share that came from one user or API key.
3. The crossover: for each plan, the usage level where the next plan costs less than overage.

Your head of revenue or CS lead approves it (how to build a benchmark).

The trigger, per account (default to tune): run-rate (usage so far ÷ days elapsed × days in the cycle) tracks 40%+ above the highest of the account's last three invoices. One fire per cycle.

Say an account has paid at most $4,000 in each of the last three months and is tracking to $7,200 by day 12. Expanders who looked like this moved to the $6,000 plan. The $1,200 between them is a comparison, not a forecast. (The numbers are illustrative.)

Run it as a daily saved query on Orb's usage and invoice data. As a backstop, set an Orb cost alert on each subscription at 1.4 times its highest recent invoice: it fires when the bill so far crosses that line, later than the run-rate check. Under about a hundred usage-billed accounts, do it by hand from a weekly billing export.

• Active users vs expanders: default until the benchmark says otherwise, growth has active users up at least 20% while volume is up 40%. Flat users with triple the volume looks like a script.
• Spread across normal work: growth shows up in three or more of the features your expanders used. One endpoint at 2 a.m. doesn't.
• Share from one user or key: over half the increase from one source looks like an accident – a retry loop, or a sandbox job pointed at production.
• Season or known project: the same month last year, and CRM notes on a migration, launch or backfill the customer told you about.

If the growth comes from a new department, it's also a second-department gap; note it there.

Leave it alone if (defaults): the spike matches last year's peak within 20%, the customer told you about the project and budgeted for it, prepaid credits cover the extra, or the extra is under $500. Renewal inside 30 days? Leave this play alone and take the spike into the renewal conversation. Everything else picks a move.

Set Recommended move to No move, write the reason in one line, and set Review date to the end of the cycle. Calling about a peak they told you about says you weren't listening. The leave-it-alone play covers the call in full.

• Growth: active users and spread at the expanders' level, no single source over half. Plan conversation.
• Accident: one source over half, or flat users with a concentrated meter. Meter note.

When the fields disagree – users up a little, one meter up a lot – draft the meter note as a question, not a claim. Under seven days left, it's today's work.

The projection, the crossover and the opener below. Lead with the growth, not the bill, and put both numbers side by side. Below the crossover, the next plan costs more: send the heads-up without the plan line. A cheaper plan gives up some overage, but it buys committed revenue and a customer who trusts the bill. If the growth holds for two cycles, it's an upgrade case for the plan-upgrade play.

The note below, with the meter, the day it started and the source filled in, so the customer can act in minutes. Offer a cap now and help finding the cause.

The AM reads the evidence and runs it as drafted, changes it, or passes. If the customer would rather ride the overage a cycle, fine – the job is no surprises. Before acting, record the success measure and review date (default: eight weeks on). A conversation before cycle end is activity, no dispute is progress, a plan change is the result. Once the meter notes have been right for a few cycles, your team can choose to send them automatically from HubSpot, triggered by the Orb alert, so each send is logged on the record.

When the customer says yes, change the plan in Orb mid-cycle: the new rate from today, earlier usage at the old rates. Orb may issue two invoices, one closing the old plan and one for the new. Say so in the confirmation, so nothing reads like a penalty.

On the review date, record three answers: was there a dispute, did the plan change, and what else played a part? The eight-week review has the full method. If nothing moved, change the move, stop it, or give it time. An invoice 40%+ above the highest of the three before it, with no logged conversation, is a miss; find the rule that let it through. Each quarter, add new expanders to the benchmark and update the crossovers.