Rep activity leaderboard
Shows what each rep actually did last month, calls, emails, meetings and tasks, next to the revenue they closed.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Tie rep activity to revenue
Coming soonBlu builds a step
About this recipe
When to use it
"Do more activity" is useless advice without knowing which activity correlates with revenue for your team specifically. This ranks reps on calls, emails, meetings, and tasks, then overlays revenue and quota attainment so the real correlation shows up.
What it delivers
Builds a per-rep activity leaderboard across calls, emails, meetings, and tasks, with revenue correlation and quota attainment overlaid to surface which activities actually move the needle.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Shows what each rep actually did last month, calls, emails, meetings and tasks, next to the revenue they closed.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Tie rep activity to revenueCreate an Insights report called "Rep Activity Leaderboard". Series A: Event "Call completed" OR "call_logged", aggregation: Count grouped by owner_id, label: "Calls" Series B: Event "Messaged email" where direction = outbound (sent emails), aggregation: Count grouped by created_by (the rep), label: "Outbound Emails" Series C: Event "Meeting scheduled" where canceled_at is null, aggregation: Count grouped by created_by, label: "Meetings Booked" Series D: Event "Task completed", aggregation: Count grouped by assignee_id, label: "Tasks Completed" Series E: Sum of Deal won.amount grouped by owner_id (rep's revenue contribution in period), unit: $, label: "Revenue Closed" Series F: Computed: Series E / Series A × 100, label: "Revenue per 100 Calls" - The Gong-popularized leading-indicator metric: ties activity volume to revenue outcomes. Time range: Last 30 days Breakdown: By owner_id (per-rep, sortable leaderboard) Compare: Previous period (prior 30 days) Chart type: Sortable table (the leaderboard) with rep name, all activity counts, revenue closed, and the activity-to-revenue ratios. Plus a secondary chart showing activity volume distribution per rep (stacked bar). Sort modes (toggle): - By Revenue Closed (descending) to "Top Performers" - By Calls (descending) to "Most Active" - By Revenue per 100 Calls (descending) to "Most Efficient" - By Activity Velocity (week-over-week change) to "Rising / Falling Stars" Annotations: - Flag reps with high activity (top quartile in calls/emails) but low revenue (bottom quartile): coaching opportunity, likely qualification or close-rate issue. - Flag reps with low activity (bottom quartile) but high revenue (top quartile): outliers worth understanding (might be working strategic accounts, or might be inheriting deals). - Highlight any rep whose activity dropped >30% week-over-week (engagement drop: disengagement or PTO; flag for manager check-in). - Surface team averages alongside each metric (so any rep can see how they compare). - Add the trailing-week revenue-per-call benchmark; below team-average × 0.5 indicates serious efficiency issue. Use case: the canonical sales-manager weekly review. Activity metrics are leading indicators (per Gong); revenue is the lagging outcome. Reading them together surfaces both the "rising stars" (activity climbing, revenue about to follow) and the "coaching opportunities" (activity high but revenue stuck). Taxonomy notes: - Call completed and call_logged are both canonical (varies by integration: HubSpot/Salesforce typically emit Call completed with metadata; manually-logged calls emit call_logged). - Messaged email.direction is a canonical property; outbound emails have direction = "outbound". - Meeting scheduled.canceled_at being null means the meeting wasn't canceled. End_time being in the past indicates it actually occurred. - Task completed.assignee_id is the rep responsible for the task. - "Rep" identification varies by event: - Call completed: created_by - Messaged email: created_by - Meeting scheduled: created_by - Task completed: assignee_id - Deal won: owner_id These should all resolve to the same Users object (owner_id is a canonical user-attribute): Lovable's translation layer must unify these for per-rep aggregation.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /rep-activity-leaderboard in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 