MARKET RESEARCH
Category Glossary Drift Reconciliation
Compares your internal category glossary against current Brave Search usage and flags terms where the market's meaning has drifted from your definition.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled reconciliation run begins
- ActionRead current glossary from CodaCoda
- ActionFetch current usage via Brave SearchBrave Search
- ActionRate definition drift with OpenAIOpenAI
- LogicKeep terms over drift threshold
- OutputOpen Linear task per drifted termLinear
What it does
Keeps your messaging glossary honest. It reads your maintained glossary of category terms, checks how each term is currently used in the wild via Brave Search, and detects drift — cases where the prevailing definition, connotation, or scope no longer matches your internal entry. For every drifted term it files a Linear task with the evidence so an owner can revise the entry.
When to use it
Use it when your brand language is documented but the market keeps moving — terms you defined a year ago now mean something different to buyers. Ideal for content and product-marketing teams who own a living glossary.
How it works
- 1A scheduled run begins the reconciliation.
- 2The current glossary is read from Coda.
- 3Brave Search returns current usage snippets for each glossary term.
- 4An OpenAI step compares prevailing usage to your stored definition and rates drift.
- 5A logic step keeps only terms exceeding the drift threshold.
- 6A Linear task is opened per drifted term with usage evidence and the current definition.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect Brave SearchWeb, news, image, video search.
- 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.