Outbound Kitchen

Outbound Kitchen

Share this post

Outbound Kitchen
Outbound Kitchen
6 Buying Signals That Double Your Meeting Rate

6 Buying Signals That Double Your Meeting Rate

Ranked by timing impact + detection ease.

Elric Legloire - Outbound Chef's avatar
Elric Legloire - Outbound Chef
Aug 10, 2025
∙ Paid
6

Share this post

Outbound Kitchen
Outbound Kitchen
6 Buying Signals That Double Your Meeting Rate
1
Share

In outbound, you control who you target. You can't control when they're “ready to buy”.

But the problem is most “signals” advice creates noise.

Reps chase everything.

Meanwhile, accounts experiencing acute pain, the ones who'd sign this quarter, slip through unnoticed.

After 3 years of tracking signals, I've identified the 6 that actually increase your booking rate.

Below: The 6 exact signals to track, why they work, and implementation templates you can deploy today.


Bonus for paid subs: I share an AI prompt to generate niche-specific signals your competitors aren’t tracking.


The Top 6 Signals (ranked)

How I ranked these

  1. Tightest correlation with purchase timing

  2. Ease of detection (low lift, reliable)

  3. Time-to-meeting (how fast a rep can convert)


1) Former customers & alumni users

Why it works

  • Trust + known playbook: They’ve seen the movie; evaluation risk drops.

  • Political cover: Champions can say “I shipped this before,” which shortens consensus.

  • Faster proof: Prior configs/results exist; you can tailor and reuse.

How to run:

  • Detect:

    • LinkedIn Sales Navigator or Common Room/UserGems/Champify/LoneScale on your past users/champions changing jobs → CRM.

  • CRM Fields:

    • Signal_Type=Alumni

    • Prev_Use_Case

    • Old_company

    • Job_change_date

Examples:

Champion - Building on Past Experience:

Subject: {{our_product}}

Hi {{first_name}}, saw you were pretty involved with {{our product/company}} at {{past_account_name}}. 

I'd love to hear your thoughts on what was most valuable. 

Are you seeing a similar [approach to managing problem/initiative] at {{new_company}}?

End User Template:

Subject: {{our_product}}

Hi {{first_name}},

Noticed you might used {{our product}} at {{old_company}} before joining {{new_company}}. 

I'm guessing you're comparing how {{new_company}} handles {{workflow}} to what you had before.

Users who've worked with us before typically get their teams up and running 2x faster because they know exactly what good looks like.

We've actually added {{new_feature}} since you last used it.

What do you use at {{new_company}}?

2) New leadership ≤ 90 days

Why it works

  • Mandate for early wins in quarter one; new leaders are shopping for quick proof.

  • Window for re-wiring: Before habits set, process + tooling are in play.

  • Vendor amnesty during transitions: incumbents are reviewable.

  • Budget air cover + exec attention = faster approvals.

  • External hires bring trusted playbooks; internals move faster with crisp ROI (promotions)

How to run

  • Detect: Sales Navigator role-change alerts on your personas; weekly Clay/LinkedIn scrape

  • Qualify fast: Confirm remit (team size, current stack, top 1–2 initiatives).

  • Fields:

    • Hire_Type=First/Replacement

    • Leader_Tenure_Days

    • Source=Internal/External

    • Top_Initiatives (free text)

First Leader (Building the Function) Template:

Subject: building {{function}}

Hi {{first_name}},

Congrats on joining {{company}} as their first {{title}}.

I imagine you're designing processes, picking tools, and setting foundations that'll scale with the company's growth.

We've helped 20+ first {{function}} leaders avoid the costly mistakes that come with no playbook to follow.

{{similar_company}}'s first {{title}} used our {{app}} to go from zero to fully operational in 45 days, beating their 90-day target.

Have you consider using a {{app}} to build your function?

Replacement Leader Template:

Subject: congrats

Hi {{first_name}},

Saw you stepped into the {{title}} role at {{company}}, following {{predecessor_name}}.

