Jipup CRM workflows · Buying signals
Buying signals HubSpotSalesforcePipedrive Native integration with HubSpot and Salesforce, and other CRMs

Buying signals happen every week. None of them reach your CRM.

Your best customer contact just joined a prospect. The role you sell to was just filled at a target account. Your sponsor, meanwhile, has left. All three events are public and dated, and none of them leaves a trace in your CRM. Agents read them, create the record and trigger the task.

your CRM · tracked accounts
AccountSignalWhat the agent writes
Gusto · prospect - -
Notion · target account - -
Ramp · customer - -
Rippling · target account - -
Deel · customer - -
2 opportunities · 1 risk · 3 tasks created 5 accounts. No signal surfaced so far.
The problem · 1

The buying signals your CRM never records.

A white paper downloaded, a pricing page visited: those are strong signals, and a form writes them into your CRM, where someone eventually follows up. The five below are just as strong, and nothing writes them anywhere: they are people moving, and it all happens outside your CRM.

The problem · 2

The signal isn't missing. It's somewhere else.

It is public, it is dated, and it never reaches the person who could act on it. Here are the four reasons it gets lost on the way. Then a fifth, which isn't an opportunity at all.

01

The signal lives on LinkedIn, not in your CRM

The profile says "VP Marketing at Gusto, since March". Your record says "Marketing Manager at Ramp". Both are readable; only one of them triggers a sales action, and it isn't the one that's true.

profile VP Marketing · Gusto · March 2026
CRM Marketing Manager · Ramp
no task, no owner notified

What it costs: a target account where you already have an ally, and where you keep prospecting cold. Keep your contacts' job titles up to date in your CRM →

02

You find out after the decision

A new decision-maker reshuffles things in their first months: incumbent vendors, tools, contracts that used to renew without discussion. After that window, everything is signed again. Hearing about their arrival a year later means hearing that a competitor was chosen.

starts the role September
you find out the next August, by chance
decision made ten months ago

What it costs: the only window where a fresh budget was looking for a solution, the one where you had nothing left to prove.

03

A job change alert is not a CRM record

Alerts already exist: a notification, an export, a watch list in a spreadsheet. But no record gets created, no owner gets assigned, no task gets scheduled: what isn't in the CRM doesn't get worked by anyone.

alert "14 new hires this week"
records created 0 · tasks 0
read once, never reopened

What it costs: a monitoring tool you pay for, read on Monday, and that books no meetings.

04

The target account is empty

The company record exists, the strategic account list exists, and there are no contacts in it, or only an intern who left in 2024. There is nobody for the signal to attach to.

account Notion · 2026 target
contacts 0
watched, never contacted

What it costs: a target account list that does nothing, because an account doesn't pick up the phone. Find the email and mobile of the contacts you add →

05 · a different kind

And the reverse: the signal you'd rather not get

The same event, read defensively. The person who chose you, who defended you in the buying committee and renews every year, has just left the account. Your usage hasn't moved, but your point of contact no longer exists. It is the earliest churn indicator, and it usually shows up as a cancellation notice.

What it's worth: a few months to win over their successor, instead of a non-renewal email. Same agent, same scan, different action.

Rachel Nguyen · sponsor
yesterday Head of People Ops · Deel
today no current role at Deel
The problem · 3

A buying signal has an expiry date.

That is what sets it apart from missing data. A missing email address stays missing until someone looks for it; a new hire doesn't stay new. The signal is worth something while the person decides who they will work with, and nothing after.

A decision-maker joins a target account: their first twelve months Illustrative diagram · no duration is fixed: detection runs as often as you schedule it
Starts the role Budget committed What happens on their side they make their choices renewals Without monitoring, what you know by chance at best, once the decision is made With the agent, what you know you know, and so does your CRM on the first run after the arrival: record created, task sent month 0 3 months 6 months 9 months 1 year
The window: they make their choices You don't know they've arrived An event, outside your CRM

