MARKET RESEARCH
Tech-Stack Shift Detector from Job Descriptions
Parses the skills and tools named in competitor job descriptions, detects when a new technology starts appearing across multiple reqs.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule kicks off the scan
- ActionApify collects full job-description textApify
- ActionOpenAI extracts named technologies from each JDOpenAI
- ActionCompare against prior stack profile in SnowflakeSnowflake
- LogicKeep only tools crossing the emergence threshold
- ActionWrite research brief to NotionNotion
- OutputSlack summary of the stack shiftSlack
What it does
Job descriptions list the exact tools a company expects new hires to use. When a competitor suddenly requires a technology they never mentioned before, it signals a platform migration, a new architecture bet, or a product direction. This workflow extracts named tools from JD text and tracks first-and-rising mentions per competitor.
When to use it
Use it when a competitor's technical direction is strategically relevant, for example to spot a rival adopting a new AI stack, switching cloud providers, or moving to a new data platform.
How it works
- 1A weekly schedule kicks off the scan.
- 2Apify collects full job-description text for each tracked competitor.
- 3OpenAI extracts a normalized list of technologies and tools mentioned in each JD.
- 4Mention counts are compared to the company's prior stack profile in Snowflake to find new or sharply rising tools.
- 5A logic step keeps only technologies crossing the emergence threshold.
- 6A research brief is written to Notion and a summary is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SnowflakeWarehouses, queries, shares.
- 4Connect NotionPages, databases, comments.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Market Research workflows
Weekly Materiality-Ranked Filing Digest by Email
Each Friday, aggregates the week's regulatory filings across the coverage universe, ranks them by materiality.
Earnings Keyword-Spike Alert into Linear
Scans new earnings-call transcripts for a set of strategic keywords you care about, and when a competitor's mention frequency spikes above its historical baseline.
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.
Discover Adjacent Segments from BigQuery and Rank Expansion Bets
On a schedule, scans BigQuery public industry data for fast-growing NAICS sectors adjacent to your core segments, scores them as expansion bets.
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.
Cross-Competitor Theme-Shift Analyst
An agent that gathers the latest earnings transcripts across all tracked competitors, compares this quarter's themes against the prior quarter stored in Coda.
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.