The buying signals library
99 sales and buying signals for outbound, each with where to detect it, how fast it fades and the first line it earns.
99 signals · 12 categories · 3 motions · 32 rated strong
A buying signal is an event that suggests an account has a reason to buy now. Its half-life is how long that reason stays fresh enough to mention in your first line.
Updated · Free to browse
Enriched, scored, then written to the CRMSales signals list, all 99
Pick a motion, keep three signals, and test the first line. If you cannot write a specific one, cut the signal. Strength and half-life are IV's working estimates, not benchmarks. Intent data is account level, so write to the topic, never the tracking.
Showing 99 of 99 signals
-
Where to detect it
ATS scrapers or Clay job posting enrichment counting open SDR and BDR requisitions per company. Flag three or more open at the same time.
Best forSales engagement tools, data providers, outbound agencies, sales training.
Example first lineCommon pitfallFour SDR roles open at [Company] at once usually means the pipeline target went up before the lead sources did.
Pitching headcount replacement to the leader who just won budget to hire. Sell faster ramp, not fewer reps.
-
Where to detect it
Job boards for a first AE or Head of Sales at companies under about 30 people, confirmed in LinkedIn Sales Navigator that the founder still carries the sales title.
Best forCRM setup, sales process consultants, commission and CPQ tools.
Example first lineCommon pitfallYour first AE posting says they will build the playbook. Hard to do when the deals so far live in your inbox.
Writing to the new hire before they start. The founder owns this decision until day one.
-
Where to detect it
Keyword search across job descriptions (phrases like clean up our CRM, reduce churn, migrate off) using ATS scrapers, Google Jobs or Clay's job posting search.
Best forAnyone selling the outcome that role is meant to deliver.
Example first lineCommon pitfallYour ops posting says the hire will untangle HubSpot. We do that as a fixed project, so whoever you hire starts on a clean instance.
Positioning against the hire. Offer to make their first quarter easier, not to replace them.
-
Where to detect it
Upwork and Contra project feeds plus contract roles on LinkedIn, filtered for your service keywords and checked every few hours.
Best forAgencies, consultants and freelancers.
Example first lineCommon pitfallYour brief mentions moving 12 Zaps into n8n. Is the goal lower cost, or getting off the task limits?
Replying with a generic proposal. The brief already gives you the first line, so quote it back.
-
Where to detect it
LinkedIn Sales Navigator job change alerts filtered by title, Clay job change enrichment on your target accounts, and appointment press releases.
Best forMost B2B sellers whose buyer is that executive.
Example first lineCommon pitfallCongrats on the CRO role. Most new revenue leaders I talk to spend month one finding out what the CRM actually tracks.
Congratulations with nothing behind it. The line needs a reason that only exists because they are new.
-
Where to detect it
Closed won contacts in your CRM monitored for job changes with Clay job change enrichment, LinkedIn alerts or a dedicated job change tool.
Best forAny product that had happy users at the previous company.
Example first lineCommon pitfallYou ran [Product] at [Old Company]. At [New Company], is that setup something you want to rebuild, or inherit as it is?
Acting as if they owe you a meeting. They may have liked the old tool less than your CRM says.
-
Where to detect it
Job change monitoring on customer contacts, email bounces from the customer domain, and LinkedIn alerts.
Best forAccount managers and customer success teams.
Example first lineCommon pitfallWith [Name] moving on, I want to make sure whoever owns [workflow] now has the setup notes and a direct line to us.
Waiting until renewal. The replacement forms an opinion of you in their first month.
-
Where to detect it
LinkedIn post monitoring on saved leads in Sales Navigator, podcast guest appearances, and the company blog.
Best forAnyone whose offer maps directly to one of the stated priorities.
Example first lineCommon pitfallYour post put attribution at the top of the first 90 days. Which number do you trust today, HubSpot or the ad platforms?
Quoting the post back with nothing added. Ask one question that shows you understood the problem.
-
Where to detect it
SEC EDGAR full text search and Form D filings, filtered by industry and offering size.
Best forSellers who want to arrive before the funding press and the vendor rush.
Example first lineCommon pitfallLooks like [Company] closed a new round recently. Before the inbound vendor noise starts, is outbound in the plan for next quarter?
Sounding like surveillance. Keep it short and never recite the filing details.
-
Where to detect it
SEC Form D filings for pooled investment funds, fund announcements, Google News and fund partner posts.
Best forFounders raising, plus fund admin, legal and platform services.
Example first lineCommon pitfallWith Fund III closed, I assume [Partner] is writing first cheques in [sector] again. We are raising our seed in [month].
Writing to the general inbox. Find the partner who covers your stage and sector.
-
Where to detect it
BuiltWith historical data or scheduled Wappalyzer scans compared over time.
Best forCompetitors of the removed tool and migration services.
Example first lineCommon pitfallLooks like the Intercom widget came off your site this month. Moving to something else, or rethinking chat entirely?
Assuming they chose nothing. Check what replaced it before you pitch.
-
Where to detect it
Vendor community forums, Reddit, Slack communities and GitHub issues, searched for your tools by name.
Best forIntegration builders, iPaaS and automation consultants.
Example first lineCommon pitfallSaw your question in the HubSpot community about syncing deal stages to Notion. Did anyone ever answer it?
Pitching in the public thread. Answer there if you can, then follow up directly.
-
Where to detect it
Website visitor identification tools such as RB2B, Warmly or Common Room, alongside GA4 or PostHog page events.
Best forAny company with a public pricing page and real traffic.
Example first lineCommon pitfallTeams your size usually ask whether to start on [plan] or [plan]. Here is the one paragraph answer.
Saying you saw them on your pricing page. Reference the question they are likely asking, never the tracking.
-
Where to detect it
Account level visitor identification (Warmly, Common Room, RB2B) and reverse IP enrichment in HubSpot or Clay.
Best forSellers with buying committees of three or more.
Example first lineCommon pitfallWhen a few people at a company look at [use case] at the same time, it usually means a project just got approved. Is that the case at [Company]?
Office IPs are shared and VPNs mislead. Confirm the account before you act.
-
Where to detect it
G2 Buyer Intent, Capterra and TrustRadius intent data for your category and competitor pages.
Best forSaaS listed on review sites with active category traffic.
Example first lineCommon pitfallIf [Company] is comparing [category] tools, the question that usually decides it is [X]. Here is our honest answer.
Bashing the competitor they were looking at. Be the fair comparison.
-
Where to detect it
Form analytics in HubSpot, PostHog or Clarity, where the person has already given their email and consent.
Best forAny team with a demo or contact form.
Example first lineCommon pitfallLooks like the booking did not go through. Want me to send two times that work this week?
Following up on partial data the person never submitted. Only act where they gave you the email and consent.
-
Where to detect it
Visitor identification matched against closed lost opportunities in the CRM.
Best forAny team with a pipeline history worth mining.
Example first lineCommon pitfallIt has been a few months since we talked about [project]. Did the [alternative] route work out the way you hoped?
Reopening with the same pitch that lost. Lead with what changed on your side or theirs.
-
Where to detect it
Product analytics (PostHog, Amplitude, Mixpanel) or billing data synced into the CRM with reverse ETL.
Best forPLG and SaaS sellers with usage-based or seat-based plans.
Example first lineCommon pitfallYour workspace is close to the seat limit. Want me to sort the upgrade before someone gets locked out mid sprint?
Leading with the upsell. Lead with not breaking their work.
-
Where to detect it
Product analytics events piped into a PQL tool or the CRM, grouped by workspace.
Best forPLG SaaS with team plans.
Example first lineCommon pitfallFive people from [Company] joined [Product] this week. Want a 20 minute setup so the workspace matches how your team works?
Writing to whoever signed up last. Find the person who sent the invites.
-
Where to detect it
Signup data grouped by email domain, enriched with Clay or your CRM's company data.
Best forPLG SaaS selling team or company plans.
Example first lineCommon pitfallThree separate [Product] workspaces exist at [Company] right now. Want them merged into one before the data splits further?
Personal email domains. Exclude gmail and similar before grouping.
-
Where to detect it
Usage cohorts in product analytics or customer success platforms such as Vitally or Gainsight.
Best forCustomer success and account management.
Example first lineCommon pitfall[Workflow] usage at [Company] dropped off this month. Did something change on your side, or did we break something?
Waiting for the renewal call to ask. By then the decision is made.
-
Where to detect it
Product analytics by team or email group, and new users whose titles map to a department you do not serve yet.
Best forSaaS that expands across departments.
Example first lineCommon pitfallA few people from finance started using [Product] this month. Do they need the same setup as ops, or something different?
Billing them before you help them. Earn the second team first.
-
Where to detect it
LinkedIn keyword search, Sales Navigator saved lead activity, and post monitoring in tools like Common Room.
Best forAny seller with a clear point of view on that problem.
Example first lineCommon pitfallYour post about reps spending Friday updating the CRM got me thinking. Is the fix a process change or a tooling change at [Company]?
Leaving a pitch in the comments. Comment with substance, then follow up in a DM.
-
Where to detect it
Reddit, LinkedIn, X and Slack communities such as RevGenius, monitored with keyword alerts.
Best forAnyone in the category being asked about.
Example first lineCommon pitfallSaw your thread asking for a [category] recommendation. Happy to give a straight answer, including when we are not the right fit.
Pitching in the thread. Answer helpfully and only DM when invited or when the thread asks for it.
-
Where to detect it
G2, Capterra and TrustRadius reviews of competitors where the reviewer's company is shown, plus Reddit threads.
Best forCompetitors who genuinely fix the complaint.
Example first lineCommon pitfallThe usual complaint about [Competitor] is the reporting once you pass a few thousand contacts. Is that the wall [Company] is hitting?
Quoting their review back to them. Reference the common complaint, not their words.
-
Where to detect it
Competitor pricing page monitoring, changelogs, community threads and Reddit, then BuiltWith to list their customers.
Best forDirect alternatives with a stable pricing story.
Example first lineCommon pitfall[Competitor] moved [feature] to the Enterprise plan this month. If that affects [Company], here is what the same setup looks like with us.
Undercutting on price alone. Switching cost is the real objection; address it.
-
Where to detect it
Google News, competitor blog posts and status pages, and community threads, with BuiltWith to find the affected customers.
Best forAlternatives with a migration path.
Example first lineCommon pitfallWith [Competitor] winding down [product], you have until [date] to move. Want the migration checklist we use?
Fear tactics. Be the calm option with a plan.
-
Where to detect it
Trust centre pages (often hosted by compliance automation platforms) showing in progress, plus GRC and security job posts.
Best forCompliance automation, auditors, security consultants, policy tooling.
Example first lineCommon pitfallYour trust page says SOC 2 is in progress. Is the evidence collection automated, or are screenshots still landing in a shared drive?
Pitching the platform they already bought. Check which tool hosts the trust page.
-
Where to detect it
Your CRM and LinkedIn history, plus teammates' past employers cross-referenced in Clay.
Best forAny team with tenured people.
Example first lineCommon pitfallIt has been a while since [Old Company]. I am now at [Your Company] working on [X], and it reminded me of the [project] we did.
Leaning on the past and skipping relevance. The history opens the door; the reason keeps it open.
-
Where to detect it
Customer calls and QBR notes logged in the CRM, plus a standing referral question in your check-ins.
Best forEvery team with happy customers.
Example first lineCommon pitfall[Customer] mentioned you are dealing with [problem] at [Company], the same thing we fixed for them. Worth 20 minutes?
Waiting for a formal intro that never comes. Ask the customer if you can use their name, then send.
-
Where to detect it
Closed lost reason and follow up date fields in the CRM, with a task created at close.
Best forAny team that logs why deals were lost.
Example first lineCommon pitfallWhen we spoke in March you said to come back after the Q3 migration. Is that done?
No reason logged at close. Without it this signal does not exist, so fix the CRM field first.
-
Where to detect it
Partner portals and account mapping tools such as Crossbeam or Reveal.
Best forEcosystem-led sellers with active partners.
Example first lineCommon pitfall[Partner] mentioned you are rolling out [their product] and need help with [X]. That is the piece we usually handle.
Going around the partner. Keep them in the loop or the next referral stops.
-
Where to detect it
Scrape job descriptions for tool names (Salesforce, HubSpot, Snowflake, Zapier) with an ATS scraper or Clay's job posting search, and tag the stack each post mentions.
Best forIntegration partners, competitive displacement, implementation shops.
Example first lineCommon pitfallYour data engineer posting lists dbt and Snowflake but nothing for getting data back into HubSpot, which tends to be the gap that hire inherits first.
Trusting a recycled job template. Check the posting date and whether the tool still shows in BuiltWith.
-
Where to detect it
Store posting IDs and titles in a Clay table or ATS scraper over time and flag a title that is reopened or refreshed after closing.
Best forRecruiting firms, fractional leaders, outsourced services.
Example first lineCommon pitfallThe Head of Partnerships role went back up this week. If the search runs another month, who is working the partner list in the meantime?
Implying they failed to hire. Lead with the work that is not getting done, not the vacancy.
-
Where to detect it
Job boards filtered by location versus HQ country, plus LinkedIn Sales Navigator headcount by geography to spot the first roles outside the home market.
Best forEOR and payroll, localisation, compliance, regional agencies.
Example first lineCommon pitfallThree roles in Berlin this month and none there last quarter. Is [Company] setting up an EU entity or hiring remote first?
Pitching a full market entry on the back of one remote hire. Count the roles before you assume expansion.
-
Where to detect it
Job boards, executive search listings and LinkedIn job posts filtered for VP and Head titles in the function you sell to.
Best forInterim and fractional leaders, agencies that cover the function.
Example first lineCommon pitfallThe VP Marketing search at [Company] has been open a while. Who owns the agency and tool decisions until it closes?
Selling to an empty seat. Find out who is covering the role today and write to them.
-
Where to detect it
LinkedIn title changes at the same company, picked up by Sales Navigator saved lead alerts or Clay job change enrichment.
Best forTools and services the new, wider scope now covers.
Example first lineCommon pitfallSaw you now own RevOps as well as marketing ops. Does reporting still live in two places?
Treating it like an outside hire. They know the stack, so do not explain their own company to them.
-
Where to detect it
Google News alerts for CEO appointments, press releases and LinkedIn title changes on your account list.
Best forSales process, CRM, enablement, interim executives.
Example first lineCommon pitfallWith [Name] stepping in as CEO, I would guess the pipeline that lived in [Founder]'s head now needs a home in the CRM.
Assuming a CEO change means trouble. Keep the tone neutral and practical.
-
Where to detect it
LinkedIn job change alerts seen from the old company side, often followed by an open leadership role on the careers page.
Best forInterim and fractional providers, agencies that can cover the function.
Example first lineCommon pitfallWith the Head of Growth seat open, who is running paid and lifecycle at [Company] this quarter?
Speculating about why they left. Never reference it.
-
Where to detect it
Crunchbase, Dealroom, Google News and Clay funding enrichment, plus SEC Form D for US raises.
Best forGTM services, recruiting, tooling for teams about to scale.
Example first lineCommon pitfallThe announcement says the round goes into doubling the sales team. Who is building the pipeline engine those hires will run?
Opening with congratulations. Every vendor does. Quote what the money is for instead.
-
Where to detect it
Earnings transcripts on investor relations pages and SEC 10-Q and 8-K filings, searched for your problem keywords.
Best forEnterprise sellers into public companies.
Example first lineCommon pitfallOn the Q3 call your CFO called out sales efficiency twice. Which team below the CRO owns that number day to day?
Emailing the CEO. Find the owner one or two levels down.
-
Where to detect it
Pricing page monitoring with a change detection tool or a scheduled scraper, plus the changelog and Google News.
Best forBilling, pricing consultants, retention and churn tooling.
Example first lineCommon pitfallSaw the new Pro tier on your pricing page. Who is handling the conversations with customers on the old plan?
Implying the change was a mistake. Ask about the migration, not the decision.
-
Where to detect it
SEC EDGAR S-1 and F-1 filings and Google News.
Best forCompliance, finance operations, security, investor relations.
Example first lineCommon pitfallThe S-1 lists manual revenue reporting as a risk. Is that being fixed before the listing or after?
Arriving late. Most vendor choices are made in the year before the filing, so treat this as a narrow window.
-
Where to detect it
Crunchbase acquisitions, press releases and Google News.
Best forIntegration, CRM migration, data cleanup, HR systems.
Example first lineCommon pitfallAfter the [Target] deal you have two CRMs and two support desks. Which one survives?
Assuming the buyer's system wins. Ask.
-
Where to detect it
Crunchbase, press releases and Google News, plus domain and LinkedIn page changes after close.
Best forSellers who can help integrate into the parent, or who need to protect an existing account.
Example first lineCommon pitfallNow that [Company] sits inside [Parent], are tool decisions moving to their procurement or staying with your team?
Ignoring consolidation risk. If you already sell to them, this is a churn signal too.
-
Where to detect it
Product Hunt, company changelog and blog, press releases and Google News.
Best forMarketing agencies, GTM consultancies, analytics.
Example first lineCommon pitfall[Product] looks like it sells to a different buyer than your core product. Is the sales motion different too?
Generic praise for the launch. Say something only someone who read the page would say.
-
Where to detect it
Pricing page adds an Enterprise tier, a trust or security page appears, and job posts for enterprise AEs or solutions engineers.
Best forSecurity and compliance, sales enablement, CPQ.
Example first lineCommon pitfallThe new Enterprise tier mentions SSO and audit logs. Who is answering the security questionnaires that come with it?
Assuming they are ready. Many teams add the tier before the first enterprise deal exists.
-
Where to detect it
Partner directories (HubSpot App Marketplace, Salesforce AppExchange), press releases and Google News.
Best forPartner operations, PLG tooling, co-marketing agencies.
Example first lineCommon pitfallNow that you are on the HubSpot marketplace, how are installs from it routed to sales?
Treating a listing as traction. Ask about the plan, not the results.
-
Where to detect it
BuiltWith or Wappalyzer, Clay technographic enrichment, and job posts that name the tool.
Best forIntegration partners and add-on products.
Example first lineCommon pitfallSpotted Segment on [Company]'s site. Are those events making it into HubSpot, or stopping at the warehouse?
Technographic tags go stale. Check the script is still live before you mention it.
-
Where to detect it
BuiltWith and Wappalyzer, G2 reviews that list the reviewer's company, and job posts that require the tool.
Best forDisplacement sellers with a clear reason to switch.
Example first lineCommon pitfallYou are on [Competitor], which is fine for [use case]. Has [specific limit] come up yet now that you have [team size or volume]?
Guessing the renewal date and stating it. Ask when it is instead.
-
Where to detect it
Wappalyzer version detection, public docs, and job posts asking for experience on the legacy platform.
Best forMigration and modernisation shops.
Example first lineCommon pitfallYour careers page asks for Magento 1 experience. Is a replatform on the roadmap, or are you keeping it running?
Telling them their stack is old. They know. Talk about the migration risk they are carrying.
-
Where to detect it
BuiltWith and Clay technographics showing two tools in the same category, or job posts listing both.
Best forConsolidation and implementation consultants.
Example first lineCommon pitfallI see both Pipedrive and HubSpot on [Company]'s site. Is one of them on the way out?
One of them may be a leftover tag. Confirm both are in use first.
-
Where to detect it
Job posts mentioning dbt, Snowflake or BigQuery, CDP scripts in BuiltWith, and the engineering blog.
Best forReverse ETL, analytics agencies, data consultancies.
Example first lineCommon pitfallThe analytics engineer role mentions a new Snowflake setup. Is getting that data back into the CRM in scope, or a later phase?
Selling to data engineering when the pain sits in sales ops. Follow the use case.
-
Where to detect it
Job posts mentioning AI agents or LLMs, company blog and changelog, and leadership posts on LinkedIn.
Best forAI engineering firms, governance, training and evaluation tools.
Example first lineCommon pitfallYour AI ops posting mentions agents in support. Is that a pilot, or is something already live with customers?
Hype language. Ask about the specific workflow, not AI in general.
-
Where to detect it
Bombora, 6sense, G2 Buyer Intent and TrustRadius intent feeds, mapped to your target account list.
Best forSellers with a defined category and enough accounts to filter.
Example first lineCommon pitfallTeams looking at [category] right now mostly get stuck on [specific problem]. Here is how we would handle it at [Company].
Intent is account level and probabilistic. Never write as if a named person searched for something.
-
Where to detect it
Docs analytics in PostHog or GA4 combined with visitor identification or logged in docs.
Best forDeveloper tools and API products.
Example first lineCommon pitfallMost teams reading the [endpoint] docs are building [use case]. If that is you, here is the example repo.
Sending a sales email to an engineer. Send code, not a calendar link.
-
Where to detect it
Page level analytics plus account level visitor identification.
Best forTeams with honest comparison pages against named competitors.
Example first lineCommon pitfallThe question we hear most from teams on [Competitor] is how migration works. It takes about [timeframe] and here is what moves.
Replacing a fair comparison with a hard sell. They came for the comparison.
-
Where to detect it
Integration events in product analytics or your app's admin logs.
Best forProducts where integrations drive stickiness and upgrades.
Example first lineCommon pitfallYou just connected Salesforce. The sync setting most teams change in week one is [X]. Want me to check yours?
Assuming it is working. Check the sync is healthy before you mention it.
-
Where to detect it
Docs and in-app page views by logged in users, joined to their plan level.
Best forSaaS with an enterprise or security tier.
Example first lineCommon pitfallIf IT is asking about SSO for [Product], I can send the security pack and the plan comparison in one go.
Pushing the top plan when they only need one feature. Ask what triggered the question.
-
Where to detect it
LinkedIn post engagement, Common Room, and social listening tools that export engagers.
Best forFounders and teams who post consistently.
Example first lineCommon pitfallYou pushed back on my point about [topic]. Fair. How do you handle it at [Company]?
Thanks for liking my post is not a first line. A like is weak; a comment is the signal.
-
Where to detect it
Engager exports from competitor LinkedIn posts and webinars, via social listening tools or manual review.
Best forCategory challengers with a different angle.
Example first lineCommon pitfallYou commented on [Competitor]'s post about [topic]. We see it differently: [one line view]. Curious which matches [Company].
Mentioning that you watched them engage with a competitor. Lead with the topic.
-
Where to detect it
Podcast search (Listen Notes, Apple Podcasts, Spotify), YouTube, and Google News for the person's name.
Best forSellers who can respond to a specific point the person made.
Example first lineCommon pitfallOn [Podcast] you said outbound stopped working once the team passed 20 reps. What did you change after that?
Saying you loved the episode without quoting it. Prove you listened.
-
Where to detect it
Your closed won list, Clay company search for lookalikes, and G2 category peers.
Best forSellers with vertical focus and a fresh result.
Example first lineCommon pitfallWe just finished [project] for a [segment] team your size. The problem was [X]. Is that live at [Company] too?
Naming the client without permission. Describe the problem, not the logo.
-
Where to detect it
Crunchbase and Google News on the competitors of each target account, mapped with G2 categories or Clay.
Best forGTM, marketing and product agencies.
Example first lineCommon pitfall[Competitor] raised last week and says the money goes into sales. How is [Company] thinking about the next two quarters?
Making them feel behind. Offer a plan, not anxiety.
-
Where to detect it
Event sponsor and speaker pages scraped into Clay, plus LinkedIn event posts.
Best forEvent services, pipeline agencies, anyone attending the same event.
Example first lineCommon pitfallYou are speaking on [topic] at [Event]. How are you following up with the people who scan at your booth?
Asking for a meeting at the event when they are working it. Offer to help them get value from it.
-
Where to detect it
Event attendee apps, badge scans, Luma guest lists where shared, and LinkedIn posts tagged with the event.
Best forAnyone who actually went.
Example first lineCommon pitfallWere you in the [session] at [Event]? The point about [X] is the one I keep thinking about.
Pretending you met. If you did not talk, say you were in the same room, nothing more.
-
Where to detect it
Webinar listings on LinkedIn events, Luma, Zoom event pages and the company site.
Best forSellers whose offer is the next step after the webinar's advice.
Example first lineCommon pitfallSaw [Company]'s webinar on [topic] next week. Who builds the follow up for the attendees once it is done?
Pitching to compete with their own content. Position as what makes it work.
-
Where to detect it
Your webinar platform (Zoom, Luma) synced into the CRM.
Best forTeams that run their own events.
Example first lineCommon pitfallYou registered for [event]. The question we did not get to on the day was [X], so here is the short answer.
Sending the same follow up to attendees and no shows. Split them.
-
Where to detect it
Product Hunt daily launches filtered by topic, pulled on a schedule.
Best forGrowth services, onboarding and analytics tools.
Example first lineCommon pitfallCongrats on the launch. Where are the new signups landing, and who is talking to them this week?
Upvote-for-upvote messages. Offer something tied to what launch day creates.
-
Where to detect it
Regulator websites, Google News and industry newsletters, with affected companies listed by industry and geography in Clay.
Best forCompliance, legal tech, security and consulting.
Example first lineCommon pitfallDORA covers [Company] as an EU [entity type]. Who owns the ICT third-party register internally?
Selling fear about fines. Lead with the specific obligation and who has to deliver it.
-
Where to detect it
The Companies House API and streaming API for new officers, accounts size changes and registered charges.
Best forUK finance, legal, payroll and accounting services.
Example first lineCommon pitfall[Company] just appointed a new finance director per Companies House. Is the month end close something they inherit or rebuild?
Reading too much into routine filings. Filter for changes that create work.
-
Where to detect it
SAM.gov awards in the US, Contracts Finder in the UK and TED in the EU.
Best forCompliance, staffing, subcontractors and delivery partners.
Example first lineCommon pitfallCongrats on the [Agency] award. Delivery usually starts with reporting requirements the team has not met before. Is that covered?
Pitching before delivery starts. Time it to mobilisation.
-
Where to detect it
Regulator registers such as the FCA register, state licensing databases and banking regulator lists.
Best forFintech infrastructure, compliance, onboarding and KYC tooling.
Example first lineCommon pitfallSaw [Company] is now FCA authorised. Is customer onboarding moving off the manual process now that you can scale it?
Assuming they launch tomorrow. Authorisation often comes months before go-live.
-
Where to detect it
USPTO trademark search, UK IPO and EUIPO filings by applicant name.
Best forLaunch agencies, branding, web and GTM services.
Example first lineCommon pitfallSaw the [Name] trademark filing. If that is a new product, who is planning the launch?
Revealing an unannounced product to the wrong person. Write to the founder or marketing lead only.
-
Where to detect it
LinkedIn shared connections, your team's networks mapped in a tool like Clay, and investor or customer overlaps.
Best forFounder-led sales and high value accounts.
Example first lineCommon pitfall[Mutual] suggested I reach out. She said [Company] is working on [X] and that we had compared notes on it before.
Name-dropping without asking. Get the connection's OK, or better, the intro.
-
Where to detect it
Churned accounts in the CRM watched for funding, hiring and leadership changes with Clay enrichment.
Best forProducts that improved since the account left.
Example first lineCommon pitfallA lot changed at [Company] since you left [Product], and on our side too. [Reason they left] is fixed. Worth a look?
Pretending they never left. Name the reason and what changed.
-
Where to detect it
Community analytics in Common Room or Slack and Discord exports.
Best forCompanies running a real community.
Example first lineCommon pitfallYour question in #[channel] about [topic] was a good one. Want me to walk through how other teams handle it?
Turning every community question into a sales call. Most people are there to learn.
-
Where to detect it
LinkedIn Sales Navigator department headcount growth, or Clay headcount enrichment snapshotted monthly.
Best forDeveloper tools, cloud cost, security, internal tooling.
Example first lineCommon pitfallEngineering at [Company] went from about 40 to 60 people on LinkedIn since spring. Is onboarding still a doc and a buddy?
Sending on growth alone. Pair it with a second signal, because growth is not a reason to reply.
-
Where to detect it
Company announcements, Crunchbase people data and LinkedIn advisor role updates.
Best forGTM services and sales tooling, as supporting context.
Example first lineCommon pitfallAdding [Advisor] to the board usually means someone is about to ask for a cleaner pipeline report.
Using it on its own. It is context for a stronger signal, not a reason to write.
-
Where to detect it
Press releases, Crunchbase debt rounds, UCC filings in US states and registered charges at Companies House in the UK.
Best forEfficiency, cost and collections tooling.
Example first lineCommon pitfallRevenue based financing tends to come with a hard look at CAC. Is paid still carrying most of [Company]'s pipeline?
Assuming distress. Debt is often a deliberate growth choice.
-
Where to detect it
WARN notices, public layoff trackers, Google News and LinkedIn posts from affected teams.
Best forAutomation and efficiency tools, approached with care.
Example first lineCommon pitfallAfter the restructure, the same pipeline target sits with a smaller team. Which manual step would you cut first?
Writing in the first week. Wait, and never frame the cut as an opportunity.
-
Where to detect it
Press releases, new Google Business Profile listings, job posts by location and LinkedIn posts.
Best forFacilities, IT, local services, recruiting.
Example first lineCommon pitfallSaw the new Austin office opening. Is the team there running on the same tools as HQ, or starting fresh?
Selling to HQ when the site lead makes the call, or the other way round. Find out which first.
-
Where to detect it
Redirect and DNS checks on your account list, press, and LinkedIn page name changes.
Best forEmail deliverability, web development, brand agencies.
Example first lineCommon pitfallSince the move to [new domain], are any mailboxes still sending from the old one? That is usually where deliverability slips.
Pitching a rebrand to a team that just finished one. Pitch what the rebrand broke.
-
Where to detect it
LinkedIn and Clay headcount enrichment snapshotted monthly, flagged at 50, 100 and 250 employees.
Best forHR, IT, internal systems and process work that breaks with size.
Example first lineCommon pitfallAround 100 people is usually when the Notion wiki stops being findable. Is it still the source of truth at [Company]?
LinkedIn headcount lags and includes contractors. Treat the number as rough.
-
Where to detect it
Published lists such as the Inc. 5000 and Deloitte Fast 500, plus Google News.
Best forContext for growth-stage services. Weak on its own.
Example first lineCommon pitfallGrowing that fast usually means the hiring plan is ahead of the onboarding process. Which team feels it most?
Every vendor emails list winners the same week. Wait a few weeks or skip it.
-
Where to detect it
Certificate transparency logs (crt.sh) and DNS monitoring on your account list.
Best forSecurity, developer tools, hosting.
Example first lineCommon pitfallNoticed [app].[company].com went live recently. Is that a customer portal, or an internal tool?
Staging and test subdomains are noise. Filter them out before you write.
-
Where to detect it
Marketing automation and form tools (HubSpot, Kit, Netlify Forms) writing into the CRM.
Best forContent-led teams with useful free resources.
Example first lineCommon pitfallYou grabbed the [asset]. The section most people skip is [X], and it is the one that matters for [use case].
Treating every download as a sales lead. Most are researching, so send help rather than a meeting ask.
-
Where to detect it
Activation events in product analytics, with a cohort of signups that never reached the key action.
Best forSelf-serve products with a clear activation step.
Example first lineCommon pitfallYou signed up but never connected [integration]. That step is where most people get stuck, so here is the two minute version.
A sales pitch to someone who has not seen value yet. Help them reach it first.
-
Where to detect it
Glassdoor and Indeed reviews searched for process and tooling complaints.
Best forInternal tooling, operations and enablement services.
Example first lineCommon pitfallTeams growing as fast as [Company] usually hit the point where handoffs between sales and onboarding live in Slack. Is that live for you?
Quoting an employee review to the company. Use it to choose the angle, never as the line.
-
Where to detect it
Competitor status pages, Downdetector and social mentions.
Best forReliability-focused alternatives, and only with restraint.
Example first lineCommon pitfallNot writing about this week, but if reliability is now on [Company]'s evaluation list, here is how we report uptime.
Ambulance chasing during the outage. Most teams should skip this one entirely.
-
Where to detect it
Competitor case study and logo pages, scraped and refreshed quarterly.
Best forLong-cycle displacement plays and nurture lists.
Example first lineCommon pitfallRead the [Competitor] case study on your [workflow]. A year in, is it still doing what the case study said?
They are mid-contract and publicly committed. Nurture, do not push.
-
Where to detect it
Registration versus attendance data from your webinar platform.
Best forTeams with recordings worth watching.
Example first lineCommon pitfallMissed [event]? The useful part starts at minute 14. Here is the link straight to it.
Guilt-tripping. People miss things. Make it easy.
-
Where to detect it
Fiscal year end from filings or Crunchbase, and LinkedIn posts about kickoff.
Best forTools and services that need a budget line.
Example first lineCommon pitfallMost teams lock next year's tool budget a month before kickoff. When does that happen at [Company]?
Every vendor sends this in December. Arrive earlier with something specific.
-
Where to detect it
Breach disclosures, state attorney general notices, SEC 8-K item 1.05 filings and Google News.
Best forSecurity vendors, with great care.
Example first lineCommon pitfallThe next audit after an incident usually asks who has access to what. Is that pulled by hand at [Company] today?
Referencing the breach directly. Talk about the next audit, not the incident.
-
Where to detect it
Automated scans with axe or Lighthouse, and cookie consent checks scraped across your account list.
Best forWeb agencies, privacy and accessibility specialists.
Example first lineCommon pitfall[Company]'s site sets analytics cookies before the consent banner loads. Want the two line fix?
Shaming or legal threats. Offer the fix, keep it small.
-
Where to detect it
Accelerator directories and LinkedIn education and experience fields.
Best forFounder-to-founder selling.
Example first lineCommon pitfallFellow [Accelerator] founder here. We help batch companies with [X]; happy to share what worked for [batch peer] if useful.
Shared alumni status alone is not a reason. Pair it with a real one.
No signals match those filters.
Want all 99 in a spreadsheet? We email it to you, ready for Google Sheets or Excel.
A list tells you what to watch. It does not watch.
Each signal needs a source checked on a schedule, a contact you can reach, a score that accounts for age, and a sequence that writes back to your CRM. That is the Pinpoint framework behind our GTM engineering and CRM setup work.
- 01Signal map
Cut this list to the two or three signals that fire for your ICP, each with a detection method and a cadence.
- 02Data layer
Detection on a schedule, then an enrichment waterfall that runs until the contact is verified.
- 03Score and route
One score per account from trigger type, trigger age, fit and contactability.
- 04Sequence and CRM
Email, LinkedIn and voice in a fixed order, with every touch written back the same day.
Questions
Questions people ask before they pick.
A buying signal is an event that suggests an account has a reason to buy now. Examples include a new executive in the buyer role, a funding round, a job post that describes the problem you fix, or repeat visits to your pricing page. A good signal is specific enough to reference in the first line of your message.
Signal half-life is how long a signal stays fresh enough to act on and mention. A pricing page visit fades in days, while a new executive stays relevant for roughly 60 to 90 days. The half-life values in this library are IV's working estimates, not measured benchmarks. Use them to set how often you check each source: daily for fast decay, weekly for slow.
Three at most, and two is often better. Every extra signal thins the list and makes the copy more generic. Start with the signals you can detect reliably on a schedule and write a specific first line for, then add more only once those are running.
Yes. Browsing is free and open. Enter your email next to the table and we send the full library as a spreadsheet you can open in Google Sheets or Excel.
Free 30 minute signal audit
Picked your three? We build the system that watches for them.
You have the list. On the call we cut it to the signals that fire for your ICP, check which ones you can actually detect, and test the first line on real accounts.
Pick a time in the calendar below to schedule a 30 minute call with me.
- 01You talk. Who you sell to and what you send today.
- 02We map. The signals that fire for your ICP and the two to start with.
- 03You keep it. The signal map and a budget range, whether or not you build with us.
Ishan Vats, founder of IV Consulting. We run our own outbound on the same system.
More free GTM tools: Email domain checker · Cold email calculator · GTM glossary · GTM and CRM setup
Loading the calendar. If it does not appear, book the signal audit on cal.com.