How Sales Playbook Generator Distills Won Deal Patterns
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 Pipedrive, Notion, 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. Sales Playbook Generator automates the sales enablement and revenue operations workflow from data extraction through analysis to structured output, with zero manual CRM entry.
Teams typically spend 2–4 hours per cycle on the manual version of this workflow. Sales Playbook Generator reduces that to seconds per execution, with consistent output quality and zero CRM data entry.
What This Blueprint Does
Four Agents. Six Sections. A Tactical Playbook From Your Won Deals.
The Sales Playbook Generator pipeline runs 4 agents in sequence. Fetcher pulls data from Pipedrive and Notion, and Formatter delivers the output. Here is what happens at each stage and why it matters.
- Fetcher (Schedule + Code): Schedule Trigger fires quarterly (1st of quarter, 08:00 UTC) or manual Webhook for on-demand runs.
- Assembler (Code-only): Reconstructs deal timelines from activities and notes.
- Analyst (Tier 2 Classification): the analysis model receives ONE aggregate call with all deal timelines.
- Formatter (Tier 2 Classification): the analysis model generates a structured Notion playbook document with script examples, objection response frameworks, competitive positioning guides, and benchmark metrics.
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 22-node n8n workflow — import and deploy
- Quarterly Schedule Trigger (1st of quarter, 08:00 UTC) or manual Webhook for on-demand runs
- Pipedrive API pagination for won deals with activities, notes, and contact data
- 90-day configurable lookback window for deal analysis
- 6-section playbook taxonomy: discovery_questions, objection_handling, competitive_positioning, value_propositions, closing_techniques, deal_dynamics
- Evidence strength ratings: STRONG (5+ deals), MODERATE (3–4 deals), EMERGING (2 deals)
- Notion playbook document with script examples, objection frameworks, and benchmarks
- Configurable: lookback window, minimum deals threshold, competitor section toggle, evidence threshold, Notion database target
- AGGREGATE architecture: single Analyst + Formatter calls — $0.11/run regardless of deal count
- Dual the analysis model: no the primary reasoning modelrequired
- ITP 8 variations, 14/14 milestones, $0.11/run measured
Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Sales Playbook Generator 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 Playbook Generator execution flow.
Step 1: Fetcher
Tier: Schedule + Code
The pipeline starts here. Schedule Trigger fires quarterly (1st of quarter, 08:00 UTC) or manual Webhook for on-demand runs. Fetcher paginates Pipedrive API for won deals over a configurable 90-day lookback window with associated activities, notes, and contact data.
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
Reconstructs deal timelines from activities and notes. Extracts discovery questions, objections raised, competitive mentions, value propositions cited, closing techniques used, and quantitative deal dynamics (cycle length, stage progression, discount patterns).
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 deal timelines. Produces a 6-section sales playbook (discovery_questions, objection_handling, competitive_positioning, value_propositions, closing_techniques, deal_dynamics) with evidence strength ratings: STRONG (5+ deals), MODERATE (3–4), EMERGING (2).
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 a structured Notion playbook document with script examples, objection response frameworks, competitive positioning guides, and benchmark metrics. Conditional competitor section toggle.
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
null is not the same as absent for Stripe's recurring field. Setting it to null created a spurious monthly subscription alongside the one-time price. The fix: omit the recurring parameter entirely. Do not set it to null, do not set it to undefined — leave it out of the request body completely.
— ForgeWorkflows Engineering
Cost Breakdown
Every metric is ITP-measured. The Sales Playbook Generator turns Pipedrive won-deal patterns into a tactical 6-section playbook — extracting discovery questions, objection responses, competitive positioning, and closing techniques with evidence strength ratings at $0.11/run.
The primary operating cost for Sales Playbook Generator is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.11/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 $0.04/month (quarterly runs) + Pipedrive/Notion 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 Playbook 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 historyREADME.md— Setup and configuration guidedocs/TDD.md— Technical Design Documentsales_playbook_generator_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 Playbook 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 account (pipedriveApi credential with deals, activities, notes scopes), Notion workspace (integration token with Bearer prefix), Anthropic API key
- You have API credentials available: Anthropic API, Pipedrive (pipedriveApi), Notion (httpHeaderAuth, Bearer prefix)
- 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 review quarterly pipeline metrics — that is what Quarterly Business Review Generator does
- Does not diagnose stalled deals — that is what Deal Stall Diagnoser does
- Does not re-activate lost deals — that is what Lost Deal Re-Activation Agent does
- Does not modify Pipedrive data or reassign deals — read-only analysis with Notion output
- Does not scrape external websites — all data from Pipedrive API
- Does not coach individual reps — generates a team-level playbook from aggregate patterns
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 review quarterly pipeline metrics — that is what Quarterly Business Review Generator 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 diagnose stalled deals — that is what Deal Stall Diagnoser 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 re-activate lost deals — that is what Lost Deal Re-Activation Agent 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 Playbook Generator bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Notion. Here is the recommended deployment path:
- Step 1: Import workflow and configure credentials. Import sales_playbook_generator_v1_0_0.json into n8n. Configure Pipedrive pipedriveApi credential (deals, activities, notes scopes), Notion httpHeaderAuth credential (Bearer token), and Anthropic API key following the README.
- Step 2: Configure lookback window and playbook parameters. The Schedule Trigger defaults to quarterly (1st of quarter 08:00 UTC). Configure LOOKBACK_DAYS (default 90), MIN_DEALS threshold (default 15), INCLUDE_COMPETITOR_SECTION (true/false), EVIDENCE_THRESHOLD, and NOTION_DATABASE_ID for your playbook destination.
- Step 3: Activate and verify. Enable the workflow in n8n. Trigger a manual run via the Webhook URL. Verify the Notion playbook page appears with 6 sections (or 5 if competitor section disabled), evidence strength badges, script examples, and benchmark metrics.
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 Playbook 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 Quarterly Business Review Generator?+
Complementary products covering different outputs from your pipeline data. QBR generates a quarterly metrics dashboard — win/loss ratios, revenue totals, activity volumes. SPG generates a tactical playbook — specific discovery questions, objection scripts, and closing techniques extracted from your actual wins. QBR tells management how the quarter went; SPG tells reps what to say on the next call.
What are the six playbook sections?+
Discovery Questions — most effective questions from won deals, ranked by frequency and categorized by stage. Objection Handling — common objections and winning responses (price/timing/competition/authority/need). Competitive Positioning — win-against patterns and differentiators that resonated. Value Propositions — messaging that appeared in wins, ranked by frequency and persona. Closing Techniques — late-stage patterns: proposals, urgency drivers, decision accelerators. Deal Dynamics — quantitative benchmarks: cycle length, stage progression, discount patterns.
How does evidence strength work?+
Each pattern is classified by how many won deals support it. STRONG (5+ deals) means the pattern is reliable and repeatable. MODERATE (3–4 deals) means the pattern is emerging but needs more data. EMERGING (2 deals) means the pattern was observed but is too early to generalize. Evidence ratings help reps prioritize which techniques to adopt immediately versus experiment with.
Can I exclude the competitive positioning section?+
Yes. Set INCLUDE_COMPETITOR_SECTION to false in the Config Loader. The Analyst still produces the other 5 sections (discovery, objections, value props, closing, deal dynamics). Useful when competitor data is sparse or when the playbook is shared externally.
How often should I run it?+
Quarterly is the default (1st of quarter at 08:00 UTC). This provides a fresh playbook at the start of each sales quarter with enough deal data (90-day lookback) for meaningful patterns. You can also trigger on-demand via Webhook after a particularly strong month or when onboarding new reps. The ITP test results in the bundle show measured performance across edge cases, not just happy-path data.
Why is it $0.11/run?+
AGGREGATE architecture. Instead of analyzing deals individually, all deal timelines 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 deal count. 4 quarterly runs = $0.44/year in LLM costs.
Does it use web scraping?+
No. All data comes from the Pipedrive API: won deals, activities, notes, and contact data. No web_search, no external data sources, no scraping. This makes the pipeline fast, reliable, and deterministic.
How does it differ from Deal Stall Diagnoser?+
Different deal populations and different purposes. DSD analyzes stalled deals to diagnose why they are stuck. SPG analyzes won deals to extract what made them succeed. DSD is diagnostic (what went wrong); SPG is prescriptive (what to replicate).
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.