PBK-A002 / implementation playbook / Outbound sales

Founder-Led Outbound Lite Stack Playbook

Founder-Led Outbound Lite Stack Playbook
Outcome

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

Overlap cleanup6 operator steps mapped with input, output, QA, and failure signals.
DIFFICULTY
Beginner
Outbound sales
TIME
5h
implementation estimate
STEP COUNT
6
operator steps
OWNER
Founder
Founder
TOOLS
4
required components
Prerequisites
  • 01Apollo account
  • 02HubSpot workspace
  • 03Zapier account
  • 04Sending domain status checked
RUNBOOK

Operator step flow

01
CRM
Founder

Inventory existing outbound ownership

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

Founder 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.

02
Enrichment
Founder

Choose HubSpot vs Apollo record ownership

Input

HubSpot 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

Founder 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 enrichment layer.

03
Workflow
Founder

Disable duplicate Zapier handoffs

Input

Zapier 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

Founder confirms the Zapier handoff against a manual sample before the next step runs.

Failure signal

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

04
AI
Founder

Limit Smartlead to sending state

Input

Smartlead 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

Founder 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 ai layer.

05
Outreach
Founder

Run founder sample review

Input

Apollo 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

Founder 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 outreach layer.

06
Analytics
Founder

Document the weekly cleanup rule

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

Founder 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.

LAUNCH CHECKS

Checks before scale-up

Ownership map

Founder

Gate
Pass signal

Apollo, HubSpot, Zapier, and Smartlead each own one narrow job.

Failure signal

Founder still cannot name which tool owns each outbound state.

Duplicate path check

Founder

Gate
Pass signal

No record can enter the workflow through two automated paths.

Failure signal

Zapier or Apollo creates records that HubSpot also creates.

Weekly rule

Founder

Gate
Pass signal

The weekly review rule names the tool, owner, and stop condition.

Failure signal

A future cleanup depends on memory instead of a written rule.

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
  • 01When outbound becomes a weekly operating cadence for more than one seller, Zapier and HubSpot sequence limits become the first pressure points.
SUBSTITUTIONS

Tool swaps and tradeoffs

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