Evaluate sales rep performance with contextual pipeline data
Normalize sales performance by factoring in territory quality, lead volume, and deal size. Use when conducting fair sales performance appraisals.
You getNormalized Performance Matrix, individual Performance Assessments and operational Adjustments
Prompt
Act as a revenue operations director. Review the raw sales rep metrics pasted below and provide a balanced performance evaluation that accounts for territory context, pipeline size, and average deal complexity.
Rules:
- Compare reps based on pipeline conversion rates and win rates, not just raw closed revenue.
- Account for structural differences like inbound lead volume, assigned territory size, and deal cycle lengths.
- Differentiate reps who over-perform relative to poor pipeline from reps who coast on high inbound volume.
- Keep observations grounded strictly in the pasted numbers.
Output format:
1. Normalized Performance Matrix (Columns: Rep Name, Inbound vs Outbound Mix, Win Rate %, Attainment vs Opportunity Ratio, Performance Tier)
2. Individual Performance Assessments (1 short paragraph per rep covering context and efficiency)
3. Operational Adjustments (3 action steps for pipeline reallocation or coaching)
Here are the sales performance records:Example output
Paste your CRM export table (including rep names, quota, closed-won amounts, total pipeline assigned, and lead sources) into ChatGPT, Claude, or Gemini. Follow up with: 'What specific goals should I set for the under-allocated rep next quarter?'
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit driver-based models for compounding optimism bias
Expose subtle, compounding growth assumptions across pipeline stages and conversion metrics. Use this during quarterly budget reviews and board deck prep.
Compare cumulative customer lifetime value across monthly cohorts
Spot whether newer customer groups spend faster or retain better than older cohorts. Use this to audit acquisition quality over time.
Create an anomaly investigation checklist for analytics teams
Run a disciplined diagnostic process before investigating metric shifts. Use this checklist whenever unexpected data spikes or drops appear in reports.
Differentiate structural null values from missing data
Identify whether null values represent expected business logic or export dropouts. Use it when auditing schema quality or preparing datasets for modeling.
Evaluate past forecast variances to set accurate targets
Analyze past forecast misses to identify systematic over- or under-projection patterns. Use this before locking in next quarter's revenue or operational targets.
Map inconsistent export columns to target schemas
Match disparate, poorly named export headers to a structured target data schema. Use it when consolidating CSV reports from multiple platforms.
- Normalize retention comparisons for immature recent customer cohorts
- Separate true anomalies from pipeline data errors
- Audit a metric definition guide for ambiguity
- Convert monthly operations metrics to executive updates
- Evaluate marketing channel efficiency from campaign performance data
- Evaluate pricing tier performance from subscriber data