Sales-led Enterprise Motion
Overview
The Sales-led Enterprise motion models cold committee-driven buying in larger accounts. Unlike PLG motions where a Champion often appears first, enterprise deals frequently start with an inbound demo request or outbound engagement from a mid-level stakeholder — and the committee assembles around them.
Use this motion when you are working enterprise accounts (typically 500+ employees) where multiple senior stakeholders must align before a purchase can proceed.
When to Use This Motion
Sales-led Enterprise fits accounts that:
- Are non-customers with 500 or more employees in your target industries
- Engage via inbound demo requests, RFP or RFQ submissions, or outbound campaigns
- Require formal security review, procurement, and legal sign-off before a purchase
If the account is smaller and self-service-oriented, the PLG Acquisition motion is a better fit. If the account is an existing customer, consider PLG Expansion or Renewal.
The Role Set
All five roles are required for a complete buying group. Enterprise deals rarely close without all five stakeholder types engaged.
| Role | Intent | Required |
|---|---|---|
| Champion | Internal advocate driving the deal. | Yes |
| Economic Buyer | Final budget approver. | Yes |
| Technical Evaluator | Owns architecture, integration, security review. | Yes |
| IT / Security | Security questionnaire, vendor risk review. | Yes |
| Procurement | Contract negotiation, MSA, payment terms. | Yes |
Champion
The Champion is the internal stakeholder most invested in the outcome. In enterprise, they are often a Director or VP-level practitioner who initiated the evaluation or is most engaged with the product.
Demographic criteria:
- Title keywords: Manager, Lead, Head of
- Seniority: IC, Manager, Director
- Functions: Product, Operations, Marketing
Economic Buyer
The Economic Buyer holds final budget authority. In large organizations this is typically a VP or C-level leader — often in Finance or the relevant business unit — who approves capital expenditure above a certain threshold.
Demographic criteria:
- Title keywords: CFO, VP Finance, VP, Head of
- Seniority: VP, C-level
- Functions: Finance, Executive
Technical Evaluator
The Technical Evaluator assesses whether the product fits the company's architecture and integration requirements. In enterprise deals, this role often overlaps with a formal proof-of-concept or pilot.
Demographic criteria:
- Title keywords: Engineer, Architect, CTO, VP Engineering
- Seniority: IC, Manager, Director, VP
- Functions: Engineering, IT
IT / Security
IT and Security conduct formal vendor risk review — reviewing SOC2 reports, completing security questionnaires, and evaluating SSO/SAML requirements. Their sign-off is typically a prerequisite for procurement.
Demographic criteria:
- Title keywords: CISO, Security, Head of IT, IT
- Seniority: Manager, Director, VP, C-level
- Functions: Security, IT
Procurement
Procurement owns the commercial process — vendor onboarding, Master Service Agreement negotiation, payment terms, and multi-year contract structures. Their engagement typically signals the deal is past technical evaluation.
Demographic criteria:
- Title keywords: Procurement, Purchasing, Vendor
- Seniority: Manager, Director
- Functions: Procurement, Finance
Suggested Signals and Role Attribution
Assign signal points in Signal Mapping under the lens of this ICP. Enterprise signals tend to be higher-touch than PLG signals, and later-stage signals carry more weight.
| Signal | Strongest For | Notes |
|---|---|---|
| Inbound demo request | Champion, Economic Buyer | Strong intent; often the first high-confidence signal |
| RFP or RFQ submission | Procurement, Champion | Indicates a formal evaluation process |
| Security questionnaire | IT / Security | Often sent mid-cycle; weight heavily |
| Content gating form completion | Champion, Technical Evaluator | White papers, technical briefs, architecture guides |
| Webinar or event attendance | Champion, Technical Evaluator | Multi-stakeholder attendance is especially significant |
| Pricing or packaging page visits | Economic Buyer | Budget side beginning to engage |
| API or integration documentation | Technical Evaluator | Technical evaluation underway |
| MSA or contract template request | Procurement | Late-stage commercial signal |
| Multi-stakeholder content engagement (account-wide) | All roles | Account-level signal; configure at the account layer |
Tip
Account-level signals (multi-stakeholder content engagement, sales cycle stage signals) are configured in the Account Signals section of your ICP, not in Signal Mapping.
Common Configuration Patterns
| Setting | Default | Notes |
|---|---|---|
| Score individual leads | On | Track each committee member's engagement individually |
| Buying group construction | On | Assemble the five-role committee per account |
| Eligibility emphasis | Account rules (employee count + industry + non-customer status) | Filter to 500+ employees in target industries before scoring |
| Qualification emphasis | Committee-level engagement across all five role types | Single-role engagement is insufficient; breadth matters |
| Confidence threshold | Higher | Set a higher bar — enterprise deals require more complete signal |
| Tiebreak order | By signal recency | Most recently engaged stakeholder fills the role |
| Match strictness | Loose | Committee engagement surfaces through more touchpoints than any list captures exhaustively |
Completeness is everything: the Sales-led Enterprise motion requires all five roles. An account with only two or three roles filled should be treated as early-stage, regardless of individual signal strength. Weight your confidence threshold accordingly.
Breadth over depth: a Champion with very high engagement but no Economic Buyer or Procurement signal is a stalled deal. Configure alerts or pipeline rules to surface incomplete buying groups after a set number of days.
Why match strictness is loose: this preset starts in Loose mode, so the rubric may add signals related to what you wrote even if you didn't list them by name — a cold buying committee surfaces through webinars, gated content, RFP artifacts, and other touchpoints that no customer lists exhaustively. Switch to Strict on the Rubric tab if you'd rather the rubric stick to exactly what you named.
Worked Example
Account: Fortis Financial Group (1,400 employees, financial services, non-customer)
Active leads:
| Lead | Activity | Role Assigned |
|---|---|---|
| Annika B. (Director of Revenue Operations) | Attended two webinars, downloaded architecture brief, submitted inbound demo request | Champion |
| Greg M. (CFO) | Visited enterprise pricing page; attended CFO-track session at industry event | Economic Buyer |
| Pavel N. (Staff Software Architect) | Reviewed API reference, completed technical integration guide, participated in proof-of-concept | Technical Evaluator |
| Lisa C. (VP Information Security) | Submitted security questionnaire, requested SOC2 report | IT / Security |
| Renata D. (Senior Procurement Manager) | Requested MSA template, opened vendor onboarding checklist | Procurement |
Buying group assessment:
All five required roles are filled. Annika initiated the evaluation and is driving internal momentum. Greg's event attendance and pricing engagement suggests budget-side awareness. Pavel's PoC participation, Lisa's security questionnaire, and Renata's procurement activity confirm the deal is in active evaluation.
Result: Fortis Financial Group surfaces as a high-priority enterprise opportunity with a fully assembled buying committee. Full sales cycle engagement — executive sponsor, security review support, and commercial terms — is appropriate.
Next Steps
- PLG Expansion — if the account is already a customer
- Renewal — for tracking existing customers approaching contract end
- Signal and Role Attribution — how to assign signal points to roles in this ICP