Pipeline Playbooks — Page 2
How to Handle Form Submissions: Identity, Fit, Intent, and Urgency
A form submission contains information a visitor chose or attempted to provide, but every field has a different evidentiary meaning. This playbook separates identity, ICP fit, stated intent, urgency, traffic integrity, and treatment so that natural and campaign traffic enter one controlled qualification path.
Guide
How to Resolve Multiple Signals From the Same Person or Company
One person can visit, reply, and submit a form; several people at one company can do the same. More events do not automatically mean more leads or stronger intent. This framework preserves raw evidence, resolves identity carefully, and groups related events into actionable signal episodes.
Framework
How to Separate Deliverability Events From Buyer Signals
Email systems produce many events before a buyer does anything: acceptance, delay, bounce, security inspection, link scanning, and automated replies. This guide separates transport and control-plane evidence from human commercial signals so reporting, suppression, contact replacement, and follow-up remain accurate.
Guide
How to Prioritize Signals Without a Black-Box Lead Score
Signal priority should answer which valid item needs attention first and why. It should not pretend to predict a purchase. This decision guide uses visible hard gates, explicit requests, evidence confidence, ICP fit, freshness, consequence, and service obligations to create an auditable work queue.
Guide
How to Handle Anonymous Website Activity in B2B GTM
Anonymous activity can reveal which content was requested, when, and in what technical context. It cannot name a person or explain a buying decision. This guide shows how to filter machine noise, preserve uncertainty, use possible company context carefully, and route activity to research rather than invented outreach.
Guide
How to Verify a Signal Before Creating a Qualified Lead
A signal begins the qualification decision; it does not replace it. This checklist shows how to verify event validity, identity and profile completeness, agreed ICP criteria, freshness, treatment, and evidence traceability consistently across landing page visits, direct replies, and forms.
Checklist
How to Route Wrong-Contact, Referral, and Forwarded Replies
A wrong-contact reply can improve account data, a referral can reveal a possible route, and a forward can show internal circulation. None proves that the next person is interested or can be contacted automatically. This playbook preserves the original person's treatment while verifying the new route.
Guide
How to Handle Conflicting, Duplicate, or Stale Signals
Pipeline evidence changes. Providers retry events, people correct forms, roles change, replies contradict earlier activity, and once-current research expires. This framework separates immutable observations from revisable conclusions and gives each duplicate, conflict, supersession, and stale state a controlled resolution path.
Framework
How to Design a 30-Day B2B Follow-Up Window
A follow-up window is not permission to send for 30 straight days. It is a bounded period for observing evidence, choosing the next useful action, honoring contact and company stop states, and deciding whether the company should advance, enter another round, or close. This playbook makes each part explicit.
Guide
How to Run Multi-Round Company Outreach Without Repeating Yourself
A second outreach round should not be the first round with a new subject line. It should begin only when the company has no active lead or governing human interaction, remain inside all stop controls, and use prior evidence to change the account hypothesis, contact rationale, or useful offer.
Guide
How to Replace a Contact Without Resetting Account Learning
A new contact does not create a new account history. When an address bounces, a person has left, a role is wrong, or follow-up proves a mismatch, the replacement must inherit relevant company learning, prior message exposure, stop controls, and the current round boundary without inheriting unsupported assumptions about the person.
Guide
Hard Bounce, Unsubscribe, Wrong Contact, or Company Stop? A Decision Guide
A failed address, a role correction, an opt-out, and a request to stop contacting the company create different evidence and different operational consequences. This guide provides a scope-first decision method so teams stop what must stop, preserve useful account learning, and never treat replacement as a way around a clear request.
Guide