PBK-A003 / implementation playbook / Outbound sales

RevOps-Controlled Outbound Engine Playbook

RevOps-Controlled Outbound Engine Playbook
Outcome

CRM sync rules are fixed before outbound automation pushes enriched records, sequence state, or replies across systems.

Pre-launch guardrail9 operator steps mapped with input, output, QA, and failure signals.
DIFFICULTY
Advanced
Outbound sales
TIME
18h
implementation estimate
STEP COUNT
9
operator steps
OWNER
RevOps
RevOps, Sales Ops
TOOLS
5
required components
Prerequisites
  • 01Salesforce admin access
  • 02n8n workflow owner
  • 03Smartlead suppression list export
  • 04Outreach ownership decision
RUNBOOK

Operator step flow

01
CRM
RevOps

Lock Salesforce source-of-truth fields

Input

Salesforce 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 Salesforce handoff against a manual sample before the next step runs.

Failure signal

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

02
Enrichment
Sales Ops

Export current sequence and suppression state

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

Sales Ops 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.

03
Workflow
RevOps

Define Clay write-back limits

Input

Smartlead 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 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 workflow layer.

04
AI
Sales Ops

Build n8n sync guardrails

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

Sales Ops 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

Test Smartlead reply and bounce routing

Input

Outreach 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 Outreach handoff against a manual sample before the next step runs.

Failure signal

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

06
Analytics
Sales Ops

Reconcile Outreach ownership

Input

Salesforce 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

Sales Ops confirms the Salesforce handoff against a manual sample before the next step runs.

Failure signal

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

07
CRM
RevOps

Run duplicate and stale-state audit

Input

Clay 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 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 crm layer.

08
Enrichment
Sales Ops

Approve rollback path

Input

Smartlead 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

Sales Ops 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 enrichment layer.

09
Workflow
RevOps

Schedule post-launch sync review

Input

n8n 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 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 workflow layer.

LAUNCH CHECKS

Checks before scale-up

CRM write guard

RevOps

Gate
Pass signal

Every automated write has an owner, source, and overwrite rule.

Failure signal

Salesforce accepts enrichment fields without source or overwrite rules.

Sequence state

Sales Ops

Gate
Pass signal

One system owns each sequence state and the other reads it.

Failure signal

Reply, bounce, or suppression state is split between Smartlead and Outreach.

Rollback path

RevOps

Gate
Pass signal

The team can pause n8n and restore the last clean CRM state.

Failure signal

Rollback requires manual field cleanup across multiple systems.

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 before adding the fourth SDR or before letting both Outreach and Smartlead touch the same audience.
SUBSTITUTIONS

Tool swaps and tradeoffs

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