Detect technology adoption or removal

Each week, re-reads the tech stack at your target accounts, works out what was added and removed, and flags accounts that added a tool that works with you or dropped a competitor.

Use this workflowHow it works

9 stepsWeekly check

The workflow diagram

Detect technology adoption or removal: workflow diagramThe 9 steps of this workflow, from its trigger to the final step.Every Tuesday, for each target account. Scores, schedules and toolsBWWHENTRIGGEREvery Tuesday, for eachtarget accountScores, schedules and toolsRead the current tech stack. Paid per resultDATHENRead the current techstackPaid per resultWhat was added and removed?. Waits and logicBWTHENWhat was added andremoved?Waits and logicSave the stack and changes. Audiences and recordsBWTHENSave the stack andchangesAudiences and recordsAn opportunity?. Waits and logicBWTHENAn opportunity?Waits and logicOpportunity?Opportunity?Add to Stack changes. Audiences and recordsBWTHENAdd to Stack changesAudiences and recordsResearching your topic too?Researching yourtopic too?Mark as in market. Audiences and recordsBWTHENMark as in marketAudiences and recordsAlert the owner. AIMEEAITHENAlert the ownerAIMEEThis path stops hereThis path stops hereYesNoYesNo
This is the workflow BrandWell builds on your canvas when you add it. You can change any step.

What this workflow does

Each week, re-reads the tech stack at your target accounts, works out what was added and removed, and flags accounts that added a tool that works with you or dropped a competitor. In-market accounts get priority.

Why it works. A stack change is a decision in motion, and reaching out while the team is still choosing beats arriving after the contract is signed.

Nothing is sent outside your team, so nothing waits for approval.

How it works

It starts: Every Tuesday, for each target account, or run it now.

  1. 1

    Read the current tech stack

    Runs a BrandWell data lookup and brings the result back into the workflow.

  2. 2

    What was added and removed?

    AIMEE classifies, extracts or writes using your instruction.

  3. 3

    Save the stack and changes

    Saves what was found onto the record.

  4. 4

    An opportunity?

    AIMEE classifies, extracts or writes using your instruction.

  5. 5

    Opportunity?

    If yes, it goes on to "Add to Stack changes". If no, it stops for that person.

  6. 6

    Add to Stack changes

    Saves the people to an audience you can use anywhere.

  7. 7

    Researching your topic too?

    If yes, it goes on to "Mark as in market". If no, it goes on to "Alert the owner".

  8. 8

    Mark as in market

    Saves what was found onto the record.

  9. 9

    Alert the owner

    AIMEE tells the right person, with the context they need.

What you need

  • Workflow Wallet funds for paid lookups
  • MarketPulse in your BrandWell plan
  • AIMEE in your BrandWell plan
  • A list of target accounts
  • Your competitors
  • A MarketPulse topic

What it costs

Paid steps are charged per result from your Workflow Wallet, and you set the limit.

  • Assumes plan with MarketPulse intent data enabled. Subscription fees are separate. Pulls use your plan allowance; extra pulls cost more unless explicitly included below.
  • Assumes AIMEE is already enabled in your plan. Subscription fees are separate.
  • Execution estimates are not a total campaign price. External tool subscriptions, model usage, advertising spend and delivery costs are separate unless explicitly itemized.

$1.19 typical per 100 checks, up to $1.19

Free sources run first when they can answer. You see a price before anything paid runs. Estimates use current customer prices.

Data partners

Free sources run first, then the rest in the order this workflow tries them.

  • Read the current tech stack

    • Tomba

Related workflows