How Post-Demo Intelligence Brief Automates Sales Enablement

AI intelligence briefs for every demo — before and after. That single sentence captures a workflow gap that costs sales teams hours every week. The manual process behind what Post-Demo Intelligence Brief automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Calendly, Notion, Gmail, 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 teams handling sales enablement and meeting prep 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 Post-Demo Intelligence Brief fills.

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

Post-Demo Intelligence Brief is a multiple-node n8n workflow with 4 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:

• 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. Specifically, you receive:

• Production-ready 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

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

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 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 Fetcher 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: 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.

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

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 4: Formatter

Tier: 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. Follow-up gate optionally skips Gmail draft creation.

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.

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 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 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 $23.40/month (100 demos/month), depending on your usage volume and plan tiers.

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

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:

• post_demo_intelligence_brief_v1_0_0.json — The 28-node n8n workflow
• README.md — 10-minute setup guide with Calendly, Notion, Gmail, and Anthropic configuration
• system_prompt_researcher.txt — Researcher system prompt (company and attendee intelligence via web_search)
• system_prompt_analyst.txt — Analyst system prompt (DAP 5-category scoring with demo strategy)
• system_prompt_formatter.txt — Formatter system prompt (Notion brief + Gmail follow-up draft)
• dap_scoring_guide.md — DAP criteria definitions, category descriptions, and scoring calibration
• calendly_webhook_setup.md — Calendly webhook configuration and HMAC-SHA256 verification setup
• itp_results.md — ITP test results — 20 records, 14/14 milestones, 95% DAP accuracy
• CHANGELOG.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.

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.

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.