FINANCE

Flag premium-tier seats that only use basic features

Scans BigQuery feature-usage data for users on premium license tiers who only touch basic features.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule starts tier review
  • ActionQuery feature usage for over-tiered seats in BigQueryGoogle BigQueryBigQuery
  • LogicRequire consistent basic-only usage to qualify
  • ActionEmail app owner the downgrade-candidate listOutlook
  • OutputLog each downgrade candidate as a ClickUp taskClickUpClickUp

What it does

Finds the subtler form of license waste: people sitting on an expensive premium tier while only ever using basic functionality. It analyzes feature-level usage in BigQuery, identifies premium seats that never exercise premium features over a lookback window, and routes the downgrade candidates to the app owner.

When to use it

Use this when full deprovisioning isn't right but the seat is over-tiered. Tier downgrades recover real money without removing anyone's access, making them an easy win that pure idle-seat scans miss entirely.

How it works

  1. 1A monthly schedule starts the tier review.
  2. 2BigQuery queries feature-usage events to find premium-tier users whose activity stayed within the basic feature set.
  3. 3A logic step requires a minimum lookback of consistent basic-only usage to avoid false positives.
  4. 4Outlook emails the app owner a consolidated downgrade-candidate list with per-seat tier savings.
  5. 5Each candidate is logged as a ClickUp task so the downgrade decision is tracked to completion.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect ClickUpDocs + tasks + chats in one workspace.
  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.