You're probably assessing what to keep vs. what needs reimagining, especially around {{function_area}}.

We work with other {{function}} leaders who need to show momentum fast, without disrupting what's working.

{{similar_company}}'s new {{title}} kept their team stable while cutting {{metric}} by 30% in 90 days using our framework.

What's your take on the current {{function}} stack?

3) High-intent website & content

Why it works

  • Accounts repeatedly hitting BOFU (bottom of the funnel) pages (pricing/integrations/case studies) are far likelier to convert.

  • A live problem is under discussion (budget/timing on the table).

  • A shortlist is forming (pricing = comparison; finance/procurement looped).

Example of high intent pages:

  • Pricing page

  • Competitor page

  • Demo request (but didn't book)

  • Integrations page

How to run

  • Detect:

    • 1st party data:

      • If you already got the email of your prospect in your system:

        • With your Marketing Automation Platform: HubSpot/GA4 events +

      • If you don't have the email in your system (to indentify contacts or the account):

        • Clearbit Reveal/Vector

  • CRM Fields:

    • Intent_Page

    • Visit_Count_7d

Example

Subject: {{topic/problem_area}}

Hi {{first_name}},

Saw {{company}}'s recent {{trigger_event}}, sounds like {{topic/problem_area}} is becoming a priority.

With {{market_context}}, you're likely comparing approaches to {{specific_challenge}} and building a business case for Q{{quarter}}.

Companies at your stage typically get stuck on {{common_obstacle}},  we've helped similar teams navigate this exact decision.

They got to full deployment in 6 weeks after solving {{specific_blocker}}.

Interested to learn more?

4) Tech stack change

(uninstalled competitor, installed complementary, tool in job posts/JDs)

Why it works

  • There’s an active change project (task force, budget, weekly decisions).

  • Fresh pain after outages/cost/adoption issues—receptive to “no-dip migration.”

  • New gaps appear: Complementary installs expose handoff/reporting/governance gaps you can close.

  • JD tech mentions signal standardization—leaders need faster ramp.

How to run

  • Detect:

    • Website tech: BuiltWith/Wappalyzer nightly diff (what’s live).

    • JD tech: TheirStack/Sumble to parse job posts (internal tools not visible on site).

  • Fields:

    • Tech_Event=Install/Uninstall/JD_Mention,

    • Tool_Name

    • Tool_Category=Partner/Competitor

    • Confidence

Competitor

Subject: {{competitor}}

Hi {{first_name}},

Saw {{company}} recently moved off {{competitor}}.

I imagine you're still settling workflows and probably hitting some gaps {{competitor}} couldn't fill.

We've helped 15 companies migrate from {{competitor}} without any business disruption, they typically see 40% better {{metric}}.

{{customer_name}} made the same switch and finally solved {{specific_problem}} that made them leave.

What finally pushed you to make the change?

Partner

Subject: {{partner_tool}}

Hi {{first_name}},

Noticed {{company}} recently added {{partner_tool}} to your stack - smart move for {{use_case}}.

You're probably discovering some handoff friction between {{partner_tool}} and your {{process}} workflow.

We've built a native integration specifically for {{partner_tool}} users - 20+ joint customers now run both seamlessly.

{{customer}} connected them last month and eliminated 5 hours of manual work weekly.

How's the {{partner_tool}} rollout going?

5) Expansion (raise, new region/product)

Why it works

  • Board targets: Capital converts to capacity/revenue under a clock—leaders must remove bottlenecks now.

  • Conditional budget: Money flows if you tie directly to near-term initiatives (hiring ramp, region launch, partner motion, compliance).

  • Scale pain: New regions/products stress onboarding, data quality, SLAs—leaders need force multipliers.

  • Standardization moment: Growth demands one way of working + one set of dashboards.

How to run

  • Detect: press/DB for raise/expansion → confirm pressure via hiring, region-specific rules, or partner announcements.

  • Fields:

    • Expansion_signal: new office/funding/product

    • Raise_Amount

    • Region

    • Hiring_YesNo

    • Target_Function.

