Claim your spot
Playbook

Stop Prospecting by Job Title. Build a Trigger List.

· 10 min read

A list of IT directors is not a prospecting strategy. It tells you who might buy someday. It gives you no credible reason to contact this account now, no useful opening, and no standard for deciding when to move on.

Your list needs a reason, not more rows

Small advisory firms can buy thousands of contacts in an afternoon. That has made list building easy and prospecting harder.

You load a broad set of titles into a sequence. The messages mention cost savings, digital transformation, or a "quick conversation." Activity goes up. Replies do not tell you much because most of the accounts had no visible reason to care.

The problem starts before the first email. You selected a person, but you did not select a moment.

A better prospecting list starts with an observable change inside an account. A contract is approaching renewal. The company is opening locations. A new technology leader has inherited a messy environment. A merger has created overlapping vendors. A client or supplier has made a relevant introduction. The event does not prove a deal exists. It gives you a reasonable problem to investigate.

That is a much higher bar than "works in IT at a company with 200 employees." Good. Your team has limited time. The list should force a choice about where that time goes.

Define what counts as a buying trigger

A trigger is a dated piece of evidence that may change a company's technology priorities, risk, cost, or operating requirements.

Use four tests before an account enters active prospecting:

  • The event is specific enough to verify from a named source.
  • The event connects to a problem your firm can credibly help investigate.
  • The timing creates a reason to act or learn something now.
  • You can contact the account without pretending to know facts you have not confirmed.

A company hiring a network engineer may indicate expansion, a backfill, or nothing relevant to your offer. Treat it as a clue. Do not turn it into a fake conclusion such as "I saw your network is struggling."

The trigger gets the account researched. Discovery determines whether the problem is real.

Choose trigger families that match your practice

Do not monitor every possible business event. Pick two or three trigger families that match the work you want and the evidence you can maintain.

Contract and lifecycle events

Known renewal dates, lease expirations, hardware end-of-support dates, and planned implementation milestones can create clear planning windows. These are strongest inside your existing network because the timing comes from client records, partner conversations, or prior work.

Handle private contract information carefully. A renewal date learned through a client relationship is account context, not a reason to spray a competitor's contact list. Record the source and access boundary beside the date.

Business change

New locations, acquisitions, divestitures, funding, leadership changes, and rapid hiring can affect networks, security, communications, cloud spend, and support. Use the company's announcement, a public filing, a job posting, or a direct relationship as the source.

Business change only matters when you can connect it to a sensible technology question. "Congratulations on the funding" is not useful prospecting. "How are you planning connectivity and support for the three locations announced for next quarter?" at least shows you did the work.

Operating friction

Service complaints, public outages, compliance deadlines, supplier consolidation, and repeated hiring for the same operational gap may point to unresolved work. Be careful here. Public pain is not permission to exaggerate the problem or exploit a bad day.

Use the signal to prepare a relevant question and a useful resource. Do not claim you understand the root cause from the outside.

Relationship events

A client introduction, supplier referral, former customer move, local event conversation, or partner account map can create better context than any purchased list. The relationship explains why the conversation is reasonable. It does not make the opportunity qualified.

Keep source attribution attached to the account. If the introduction advances, follow the same disciplined referral process you would use for any other warm opportunity.

Build a trigger card before you add a contact

Do not begin by collecting five people from the same company. Build the account case first.

Each trigger card should capture:

  • Organization and relevant location or business unit
  • Trigger type, observed date, and source link or relationship
  • What changed, stated without speculation
  • The technology decision that may follow
  • What your team needs to verify
  • Best stakeholder and why that person is relevant
  • Conversation owner, next action, and review date
  • Status: research, ready, contacted, engaged, nurture, disqualified, or closed

This record prevents a useful signal from becoming a random note in Slack. It also lets another advisor challenge the logic before anyone sends a message.

Advisor OS CRM connects organizations, contacts, source attribution, activities, reminders, and opportunities. Keep the trigger with the account context so the original reason for outreach does not disappear once a conversation starts.

Separate evidence from your theory

This is where sloppy prospecting gets creepy.

Evidence: the company announced two new locations opening this year. Theory: the current network and support model may need to change. Question: who owns the technology plan for those openings?

Write those as three separate fields. Your first message can reference the evidence and ask the question. It should not present your theory as an inside fact.

Source quality matters too. A company filing or announcement is stronger than an automated intent score. A direct client conversation is useful but may have confidentiality limits. A social post can point you toward research, but it should not carry a serious claim by itself.

AI can help summarize public information and flag possible events. It cannot decide whether the source is current, whether the account actually fits, or whether your message crosses a line. Someone still has to inspect the evidence.

Turn the trigger into a useful opening

The first message needs to answer three things: why this account, why now, and what small next step would be useful.

Keep it plain:

"I saw your announcement about opening locations in Raleigh and Greenville this year. We work with multi-location teams that need to sort out carrier ownership, installation timing, and support before an opening date gets close. Is that plan already set, or would a short pre-opening checklist be useful?"

The message names the public evidence. It describes a problem you understand without claiming the company has it. It offers a relevant next step instead of asking a stranger to sit through a generic introduction.

If the account responds, move it into a real discovery process. Do not treat interest in a checklist as a qualified deal. Confirm the business trigger, stakeholders, current state, timing, and next decision.

Set an exit rule before outreach starts

Trigger lists become stale lists when nobody removes anything.

Give every account a review date. Move it out of active prospecting when the source cannot be verified, the event is no longer current, the likely decision has passed, the account does not fit, the person asks you to stop, or repeated outreach produces no engagement.

Nurture is a decision, not a polite hiding place. Record what would need to change before the account returns. Maybe the next known renewal window is nine months away. Maybe the expansion was canceled. Maybe your firm does not support the required geography. Write it down.

This keeps your pipeline honest because unqualified accounts stay out of opportunity stages until discovery produces an actual decision.

Run a weekly trigger review

Start with twenty accounts, not two thousand.

Once a week, review the new signals, confirm the source, choose the best stakeholder, approve the opening, and remove expired accounts. Track which trigger families create real conversations and which only look interesting in a spreadsheet.

Do not reward the team for contact volume alone. Look at verified triggers, accounts accepted for outreach, conversations started, discovery calls earned, opportunities qualified, and disqualification reasons. The goal is not to manufacture a giant top of funnel. It is to spend more time on accounts where your advice may be relevant now.

Your prospecting list should make an argument. This account changed. That change may create this decision. We have enough evidence to start a respectful conversation.

If your current system cannot keep the source, account, contact, activity, and next action connected, run the free Advisor OS agency scorecard. Find the operating gap before you buy another list.

Build a prospecting list your team can defend

See how Advisor OS connects organizations, contacts, source attribution, activities, reminders, opportunities, and account context in one advisor operating system.

Request an Advisor OS demo