SALES

Cross-Team Usage Sprawl to Multi-Department Land

Detects when usage of a single-team account spreads across multiple departments via BigQuery email-domain and org-unit signals.

CategorySales
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionCount active departments per account in BigQueryGoogle BigQueryBigQuery
  • LogicKeep accounts spanning 3+ departments on a 1-team contract
  • ActionCreate department-expansion play in AttioAttio
  • OutputRoute play to AE in SlackSlack

What it does

Spots when a product that landed in one team has organically spread to other departments inside the same company, and packages that sprawl as a multi-department expansion play with the evidence to support a larger contract.

When to use it

Use this for land-and-expand motions where a single team's seat ends up serving an entire org. Ideal when usage data carries org-unit or department metadata and you run Attio as your CRM.

How it works

  1. 1A daily schedule starts the run.
  2. 2A BigQuery query groups active users by company domain and counts distinct departments or org units per account.
  3. 3A logic step keeps accounts where usage now spans three or more departments but the contract still covers one.
  4. 4An Attio step creates a department-expansion record with the department breakdown as proof points.
  5. 5A Slack step routes the play to the account owner with a suggested company-wide proposal.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect AttioReal-time CRM with structured data + powerful views.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.