How Quarterly Business Review Generator Compiles QBR Data

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 Pipedrive, Notion, Slack, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 2–4 hours 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. Quarterly Business Review Generator automates the deal intelligence and crm enrichment workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Three Agents. One Quarterly Run. Executive QBR Document.

The Quarterly Business Review Generator pipeline runs 3 agents in sequence. Assembler pulls data from Pipedrive and Notion and Slack, and Formatter delivers the output. Here is what happens at each stage and why it matters.

• 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:

• ITP-tested 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

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Quarterly Business Review Generator adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

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

The pipeline starts here. 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 ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

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.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 3: Formatter

Tier: HTTP

This is the final deliverable — what lands in your inbox or dashboard. 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.

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.

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

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 Independent Test Protocol (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 for a sales ops analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 2–4 hours 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 <$1/month (quarterly cadence), depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (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.

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.

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:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• TDD.md — Technical Design Document
• analyst_system_prompt.md — Analyst system prompt
• quarterly_business_review_generator_v1.0.0.json — n8n workflow (main pipeline)

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.

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.

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 provide real-time dashboards — generates a point-in-time executive document

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 forecast future pipeline — for forward-looking forecasts see RevOps Forecast Intelligence Agent

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 update or modify Pipedrive data — read-only CRM access

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.

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:

1. 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.
2. 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.
3. 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.