Signal-based prospecting: a worked example and qualification worksheet

Updated September 8, 2026

Signal-based prospecting uses an observable event to decide why an otherwise suitable account deserves attention now. The useful output is a defensible next action: research, contact, wait or exclude. This guide walks through a small outbound example from evidence to message, with a reusable worksheet and explicit cost checks. The three accounts are fictional teaching examples, not Hilead customers or measured campaign results.

1. 1

   Define one segment and one business problem

   For this example, imagine selling a prospecting workflow to B2B SaaS teams with 20–200 employees that operate outbound sales. The relevant buyer is the person responsible for sales development. Exclude existing customers, active opportunities, suppressed contacts and businesses outside the segment. Write the rules before reviewing signals so a dramatic event cannot override poor fit. Use the ICP guide to adapt this segment to your actual customers.

2. 2

   Keep the source separate from your interpretation

   For Account A, the illustrative observation is three open SDR roles posted five days ago. In a real evaluation, save the careers-page URL, event date, observation date and the exact relevant detail. The hypothesis is that onboarding new SDRs may create a need for prospect data and consistent outreach. Budget, dissatisfaction with an existing tool and willingness to meet are still unknown. A job posting can also be a replacement hire or an expired listing, so verify the source before acting.

3. 3

   Apply the same review rules to all three accounts

   Use hard fit requirements first. Then classify timing as current, stale or unknown and evidence as verified or unverified. For this exercise, evidence within 30 days is eligible for review; this is a chosen operating rule, not a universal buying window. A fits and has current evidence, B fits but its event is stale, and C fails the segment rule. None is automatically ready to buy. The lead-prioritization framework explains how to turn these decisions into owner and action tiers.

4. 4

   Find the buyer and capture only the relevant profile

   For Account A, verify who currently owns sales development. Open that person’s LinkedIn profile or select the relevant search result in the Hilead extension. Review the role and company before saving. Selected-profile import supports up to 50 profiles at a time; Top of search can request up to 500, subject to account limits and available results. For a one-account test, there is no reason to import every employee. The illustration below shows the existing search-import interface and sample data; it is not evidence from these fictional accounts.

   
5. 5

   Choose enrichment and check the cost before confirming

   Free CSV capture does not include paid contact lookup. Saving and enriching use an account, and the panel displays the estimated maximum credit cost for the options selected. Work email starts at one credit, personal email costs three and phone lookup costs ten. Request only what the chosen channel needs. For a hypothetical phone-only batch of three contacts, three successful lookups use 30 credits; if one returns no result and its ten-credit charge is refunded, the net is 20. This illustrates credit arithmetic, not a measured hit rate or a quote for other selected options. Review current prices and the import tutorial.

6. 6

   Review the result before adding outreach

   Confirm the contact belongs to the intended buyer and inspect whether the requested field was returned. Missing data is a research outcome, not a reason to guess an address. A verified email can still bounce. Save the lead to the intended audience only after checking its linked campaigns: adding a member can make the lead eligible for those campaigns. Keep evaluation work out of an active sending audience until the owner has reviewed targeting, channel eligibility and copy. Store the original evidence in your worksheet so the decision remains explainable.

7. 7

   Draft a question based on the possible consequence

   Illustrative first message: “Hi Alex — your careers page lists three SDR openings. When new reps join, keeping account research consistent can become extra work for the sales lead. Is that something your team is reviewing, or is the current process already working well?” Replace the name and opening only after checking them. This is a conversation hypothesis, not proof of a problem. Avoid invented familiarity, promises of results or claiming to know the recipient’s budget. The personalization guide develops the same evidence-to-message approach.

8. 8

   Copy the worksheet and record the actual decision

   Open the signal prospecting worksheet in English or the French qualification worksheet and save a copy. Both separate observed facts, hypotheses, unknowns and the next decision; the English version includes the three illustrative accounts above. Replace the examples with your own evidence, reviewer, contact result and next action. You can use the worksheet manually with any tool; its rules are not automatically installed in Hilead. For another event family, adapt the job-change playbook.

9. 9

   Measure what happened, including the rejected records

   Record reviewed accounts, fit failures, stale or unverifiable signals, usable contacts, messages sent, positive replies and meetings held. Measure credits spent per usable contact separately from time spent researching. Define positive replies before the test and keep signal families separate. To investigate whether timing helps, compare similar eligible accounts using a documented assignment method and observation window. Three illustrative accounts cannot demonstrate conversion lift; the worksheet deliberately contains no invented success rate. Expand only after you can explain both the useful results and the false positives.

Keep reading

Lead prioritization: a fit, intent, and confidence frameworkRead article

Job change signals for sales prospectingRead article

How to export and enrich a LinkedIn search with HileadRead article