Why Scores Are Role-Based

Prodoscore does not compare a salesperson to a developer or a customer success manager to a recruiter. Different jobs require different tools and produce different activity patterns — a fixed universal scale would be meaningless and unfair.

Instead, each role has its own baseline score calculated from the activity patterns of employees in that role across the Prodoscore network. Individual scores are then benchmarked against that role baseline.

Activity Weights by Role

Different activities are assigned different weights depending on the role. For a sales organization, CRM activities likely have a higher weight than document creation. For a marketing team, the opposite may be true. Weights are set on a scale of 1 to 5, where 5 represents the highest weight.

The algorithm automatically normalizes weights over time based on how your team actually works — adapting to your organization's unique patterns rather than applying fixed universal values.

Custom Roles

When a custom role is created, it must be aligned to one of Prodoscore's default base roles (e.g., Sales, Customer Success, Knowledge Worker). The base role baseline serves as the starting benchmark for the custom role until the custom role develops its own data history.

Score Interpretation

Prodoscore generally considers a score between 40 and 75 to be average for most roles. Scores above 75 typically indicate an above-average day; scores below 40 may warrant a follow-up. However, always interpret scores in context — a busy travel day, a long offsite, or a personal event can all naturally produce lower scores.