How Sales Rep Performance Coach Builds Weekly Briefs
The Problem
Your sales team has 47 deals in the proposal stage. 12 have not had contact in 5+ days. Three have gone completely dark. Which ones are at risk — and which ones just have a slow procurement process? A rep answering this question manually checks Hubspot, Slack, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 30–60 minutes per cycle of triage before any follow-up happens.
The cost is not just time — it is revenue leakage. Deals slip because signals were missed. Pipeline reviews rely on data that was accurate two days ago. Scoring criteria drift between team members, and the CRM becomes a lagging indicator rather than an operational tool. Sales Rep Performance Coach automates the sales coaching and revenue operations workflow from data extraction through analysis to structured output, with zero manual CRM entry.
Teams typically spend 30–60 minutes per cycle on the manual version of this workflow. Sales Rep Performance Coach reduces that to seconds per execution, with consistent output quality and zero CRM data entry.
What This Blueprint Does
Four Agents. Five Dimensions. Weekly Coaching for Every Rep.
The Sales Rep Performance Coach pipeline runs 4 agents in sequence. Fetcher pulls data from Hubspot and Slack, and Formatter delivers the output. Here is what happens at each stage and why it matters.
- Fetcher (Schedule + Code): Schedule Trigger fires weekly (Monday 08:00 UTC) or manual Webhook for on-demand runs.
- Assembler (Code-only): Computes per-rep metrics across 5 performance dimensions: activity_volume (calls, emails, meetings, tasks vs team average and baseline), conversion_efficiency (win rate, stage progression), deal_velocity (days in stage, time-to-close), pipeline_coverage (weighted pipeline value, new deals, refresh rate), and engagement_quality (meeting-to-deal ratio, follow-up cadence).
- Analyst (Tier 2 Classification): the analysis model receives ONE aggregate call with all rep metrics and team averages.
- Formatter (Tier 2 Classification): the analysis model generates Slack Block Kit coaching messages — one per rep.
When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:
- ITP-tested 26-node n8n workflow — import and deploy
- Weekly Schedule Trigger (Monday 08:00 UTC) or manual Webhook for on-demand runs
- HubSpot API pagination for rep activity data (calls, emails, meetings, deals, tasks)
- 7-day lookback + 30-day baseline for trend detection
- 5-dimension performance taxonomy: activity_volume, conversion_efficiency, deal_velocity, pipeline_coverage, engagement_quality
- Team average benchmarking with coaching priority classification (HIGH/MEDIUM/LOW)
- Per-rep coaching assessments with specific action items grounded in data
- Configurable coaching tone: constructive, direct, or motivational
- Slack per-rep coaching messages (DM or channel mode)
- AGGREGATE architecture: single Analyst + Formatter calls — $0.14/run regardless of rep count
- Dual the analysis model: no the primary reasoning modelrequired
- ITP 8 variations, 14/14 milestones, $0.14/run measured
Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Sales Rep Performance Coach adapts to your specific process, terminology, and integration requirements without forking the entire workflow.
Every agent prompt is a standalone text file. Customize scoring thresholds, qualification criteria, and output formatting without touching the workflow JSON.
How the Pipeline Works
Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Sales Rep Performance Coach execution flow.
Step 1: Fetcher
Tier: Schedule + Code
The pipeline starts here. Schedule Trigger fires weekly (Monday 08:00 UTC) or manual Webhook for on-demand runs. Fetcher paginates HubSpot API for rep activity data — calls, emails, meetings, deals, tasks — over a 7-day lookback window plus a 30-day baseline. Collects owner records for rep identification.
This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.
Step 2: Assembler
Tier: Code-only
Computes per-rep metrics across 5 performance dimensions: activity_volume (calls, emails, meetings, tasks vs team average and baseline), conversion_efficiency (win rate, stage progression), deal_velocity (days in stage, time-to-close), pipeline_coverage (weighted pipeline value, new deals, refresh rate), and engagement_quality (meeting-to-deal ratio, follow-up cadence). Calculates team averages and flags coaching priorities: HIGH (<70% team avg), MEDIUM (70–100%), LOW (>team avg).
Why this step matters: The result is a prioritized action queue, not just a data dump.
Step 3: Analyst
Tier: Tier 2 Classification
the analysis model receives ONE aggregate call with all rep metrics and team averages. Produces per-rep coaching assessments citing specific data points — strengths to reinforce, areas to improve, and concrete action items. Configurable coaching tone: constructive, direct, or motivational.
Every field in the output is structured for the next agent to consume without parsing.
Step 4: Formatter
Tier: Tier 2 Classification
This is the final deliverable — what lands in your inbox or dashboard. the analysis model generates Slack Block Kit coaching messages — one per rep. Supports DM mode (private coaching per rep) or channel mode (team-visible coaching digest). Each message includes performance snapshot, coaching priority, dimension-level insights, and specific action items.
The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.
All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.
This blueprint runs on your own n8n instance with your own API keys. Your CRM data never leaves your infrastructure.
Why we designed it this way
Found 4 leaked gate reports, 2 missing READMEs, 26 test artifacts in customer bundles. Manual review missed all of them. Mechanical verification catches what manual review misses. Our bundle checker now validates 8 things: no test data, no gate reports, no internal docs, README present, CHANGELOG present, LICENSE present, workflow JSON valid, prompts present.
— ForgeWorkflows Engineering
Cost Breakdown
Every metric is ITP-measured. The Sales Rep Performance Coach turns HubSpot activity data into personalized weekly coaching for every rep — computing 5-dimension performance metrics, benchmarking against team averages, and delivering Slack coaching briefs with specific action items at $0.14/run.
The primary operating cost for Sales Rep Performance Coach is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.14/run (ITP-measured average, 5 reps). This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.
To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour for a sales ops analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.
Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is $0.61/month (weekly runs) + HubSpot/Slack included tiers, depending on your usage volume and plan tiers.
Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 8 variations, 14/14 milestones PASS. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.
All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.
Monthly projection: if you run this blueprint 100 times per month, multiply the per-execution cost by 100 and add your infrastructure costs. Most teams find the total is less than one hour of manual labor per month.
What's in the Bundle
6 files — workflow JSON, system prompts, TDD, and complete documentation.
When you purchase Sales Rep Performance Coach, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:
CHANGELOG.md— Version historyREADME.md— Setup and configuration guideTDD.md— Technical Design Documentsales_rep_performance_coach_v1.0.0.json— n8n workflow (main pipeline)system_prompts/analyst_system_prompt.md— Analyst system promptsystem_prompts/formatter_system_prompt.md— Formatter system prompt
Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.
Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.
Who This Is For
Sales Rep Performance Coach is built for Sales, Revops teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:
- You operate in a sales or revops function and handle the workflow this blueprint automates on a recurring basis
- You have (or are willing to set up) an n8n instance — self-hosted or cloud
- You have active accounts for the required integrations: HubSpot account (OAuth2 with contacts, deals, engagements scopes), Slack workspace (Bot Token with chat:write + users:read scopes), Anthropic API key
- You have API credentials available: Anthropic API, HubSpot (OAuth2), Slack (Bot Token, httpHeaderAuth)
- You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)
This is NOT for you if:
- Does not forecast pipeline revenue — that is what RevOps Forecast Intelligence Agent does
- Does not monitor account health — that is what Account Health Intelligence Agent does
- Does not diagnose stalled deals — that is what Deal Stall Diagnoser does
- Does not modify HubSpot data or reassign deals — read-only analysis
- Does not scrape external websites — all data from HubSpot API
- Does not track individual deal outcomes — provides aggregate rep-level coaching
Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.
All sales are final after download. Review the full dependency matrix, prerequisites, and integration requirements on the product page before purchasing. Questions? Contact support@forgeworkflows.com.
Edge cases to know about
Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.
Does not forecast pipeline revenue — that is what RevOps Forecast Intelligence Agent does
This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.
Does not monitor account health — that is what Account Health Intelligence Agent does
We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.
Does not diagnose stalled deals — that is what Deal Stall Diagnoser does
This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.
Review the error handling matrix in the bundle for the full list of documented failure modes and recovery paths.
Getting Started
Deployment follows a structured sequence. The Sales Rep Performance Coach bundle is designed for the following tools: n8n, Anthropic API, HubSpot, Slack. Here is the recommended deployment path:
- Step 1: Import workflow and configure credentials. Import sales_rep_performance_coach_v1_0_0.json into n8n. Configure HubSpot OAuth2 credential (contacts, deals, engagements scopes), Anthropic API key, and Slack httpHeaderAuth credential (Bearer token with chat:write + users:read scopes) following the README.
- Step 2: Configure schedule and coaching parameters. The Schedule Trigger defaults to weekly (Monday 08:00 UTC). Adjust the cron expression to match your coaching cadence. Configure the coaching tone (constructive/direct/motivational), delivery mode (dm/channel), Slack channel ID, and HubSpot owner-to-Slack user ID mapping.
- Step 3: Activate and verify. Enable the workflow in n8n. Trigger a manual run via the Webhook URL with sample data. Verify per-rep coaching messages appear in Slack with performance snapshots, coaching priorities, dimension-level insights, and specific action items.
Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.
Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.
For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.
Ready to deploy? View the Sales Rep Performance Coach product page for full specifications, pricing, and purchase.
Run a manual test with sample data before switching to production triggers. This catches credential misconfigurations and API endpoint issues before they affect real workflows.
Frequently Asked Questions
How does it differ from RevOps Forecast Intelligence Agent?+
Complementary products covering different units of analysis. RFIA forecasts pipeline revenue from HubSpot deal data — the pipeline view. SRPC coaches individual reps from HubSpot activity data — the people view. RFIA tells you what your pipeline will do; SRPC tells you what each rep should do differently.
What are the five performance dimensions?+
Activity Volume — calls, emails, meetings, tasks vs team average and 30-day baseline. Conversion Efficiency — win rate, stage progression, lead-to-opportunity conversion. Deal Velocity — days in stage, time-to-close, pipeline movement speed. Pipeline Coverage — weighted pipeline value, new deals created, refresh rate. Engagement Quality — meeting-to-deal ratio, follow-up cadence, multi-touch patterns.
How does coaching priority work?+
Each rep is classified based on their performance relative to team averages. HIGH priority (<70% of team average) means the rep needs immediate attention. MEDIUM (70–100%) means developing but with room to improve. LOW (above team average) means performing well — the coaching focuses on reinforcement and stretch goals.
Can I choose between DM and channel delivery?+
Yes. Configure the COACHING_MODE variable: "dm" sends private coaching messages to each rep individually, "channel" posts a team coaching digest to a shared Slack channel. DM mode is better for sensitive feedback; channel mode builds team accountability. Review the error handling matrix in the bundle — it documents the recovery path for each failure mode.
Why is it so cheap at $0.14/run?+
AGGREGATE architecture. Instead of making one LLM call per rep (which would cost $0.03×N), all rep metrics are assembled by code-only nodes and sent to the Analyst in a single call. The Formatter also receives one call. Two Sonnet 4.6 calls total regardless of team size. 52 weekly runs = $7.28/year in LLM costs.
How many reps can it handle?+
The Analyst receives all rep data in one call. Sonnet 4.6 handles context windows up to 200K tokens. Practical limit depends on your team size and activity density — teams of 5–50 reps fit comfortably. For very large teams (100+), the Assembler can be configured to filter by team or region.
Does it use web scraping?+
No. All data comes from the HubSpot API: owner records, deal data, engagement data (calls, emails, meetings), and task data. No web_search, no external data sources, no scraping. This makes the pipeline fast, reliable, and deterministic.
How does it differ from Account Health Intelligence Agent?+
Different units and taxonomies. AHIA monitors per-account health from HubSpot engagement data (deals, tickets, engagements). SRPC monitors per-rep performance from HubSpot activity data (calls, emails, meetings, deals, tasks). AHIA tells you which accounts need attention; SRPC tells you which reps need coaching.
Is there a refund policy?+
All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions? Contact support@forgeworkflows.com before buying. Full terms at forgeworkflows.com/legal.
What should I do if the pipeline dead-letters a record?+
Check the dead letter output for the failure reason — the error context includes which agent failed and why. Common causes: missing input fields, API rate limits, or malformed data. Fix the underlying issue and reprocess. The error handling matrix in the bundle documents every failure mode and its recovery path.
Related Blueprints
RevOps Forecast Intelligence Agent
AI pulls your entire HubSpot pipeline every week, computes coverage ratio and deal velocity, and delivers a forecast brief with risks, focus areas, and rep leaderboard — to Notion and Slack.
Account Health Intelligence Agent
Weekly AI health briefs for every account.
Deal Stall Diagnoser
Diagnose why deals stall. Get unstuck.