MRR names that survive plan renames

Name the revenue intent, not the SKU label—or the next pricing rename breaks every report.

Planning documents and charts spread across a desk

Teams often treat metric names as disposable labels. A marketer renames a plan, an engineer ships a new paywall, and suddenly plan_upgrade and expand_mrr both exist for the same moment. Subscription reports that once looked clean become archaeological digs.

Prefer verbs that describe intent. Keep platform out of the event name—put it in a property so web and app stay comparable during revenue reviews. Write allowed properties on the same day you create the signal.

In Baseline Audit engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.