Detection rules are the core of Revenue Observability. They're the logic that decides: this deal has a blind spot, and here's what it is. But building good detection rules is harder than it sounds.
The most common mistake? Making rules too sensitive. If every deal triggers an alert, nobody pays attention to any of them. That's alert fatigue, and it kills adoption faster than anything.
The anatomy of a good detection rule
Every effective detection rule has four components:
See your pipeline's blind spots
Customer City connects to your revenue stack and surfaces the silent failures killing your deals.
Start with these 5 rules
If you're just getting started with detection rules, begin with these five. They catch the highest-impact blind spots with the lowest false-positive rate:
Tuning for your team
Every team is different. Enterprise sales cycles are longer than mid-market. Some industries have naturally slower response times. The key is to start with the defaults, measure false positives for 2 weeks, then adjust thresholds. Customer City makes this easy with per-rule sensitivity controls.