Examples:

For new product

Subject: {{new_product}}

Hi {{first_name}},

Saw {{company}} is launching {{new_product}} for {{market/use_case}}.

I imagine you're building go-to-market motions from scratch while trying not to disrupt what's working for {{existing_product}}.

We've helped 30+ companies successfully launch their second product line without cannibalizing their core business.

{{similar_company}} launched their new product and hit 25% of their annual target in Q1 alone by solving {{specific_challenge}}.

How are you planning to balance resources between the new and existing products?

For funding

For this one, please stop sending the typical generic message:

“Congrats on your funding → Buy my shit”

Here are 2 examples run by Brex and Default recently, that you can use:

Brex ran an outbound play targeting 300 Bay Area startups that raised funding in the last 6 months.

  • Sent a bottles of champage with handwritten notes saying, “Congrats on your recent fundraise! Building a startup is hard, and we’re rooting for you.”

  • CEO followed up with an email offering a demo.

Results:

  • 75% booked a demo (225 demos).

  • 75% of those became customers (169 new clients).

  • Total cost: ~$19k.

  • If they’d done this today, they’d be getting ~$20M ARR. (Today’s ACV: $120k - Repvue 2024)

No alternative text description for this image

6) Hiring or downsizing in your buying center

Why it works:

  • Expansion → ramp pressure: managers pay to compress ramp, reduce errors.

  • Downsizing → do more with less: CFO pushes consolidation + automation; decisions tilt to cost per output.

  • Politics favor change: team shifts lower resistance to new tooling.

How to run:

  • Detect:

    • Open roles (now): Careers page + LinkedIn Jobs. Count relevant postings (title/keyword list)

    • Team growth trend (last 90 days):

      • Sales Navigator (at the account level) you can see the team growth

      • Clay method

        • Aggregate to the company row:

          • Hires_90d = count of recent-hire rows.

          • Team_Size_Current = count of in-function rows.

  • Fields:

    • Headcount_Change (Up/Flat/Down)

    • Team_Size_Current

    • Hires_90d

    • Open_Roles_Count

    • Open_Roles_Count

    • Function

    • Layoff_Source.

  • Tools: LinkedIn Jobs, Apify/Clay scrapers, LoneScale, Zapier → CRM.

Expansion/Growing Template:

Subject: Scaling {{department}}

Hi {{first_name}},

Saw you're hiring {{number}} {{role_type}}.

Sounds like ramp time and maintaining quality while scaling fast is might be top of mind.

We've helped other sales teams cut new hire ramp from 90 to 35 days while maintaining performance standards.

{{customer}} hired 50 reps last quarter and beat their productivity targets by solving {{specific_bottleneck}}.

How are you planning to onboard that many people?

Downsizing Template:

Subject: current team

Hi {{first_name}},

Noticed {{company}} streamlined the {{department}} team.

You're probably looking at how to maintain (or increase) output with fewer resources and tighter budgets.

We help lean teams automate what used to require headcount, typically seeing 45% efficiency gains.

{{customer}} went through similar restructuring and actually improved their {{metric}} with 30% fewer people by fixing {{process_inefficiency}}.

What processes are you looking to optimize first?

Standard fields (use across all signals)

  • Signal_Type

  • Signal_Strength (A/B/C)

  • Signal_Date

  • Source


AI Prompt: Find your unique signals

The 6 signals above will book meetings.

But your competitors can run them too. If you want signals tied to your ICP (and trackers you can automate in n8n / Clay / Apify), grab my “Find-Your-Unique-Signals” prompt below.

It turns your website, case studies, and reviews into a Top-10 signal pack and how to implement them.

  • Paid subscribers: the full prompt is unlocked right here.

  • Free readers: tap “Upgrade” to get it.

Keep reading with a 7-day free trial

Subscribe to Outbound Kitchen to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Elric Legloire
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share