The durations are an example; the mechanism isn't. A buying signal doesn't decay like a wrong value you eventually fix: once the window has passed, it is worth nothing, even fixed. That is the one reason run frequency matters more here than anywhere else.

What you can do about it

Champion tracking and new hire detection, with a CRM record at the end.

Two workflows read people's moves: one starts from your contacts, the other from your accounts. Both end in the same place: an up-to-date record in your CRM, a note that explains why, and a task on the right rep's desk. You can run both.

LinkedInClaudeHubSpotSalesforce

Answers The signal lives on LinkedIn · A job change alert is not a CRM record · The signal you'd rather not get

Job change tracking

Signals · Update

It starts from your contacts: the people who already know you. Record by record, it checks whether each person still holds the role your CRM has on file. When they've moved, it writes the change and flags it both ways: the opportunity at their new employer, the risk at the old one.

  • Detects a move to a new employer, an internal promotion, and a departure with no new role
  • Qualifies the new role against your personas and ICP before triggering any action
  • Creates the sales task, assigned to the record owner, due in 48 hours
  • Writes a note on the contact, and one on the company they just left
  • Repoints the primary company to the new employer
  • Finds the email and mobile at the new company, optional

Qualification reads criterion by criterion, with no score: a persona (department × level) and an ICP segment must both match. Off target, the agent updates the record and stops there. It doesn't invent a task for a signal that isn't one.

LinkedIn Sales NavigatorClaudeHubSpotSalesforce

Answers You find out after the decision · The target account is empty · An internal promotion creates the role you sell to

New hire detection

Signals · Prospecting

It starts from your accounts: a list of companies, and the roles you sell to. On every run, it surfaces the people who recently started in those roles at those companies, including people who were never in your database, and pushes them into your CRM.

  • Source: a company segment from your CRM, or your target account list
  • Several roles per agent, with their French and English variants and gendered title forms
  • Time-in-role slider, from 1 to 12 months
  • Internal promotions are opt-in: the role is new, the person isn't
  • Creates the missing contact, updates the existing one, never a duplicate
  • Note on the contact, and a note on the company they left if it's in your CRM
  • Email, mobile and task optional, as in Job change tracking

The same arrival is never delivered twice: the agent remembers what it has already surfaced, by person, by company and by start date. If the person changes roles again later, that's a new event and it surfaces again.

Four workflows in all · Job change tracking and New hire detection on this page, plus CRM enrichment and Duplicate detection and merging

How it works

You describe who matters. Job change alerts run on their own.

OAuth connection to your CRM, once. Then: which accounts, which roles, how often, and what the agent is allowed to write. The screens below are from New hire detection, the newer of the two workflows.

01 The roles you sell to, in every variant, because LinkedIn doesn't do any of that for you.

Agent settings · New hire detection All changes are saved.
Schedule · Frequency
Manual Weekly Monthly Cron
Source · Which companies the agent runs on
HubSpot segment · 2026 target accounts312 companies
This agent starts from companies, not contacts: it's the only workflow that does.
Target role · VP Sales
VP Sales Head of Sales Chief Revenue Officer Directeur commercial Directrice commerciale Sales Manager Sales Assistant Intern
French and English variants, masculine and feminine forms, and exclusions are suggested; you tick them. "Directeur" and "Directrice" are two separate searches on LinkedIn: searching for one never returns the other.
Time in role
3 months
From 1 to 12 months. Wide on the first run to catch up on existing hires, tighter afterwards.
Scope
Include internal promotions
Contact location · United Statesoptional
With an internal promotion, the role is new, not the person: they're already at the company, and often already in your CRM under their old title.
Volume per run
All companies in the source≈ 312 credits
What it does with each arrival
Note on the contactfree
Note on the company they leftfree
Task for the account ownerfree
Work email+5 credits / record
Mobile+50 credits / record
Creating or updating the contact record isn't optional: it's what the agent does. Nothing is charged when an enrichment finds nothing.
Run Save 1 credit per company scanned

02 One run, company by company, and most of them return nothing, which is normal.

