How Post-Demo Intelligence Brief Automates Sales Enablement

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 Calendly, Notion, Gmail, 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. Post-Demo Intelligence Brief automates the sales enablement and meeting prep workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Five DAP Categories. Intelligence Before Every Demo.

The Post-Demo Intelligence Brief pipeline runs 4 agents in sequence. Fetcher pulls data from Calendly and Notion and Gmail, and Formatter delivers the output. Here is what happens at each stage and why it matters.

• Fetcher (Webhook + Code): Calendly webhook (invitee.created) triggers on every new demo booking.
• Researcher (Tier 2 Classification): the analysis model + web_search enriches every demo booking with company overview, recent news, competitive landscape, technology stack, and attendee professional context.
• Analyst (Tier 2 Classification): the analysis model scores Demo Actionability Potential (DAP) across 5 categories: strong_buy_signal, technical_evaluation, stakeholder_alignment, timing_mismatch, poor_fit.
• Formatter (Tier 2 Classification): the analysis model generates two outputs: (1) structured Notion pre-demo brief with 7 sections — Company Overview, Attendee Profile, Competitive Landscape, Talking Points, Potential Objections, Demo Strategy, DAP Summary; (2) personalized Gmail follow-up draft.

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 28-node n8n workflow — import and deploy
• Calendly webhook trigger (invitee.created) with HMAC-SHA256 signature verification
• Company and attendee intelligence enrichment via the analysis model + web_search
• DAP 5-category demo outcome prediction: strong_buy_signal, technical_evaluation, stakeholder_alignment, timing_mismatch, poor_fit
• Structured Notion pre-demo brief with 7 sections (Company Overview through DAP Summary)
• Personalized Gmail follow-up draft with configurable send gate
• Event type filtering — only process demos matching your event type name
• Triple-the analysis model: $0.234/demo all-in — no the primary reasoning modelrequired
• ITP test results with 20 records, 14/14 milestones, 95% DAP accuracy

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Post-Demo Intelligence Brief 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 Post-Demo Intelligence Brief execution flow.

Step 1: Fetcher

Tier: Webhook + Code

The pipeline starts here. Calendly webhook (invitee.created) triggers on every new demo booking. Fetcher verifies HMAC-SHA256 signature, extracts invitee email, name, company, and event details from the Calendly API, and assembles the enrichment payload. Event type filtering ensures only demos matching your configurable event type are processed.

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

Tier: Tier 2 Classification

the analysis model + web_search enriches every demo booking with company overview, recent news, competitive landscape, technology stack, and attendee professional context. Produces structured intelligence payload covering company fundamentals, market position, and individual attendee relevance signals.

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 scores Demo Actionability Potential (DAP) across 5 categories: strong_buy_signal, technical_evaluation, stakeholder_alignment, timing_mismatch, poor_fit. DAP is informational only — every demo gets a full intelligence brief regardless of score. Includes talking points, potential objections, and demo strategy recommendations.

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 two outputs: (1) structured Notion pre-demo brief with 7 sections — Company Overview, Attendee Profile, Competitive Landscape, Talking Points, Potential Objections, Demo Strategy, DAP Summary; (2) personalized Gmail follow-up draft. Follow-up gate optionally skips Gmail draft creation.

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.

3 of 20 test deals had no activity history — no calls, no emails, no meetings. Without a dead letter queue, those 3 would have crashed the pipeline and blocked the other 17. The dead letter queue caught them; the pipeline processed the other 17 normally. Quarantine bad data, do not let it block good data.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Post-Demo Intelligence Brief generates pre-demo intelligence from every Calendly booking — enriching via web_search, scoring demo actionability across 5 categories, and delivering structured Notion briefs with Gmail follow-up drafts at $0.234/demo.

The primary operating cost for Post-Demo Intelligence Brief is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Demo: $0.234/demo (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 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 $23.40/month (100 demos/month), depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 20 records, 14/14 milestones PASS, 95% DAP accuracy. 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 prompts, scoring guides, and complete documentation.

When you purchase Post-Demo Intelligence Brief, 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
• docs/TDD.md — Technical Design Document
• post_demo_intelligence_brief_v1.0.0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/formatter_system_prompt.md — Formatter system prompt
• system_prompts/researcher_system_prompt.md — Researcher 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.

Post-Demo Intelligence Brief is built for Sales 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 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: Calendly account (webhook endpoint), Notion workspace (API access), Google Workspace (Gmail OAuth2)
• You have API credentials available: Anthropic API, Calendly (httpHeaderAuth), Notion (httpHeaderAuth), Gmail (OAuth2)
• 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 predict no-show risk — that is what No-Show Predictor does
• Does not send outreach emails — generates intelligence briefs and follow-up drafts
• Does not score lead quality — that is what Inbound Lead Qualifier does
• Does not update CRM deal stages — that is what Deal Intelligence Agent does
• Does not predict objections from CRM data — that is what Prospect Objection Predictor does
• Does not generate post-meeting follow-ups — that is what Meeting Follow-Up Agent does

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 predict no-show risk — that is what No-Show Predictor 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 send outreach emails — generates intelligence briefs and follow-up drafts

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 score lead quality — that is what Inbound Lead Qualifier 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.

Deployment follows a structured sequence. The Post-Demo Intelligence Brief bundle is designed for the following tools: n8n, Anthropic API, Calendly, Notion, Gmail. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import post_demo_intelligence_brief_v1_0_0.json into n8n. Configure Calendly httpHeaderAuth credential (Bearer token), Notion httpHeaderAuth credential (Bearer token), Gmail OAuth2 credential, and Anthropic API key following the setup guides.
2. Step 2: Configure webhook and event filtering. Set up the Calendly webhook subscription pointing to your n8n webhook URL with invitee.created event. Configure CALENDLY_EVENT_TYPE to match your demo event type name. Set your HMAC signing key for signature verification.
3. Step 3: Activate and verify. Enable the workflow in n8n. Create a test Calendly booking for a demo event. Verify the Notion brief is created with all 7 sections, Gmail draft appears (if follow-up gate is enabled), and the webhook responds with success.

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 Post-Demo Intelligence Brief product page for full specifications, pricing, and purchase.