SALES

Seat-Limit Expansion Play from Product Telemetry

Watches BigQuery product usage and, when an account crosses 90% of its licensed seats, builds a warm seat-expansion play in Salesforce with proof points and alerts the owning AE…

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionQuery seat-utilization ratios in BigQueryGoogle BigQueryBigQuery
  • LogicKeep accounts above 90% with no open expansion opp
  • ActionCreate expansion opportunity with proof points in SalesforceSalesforce
  • OutputDM the owning AE with the play in SlackSlack

What it does

Detects when a paying account is running out of headroom on its seat license and turns that signal into a ready-to-run expansion conversation for the account executive — complete with the numbers that justify the upsell.

When to use it

Run this when your product-led growth motion has reliable seat telemetry in a warehouse and you want AEs to reach out before customers hit a hard limit and churn out of frustration. Ideal for teams selling per-seat licenses where natural team growth is the primary expansion lever.

How it works

  1. 1A daily schedule kicks off the run.
  2. 2A BigQuery query computes active-seat-to-licensed-seat ratio per account over the trailing 30 days.
  3. 3A logic step keeps only accounts above 90% utilization that are not already in an open expansion opportunity.
  4. 4A Salesforce step creates an expansion opportunity and attaches proof points (current seats, 30-day growth rate, projected overage date).
  5. 5A Slack step direct-messages the account owner with the play summary and a link to the opportunity.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  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.