MARKET RESEARCH

On-Demand Patent Deep Dive Report

Triggered by a webhook with a competitor name, an agent gathers that company's full patent history, analyzes filing velocity and technology focus.

CategoryMarket Research
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook with competitor nameHTTP webhook
  • ActionPull full filing historyFirecrawl
  • LogicAnalyze velocity + technology focus
  • LogicGuard against sparse results
  • OutputPublish deep-dive page to ConfluenceConfluenceConfluence

What it does

Produces a focused, single-competitor patent dossier on request. Give it a company name and it returns a structured analysis of their entire patent portfolio — filing trends over time, dominant technology areas, and recent strategic shifts.

When to use it

Use when a specific deal, partnership evaluation, or board question demands a thorough look at one competitor's IP, rather than the broad quarterly sweep.

How it works

  1. 1A webhook fires with the target competitor's name and optional date range.
  2. 2Firecrawl pulls the competitor's full filing history from patent databases.
  3. 3An agent analyzes filing velocity, technology-area concentration, and notable recent applications, comparing recent activity to historical baselines.
  4. 4A logic check confirms enough filings were found to warrant a report; sparse results return a short note instead.
  5. 5The agent writes a formatted deep-dive page — charts described in prose, key findings, and a recommendations section — into the team's Confluence space.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect FirecrawlCrawl, scrape, structured extract.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.