Clay Pricing

Buying path

Start with Clay's free workspace when the aim is to learn tables, waterfalls, Claygent and the shape of the data before committing. Use the time-limited trial when the evaluation must include CRM connections, webhooks or HTTP API integrations. For a production prospecting motion that does not depend on first-party system sync, Launch is the clearest paid benchmark.

Treat Growth as the threshold for an operating GTM system rather than as a simple capacity bump. Its value appears when Clay needs to refresh CRM or warehouse data, react to web intent, call arbitrary HTTP endpoints or push audiences downstream. Enterprise becomes the appropriate commercial conversation when the deployment needs larger data layers, bulk work, stronger permissions or dedicated implementation support.

Upgrade triggers

Upgrade because a workflow needs a gated capability or durable operating scale, not because one enrichment looked expensive. Launch fits repeatable sourcing and signal-driven prospecting; Growth becomes necessary when source-of-truth sync and broader activation are part of the workflow. A higher Actions tier solves orchestration capacity, while a larger Data Credits tier solves marketplace data or AI consumption, so diagnose which meter is creating pressure before changing the plan.

Workflows can strengthen that operating case, but the graph-based Workflows product is still in open beta. Its runs use the same Actions and Data Credits as tables, with billable nodes charged per record. Treat it as a feature under evaluation and keep mature Functions or table-based logic available for production work that cannot absorb beta change.

API and team boundaries

Clay does not present programmatic access as a separate meter: Public API, CLI and Agent Plugin calls consume the same Actions and Data Credits as equivalent in-product work. The Agent Plugin is open beta, workflow building through the plugin or CLI is Alpha, and capabilities vary by plan. Searches and routines have tiered limits, read-only table access is Enterprise-only, and HTTP API integrations inside Clay begin with Growth.

Workspace access is not priced per seat on the current plan table, and adding collaborators does not create independent usage pools. Actions and Data Credits belong to the workspace. Enterprise adds deeper roles, permissions and budget controls, while connections, CRM licenses, data-provider subscriptions, AI-provider keys, sequencers, ad platforms and other destination tools can still be billed by their owners.

Final pricing check

Before paying, reproduce the intended workflow with representative rows and note each step that uses an Action, Data Credits or an external account. Enrichment cost varies with data type, provider, waterfall order, success conditions and AI model. A universal cost per record or lead would therefore be misleading; use in-product previews and a small run to build an estimate for the actual workflow.

Then verify billing cadence, annual total, included Actions, selected Data Credits, rollover rules, top-up terms, renewal date and permissions. Annual pricing lowers the monthly equivalent but changes commitment and credit delivery. Confirm the Workflows beta boundary, developer availability, CRM sync scope, export behavior and downstream charges immediately before procurement.