AIAutomationStacks
PLAYBOOKS / IMPLEMENTATION

AI automation playbooks

Practical implementation guides for selecting, sequencing, and operating AI automation stacks without buying redundant tools.

Search playbooks
4 playbooks
FiltersNo active filters
01 / Stack
02 / Tool
03 / Comparison
04 / Use case
05 / Difficulty
06 / Owner
07 / Stage
4 playbooks
Outcome group

Outbound sales

Implementation entries are grouped by the outcome they operate, with owner, QA, failure, stack, and cost signals visible before opening the runbook.

4 playbooks
PBK-A004

Clay-Heavy GTM Engineering Stack Playbook

Failure-mode QAIntermediate
Outcome

The team can spot Clay, Apollo, Smartlead, HubSpot, and n8n failure modes before scaling send volume.

OWNER
GTM Engineer
STEPS
7 steps
TIME
10h setup
ROLES
2
GTM EngineerRevOps
Decision point

Confirm the owner before connecting production data.

QA (3)

Confirm required tools are connected with the right permissions.

Failure mode

The workflow ships before ownership is clear.

Review

Stack reviewed 2026-05-22

Evidence

Official cost evidence

Context

PBK-A004 mapped to COST-A004 for STK-A004

Required tools
clayapollosmartleadhubspotn8n
Run playbook View stackSee cost model
PBK-A002

Founder-Led Outbound Lite Stack Playbook

Overlap cleanupBeginner
Outcome

A founder can reduce overlap by deciding when Apollo, HubSpot, Zapier, and Smartlead should each own a narrow part of outbound.

OWNER
Founder
STEPS
6 steps
TIME
5h setup
ROLES
1
Founder
Decision point

Confirm the owner before connecting production data.

QA (3)

Confirm required tools are connected with the right permissions.

Failure mode

The workflow ships before ownership is clear.

Review

Stack reviewed 2026-05-22

Evidence

Official cost evidence

Context

PBK-A002 mapped to COST-A002 for STK-A002

Required tools
apollohubspotzapiersmartlead
Run playbook View stackSee cost model
PBK-A003

RevOps-Controlled Outbound Engine Playbook

Pre-launch guardrailAdvanced
Outcome

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

OWNER
RevOps
STEPS
9 steps
TIME
18h setup
ROLES
2
RevOpsSales Ops
Decision point

Confirm the owner before connecting production data.

QA (3)

Confirm required tools are connected with the right permissions.

Failure mode

The workflow ships before ownership is clear.

Review

Stack reviewed 2026-05-22

Evidence

Official cost evidence

Context

PBK-A003 mapped to COST-A003 for STK-A003

Required tools
salesforceclaysmartleadn8noutrearch
Run playbook View stackSee cost model
PBK-A001

SMB Outbound Velocity Stack Playbook

Build pathIntermediate
Outcome

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

OWNER
RevOps
STEPS
8 steps
TIME
14h setup
ROLES
2
RevOpsSDR Lead
Decision point

Confirm the owner before connecting production data.

QA (3)

Confirm required tools are connected with the right permissions.

Failure mode

The workflow ships before ownership is clear.

Review

Stack reviewed 2026-05-22

Evidence

Official cost evidence

Context

PBK-A001 mapped to COST-A001 for STK-A001

Required tools
hubspotapolloclayn8nsmartlead
Run playbook View stackSee cost model