Sales-Led Growth (SLG) Sales & Operations Playbook
1. The Enterprise SLG CRM Data Model
A strict enterprise SLG model operates on a top-down relationship hierarchy. Unlike PLG, which tracks user habits, the SLG model focuses on mapping organizational charts, identifying champions, and tracking large, high-ticket deal stages.
graph TD
subgraph "SLG CRM Architecture"
MQL(Inbound MQL / Outbound Prospect) --> C(Contact / Stakeholder Matrix)
C --> CO(Company Record)
CO --> O(Active Enterprise Opportunity)
O --> A(Account / Billable Financial Entity)
end
style MQL fill:#e3f2fd,stroke:#b3e5fc
style C fill:#e8f5e9,stroke:#c8e6c9
style CO fill:#fbe9e7,stroke:#ffccbc
style O fill:#fff3e0,stroke:#ffe0b2
style A fill:#f3e5f5,stroke:#e1bee7
Core Objects & Fields for SLG
- Companies: The target corporate organization. Crucial fields include annual revenue, total enterprise employee count, and compliance framework requirements (e.g., SOC2, HIPAA, GDPR).
- Contacts (The Stakeholder Matrix): Real individuals within the target company. For SLG, you must track their specific buying role via a dropdown field: Economic Buyer, Technical Gatekeeper, Executive Sponsor, or Champion.
- Opportunities: Active, human-negotiated sales deals. Key tracking metrics include Estimated Close Date, Contract Value (ARR), and Weighted Pipeline Value based on deal probability.
- Accounts: Activated only upon closing a deal. Manages invoicing, multi-year contract renewals, and professional services billing blocks.
2. The 4-Stage Sales-Led Enterprise Pipeline
The SLG pipeline is a multi-step, value-first framework designed to systematically de-risk a major software purchase for an enterprise client.
graph LR
A[1. Discovery & Qual] --> B(2. Tailored Demo)
B --> C(3. Guided PoC)
C --> D(4. Procurement & Close)
Stage 1: Discovery & Technical Qualification
- Operational Focus: A 30-minute introductory meeting between an Account Executive (AE) and the prospect. The goal is entirely diagnostic: verifying pain points, documenting their current tech stack (for integration compatibility), and confirming budget scope.
- CRM Gating Criteria: Opportunity cannot advance unless the core problem is documented and a formal demonstration is scheduled with key stakeholders.
- Core Sales Metric: MQL-to-SQL Conversion Rate (The percentage of discovery calls that turn into real opportunities).
Stage 2: Tailored Presentation & Scope Alignment
- Operational Focus: The AE and a Solutions Engineer present a deeply customized demonstration of the software. Instead of showing the entire feature set, you focus strictly on solving the specific organizational gaps uncovered during Stage 1.
- CRM Gating Criteria: The prospect must explicitly agree to the success criteria parameters required to launch a Proof of Concept (PoC) evaluation.
- Core Sales Metric: Pipeline Velocity (How fast a deal moves from introduction to active validation).
Stage 3: The Guided Proof of Concept (PoC)
- Operational Focus: A time-boxed evaluation window (typically 14 to 30 days) where the prospect tests the software. Unlike a passive free trial, the sales team schedules weekly syncs, builds a joint mutual action plan, and proactively guides the technical team to their Aha! Moment.
- CRM Gating Criteria: Technical stakeholders sign off that all predefined success metrics (e.g., specific API response times, workflow automation wins) have been achieved.
- Core Sales Metric: PoC Win Rate (Percentage of technical evaluations that result in a verbal agreement).
Stage 4: Commercial Close & Legal Procurement
- Operational Focus: Navigating the enterprise purchasing bureaucracy. The AE coordinates with the prospect’s InfoSec team for security clearances, facilitates legal contract redlines (Master SaaS Agreements, SLAs), and finalizes commercial discount structures.
- CRM Gating Criteria: Legal sign-off from both entities and execution of the digital signature (e.g., DocuSign).
- Core Sales Metric: Average Deal Size (ACV/ARR) & Win Rate.
3. Core Operational Rules for Enterprise SLG
To maintain a predictable enterprise pipeline and protect engineering resources, your sales operations must enforce three absolute guardrails:
- Rule 1: Enforce Strict BANT Gates Before Stage 3: A Proof of Concept (PoC) consumes valuable company resources (Solutions Architect time, custom sandbox configurations). Never authorize a deal to move to Stage 3 unless Budget, Authority, Need, and Timeline (BANT) have been explicitly verified and logged in the CRM.
- Rule 2: Never Deliver a Proposal via Email Post-Demo: When a custom proposal or pricing framework is generated, it must be reviewed live during a scheduled presentation. Emailing a high-ticket contract blindly allows the prospect to review the price in isolation without the context of the business value, frequently stalling the deal.
- Rule 3: Enforce a Clean Handoff Blueprint: The moment a deal marks as Closed-Won, a mandatory automation must trigger a workflow passing all discovery notes, PoC success parameters, and integration details to the Customer Success and Implementation engineering teams. This ensures a seamless onboarding experience for the client.