Skip to content

Turn a public business change into a reviewed sales signal

Before anyone is contacted, a public event should be traced to its source, matched to the right organisation, split into what it says and what you infer from it, and checked against a contact route your team has approved. This guide sets out those checks, with a worked signal card on fictional data and a downloadable template. It is not legal advice, it promises no replies or sales, and it does not treat a public record as permission to contact anyone.

Define the target account

A public event only means something against a defined customer. Write down who you sell to before you watch any source.

  1. 01

    State the offer in one sentence

    Say what you sell and to whom. If a colleague cannot repeat it back, the signals chosen from it will drift.

  2. 02

    Describe the target account in fields your team sets

    Territory, sector, legal form and a size band that your team chooses. Legal form matters later, because the contact rules can differ for a limited company, a partnership and a sole trader.

  3. 03

    Name the event that would matter and say why

    Pick one type of event with a plain link to the offer. If nobody can explain why the event bears on what you sell, it is not a signal for you.

  4. 04

    List exclusions before you search

    Existing customers, open conversations, competitors, anyone on a suppression list and organisations your team has decided not to approach. Applying these first saves checking accounts you would drop anyway.

  5. 05

    Name the person who takes the reply

    A sales owner who is in post, with a response window your team chooses. A signal with nobody to answer it is still research.

Select approved sources

Prefer dated, official records that you can open again. Approve each source before anyone relies on it.

  1. 01

    Start with official publications and registers

    Examples are goods-vehicle licensing publications, care-provider registers, the sponsor register and company filings. The lead-generation page names several. Each records some things and not others.

  2. 02

    Write down what the source does and does not say

    For each source, record what it lists, how often it updates, and which questions it cannot answer. A register entry shows that something was filed. It does not explain why.

  3. 03

    Keep the link and the capture date for every entry

    A reviewer should be able to open the original record and see what you saw. If a page changes later, the stored date shows which version you used.

  4. 04

    Treat third-party alerts as pointers

    An alert from a data service or a news site tells you where to look. Open the original record before a card relies on it.

  5. 05

    Decide what you will not use

    Do not scrape personal-contact lists from the web, guess email addresses or buy contact data with no recorded origin. Check the terms of any source or service you plan to use, and prefer the official route to the data.

Verify event and identity

Two questions come before anything else. What exactly happened, and to which organisation?

  1. 01

    Read the status word in the original record

    Applied, granted, proposed, withdrawn and refused are different events. A card that says granted when the record says applied is wrong, and so is any message built on it.

  2. 02

    Keep three dates apart

    The date of the event, the date the source published it and the date you captured it are not the same. Record each one, and use the source's own wording for the first two.

  3. 03

    Match the legal entity

    Check the legal name, the registered number, the registered address and the operating location against the official register. Watch for similar names and for group companies that trade under one brand.

  4. 04

    Check that the organisation is still active

    Look at its current status at the source on the day you build the card, not at a copy from an earlier date.

  5. 05

    Stop on a weak match

    A near match, a missing number or two plausible companies stops the card for a person to review. Do not choose the likelier one and carry on.

  6. 06

    Check the event is still current

    Signals age. Your team sets how old an event can be for this offer, and anything older is dropped or researched again.

Separate fact from inference

The card has two columns, what the source says and what you think it might mean. Keep them apart.

  1. 01

    Write the fact exactly as the source states it

    One sentence, with the status word and the date, and nothing added. If the source does not say it, it does not go in this column.

  2. 02

    Label every interpretation as a hypothesis

    For example, that the organisation may be changing how it operates. Add why you think so and what would test it. A hypothesis is a question for a person to check, not a finding.

  3. 03

    Do not read intent into a record

    A public record does not prove buying intent, urgency, growth, a problem or a budget. It can be a timely reason to research an account and nothing more.

  4. 04

    Write down what you do not know

    Typical gaps are the budget, the timing, the current supplier and who decides. Naming them is the commercial uncertainty line on the card.

  5. 05

    Keep the opening message to the fact

    A message may refer to what the source says. It should not claim a need, a supplier review or a plan that the record does not show.

  6. 06

    End with a decision, not a score

    A figure that looks precise invites false confidence. Use three outcomes, pursue, research further or drop, with a written reason for each.

Approve contact route

