How Quarterly Business Review Generator Automates Deal Intelli...
The Problem
AI-generated QBRs from your Pipedrive data. That single sentence captures a workflow gap that costs sales, revops teams hours every week. The manual process behind what Quarterly Business Review Generator automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Pipedrive, Notion, Slack, copies it into a spreadsheet or CRM, applies a mental checklist, writes a summary, and routes it to the next person in the chain. Repeat for every record. Every day.
Three problems make this unsustainable at scale. First, the process does not scale. As volume grows, the human bottleneck becomes the constraint. Whether it is inbound leads, deal updates, or meeting prep, a person can only process a finite number of records before quality degrades. Second, the process is inconsistent. Different team members apply different criteria, use different formats, and make different judgment calls. There is no single standard of quality, and the output varies from person to person and day to day. Third, the process is slow. By the time a manual review is complete, the window for action may have already closed. Deals move, contacts change roles, and buying signals decay.
These are not theoretical concerns. They are the operational reality for sales, revops teams handling deal intelligence and crm enrichment workflows. Every hour spent on manual data processing is an hour not spent on the work that actually moves the needle: building relationships, closing deals, and driving strategy.
This is the gap Quarterly Business Review Generator fills.
Teams typically spend 30-60 minutes per cycle on the manual version of this workflow. Quarterly Business Review Generator reduces that to seconds per execution, with consistent output quality every time.
What This Blueprint Does
Three Agents. One Quarterly Run. Executive QBR Document.
Quarterly Business Review Generator is a multiple-node n8n workflow with 3 specialized agents. Each agent handles a distinct phase of the pipeline, and the handoff between agents is deterministic — no ambiguous routing, no dropped records. The blueprint is designed so that each agent does one thing well, and the overall pipeline produces a consistent, auditable output on every run.
Here is what each agent does:
- Assembler (HTTP + Code): Quarterly scheduled trigger pulls deal data from Pipedrive: all deals closed in the lookback period, open pipeline, activity history, and rep assignments.
- Analyst (Tier 1 Reasoning): Single the primary reasoning model call receives the pre-aggregated data and generates a 7-section QBR: Executive Summary, Pipeline Health, Win/Loss Analysis, Deal Velocity, Rep Performance, Risk Factors, and Strategic Recommendations.
- Formatter (HTTP): Converts the Analyst output into Notion block format and creates a new page in your configured Notion database.
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. Specifically, you receive:
- Production-ready 20-node n8n workflow — import and deploy
- Quarterly automated QBR generation from your Pipedrive pipeline data
- 7-section executive document: Executive Summary, Pipeline Health, Win/Loss Analysis, Deal Velocity, Rep Performance, Risk Factors, Strategic Recommendations
- Single the primary reasoning modelcall on pre-aggregated data — lowest cost-per-run in the catalog ($0.155)
- Notion delivery with structured headings and content blocks
- Slack notification with top strategic recommendation
- Configurable lookback period (default: 90 days)
- ITP test results with 8/8 tests and 14/14 milestones
Every component is designed to be modified. The agent prompts are plain text files you can edit. The workflow nodes can be rearranged or extended. The scoring criteria, output formats, and routing logic are all exposed as configurable parameters — not buried in application code. This means Quarterly Business Review Generator adapts to your specific process, terminology, and integration requirements without forking the entire workflow.
Every agent prompt in the bundle is a standalone text file. You can customize scoring criteria, output formats, and routing logic without modifying the workflow JSON itself.
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 Quarterly Business Review Generator execution flow.
Step 1: Assembler
Tier: HTTP + Code
Quarterly scheduled trigger pulls deal data from Pipedrive: all deals closed in the lookback period, open pipeline, activity history, and rep assignments. Pre-aggregates metrics — win rate, average deal size, stage velocity, pipeline coverage — into a structured data package. All computation happens before the LLM call, minimizing token cost.
This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Assembler identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.
Step 2: Analyst
Tier: Tier 1 Reasoning
Single the primary reasoning model call receives the pre-aggregated data and generates a 7-section QBR: Executive Summary, Pipeline Health, Win/Loss Analysis, Deal Velocity, Rep Performance, Risk Factors, and Strategic Recommendations. Each section includes period-over-period comparisons, evidence citations from the data, and specific action items. Not a dashboard summary — a reasoned document that explains why and recommends what to do.
This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Analyst identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.
Step 3: Formatter
Tier: HTTP
Converts the Analyst output into Notion block format and creates a new page in your configured Notion database. Each QBR section becomes a structured Notion heading + content block. Sends a Slack notification with the Notion link and a one-line summary of the top strategic recommendation.
This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Formatter identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.
The entire pipeline executes without manual intervention. From trigger to output, every decision point is deterministic: if a condition is met, the next agent fires; if not, the record is handled according to a documented fallback path. There are no silent failures. Every execution produces a traceable audit trail that you can review, export, or feed into your own reporting tools.
This architecture follows the ForgeWorkflows principle of tested, measured, documented automation. Every node in the pipeline has been validated during ITP (Inspection and Test Plan) testing, and the error handling matrix in the bundle documents the recovery path for each failure mode.
Tier references indicate the reasoning complexity assigned to each agent. Higher tiers use more capable models for tasks that require nuanced judgment, while lower tiers use efficient models for classification and routing tasks. This tiered approach optimizes both quality and cost.
Cost Breakdown
Every metric is ITP-measured. The Quarterly Business Review Generator pre-aggregates your Pipedrive data and produces a 7-section executive QBR with strategic recommendations at $0.155/run — the lowest cost-per-run in the catalog.
The primary operating cost for Quarterly Business Review Generator is the per-execution LLM inference cost. Based on ITP testing, the measured cost is: Cost per Run: $0.155/run (ITP-measured average). 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 at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 20–40 minutes per cycle, that is $17–50 per execution in human labor. 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 <$1/month (quarterly cadence), depending on your usage volume and plan tiers.
Quality assurance: BQS audit result is 12/12 PASS. ITP result is 8/8 tests, 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.
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
9 files — workflow JSON, system prompt, configuration guides, and complete documentation.
When you purchase Quarterly Business Review Generator, 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:
quarterly_business_review_generator_v1_0_0.json— The 20-node n8n workflowREADME.md— 10-minute setup guide with Pipedrive, Notion, and Slack configurationsystem_prompt_analyst.txt— Analyst system prompt (7-section QBR framework, evidence-based reasoning)lookback_config_guide.md— Lookback period and pipeline filter configurationnotion_setup_guide.md— Notion internal integration and database setupslack_setup_guide.md— Slack Bot Token setup with chat:write scopeitp_results.md— ITP test results — 8/8 tests, 14/14 milestonesblueprint_dependency_matrix.md— Prerequisites and cost estimatesCHANGELOG.md— Version history
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
Quarterly Business Review Generator 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: Pipedrive (any plan), Notion workspace, Slack workspace
- You have API credentials available: Anthropic API, Pipedrive API, Notion Internal Integration, Slack Bot Token
- 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 provide real-time dashboards — generates a point-in-time executive document
- Does not forecast future pipeline — for forward-looking forecasts see RevOps Forecast Intelligence Agent
- Does not update or modify Pipedrive data — read-only CRM access
- Does not work with HubSpot, Salesforce, or other CRMs — Pipedrive only
- Does not send the QBR by email — delivers to Notion with Slack notification
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.
Getting Started
Deployment follows a structured sequence. The Quarterly Business Review Generator bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Notion, Slack. Here is the recommended deployment path:
- Step 1: Import workflow and configure credentials. Import quarterly_business_review_generator_v1_0_0.json into n8n. Configure Pipedrive API token, Anthropic API key, Notion internal integration token, and Slack Bot Token (HTTP Header Auth, Authorization: Bearer xoxb-YOUR-TOKEN) with chat:write scope.
- Step 2: Configure Notion database and lookback period. Create a Notion database for QBR documents. Set the database ID in the workflow. Configure the lookback period (default: 90 days) and optional pipeline filters.
- Step 3: Activate and verify. Enable the workflow in n8n. Trigger manually for your first QBR. Verify the Notion page is created with all 7 sections and the Slack notification arrives with the document link.
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 Quarterly Business Review Generator 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?+
Distinct products with different cadences and outputs. RFIA runs weekly against HubSpot, generating a forward-looking pipeline forecast with coverage ratios and 3-scenario projections. QBR runs quarterly against Pipedrive, generating a retrospective executive review with win/loss analysis, rep performance benchmarking, and strategic recommendations. Different CRMs, different cadences, different outputs.
Why is the cost so low at $0.155/run?+
Single LLM call architecture. The Assembler pre-aggregates all Pipedrive data into structured metrics before the Analyst runs — win rates, deal sizes, stage velocities, coverage ratios are all computed in code. The Analyst receives a compact data package, not raw API responses. One Opus call generates all 7 sections.
What does the 7-section QBR include?+
Executive Summary (key metrics, trends, headline insight), Pipeline Health (open value, coverage, stage distribution), Win/Loss Analysis (rates, themes, loss reasons), Deal Velocity (days-to-close by stage, bottlenecks), Rep Performance (per-rep metrics with benchmarking), Risk Factors (at-risk deals, concentration, seasonal), Strategic Recommendations (AI-reasoned action items with evidence).
Can I change the lookback period?+
Yes — the lookback period is configurable in the workflow. Default is 90 days (one quarter). You can set it to 30, 60, 180, or 365 days for monthly, bi-monthly, semi-annual, or annual reviews.
Can I use HubSpot instead of Pipedrive?+
This version is built for Pipedrive. The Assembler uses Pipedrive-specific API endpoints. The Analyst and Formatter are CRM-agnostic — only the Assembler would need rebuilding for HubSpot. For HubSpot weekly forecasting, see RevOps Forecast Intelligence Agent.
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.
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.
Deal Stall Diagnoser
Diagnose why deals stall. Get unstuck.
Lost Deal Re-Activation Agent
Revive dead deals with AI-researched timing.