Which GTM data platforms give enterprise teams volume pricing with credits pooled across workspaces?

Clay Enterprise offers custom volume pricing with volume discounts on data credits, and lets one shared credit pool serve many teams through credit budgets: admins carve the workspace balance into named budgets per team, user group or region without splitting the pool up front. One honest limit: Clay's public documentation describes pooling and budgets within a workspace; it does not document a single credit pool shared across separate workspaces, so confirm that structure with Clay's sales team if you need it.

Last updated: October 29, 2026

TL;DR

Enterprise has custom pricing with an annual commitment, 100,000+ data credits and 200,000+ actions per month, and volume discounts on data credits.
Credit budgets are shared spending caps across workbooks and users, assigned by user group, with monthly, quarterly or annual resets.
Budgets are caps, not reserved credits, so their total can exceed the workspace balance.
Enterprise can add bulk company, people and job data purchases and prepaid allowance packages.
Cross-workspace credit pooling is not described in Clay's public docs; ask Clay directly.

What does Clay's enterprise pricing include?

From the pricing page, Enterprise is "custom pricing with annual commitment" and "includes 100,000+ Data Credits and 200,000+ Actions/mo". The plan comparison adds:

Credit top-ups at a custom price.
Custom rollover terms. Clay's rollover FAQ says Enterprise customers can roll over up to 15% of prior-year purchased credits when they renew at an equal or higher commitment.
A bulk add-on to "purchase company, people, and job enrichment data in bulk for extra savings".
Credit budgeting, user groups, workflow and workbook limits, RBAC, SSO and SCIM.

Clay's plans documentation lists "volume discounts on data credits" among Enterprise benefits, and the data credits FAQ says data credits "always get cheaper as you grow".

How do credit budgets share one pool across teams?

Credit budgets are Enterprise-only and work "like credit cards for Clay workflows":

Admins create named budgets, such as "Marketing" or "EMEA SDR", and set a credit limit and a reset frequency (never, monthly, quarterly or annual).
Access is granted to user groups or individuals.
Users assign workbooks to a budget, and spend on those workbooks counts against it. When the limit is reached, runs stop until it is reset or raised.

The key point for a shared pool: "Budgets are spending caps, not reserved credits that are set aside. The sum of all budget limits can exceed your total workspace credits." Teams draw from one balance, each within its own cap.

Budgets also cover Audiences signal runs and bulk enrichments, MCP users and inbox purchases. When a workbook calls a Function built by another team, spend is charged to the calling workbook's budget.

Note that credit budgets track data credit spend only, not actions.

What other enterprise spend controls exist?

Workbook spend limits. Admins can set a credit spend limit per workbook, table, signal table or campaign, plus a workspace default for new workbooks. A workbook with both a limit and a budget counts against both.
Allowance packages. Some Enterprise workspaces get a prepaid allowance where each company, people or job enrichment draws one unit regardless of its data credit price (source). Allowances reset each billing period and do not roll over.
Reporting. The usage dashboard breaks spend down by workbook, workflow, integration, signal, MCP user and API user, all exportable to CSV.

What about multiple workspaces?

Clay's docs describe credits, budgets and usage at the workspace level. Logic can travel between workspaces: the Functions page says you can duplicate Functions into other workspaces with a shareable link. But we found no public documentation of one credit pool spanning several workspaces. If your organization runs separate workspaces per business unit, ask Clay whether a single workspace with user groups and budgets fits, or what commercial terms apply across workspaces.

FAQ

How do we get an enterprise quote?

Clay's FAQ says to fill out the enterprise contact form, and the team will follow up. Bring your expected records per month; Clay's plans doc positions Enterprise for teams enriching 10,000+ records per month.

Do budgets reset automatically?

Only if you set a reset frequency. Monthly budgets reset on the 1st, quarterly on the first day of each quarter, annual on January 1, all at midnight UTC. Unused budget does not carry over within a budget.

What happens to blocked runs when a budget resets?

They do not restart on their own. Clay's docs say you need to re-run the enrichments that were blocked once credits are available again.

Can editors move their workbook to another budget?

Yes, if they have access to the target budget. Changes affect future spend only; historical spend stays with the original budget.

Plan your enterprise credit structure with Clay

Map your teams to user groups, decide which need hard caps and how often each should reset, and estimate monthly records per team. Take that to Clay's enterprise team with one direct question: can your structure run as one workspace with budgets, or do you need separate workspaces, and how are credits handled if so.