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 at Enterprise
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.
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.
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.
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.
ABM vs. Volume: The Fundamental Difference
The playbook reflects where you are in the go-to-market journey.
The Iteration Cycle
Enterprise playbooks iterate weekly, but the inputs are different from seed or growth-stage.
Precision tuning, not wholesale rebuilds
At seed, playbooks pivot weekly as the team discovers what works. At enterprise, the playbook refines. Each iteration sharpens what is already proven.
Wholesale rebuilds at enterprise signal that the targeting was wrong from the start. Precision tuning signals that the foundation is right and the edges are being calibrated.
Every word reviewed. Every touchpoint intentional. Every sequence designed to advance the account, not just book a meeting.
Tools underneath the playbook
The tools are infrastructure. The playbook is the strategy that runs on them.
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.
Talk to usFrequently asked questions
What makes an enterprise playbook different from a standard sales playbook?
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.
How do you handle compliance requirements in enterprise outbound?
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.
How many stakeholders does a Phi enterprise playbook account for?
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.
How often are enterprise playbooks updated?
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.
What tools does Phi use to execute enterprise playbooks?
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.