Activity · New hire detection Trigger: scheduled
312companies scanned
9arrivals kept
6records created
0duplicates created
HubSpot objectSignalStatusCredits
Notion Emily Carter, VP Sales since September 2026 record created · note · task Succeeded 1
Gusto Jason Reed, Head of Sales since August 2026 existing record updated Succeeded 1
Airtable Internal promotion: Megan Brooks takes over as head of sales note on the contact Succeeded 1
Brex Arrival already surfaced on the previous run, not delivered again Succeeded 1
Ramp No arrival in the target roles Succeeded 1

A scanned company costs one credit whether or not it returns an arrival: you pay for the search, not the result. Everything after detection (record, notes, task) is free. Each row opens on the details: the role recognised, its start date, the profile, and a direct link to the HubSpot record.

03 What lands on the rep's desk, here from Job change tracking, with the qualification verdict.

New task · Sarah Mitchell contact owner
Subject
Follow up - Job change detected (in target) TO DO
Body
JOB CHANGE: Sarah Mitchell → VP Marketing at Gusto (since March 2026), confidence 94%. Customer contact at Ramp until February. Qualification: QUALIFIED. Persona Marketing · executive; segment "B2B SaaS, United States, 200 to 500 employees".
Due date
In 2 days D+2
And the record follows: job title, company, associated company, location, profile URL, and a note on Ramp saying your contact has left.
The math

What a buying signal is worth once it's worked, with your numbers.

Seven values are enough. Change one and everything recalculates. The math covers only one of the signals on this page: your champions changing companies, the only one whose value we can honestly put a number on. New hires at your target accounts come on top, without being counted.

roi-buying-signals-job-change Instant recalculation
Your database We count people, not companies: two decision-makers at the same customer are two champions to track.
accounts

Customers and former customers: every account where someone said yes.

people

Decision-makers, sponsors, key users: the people whose departure changes something.

%

Across our customers' databases, we observe 15 to 30% of B2B contacts changing jobs each year, depending on the segment. That is also the share that goes stale if nobody updates it.

Your sales model The two default rates are the ones we observe at our customers on reactivated champions.
€

Value of a signed contract, over the first year.

%

Well above a cold close rate: the relationship exists, and what you sell has already proven itself with them.

days

From first contact to signature, on a regular deal.

%

On reactivations, we see the cycle cut in half: there is nothing left to prove.

Optional Leave it empty to see the gain only. Filled in, the math shows the multiple and how many deals cover the year.
€

Subscription and credits used over twelve months.

Champions who move

-

Pipeline to reactivate

-

per year, if each one is worked

Expected revenue

-

Sales cycle

-

Return on investment

-

How we calculate

Nothing else is added: no productivity multiplier, no assumed growth, and none of the new hires detected at your target accounts. Pipeline to reactivate and expected revenue don't add up: the second is the share of the first that you sign.

Nothing is sent: the math runs in your browser.

The same calculator also lives on its own page: the standalone ROI calculator for job change signals → It uses the same parameters, so the link copied above keeps your values on both pages.

The default rates in this calculator (job changes at the top of the 15 to 30% range we see each year, a 40% close rate, a sales cycle cut in half) are observed across 50+ customer databases. The Ogo Security case study: a 68% close rate on reactivated champions →

Finovox Ogo Security AssessFirst Ubaq LogiSpear

We build the product with the best Revenue teams.

Getting started

The simplest way to see it is to run it on your customer accounts.

-champions to find again in year one
-in expected revenue
-head start on every deal

Based on the values you just entered. You get 250 free credits when you sign up, no credit card: enough to scan a first list and compare what it surfaces with this line. A scanned contact costs 3 credits, plus 3 if its LinkedIn URL has to be found, once per contact, since the URL is then written to your CRM. A company scanned by New hire detection costs 1 credit per run. Notes, records and tasks are free. See pricing and credit packs →

Start for free Book a demo 250 free credits, no credit card. Connect your CRM in two clicks.
Native integration with HubSpot and Salesforce · and other CRMs
HubSpot Salesforce Pipedrive