Signals to meetings

Find which signals create meetings

Every meeting started with a reason to write. Trace them back and the signals that actually produce pipeline separate from the ones that only produce activity.

Try in Unify

By Unify Documentation reviewed September 18, 2026

The conversation

Sample accounts and numbers, for illustration

YouFor the last two quarters, trace every meeting and every opportunity back to the signal or combination of signals that started the outreach, rank signals by meetings per hundred people contacted, show which combinations beat their parts, and tell me which signals we should stop working.

Unify

3 checks · CRM, mailbox and signal history

Read every meeting and opportunity created in the last two quarters from Salesforce and matched each to the sequence and reply that produced it.
Read the signal or combination recorded on each outreach: website intent, hiring, funding, leadership change, or more than one.
Counted meetings per hundred people contacted per signal and per combination, with the sample size on each.

Two hundred and eighteen meetings in two quarters traced back to a signal. Leadership changes and stacked signals lead by rate; website intent alone leads by volume and trails by rate.

218
meetings traced: 4,910
people contacted: 4.4
meetings per 100: 3
signals below 2 per 100

1New leader + hiring in the same team11.2 per 10038 meetings from 340 contacted
2Leadership change alone8.1 per 10052 meetings from 640 contacted
3Funding round5.6 per 10041 meetings from 730 contacted
4Hiring alone3.9 per 10047 meetings from 1,200 contacted
5Website intent alone1.9 per 10038 meetings from 2,000 contacted

Meetings and contacts are counts from the CRM and the outreach record. The rate is arithmetic. Why a signal converts is the reading, and it comes next.

YouWhich combinations beat their parts, and what should we stop working?

Unify

One combination clearly beats its parts. Two signals should be stacked rather than worked alone, and one should stop unless it arrives with something else.

Q1Website intent worked alone1,100 contacted, 19 meetings. Reps wrote to every visitor. 1.7 per 100.
Q1Leadership change worked alone310 contacted, 24 meetings. 7.7 per 100.
Q2New leader plus hiring, stacked340 contacted, 38 meetings. 11.2 per 100, above either alone.
Q2Website intent plus any other signal420 contacted, 26 meetings. 6.2 per 100, three times intent alone.

Stack, do not choose: Website intent is worth 1.9 per 100 alone and 6.2 per 100 when it arrives with a hire or a leader. It is a multiplier, not a signal to work on its own.
Stop: Website intent alone, at 2,000 contacted for 38 meetings. Hiring alone is borderline at 3.9 and improves sharply when a new leader is in the same team.
Sample sizes: Every line above has more than 300 contacted. Funding at 730 is the smallest that still supports a decision; nothing under 100 is ranked.

YouWhich signals get us meetings with VPs, and which only reach managers?

Unify

Leadership signals reach VPs: more than half of those meetings were with a VP or above. Hiring alone mostly gets managers, who reply but rarely own the budget.

Signal	Meetings	VP and above	Director	Manager
New leader + hiring	38	21	13	4
Leadership change alone	52	27	18	7
Funding round	41	12	17	12
Hiring alone	47	6	14	27

Persona is the title of the main attendee on the meeting in Salesforce. Replies that never became a meeting are not counted.

YouNow only this month: what started the meetings we booked, and how long did each take from signal to meeting?

Unify

Thirty-one meetings were booked this month, and 27 trace to a signal. Leadership changes turn into a meeting fastest, and funding takes nearly three weeks.

1Leadership change alone9 days7 meetings this month
2New leader + hiring11 days9 meetings this month
3Hiring alone16 days5 meetings this month
4Funding round20 days6 meetings this month

Days are the median from the date the signal was recorded to the date the meeting was booked. One month is a small sample, so it sits beside the two-quarter ranking and does not replace it.

YouWrite it up as the playbook for next quarter and keep the report running.

Unify

The playbook is one page with the numbers behind each line. The attribution reruns monthly so the ranking moves as the team does.

Playbook · Q4

Work: a new leader with hiring in the same team first, leadership changes second, funding third. Stack: website intent onto any of those, never alone. Stop: website intent alone, hiring alone outside the target team. Review monthly.

Set up

Monthly attribution Meetings and opportunities are traced to signals on the first of each month, and the ranking is written to the reporting view.
Plays updated The website-visitor play now requires a second signal before it enrolls anyone. The leader-plus-hiring combination has its own play.
Sample guard Signals with fewer than 100 people contacted in the window are shown but not ranked.

The playbook says which signals produced meetings. It does not say a rep should ignore a visitor who asks for a demo.

Signal attribution, with and without Unify

Everyone knows which signals feel good. Fewer know which ones booked the meeting.

Without Unify	With Unify
Signals are judged by how many accounts they surface, not by how many meetings they made	Every meeting and opportunity is traced back to the signal, or combination, that started the outreach
The meeting is in the CRM and the signal is in a tool; nobody joins the two	Signal history, outreach, reply and meeting sit on one account timeline
Two signals on one account get credited twice, or not at all	Combinations are counted as combinations, so stacked signals show their real rate
The team keeps writing off the signal that feels strongest, whatever it produced	The ranking is meetings per hundred outreaches by signal, which is what to write off next

Start from this prompt

Make it your own in Unify, then review the results.

Starting promptEdit in Unify

For the last two quarters, trace every meeting and every opportunity back to the signal or combination of signals that started the outreach, rank signals by meetings per hundred people contacted, show which combinations beat their parts, and tell me which signals we should stop working.

Try in Unify

What else you can ask for

The walkthrough is one path through this workflow. These are the turns people take most often.

How it changes by who you sell to

Software: Software teams stack website intent, hiring and funding on the same account and cannot tell which one got the reply. Ask for meetings by signal combination, not by single signal, and for the reply rate when intent arrived within a week of a hire.
Financial services: At banks and insurers the meetings come from a new leader or a regulatory change months after the signal. Ask for a 120-day window between signal and meeting, and weight leadership changes separately from hiring.
Healthcare: Health-system meetings follow budget cycles, so a signal in spring produces a meeting in autumn. Ask Unify to attribute within the fiscal year and to separate department-level hiring from system-level announcements.
Manufacturing: Plant expansions and new facilities produce meetings; funding rarely does. Ask for meetings by signal type across the last two quarters, and for the segment where expansion news converted best.
Professional services: Firms book meetings off partner moves and new offices, not off website visits. Ask for meetings by signal for the partner-level personas only, and drop website intent from the ranking if it never converts there.

Setup

Connect what this workflow uses

Each guide covers the connection, what Unify reads and writes, and what to check before the first run.

Questions about this workflow

How does Unify know which signal started a meeting?

Each outreach in Unify records the signal or play that triggered it. Meetings and opportunities from the CRM are matched to the outreach through the enrollment and the reply, so the signal is read from the record rather than inferred.

What about meetings that came from more than one signal?

They are counted as a combination, not credited to each signal. Combinations are ranked beside single signals, so a pair that beats its parts shows up as one line with its own rate.

Does it measure revenue?

It measures meetings and opportunities created, which the CRM can support. Closed revenue depends on the sales cycle and is not attributed to a signal here; the prompt can add it when the cycle is short enough to be honest.

How much history does it need?

Two quarters is enough to rank signals with more than about fifty outreaches each. Smaller samples are shown with their size so nobody stops working a signal on the strength of three meetings.

Find which signals create meetings