Enterprise · Playbooks: The operating system for complex deals.

Enterprise deals are won on precision, not volume. One wrong email to a procurement lead and you are blacklisted.

How we build it: How we build it at enterprise

The playbook is not a suggestion. It governs every touchpoint at every target account.

  1. 01

    Map target accounts

    Named accounts from your TAM, competitors and priorities. Each gets a profile, org structure, buying committee, known pains, competitive exposure and entry points.

  2. 02

    Map the buying committee

    6 to 10 stakeholders. VP Ops wants efficiency, the CFO ROI and risk, the CTO integration, procurement compliance and terms. Each gets their own message, sequence and objection handling.

  3. 03

    Compliance-first sequences

    Approved language, DNC scrubbing, call frequency limits, state rules and automated opt-outs. The playbook makes sure reps say the right thing.

  4. 04

    Build for procurement cycles

    Nurture across three to six months, re-engagement when stakeholders go quiet, expansion when a second department can evaluate. It runs past 'meeting booked.'

The stack: Tools underneath the playbook

The tools are infrastructure. The playbook is the strategy that runs on them.

  • Clay

    Account intelligence, stakeholder enrichment, intent signals

  • HeyReach

    LinkedIn outreach across multiple sender profiles

  • Instantly

    Email sequences with compliance controls

  • n8n

    Orchestration from enrichment to CRM

  • HubSpot

    Account-level CRM and pipeline tracking

  • Salesforce

    Enterprise CRM with account attribution

Questions: Common questions

What makes an enterprise playbook different from a standard sales playbook?

It is account-based, not list-based. Each named account gets a committee map, stakeholder messaging and multi-threaded sequences for three to six month cycles. Standard playbooks run volume; enterprise ones run precision.

How do you handle compliance requirements in enterprise outbound?

It is designed into the sequences: approved language, DNC scrubbing, frequency limits, state rules and automated opt-outs.

How many stakeholders does a Phi enterprise playbook account for?

Usually 6 to 10. VP Ops, CFO, CTO, procurement and end users each get their own message, sequence and objection handling.

How often are enterprise playbooks updated?

Weekly, on account intelligence, stakeholder responses, competitive intel and compliance flags. Enterprise playbooks refine rather than pivot.

What tools does Phi use to execute enterprise playbooks?

Clay for intelligence and intent, HeyReach for LinkedIn, Instantly for compliant email, n8n for orchestration, and HubSpot or Salesforce for account-level CRM.

Enterprise · Playbooks← Back to enterprise

Talk to us: See a Phi enterprise playbook for your accounts.

A 30-minute call on your target accounts, your buying committee and your compliance requirements. We will show you how we build it.

Talk to Phi