Phi

Enterprise · Playbooks

The Operating System for Complex Deals

Enterprise deals are not won with volume. They are won with precision. One wrong email to a procurement lead and you are blacklisted. The playbook is not a suggestion. It is the operating system for every touchpoint at every target account.

How we build it

How We Build It at Enterprise

01

Map Target Accounts

Enterprise is not list-based. It is account-based. We identify named accounts based on your total addressable market, competitive landscape, and strategic priorities. Each account gets a company profile, organizational structure, buying committee composition, known pain points, competitive exposure, and entry point identification.

02

Map the Buying Committee

Enterprise deals have 6-10 stakeholders. The VP Ops cares about efficiency. The CFO cares about ROI and risk. The CTO cares about integration. The procurement lead cares about compliance and contract terms. Each stakeholder gets their own messaging, their own sequence, their own objection handling framework.

03

Design Compliance-First Sequences

In regulated verticals, every outbound touchpoint is a potential compliance surface. Approved language for regulated products. DNC scrubbing before every campaign. Call frequency limits respected. State-specific restrictions honored. Opt-out handling automated. The playbook does not hope reps say the right thing. It ensures they do.

04

Build for Procurement Cycles

Enterprise deals take months, not weeks. Multi-touch nurture sequences keep the account warm across a 3-6 month cycle. Re-engagement triggers fire when stakeholders go quiet. Expansion sequences activate when one department is live and another is evaluable. The playbook does not end at “meeting booked.” It spans the entire buying journey.

The stack

Tools underneath the playbook

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

  • ClayAccount intelligence, stakeholder enrichment, intent signals
  • HeyReachLinkedIn outreach across multiple sender profiles
  • InstantlyEmail sequences with compliance controls
  • n8nWorkflow orchestration from enrichment to CRM
  • HubSpotAccount-level CRM and pipeline tracking
  • SalesforceEnterprise CRM with account attribution

FAQ

Frequently asked questions

  • Enterprise playbooks are account-based, not list-based. Each named account gets a dedicated buying committee map, stakeholder-specific messaging, and multi-threaded sequences designed for 3-6 month procurement cycles. Standard playbooks run volume. Enterprise playbooks run precision.

  • Compliance is built into the sequence design, not added as an afterthought. That means approved language for regulated verticals, DNC scrubbing before every campaign, call frequency limits enforced, state-specific restrictions honored, and opt-out handling automated. The playbook ensures reps say the right thing every time.

  • Enterprise deals typically involve 6-10 stakeholders. Each persona gets their own messaging, their own sequence, and their own objection handling framework. The VP of Operations, the CFO, the CTO, the procurement lead, and the end user all have different concerns. We address each one.

  • The iteration cycle is weekly. Account-level intelligence is reviewed, stakeholder response data is analyzed, competitive intelligence is gathered, and compliance flags are addressed. Unlike seed-stage playbooks that pivot frequently, enterprise playbooks refine. Precision tuning, not wholesale rebuilds.

  • Clay for account intelligence, stakeholder enrichment, and intent signal monitoring. HeyReach for LinkedIn outreach across multiple sender profiles. Instantly for email sequences with compliance controls. n8n for workflow orchestration. HubSpot or Salesforce for account-level CRM and pipeline tracking.

See what a Phi enterprise playbook looks like for your accounts

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