MARKET RESEARCH
Patent Claims Tracker Synced to Coda
Monitors a competitor's patent applications and maintains a structured Coda table with each filing's claims summary, technology area, and dedup status for ongoing analysis.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionRetrieve recent applicationsExa
- ActionScrape claims and abstractFirecrawl
- ActionSummarize and classify tech areaOpenAI
- LogicDedup against existing Coda rows
- OutputUpsert filing into Coda tableCoda
What it does
This workflow builds and maintains a living Coda database of a competitor's patent activity. On each run it finds new applications, extracts and summarizes the claims, classifies the technology area, and upserts a row into a Coda table, skipping filings already recorded. The result is a queryable, sortable patent ledger the whole team can slice by tech area or filing date.
When to use it
Use it when a one-off Slack ping isn't enough and you need a durable, structured record for trend analysis, board decks, or freedom-to-operate prep. Best when multiple people reference the same patent dataset over time.
How it works
- 1A scheduled trigger runs daily.
- 2Exa retrieves recent published applications for the tracked assignee.
- 3Firecrawl scrapes each filing's claims and abstract.
- 4An OpenAI step writes a claims summary and assigns a technology-area label.
- 5A logic step checks the Coda table for an existing row by application number to avoid duplicates.
- 6New filings are upserted as rows into the Coda patent tracker with summary, tech area, date, and link.
Set it up
What you configure once, before turning it on.
- 1Connect ExaNeural search across the web.
- 2Connect FirecrawlCrawl, scrape, structured extract.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect CodaDocs, packs, automations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Market Research workflows
Enrich Inbound Accounts with BigQuery Firmographics and Score Fit
When a new account row lands in Airtable, joins it against BigQuery public business datasets to attach firmographic attributes.
Blend BigQuery TAM with Live Competitor Signals into a Notion Brief
On demand, sizes a chosen segment from BigQuery public data, gathers current competitor signals via Brave Search, and synthesizes a one-page market brief into Notion.
Allocate Sales Territory TAM from BigQuery Geo Data to HubSpot
When triggered by a webhook, queries BigQuery public ZIP-level business data to compute TAM per sales territory.
Hiring Surge Detector with Slack Alert
Detects when a target account's open-role count jumps above its recent baseline and posts a ranked Slack alert to the GTM channel so reps can act on a company that is clearly…
Tech-Stack Shift Inference from Job Descriptions
Reads new job descriptions for target accounts, uses an LLM to extract named technologies and infer stack changes.
Weekly Hiring-Intel Briefing for GTM
An agent reviews the week's accumulated hiring signals across all target accounts, writes a narrative briefing that infers each account's likely initiatives.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.