Module 04
Pipeline Playbooks
Repeatable playbooks with clear ownership between your team and automation.
Questions this topic answers
- What does each side do?
- When is human handoff right?
- How does research become an active lead?
From Market Research to Active Lead: The B2B GTM Pipeline Explained
A B2B pipeline should explain how evidence becomes a next action, not merely display a row of funnel labels. This guide connects research, account preparation, controlled outreach, lead events, qualification, signals, and human action while keeping delivery, engagement, qualification, and ownership changes separate.
Guide
What to Do After a Click, Reply, or Form Submission
A click, reply, or form submission is the beginning of an operating decision. The event must be captured, resolved to the right record, screened for safety and stop conditions, interpreted in context, evaluated against qualification evidence, routed to an owner, and answered within a defined service window.
Guide
A GTM Readiness Checklist for Export Manufacturers
A manufacturer can have a promising market and a precise ICP while still being unready to start outreach. Before creating demand, the team must be able to make supportable claims, answer technical questions, define delivery responsibility, handle inquiries, preserve evidence, respect communication controls, and stop work safely when a condition fails.
Checklist
When to Follow Up, Change Contacts, or Stop
No response is not a complete diagnosis. The correct next action depends on delivery evidence, contact validity, role and account context, elapsed time, prior human interaction, campaign limits, and explicit stop signals. This guide replaces reflexive follow-up with a reviewable decision.
Guide
How to Design a Pipeline Around Evidence, Not Activity
Sending more messages can increase activity while making the pipeline less trustworthy. An evidence-led pipeline starts with the commercial decisions the team must make, defines the claims required for each decision, preserves event provenance, applies hard gates, and creates accountable work only when evidence changes what should happen next.
Framework
Pipeline Stages, Lifecycle States, Events, and Tasks: What Each One Means
Many pipeline failures begin with one overloaded status field. A stage is a managed process position; a lifecycle state is a validated condition of a lead; an event is a timestamped occurrence; and a task is accountable work. Each object has different rules, history, ownership, and reporting consequences.
Explainer
How to Define Entry and Exit Criteria for Every Pipeline Stage
A stage name without entry and exit criteria is a shared guess. Teams will move records for different reasons, automation will act on inconsistent states, and reports will compare unlike work. A stage contract fixes the scope, evidence, controls, ownership, time boundaries, and allowed outcomes before implementation.
Framework
How to Build a Minimum Viable Outreach Operation Before Scaling
Minimum viable does not mean a few messages and a spreadsheet. A viable outreach operation must complete the entire control loop: approved scope, verified contact path, supportable message, delivery evidence, response handling, qualification, human routing, suppression, exception review, and a decision about whether to continue.
Guide
How to Route Leads Without Losing Context or Ownership
A route is not complete when a record appears in another queue. The recipient must understand what happened, what has been promised, what evidence is known or unresolved, what communication is allowed, and what action is due. Ownership must be offered, accepted, monitored, and recoverable.
Guide
How to Build a Pipeline Evidence Ledger
A current status can tell a team what the system believes now, but not why it believes it, what evidence changed, which rule applied, or whether a stop arrived before a queued action. A pipeline evidence ledger preserves that chain without turning the database into an unstructured archive.
Template
What a Landing Page Visit Does and Does Not Prove
A landing page visit is an observable request for content, not a complete explanation of who requested it or why. This explainer shows how to validate the event, preserve attribution uncertainty, connect it to an account, and decide whether it supports research, follow-up, or qualification.
Explainer
How to Classify Email Replies Without Overstating Buyer Intent
A reply proves that a message returned through an email channel. Its commercial meaning depends on the sender, content, context, and requested action. This framework classifies replies transparently while keeping sentiment, intent, fit, urgency, and permission as separate evidence fields.
Framework