A public record is not permission to contact every person it points to. A person approves the route before anything is sent.

  1. 01

    Approve the route for each group of accounts

    Your team names the group, the channel, the wording, the timing, the frequency and who may be contacted. Approval attaches to those campaign rules and is given before launch. It is not requested again for each routine message.

  2. 02

    Choose a role or a named person on purpose

    A message to a company address and a message to a named individual are different things. Your team decides which it is sending and records why.

  3. 03

    Write down the basis your team relies on

    The rules can differ by channel and by who the recipient is, such as a limited company, a sole trader or an individual. Your team records its basis for each group and takes qualified advice where the answer matters. This guide does not decide it for you.

  4. 04

    Use only contact details you can trace

    Record where each address or number came from. If its origin cannot be shown, do not use it. Never rely on a scraped list.

  5. 05

    Check suppression and objection before the first message

    Check every place they are kept, and check again before each later send. The record-check guide covers the same test for customer and quote records.

  6. 06

    Pass anything outside the rules to a person

    A new channel, a new audience or new wording goes back to the person who owns the campaign rules before it is used.

Routine follow-up and stop rules

Write the sequence and the reasons to stop before the first message goes out.

  1. 01

    Set the sequence in advance

    The first message, the number of follow-ups and the spacing between them are part of the approved campaign rules. Routine follow-ups that stay inside those rules do not need a person to read each one.

  2. 02

    Re-check the source before a follow-up

    An application can be withdrawn or refused after you captured it. If the event could have changed, look at the source again and update the card before the next message.

  3. 03

    List the conditions that stop a record

    A request to stop, an objection, a bounce, a change in the source record, a doubt about the match or any reply the rules do not cover. The sequence stops for that record and it passes to a person.

  4. 04

    Hand positive and complex replies to the sales owner

    The owner gets the card, the source link and the message history, so the conversation does not start again from nothing.

  5. 05

    Close each record with a reason

    No reply, declined, wrong organisation, source changed, passed to sales or stopped. A reason on every closed record lets you see which rules to change.

Measure qualified replies

A reply is not a sale. Count each stage separately, in the same way each time.

  1. 01

    Define a qualified reply with your sales owner first

    For example, a reply that shows the offer is relevant and that the owner agrees is worth a conversation. Write the definition down before the first message goes out.

  2. 02

    Count the stages in order

    Signals found, cards that passed the identity and exclusion checks, cards approved, messages sent, replies, qualified replies, conversations held and opportunities opened. Keep each count apart and keep the dates.

  3. 03

    Record why signals were dropped

    A dropped card still tells you something. A pattern of weak matches or stale events points to a source or a rule to change.

  4. 04

    Ask the sales owner about each qualified reply

    Was the card accurate, and was the opening message fair to the source? Their answers show whether the earlier steps held.

  5. 05

    Try the card on past events first

    Apply the process to events from an earlier period before sending anything. You learn whether the event gives enough relevant accounts and whether the checks hold, without contacting anyone.

  6. 06

    Compare with a baseline

    Compare against how the team finds and approaches accounts today, counted the same way. This guide gives no target and no expected reply rate. The measurement guide covers the method.

Eight checks before a card is approved

Answer these in writing for each signal. The downloadable template has a field for most of them.

  1. 1.Is the offer stated in one sentence, with the event and its link to the offer written down?
  2. 2.Does the card name the source, the link and the capture date, and was the source approved first?
  3. 3.Does the card quote the status word and the event date exactly as the source gives them?
  4. 4.Do the legal name, registered number and address match the official register, with weak matches stopped?
  5. 5.Are exclusions applied, including customers, open conversations, competitors and suppressions?
  6. 6.Is the fact kept apart from the hypothesis, with the unknowns written down?
  7. 7.Has your team approved the route, recorded its own basis and traced the source of each contact detail?
  8. 8.Are the stop rules and the definition of a qualified reply written before the first message?

Download the signal card template (CSV) A plain spreadsheet file with a header and one line for each field, giving the group, whether it is required, the test, what to do if it fails and a fictional example. Edit it freely; it opens in any spreadsheet program.

Bring one event and one target account

Send one public source, a description of the account you want and your exclusions. We will say plainly whether the signal looks relevant, what the identity check would need and whether the contact route is ready for your team to approve.