2 min lesson
Alert on the metric, don't just chart it
Recall the main items in "Alert on the metric, don't just chart it", then connect each one to the work.
Step 1 of 2
Alert on the metric, don't just chart itthe part people skip
A chart waits for someone to look. An alert reaches out when the number crosses a line. The match-rate drift from the feedback-loop section should page you, not sit on a tab nobody opened for two weeks.
- Set thresholds tied to the guardrails, not arbitrary round numbers ("match rate below 65% for two days").
- Route the alert to the owner who can act, with the breakdown attached so they don't have to go hunting.
- Tune for signal: an alert that fires daily gets muted and a muted alert is worse than none.
Cursor's own field-engineering team ships this. They built an internal usage calculator in Cursor: feed it an account name or a direct team ID (e.g. straight from Stripe) and it returns a granular breakdown of how that account uses Cursor by token and by model, so GTM can forecast usage scope and trends. It started as an Airtable no-code prototype and graduated to real code as it earned its keep, hosted on Vercel and pulling live data through webhooks and a proxy. The win isn't the chart, it's the placement. Rather than make a rep open another tool, they embedded it as a tab inside Salesforce, prefiltered to the account or opportunity in view, and still take feature requests to make it more ergonomic.
"in Salesforce we have actually a tab that pulls up this usage calculator that's prefiltered to that account or that opportunity."