Turn a verified signal into an approved campaign

A signal is a reason to investigate

Narrated reference walkthrough. System-generated voice. Illustrative inputs.

0:00 The decision
This narrated reference walkthrough uses illustrative campaign inputs and sends no messages. A company change is a reason to investigate, not proof of buying intent. The workflow checks fit, timing, ownership and suppression before a reviewed first touch can become an eligible campaign. It keeps a hypothesis separate from a sourced fact.

0:30 Verify the event date
Record the source, actual event date, observation date and relevance to the problem you solve. Discovering an old announcement today does not make it fresh. A new leader can be verified. Their budget or dissatisfaction cannot be invented from the appointment. Useful research is precise about what the evidence actually supports.

1:00 Inspect eligibility
The branch reads company fit independently of timing and checks customers, open deals, opt-outs, cooldowns and overlapping campaigns. Existing relationship owners receive useful intelligence without a new cold sequence. A stopped account retains its reason. Only an eligible cohort proceeds to message strategy, contact checks and human review.

1:30 Run the eligible example
The example combines supported fit, a current verified signal, no exclusion and a reviewed first touch. The result is eligible for final campaign checks. It still does not send. Actual sender readiness, contact relevance and the approved loading contract remain separate jobs before a live campaign can start.

2:00 Fit cannot be rescued by timing
Change company fit to weak or unknown. The example moves to research or exclusion. A dramatic announcement does not establish that the company can benefit or buy. Buying contacts at this point adds cost without improving the commercial hypothesis. Check the company definition before expanding an interesting but badly matched signal cohort.

2:30 Retire stale or unverified evidence
Restore fit and make the signal stale or unverified. The example asks for retirement or verification. Keep the source and the event date so the operator can understand the decision. A real signal library needs expiry and confidence rules that reflect the company’s buying problem, not a universal timing assumption.

3:00 Honor the exclusion
Now add a customer, deal, opt-out or campaign collision. The example does not load the account. A commercial opportunity never overrides suppression. Where an existing relationship is the reason for the block, give useful intelligence to that owner. Repeated webhooks must not silently bypass the decision or reopen another campaign.

3:30 Keep unreviewed copy in draft
Remove the exclusion but make the first touch a draft. The result stays in draft. Check the sourced opener, useful insight, role match and supported proof. Remove the call to action and read the message again. If nothing useful remains, the campaign needs a better idea rather than more personalization.

4:00 Judge qualified outcomes
The campaign receipt names eligibility, hypothesis, useful asset and review state. Report campaign totals for automated work, keeping account-specific depth for Tier One ABM. Read qualified human replies, conversations and mature pipeline separately. A detected signal, a positive reply and a qualified opportunity are different stages of evidence.

4:30 Put the decision to work
Use the full workflow to test stale events, weak fit, open deals, opt-outs and duplicate notifications. Choose the outbound motion after fit, timing and economics are understood. GTMhub runs the approved campaign through outbound and ABM on the company brain, with people accountable for claims, response handling and commercial decisions.