PBK-A001 / implementation playbook / Outbound sales

SMB Outbound Velocity Stack Playbook

SMB Outbound Velocity Stack Playbook
Outcome

A working outbound motion that enriches leads, keeps HubSpot clean, and sends through Smartlead without duplicate audience ownership.

Build path8 operator steps mapped with input, output, QA, and failure signals.
DIFFICULTY
Intermediate
Outbound sales
TIME
14h
implementation estimate
STEP COUNT
8
operator steps
OWNER
RevOps
RevOps, SDR Lead
TOOLS
5
required components
Prerequisites
  • 01HubSpot admin access
  • 02Apollo workspace
  • 03Clay workspace
  • 04Smartlead workspace
  • 05n8n workflow owner
RUNBOOK

Operator step flow

01
CRM
RevOps

Freeze HubSpot field ownership

Input

HubSpot access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed crm handoff that can move to the next stack layer without creating overlap.

QA gate

RevOps confirms the HubSpot handoff against a manual sample before the next step runs.

Failure signal

HubSpot creates unclear ownership, duplicate work, or an unreviewed usage signal in the crm layer.

02
Enrichment
SDR Lead

Map Apollo source fields

Input

Apollo access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed enrichment handoff that can move to the next stack layer without creating overlap.

QA gate

SDR Lead confirms the Apollo handoff against a manual sample before the next step runs.

Failure signal

Apollo creates unclear ownership, duplicate work, or an unreviewed usage signal in the enrichment layer.

03
Workflow
RevOps

Build Clay enrichment table

Input

Clay access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed workflow handoff that can move to the next stack layer without creating overlap.

QA gate

RevOps confirms the Clay handoff against a manual sample before the next step runs.

Failure signal

Clay creates unclear ownership, duplicate work, or an unreviewed usage signal in the workflow layer.

04
AI
SDR Lead

Route enrichment through n8n

Input

n8n access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed ai handoff that can move to the next stack layer without creating overlap.

QA gate

SDR Lead confirms the n8n handoff against a manual sample before the next step runs.

Failure signal

n8n creates unclear ownership, duplicate work, or an unreviewed usage signal in the ai layer.

05
Outreach
RevOps

Create Smartlead audience boundary

Input

Smartlead access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed outreach handoff that can move to the next stack layer without creating overlap.

QA gate

RevOps confirms the Smartlead handoff against a manual sample before the next step runs.

Failure signal

Smartlead creates unclear ownership, duplicate work, or an unreviewed usage signal in the outreach layer.

06
Analytics
SDR Lead

Run a 25-record manual sample

Input

HubSpot access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed analytics handoff that can move to the next stack layer without creating overlap.

QA gate

SDR Lead confirms the HubSpot handoff against a manual sample before the next step runs.

Failure signal

HubSpot creates unclear ownership, duplicate work, or an unreviewed usage signal in the analytics layer.

07
CRM
RevOps

Sync replies and suppressions back to HubSpot

Input

Apollo access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed crm handoff that can move to the next stack layer without creating overlap.

QA gate

RevOps confirms the Apollo handoff against a manual sample before the next step runs.

Failure signal

Apollo creates unclear ownership, duplicate work, or an unreviewed usage signal in the crm layer.

08
Enrichment
SDR Lead

Review first-week owner dashboard

Input

Clay access, current outbound sales records, and the latest owner decision for this layer.

Output

A reviewed enrichment handoff that can move to the next stack layer without creating overlap.

QA gate

SDR Lead confirms the Clay handoff against a manual sample before the next step runs.

Failure signal

Clay creates unclear ownership, duplicate work, or an unreviewed usage signal in the enrichment layer.

LAUNCH CHECKS

Checks before scale-up

Sample run

RevOps

Gate
Pass signal

25 sampled records enrich, sync, and suppress without duplicate ownership.

Failure signal

Records enrich or send while HubSpot ownership is still ambiguous.

Audience boundary

SDR Lead

Gate
Pass signal

Every sending list has one CRM source and one suppression source.

Failure signal

Smartlead audiences diverge from CRM status or suppression rules.

Owner dashboard

RevOps

Gate
Pass signal

The owner can review cost, reply, bounce, and duplicate signals in one pass.

Failure signal

Weekly review cannot explain spend, bounces, replies, or duplicate records.

Decision points
  • 01Confirm the owner before connecting production data.
  • 02Decide which layer is the system of record before adding automation.
QA checklist
  • 01Confirm required tools are connected with the right permissions.
  • 02Run a manual sample before enabling automated handoff.
  • 03Check duplicate records, routing errors, and usage caps after launch.
What can go wrong
  • 01The workflow ships before ownership is clear.
  • 02Usage or credit caps are missed during QA.
  • 03A tool swap duplicates work in an adjacent stack layer.
Breakpoints
  • 01Replan when the team crosses 3 active senders or when Clay tables start running daily enrichment jobs.
SUBSTITUTIONS

Tool swaps and tradeoffs

hubspotHubSpotapolloApolloUse as an escalation path when the default tool cannot own the workflow boundary. Swap only when the receiving layer already has a clear owner.