Spot bursts of engineering hiring

Every day, counts the engineering roles each target account opened in the last two weeks.

Use this workflowHow it works

9 stepsDaily check

The workflow diagram

Spot bursts of engineering hiring: workflow diagramThe 9 steps of this workflow, from its trigger to the final step.Every day at 6:00 AM, for each target account. Scores, schedules and toolsBWWHENTRIGGEREvery day at 6:00 AM, foreach target accountScores, schedules and toolsEngineering roles opened in the last 14 days. Paid per resultDATHENEngineering roles openedin the last 14 daysPaid per resultCount the engineering roles. Waits and logicBWTHENCount the engineeringrolesWaits and logicSave the count. Audiences and recordsBWTHENSave the countAudiences and recordsA burst?A burst?Already flagged?Already flagged?Add to Engineering hiring burst. Audiences and recordsBWTHENAdd to Engineering hiringburstAudiences 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 hereThis path stops hereYesNoYesNoYesNo
This is the workflow BrandWell builds on your canvas when you add it. You can change any step.

What this workflow does

Every day, counts the engineering roles each target account opened in the last two weeks. When the count passes your burst size, the account is saved once to a burst audience, marked if it is also researching your topic, and the owner is alerted.

Why it works. A burst of engineering hires means a funded build-out, and teams in build-out mode buy tools and services fast.

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

How it works

It starts: Every day at 6:00 AM, for each target account, or run it now.

  1. 1

    Engineering roles opened in the last 14 days

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

  2. 2

    Count the engineering roles

    AIMEE classifies, extracts or writes using your instruction.

  3. 3

    Save the count

    Saves what was found onto the record.

  4. 4

    A burst?

    If yes, it goes on to "Already flagged?". If no, it stops for that person.

  5. 5

    Already flagged?

    If yes, it stops for that person. If no, it goes on to "Add to Engineering hiring burst".

  6. 6

    Add to Engineering hiring burst

    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
  • 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.

$5.32 typical per 100 account checks, up to $5.32

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.

  • Engineering roles opened in the last 14 days

    • PredictLeads

Related workflows