Brief AEs on a new lead's pay band before the first call
When a new HubSpot contact is created, an agent looks up the typical pay band for their role and city, then drops a budget briefing on the contact's timeline.
Integrations
HubSpot
Job Salary Data
Type
Categories
- Sales
Build an agent workflow that briefs sales reps on a new HubSpot contact's likely compensation band before they make first contact, so the AE can calibrate budget talking points.
Trigger: a HubSpot webhook fires whenever a new contact is created. The webhook payload includes the contact id and the contact properties.
When the trigger fires, the agent should:
1. Read the contact's job title and location (city, state, or country) from the HubSpot payload. If either is missing or blank, stop immediately and do nothing. Do not create a note. Do not call the salary API.
2. Call Job Salary Data's Get Job Salary Estimate operation with the contact's job title and location. Use the response's data array (it can return multiple publisher estimates) and pay attention to the confidence field on each estimate.
3. Interpret the response. Surface the median pay band in plain dollars. Make a judgment on whether the title at that pay band is typically an individual contributor or a budget owner (for example, Director, VP, Head of, C-level usually owns budget; Senior IC, Manager-level sometimes influences purchase decisions but rarely signs). Then propose two or three concrete talking points that match the seniority signal. A good example: 'VP Engineering in SF at the 300K to 400K median tends to own tooling budget up to 50K without procurement, so price-anchor around that ceiling and bias toward a same-week pilot.'
4. If the response's confidence is low, call that out in the note. Frame the pay band as a rough estimate rather than a hard reference. Do not invent precision the data doesn't support.
5. Create a HubSpot Note (Create Note operation) and associate it with the contact id from the webhook payload. The note body should be short and scannable: a one-line pay band summary, a one-line seniority and budget-authority read, and two to three bullet talking points. Title the note something like 'Comp-based budget brief' so it's obvious in the timeline.
Constraints: do not message the rep directly, do not update the contact's properties, do not create tasks or deals. The only side effect is one HubSpot Note attached to the contact. Skip silently when title or location is missing. Treat a low-confidence salary estimate as a reason to soften the language, not a reason to abandon the note.
What it does
- Watches HubSpot for newly created contacts and reads their job title and city or region from the contact record.
- Looks up the typical pay band for that role in that location so your team has a real number to anchor budget conversations.
- Decides whether the role usually owns budget at that level, or is more likely an individual contributor, and writes two or three calibrated talking points for the AE.
- Posts the briefing as a Note on the contact's HubSpot timeline so it shows up the moment your rep opens the record.
What you’ll need
- A HubSpot account where you can connect a CRM login and let an agent create notes on contacts.
- A Job Salary Data subscription (the free plan covers 50 lookups per month, which is plenty for testing).
- Contacts that arrive with a job title and a city, state, or country filled in. The agent skips contacts that are missing either field.
How to customize it
- Change which contact properties feed the lookup. The default uses job title and city, but you can point it at lifecycle stage, country, or a custom property your team already populates.
- Tune the briefing voice. Ask for shorter notes, a specific structure (pay band, seniority signal, two talking points), or add prompts unique to your sales motion.
- Filter which contacts trigger the workflow. Limit it to a specific pipeline, contact owner, or lifecycle stage so you don't burn lookups on contacts that won't get a first call.
- Swap the destination. Instead of a HubSpot Note, send the briefing to the contact owner over Slack or email if your team lives outside the CRM.
Use cases
- Lead Enrichment
- Notifications & Alerts
