How Competitive Pricing Intelligence Tracks Rival Pricing

Your CFO asks for a cash flow variance report by end of day. The data lives in Apollo, Notion, Slack — transactions in one, forecasts in another, vendor commitments in a third. Someone pulls each export, reconciles the numbers in a spreadsheet, flags the anomalies, and writes a narrative. This process takes 30–60 minutes per cycle. By the time the report lands, the numbers are 48 hours stale.

The problem is not the analysis itself — it is the lag between data and decision. Cash flow visibility is always retrospective. Vendor risk concentrations are discovered during audits, not in real time. Revenue trends are reported monthly when they should be monitored weekly. Competitive Pricing Intelligence automates the competitive intelligence and market data workflow, converting raw Apollo, Notion, Slack data into structured intelligence on a recurring schedule.

Four Agents. Six Signals. Weekly Competitive Pricing Intelligence.

The Competitive Pricing Intelligence pipeline runs 4 agents in sequence. Config Loader pulls data from Apollo and Notion and Slack, and Formatter delivers the output. Here is what happens at each stage and why it matters.

• Config Loader (Schedule + Code): Schedule Trigger fires weekly (Wednesday 08:00 UTC) or manual Webhook for on-demand runs.
• Researcher (Tier 2 Classification + web_search): the analysis model with web_search researches each competitor individually via SplitInBatches loop.
• Analyst (Tier 1 Reasoning): the primary reasoning model receives ONE aggregate call with all per-competitor research profiles.
• Formatter (Tier 2 Classification): the analysis model generates a Notion weekly pricing intelligence report (executive summary, per-competitor sections, cross-competitor patterns, recommended actions) and conditional Slack alerts for competitors with change significance at or above threshold..

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 29-node n8n workflow — import and deploy
• Weekly Schedule Trigger (Wednesday 08:00 UTC) or manual Webhook for on-demand analysis
• Apollo.io firmographic enrichment per competitor (employee count, industry, funding, revenue)
• Per-competitor web research via the analysis model + web_search (pricing pages, announcements, campaigns)
• 6-signal pricing taxonomy: price_increase, price_decrease, new_tier, discount_campaign, freemium_launch, enterprise_shift
• Cross-competitor strategy analysis via the primary reasoning model (market-wide trends, coordinated moves, pricing position)
• Per-competitor recommendations: RESPOND, MONITOR, or IGNORE with rationale
• Notion weekly pricing intelligence report with executive summary and per-competitor sections
• Conditional Slack alerts for significant pricing changes (configurable threshold)
• Configurable: competitor list (JSON), significance threshold, job posting signal toggle, Notion database, Slack channel
• DUAL-MODEL architecture: the analysis model per-competitor research + formatting, the primary reasoning model aggregate strategy
• ITP 20 records, 14/14 milestones, $0.83/run measured (20 competitors)

All scoring criteria, output formats, and routing rules are configurable in the system prompts — no workflow JSON edits required. This means Competitive Pricing Intelligence 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 Competitive Pricing Intelligence execution flow.

Step 1: Config Loader

Tier: Schedule + Code

The pipeline starts here. Schedule Trigger fires weekly (Wednesday 08:00 UTC) or manual Webhook for on-demand runs. Config Loader reads COMPETITOR_LIST (JSON array of competitor objects), fetches Apollo.io firmographic data per competitor (employee count, industry, funding stage, estimated revenue). Non-blocking enrichment.

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

the analysis model with web_search researches each competitor individually via SplitInBatches loop. Investigates pricing pages, plan changes, discount campaigns, freemium offerings, and enterprise positioning shifts. Classifies each finding into 6-signal taxonomy with confidence and significance scoring.

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: Analyst

Tier: Tier 1 Reasoning

the primary reasoning model receives ONE aggregate call with all per-competitor research profiles. Performs cross-competitor pricing strategy analysis: market-wide trends, coordinated moves, pricing position assessment. Generates per-competitor recommendations (RESPOND/MONITOR/IGNORE) and top-3 priority actions.

This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 4: Formatter

Tier: Tier 2 Classification

This is the final deliverable — what lands in your inbox or dashboard. the analysis model generates a Notion weekly pricing intelligence report (executive summary, per-competitor sections, cross-competitor patterns, recommended actions) and conditional Slack alerts for competitors with change significance at or above threshold.

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.

n8n cannot run a cron trigger and a webhook response in the same workflow. A single workflow file cannot have both a Schedule Trigger and a Webhook node as entry points. Every scheduled blueprint ships as two workflow files: one for the scheduled execution, one for the webhook callback.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Competitive Pricing Intelligence monitors competitor pricing moves weekly — researching each competitor individually with web_search, then synthesizing cross-competitor strategy with the primary reasoning model at $0.83/run for 20 competitors.

The primary operating cost for Competitive Pricing Intelligence is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.83/run for 20 competitors (ITP-measured). 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 $100–150/hour for a strategy consultant 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 $3.60/month (weekly runs, 20 competitors) + Apollo/Notion/Slack 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 20 records, 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.

7 files — workflow JSON, 3 system prompts, TDD, and complete documentation.

When you purchase Competitive Pricing Intelligence, 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
• competitive_pricing_intelligence_v1.0.0.json — n8n workflow (main pipeline)
• docs/TDD.md — Technical Design Document
• 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.

Competitive Pricing Intelligence is built for Strategy, Product, 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 strategy or product 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: Apollo.io account (API key for competitor firmographic enrichment), Notion workspace (integration token with Bearer prefix), Slack workspace (Bot Token with chat:write scope), Anthropic API key
• You have API credentials available: Anthropic API, Apollo.io (httpHeaderAuth), Notion (httpHeaderAuth, Bearer prefix), Slack (httpHeaderAuth, Bearer prefix, chat:write scope)
• 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 detect buying signals from news — that is what Buying Signal Detector does
• Does not monitor internal expansion revenue — that is what Expansion Revenue Detector does
• Does not diagnose stalled deals — that is what Deal Stall Diagnoser does
• Does not modify your pricing or product catalog — read-only competitive intelligence with Notion and Slack output
• Does not track competitor product features or roadmaps — focused on pricing signals only
• Does not provide real-time alerts — weekly scheduled analysis (or on-demand via Webhook)

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 detect buying signals from news — that is what Buying Signal Detector 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 monitor internal expansion revenue — that is what Expansion Revenue Detector 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 diagnose stalled deals — that is what Deal Stall Diagnoser 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 Competitive Pricing Intelligence bundle is designed for the following tools: n8n, Anthropic API, Apollo.io, Notion, Slack. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import competitive_pricing_intelligence_v1.0.0.json into n8n. Configure Apollo.io httpHeaderAuth credential (API key), Notion httpHeaderAuth credential (Bearer token), Slack httpHeaderAuth credential (Bearer token with chat:write scope), and Anthropic API key following the README.
2. Step 2: Configure competitor list and alert threshold. Set COMPETITOR_LIST as a JSON array of competitor objects (name + domain). Set SIGNIFICANCE_THRESHOLD (default 7) for Slack alert sensitivity. Configure NOTION_DATABASE_ID and SLACK_CHANNEL for output destinations. Optionally toggle INCLUDE_JOB_POSTING_SIGNALS.
3. Step 3: Activate and verify. Enable the workflow in n8n. Trigger a manual run via the Webhook URL with 2-3 test competitors. Verify the Notion weekly report appears with per-competitor sections and the Slack channel receives alerts for any competitor with significance at or above threshold.

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 Competitive Pricing Intelligence product page for full specifications, pricing, and purchase.