MARKET RESEARCH
Quarter-Over-Quarter Guidance Change Detector
After each new earnings call for a tracked company, compares the fresh guidance against last quarter's, flags raises, cuts, and reaffirmations, and posts a diff with the exact…
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires on new earnings callHTTP webhook
- ActionPerplexity extracts new guidance metrics and phrasingPerplexity
- LogicDiff against prior quarter and classify each metric
- ActionWrite guidance diff to Coda history tableCoda
- OutputPost change summary to SlackSlack
What it does
When a tracked company posts a new earnings call, this workflow extracts the forward guidance and diffs it against the guidance captured last quarter. It labels each metric as raised, lowered, reaffirmed, or newly introduced, and surfaces the precise wording change so you can judge tone, not just numbers.
When to use it
Use it when guidance trajectory is the heart of your thesis and you want an objective record of how management's outlook is shifting over time — without re-reading two transcripts side by side every quarter.
How it works
- 1A webhook fires when your transcript feed flags a new call for a tracked ticker.
- 2Perplexity extracts the new quarter's guidance metrics and exact phrasing.
- 3A logic step loads the prior quarter's stored guidance and computes the metric-by-metric diff.
- 4Each metric is classified as raise, cut, reaffirm, or new.
- 5The structured diff is written back to a Coda guidance-history table.
- 6A formatted change summary is posted to Slack for the coverage team.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PerplexitySearch-grounded answers with citations.
- 3Connect CodaDocs, packs, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.