MARKET RESEARCH
Geo-Expansion Signal from Job Locations
Aggregates the office and remote-eligible locations across competitor job postings, detects a new city or country appearing.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the analysis
- ActionApify scrapes postings and extracts each role locationApify
- ActionNormalize and load location rollups into SnowflakeSnowflake
- LogicIsolate net-new cities or countries vs. footprint
- ActionOpenAI summarizes which functions lead the entryOpenAI
- OutputSlack report of new markets and entry patternSlack
What it does
The location field on job postings is an underused tipoff: when a competitor starts posting roles based in a city where they had none, they are usually opening a market. This workflow rolls up posting locations per competitor, compares against their established geo footprint, and flags new markets.
When to use it
Run it when geographic expansion by rivals matters to your planning, for example to anticipate a competitor entering a region where you currently have an open field.
How it works
- 1A weekly schedule starts the analysis.
- 2Apify scrapes current postings and extracts the location of each role.
- 3Locations are normalized and aggregated per competitor, then loaded into Snowflake.
- 4A logic step compares this week's location set to the historical footprint and isolates net-new cities or countries.
- 5For each new geo, OpenAI summarizes which functions are being hired there (sales-led entry vs. engineering hub).
- 6A Slack message reports each competitor's new market and the likely entry pattern.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect OpenAIModels, embeddings, files.
- 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.