MARKET RESEARCH
Earnings Guidance-Change to Linear Action Items
On a schedule, scrapes a competitor's latest earnings call, detects changes to forward guidance or strategic commitments.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled post-earnings run
- ActionFind + scrape transcript (Perplexity, Firecrawl)Firecrawl
- ActionExtract guidance/commitment changes + quotes (OpenAI)OpenAI
- LogicKeep only material changes
- OutputOpen Linear issues with quoted evidenceLinear
What it does
Converts a rival's earnings signals into tracked work. It scrapes the latest call, isolates changes in forward guidance and strategic commitments (raised/cut targets, new bets, abandoned initiatives), and for each material change opens a Linear issue with the quoted evidence and a suggested response owner, so competitive intelligence actually drives action instead of dying in a doc.
When to use it
Use it when your team needs to *do something* in response to competitor moves: re-price, accelerate a roadmap item, or brief leadership. Best for product and strategy orgs that already run in Linear and want competitive triggers to land in the same queue as their other work.
How it works
- 1A schedule fires after the competitor's call posts.
- 2Perplexity finds the latest transcript URL and Firecrawl scrapes it to text.
- 3OpenAI extracts guidance and commitment changes, each with a verbatim quote and suggested internal response.
- 4A logic step keeps only changes above a materiality threshold.
- 5For each surviving item, a Linear issue is created with the quote, context, and proposed owner.
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 LinearIssues, projects, cycles, triage.
- 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.