IT OPS

Detect Overlapping Tools Paid For by the Same User

Scans Snowflake license data weekly for users holding seats in two or more tools that serve the same function.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery Snowflake assignments + Airtable category mapSnowflakeSnowflake
  • LogicFlag same-category tool overlaps per user
  • ActionRecord overlap decisions in AirtableAirtableAirtable
  • OutputRoute consolidation choice to team leads in TeamsMicrosoft Teams

What it does

It finds people paying twice for the same job — a user with both Tool A and Tool B in an overlapping category — and pushes the decision to consolidate down to the team lead. Redundant-tool spend is invisible in per-tool dashboards; this surfaces it.

When to use it

Use it after a merger, a reorg, or any period of unmanaged tool sprawl where multiple teams bought competing tools. It targets the category overlap that simple inactivity reports miss.

How it works

  1. 1A weekly schedule starts the run.
  2. 2It queries Snowflake for every user-to-tool assignment and joins against a tool-category map stored in Airtable.
  3. 3A logic step flags users holding more than one seat in the same category.
  4. 4For each overlap it computes the cheaper-to-keep option and the savings from dropping the other.
  5. 5It posts a per-team-lead summary to Microsoft Teams asking which tool to keep, and records the decision back in Airtable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  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.