Every request in Zudo gets a severity score from 0 to 100. The score answers one question: “If we build this one thing, how much impact does it have?”
The score combines three signals — how much revenue is at stake, how many accounts are asking, and how urgently you think it’s needed — so your product team can prioritize with confidence rather than gut feel alone.
Severity scores recalculate automatically every 12 hours as MRR values and account data change. You’ll always see a score that reflects the current state of your book of business, not a snapshot from when the request was created.
How the score is calculated
Zudo weighs three factors to produce the final 0–100 score:
Severity = (0.50 × Revenue Impact) + (0.20 × Breadth of Demand) + (0.30 × User Severity)
| Factor | Weight | What it captures |
|---|
| Revenue Impact | 50% | How much of your portfolio MRR the linked accounts represent |
| Breadth of Demand | 20% | How many accounts are asking for the same thing |
| User Severity | 30% | Your 1–5 urgency rating for the request |
Factor 1: Revenue impact (50%)
This factor measures how much of your total portfolio MRR is represented by the accounts linked to the request.
Revenue Impact Score = (Affected MRR / Total Portfolio MRR) × 100
| Affected MRR | Total MRR | Revenue Impact Score |
|---|
| $500 | $100,000 | 0.5 |
| $5,000 | $100,000 | 5.0 |
| $25,000 | $100,000 | 25.0 |
| $50,000 | $100,000 | 50.0 |
| $100,000 | $100,000 | 100.0 |
Factor 2: Breadth of demand (20%)
This factor captures how many accounts are linked to the request. It uses a logarithmic scale, so the first few accounts carry the most weight — going from 0 to 1 linked account is a bigger jump than going from 20 to 21.
This prevents inflating scores by linking many low-value accounts, while still rewarding genuine market-wide demand.
| Accounts linked | Breadth score |
|---|
| 0 | 0.0 |
| 1 | 20.0 |
| 2 | 31.7 |
| 3 | 40.0 |
| 4 | 46.4 |
| 5 | 51.7 |
| 7 | 60.0 |
| 10 | 69.1 |
| 15 | 80.0 |
| 20 | 86.4 |
| 31 | 100.0 |
Factor 3: User severity (30%)
This is your 1–5 urgency rating — your judgment about how badly customers need this. It accounts for context that data can’t capture: a verbal churn threat, a competitive evaluation, an expansion blocker.
| Rating | Label | Sub-score |
|---|
| 1 | Low | 0 |
| 2 | Medium-Low | 25 |
| 3 | Medium | 50 |
| 4 | Medium-High | 75 |
| 5 | High | 100 |
How to set user severity
When creating or editing a request, select a rating from the severity row. The default is 3 (Medium).
Use the rating to reflect how urgently the customer needs this — not how important you think the feature is in general:
| Rating | When to use it |
|---|
| 1 | Nice-to-have; no urgency expressed by the customer |
| 2 | The customer has mentioned it but it’s not blocking anything |
| 3 | The customer wants this and follows up occasionally |
| 4 | Blocking a workflow or expansion; customer is actively escalating |
| 5 | Churn risk, active competitive threat, or the customer is blocked completely |
When there are no linked accounts
If a request has no linked accounts, Zudo falls back to your user severity rating as the entire score. Revenue impact and breadth are both zero, so the score reflects your judgment alone.
| User severity | Score (no accounts) |
|---|
| 1 | 0 |
| 2 | 25 |
| 3 | 50 |
| 4 | 75 |
| 5 | 100 |
Severity tiers
Zudo maps the final score to four color-coded tiers used throughout the product — in the requests list, request detail pages, and the dashboard.
| Score range | Tier |
|---|
| ≥ 80 | Critical |
| 60–79 | High |
| 40–59 | Medium |
| < 40 | Low |
