MARKET RESEARCH
Detect Quarter-over-Quarter Guidance Changes Across Competitors
Weekly, compare each tracked competitor's newest filing against their prior quarter to surface raised, lowered, or withdrawn guidance.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFind competitors that filed this weekPerplexity
- ActionFetch new filing textFirecrawl
- ActionDiff guidance vs prior quarter and classify directionOpenAI
- LogicDrop filings with no guidance change
- OutputAppend guidance-delta rows to Coda trackerCoda
What it does
Runs a weekly sweep across your tracked competitors, finds anyone who filed since the last run, and compares the new filing's guidance and outlook language against the previous quarter on record. It writes a row only when guidance actually moved — raised, lowered, narrowed, or withdrawn — so the tracker stays signal, not noise.
When to use it
Use it when guidance direction is the metric you care about most and you want a clean, deduplicated change log rather than a summary of every filing. Good for finance and strategy teams building a longitudinal view of competitor confidence.
How it works
- 1A weekly schedule kicks off the sweep.
- 2Perplexity resolves which tracked companies filed in the past week and locates the filing URLs.
- 3Firecrawl pulls the new filing text.
- 4OpenAI diffs the new guidance language against the prior-quarter record and classifies the change direction.
- 5A logic gate discards filings where guidance is unchanged.
- 6Changed-guidance rows are appended to the Coda delta tracker with old-vs-new values.
Set it up
What you configure once, before turning it on.
- 1Connect PerplexitySearch-grounded answers with citations.
- 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.