Bottom line up front
Growth is the practical self-serve tier for a focused GTM team that needs roughly 6,000 Data Credits and 40,000 Actions per month, native CRM auto-sync/enrichment, HTTP API integrations, and repeatable waterfall workflows.
Enterprise is the control-plane and capacity tier: pricing and volume are custom, and the buying case is governance, isolation, support, reliability, security/compliance, and bespoke data/integration architecture - not simply "more credits."
Evidence boundary: Clay's public pricing page confirms Growth starting at $495/month, 6,000 Data Credits, 40,000 Actions/month, unused-credit accumulation up to 2x monthly allocation, CRM auto-sync/enrichment, HTTP API integrations, and waterfall as a product capability. The requested Enterprise details (dedicated IP pools, private MCP, SCIM, HIPAA/SOC 2 scope, SLA terms, RBAC depth, custom providers, dedicated personnel) are enterprise-contract items to confirm in a quote/security packet - they are not publicly itemized on the page reviewed.
At a glance
Twelve dimensions that separate the tiers, with the decision each one forces.
| Dimension | Growth | Enterprise | Decision implication |
|---|---|---|---|
| Commercial model | Starting at $495/month; self-serve packaging | Custom quote and volume | Forecast usage, providers, and service needs before comparing sticker price |
| Data capacity | 6,000 Data Credits/month; unused credits can accumulate up to 2x monthly allocation | Custom volume/commitment | Growth is bounded and predictable; Enterprise is negotiated for large or variable demand |
| Workflow capacity | 40,000 Actions/month | Custom capacity and scaling plan | Actions are execution budget, distinct from data-provider credits |
| Rate limits / concurrency | Standard plan limits; confirm exact endpoint/table limits in current contract/docs | Negotiated limits, routing, and/or dedicated worker pools | Enterprise matters when bursts and latency are operational requirements |
| Seats | Team collaboration included; exact seat allowance should be confirmed at purchase | Custom seat model and centralized controls | Model active builders, operators, approvers, and read-only users |
| Waterfall integrations | Native waterfall: sequence providers to improve coverage and control spend | Custom providers/endpoints can extend the sequence | Growth handles standard sources; Enterprise handles proprietary or regulated sources |
| CRM writebacks | CRM auto-sync and enrichment; standard native integrations | Broader architecture, governance, and custom routing | Decide whether Clay is enrichment layer, system of action, or both |
| Support | Standard/self-serve support | Dedicated solutions engineer / GTM architect and contractual support | Enterprise buys implementation certainty, not only software |
| Webhooks/API | HTTP API integrations are included; exact webhook limits need confirmation | Custom API/webhook posture and higher-volume routing may be negotiated | Put queues, retries, idempotency, and backpressure outside the happy path |
| Network/isolation | Shared service assumptions unless contract says otherwise | Dedicated IP pools and isolation options subject to contract | Relevant for allowlists, regulated data, and security review |
| Identity/security | Standard workspace access | Enterprise SSO/SCIM, advanced governance/RBAC; HIPAA/SOC 2 only as contract/security scope | Require DPA, subprocessors, retention, audit, and compliance evidence |
| Reliability | Standard platform availability | SLA guarantees subject to signed terms | Define uptime, response, credits, RTO/RPO, and exclusions |
Definitions and GTM context
The vocabulary you need to compare the tiers precisely, each with its GTM consequence.
- Waterfall enrichment
- A prioritized chain of data providers. Clay tries provider A, then provider B, and so on until it gets an acceptable answer or exhausts the chain. Example: work email provider, then mobile provider, then company-domain provider. GTM value: higher match rate with less unnecessary spend than calling every provider for every row.
- Data Credits and credit consumption rates
- A Data Credit is the usage unit for provider-sourced data. A consumption rate is how many credits a specific lookup consumes; rates vary by provider, field, and result policy and must be checked in the current Clay workspace/catalog. Example: only request a phone after an email miss, and monitor credits per qualified lead rather than treating every row equally.
- Actions
- Execution units for workflow operations such as running enrichment logic, transforms, or other table/workflow steps. Growth's public allocation is 40,000 Actions/month. Actions and Data Credits are separate budgets.
- Webhook concurrency
- The number of webhook-triggered jobs that can be in flight at once. Concurrency is not the same as monthly volume. Example: 500 simultaneous lead events can create queueing even when monthly credits remain.
- Native CRM bi-directional sync
- A two-way integration that reads records/changes from a CRM and writes enriched or routed fields back, with field mapping and update rules. Example: sync new Salesforce accounts into Clay, enrich them, and write back industry, employee band, and routing status while preventing update loops.
- Entity resolution
- Matching records that refer to the same person or organization across systems. Example: normalize Acme, Inc., its domain, CRM account ID, and warehouse key into one canonical entity before enrichment.
- Custom providers / private MCP
- A custom provider is a proprietary or contract-specific data endpoint exposed to Clay's workflow. A private MCP server is an organization-controlled Model Context Protocol server that exposes approved tools/data to an agent or workspace. Example: call an internal product-usage endpoint without exposing it to other tenants. Confirm availability, isolation, logging, and data-retention terms with Clay.
- Execution latency
- Time from trigger acceptance to completed result/writeback. GTM context: a real-time inbound router may need seconds, while nightly TAM refresh can tolerate hours. Measure p50/p95 and include provider latency, retries, queues, and CRM API limits.
- Dedicated worker pools
- Reserved execution capacity for a tenant or workload class. They reduce noisy-neighbor and burst-risk concerns but do not guarantee latency unless the contract specifies it.
- Workspace governance
- The policies and controls that determine who can build, run, approve, export, connect, or administer workflows. Enterprise governance commonly includes SSO/SCIM, role-based access control, auditability, environment separation, approval paths, and connector restrictions; verify the exact Clay feature matrix.
- SSO and SCIM
- SSO (single sign-on) delegates authentication to an identity provider. SCIM automates user and group provisioning/deprovisioning. Example: removing a user from the IdP group removes workspace access without a manual Clay action.
- SLA guarantees
- Contractual service commitments, typically availability plus support response obligations and remedies. A marketing uptime statement is not an SLA; request exact uptime, measurement window, exclusions, maintenance policy, and service credits.
Scenario 1 - Growth company, 10,000 leads/month
A focused team running a repeatable, provider-native enrichment loop inside the Growth envelope.
Import 10,000 target leads from CRM or CSV; resolve person/company identity and deduplicate.
Run a native waterfall: domain/company match first, then work email, then phone only for prioritized segments.
Use conditional logic to spend credits only when a prior provider misses; log provider, confidence, and credit cost per row.
Enrich title, seniority, employee band, industry, and intent signals; use Actions for transforms and routing.
Write approved fields to the CRM through native sync; put campaign-ready records into a sequencer or downstream activation.
Use HTTP API/webhooks for bounded event-driven intake, with an external queue, idempotency key, retry policy, and dead-letter path.
Operate a monthly budget dashboard: credits consumed/lead, waterfall hit rate, action utilization, CRM writeback failures, p95 latency, and queue depth.
Fit test: Growth works when standard providers and native integrations meet requirements, traffic can be queued, and the team can live within the 6,000-credit/40,000-action envelope or buy documented add-ons/upgrade.
Scenario 2 - Enterprise, global multi-business-unit GTM
A governed, high-volume deployment across business units with custom data paths and contractual support.
Separate business units or environments with delegated roles, approval gates, connector policies, and audit trails; provision access through SSO/SCIM.
Ingest warehouse-defined accounts and changes using a governed reverse-ETL or warehouse-native pattern; preserve warehouse IDs for entity resolution and lineage.
Route enrichment through standard Clay providers plus approved custom/private endpoints for proprietary firmographic, product-usage, or regional data.
Use high-volume automated routing with queues, backpressure, retry budgets, idempotency, and workload isolation; negotiate capacity, concurrency, worker pools, and latency targets.
Apply region/business-unit policy to fields and providers; minimize sensitive data and validate HIPAA/SOC 2 obligations against the signed scope rather than assuming a badge covers every workflow.
Write back to multiple CRMs or destinations with ownership rules, conflict resolution, and replayable change logs.
Use the dedicated solutions engineer/GTM architect to design provider fallbacks, migration, observability, and operating model; put availability and support commitments in the SLA.
Fit test: Enterprise is justified when governance, custom data paths, high-volume reliability, security review, or contractual support are blockers - not merely because a team wants a larger table.
Buying checklist
Ask Clay to confirm each of these in writing before procurement.
- Exact Growth seat limits
- Current provider-by-provider credit rates
- Monthly rollover/top-up rules
- Table, API, webhook, and concurrency limits
- Retry behavior
- CRM sync directionality and conflict handling
- Enterprise volume/overage economics
- Dedicated IP availability
- Private MCP architecture and data handling
- SSO/SCIM and RBAC matrix
- Audit logs and environment separation
- HIPAA/SOC 2 scope and reports
- Named support resources
- SLA uptime/response/remedies
- Custom-provider onboarding, ownership, and incident process
- Data residency, retention, deletion, and subprocessors
Evidence boundary
What is publicly confirmed versus what must be confirmed in contract.
- Growth starting at $495/month
- 6,000 Data Credits/month
- 40,000 Actions/month
- Unused-credit accumulation up to 2x monthly allocation
- CRM auto-sync/enrichment
- HTTP API integrations
- Waterfall as a product capability
- Dedicated IP pools
- Private MCP
- SCIM
- HIPAA/SOC 2 scope
- SLA terms
- RBAC depth
- Custom providers
- Dedicated personnel
Sources and freshness
Search cross-checks surfaced secondary summaries consistent with $495/month, 6,000 Data Credits, and 40,000 Actions, but this note treats Clay's own pricing page as authoritative for public claims.
This is a research note, not a Clay quote or security/compliance opinion. Pricing, limits, features, and contract terms can change; revalidate before procurement.