Cancellation runbook · 2026
How to Cancel Clay (Self-Serve + Workflow Migration Reality)
Clay is self-serve to cancel for non-Enterprise plans — settings → Billing → Cancel subscription. The cancellation itself is easy. The hard part is what most teams skip: documenting the accumulated workflow library (table configurations, enrichment waterfalls, AI prompts) before access ends. Clay's value is the workflow logic, not the data — and the logic doesn't migrate. This is the operator runbook: cancellation steps, credit refund handling, replacement options, and the migration overhead nobody warns you about.
The 60-second summary
- Standard plans — settings → Billing → Cancel subscription. Effective at end of current billing cycle.
- Custom Enterprise contracts — email billing@clay.com with non-renewal notice. Same template as enterprise cancel runbooks.
- Document workflows BEFORE cancellation — 4-12 hours of GTM-engineer time to capture table configurations and enrichment logic.
- Consider downgrade first — cutting Pro → Starter saves $2.4K/yr while preserving the workflow library.
Step 1 — Determine your billing cadence + plan
Clay offers Free, Starter ($149/mo), Pro ($349/mo), Business ($800/mo+), and Enterprise (custom) tiers. All plans are credit-based — your monthly fee includes a credit allotment, with overage purchases at usage-based pricing. Most plans are monthly with optional annual (15-20% discount). Find your billing cadence in account settings → Billing → Subscription. The Enterprise tier requires custom contract negotiation; lower tiers are self-serve.
Operator tip: Clay's effective cost is often 2-3x the sticker price for active users due to credit overages. Audit your actual credit usage from the Usage tab — if you're consistently buying overage credits, the real spend is the number that matters for cancellation math, not the plan tier.
Step 2 — Document your tables + workflows BEFORE canceling
This is the step most teams skip and regret. Clay's value is the accumulated workflow library — table configurations, enrichment waterfalls, AI prompts, integrations. None of this migrates to other tools. Before cancellation: (a) export each active table to CSV (Tables → ⋯ → Export), (b) screenshot or document each table's enrichment configuration (which sources in which order, which AI prompts), (c) document any cross-table workflows or webhook integrations. This is 4-12 hours of work and skipping it means losing months of GTM-engineering work.
Operator tip: If your team has a GTM engineer, schedule a 'workflow extraction' day before cancellation. The GTM engineer documents the logic flow, not just the data. Without that, the replacement tool (Apollo, custom-built) starts from zero.
Step 3 — Cancel via account settings (self-serve for non-Enterprise)
For Free, Starter, Pro, and Business plans, Clay cancellation is self-serve: account settings → Billing → Subscription → Cancel subscription. Confirm cancellation. The account stays active through your current billing period. For Enterprise tier, written notice via email per the MSA — same template as enterprise SaaS cancel runbooks, sent to billing@clay.com.
Operator tip: If you're on Enterprise and don't see a self-serve cancel option, email billing@clay.com with non-renewal notice. Use the standard enterprise template. Clay's Enterprise team is generally cooperative on cancellation — the company's pricing model relies on usage growth, so they don't make exits painful for teams that aren't growing usage.
Step 4 — Address credit refund + integration cleanup
Clay charges credit overages above your plan allotment. If you have unused credits or recently purchased overage credits, contact billing@clay.com within 30 days of purchase to request a refund. Annual plan cancellations are typically NOT refunded for the remaining term — you keep access until your annual cycle ends. Integration cleanup: Clay connects to many sources (Apollo, ZoomInfo, Salesforce, HubSpot). Disconnect each integration in account settings → Integrations before cancellation to prevent stale connections.
Operator tip: If you have webhook-based workflows (Clay → Slack, Clay → Zapier), document the webhook URLs and trigger logic before access ends. Webhook configurations don't export cleanly — they need to be rebuilt in the replacement system.
Refund eligibility by plan type
- Free plan: Nothing to refund. Cancel anytime; data export advised before plan downgrades to read-only.
- Monthly Starter/Pro/Business plans: No refund needed. Cancel anytime, pay through end of current month, access ends on next billing date.
- Annual plans paid upfront: Generally NOT refunded. You keep access through end of contract year.
- Recently purchased overage credits: Refundable within 30 days of purchase if unused. Email billing@clay.com with purchase date and request explicit refund.
- Custom Enterprise contracts: Treated like enterprise SaaS — written notice required, refund terms per contract.
Where most teams go after Clay
The replacement decision depends on whether you actually used Clay's advanced workflow capability. Most teams that cancel Clay didn't — they bought it aspirationally. Be honest about your usage before picking a replacement:
- Apollo (turnkey): Covers basic enrichment + sequencing at $49-$119/seat/mo. Loses Clay's waterfall logic but most teams don't have the GTM engineer to maintain it anyway. Saves $1.5K-$5K/mo in effective Clay cost.
- Custom-built (data pipeline): For teams with engineering capacity, replicating Clay's waterfall in a custom data pipeline (Apollo + ZoomInfo + custom AI calls) typically costs $150-300/mo in API fees vs $349-$800/mo for Clay. Tradeoff: ongoing engineering maintenance.
- Persana / Omnimind / Gumloop (cheaper alternatives): Similar enrichment + AI orchestration at $37-$199/mo. Less mature than Clay but adequate for most under-50-rep teams. Saves $200-$600/mo.
- Skip the orchestration layer entirely: For teams that bought Clay aspirationally and never built workflows, the replacement is Apollo only — the orchestration layer was unused capacity. Saves the full Clay spend.
After cancellation — the runway
- Export tables to CSV. Each table individually via Tables → ⋯ → Export. Plan during your active subscription period.
- Document workflow logic externally. Screenshots or written documentation of enrichment waterfalls, AI prompts, cross-table dependencies. The most-skipped step.
- Disconnect integrations before cutoff. Salesforce, HubSpot, Apollo, ZoomInfo connections. Prevents stale auth tokens and partial syncs after cancellation.
- Document webhook configurations. If you built Clay → Slack, Clay → Zapier, or Clay → custom webhook flows, capture the URLs and trigger logic. These don't export.
- Calendar your replacement's renewal. When you sign your next data tool, calendar 60-90 days before its renewal as your non-renewal notice deadline.
Related reading
- Do I need Clay if I have Apollo? — overlap audit
- Are you wasting money on Clay? 7 diagnostic signs
- Clay vs Apollo — flexibility vs turnkey
- Clay vs ZoomInfo — orchestration or enterprise incumbent?
- Full Clay alternatives breakdown — pricing, fit, AI maturity
Want to try Apollo?
Apollo — 275M+ contacts, sequencing, and enrichment in one tool
Free plan is real (not a 14-day trial). Includes verified emails, mobile numbers, and basic sequencing. Most teams under 25 reps can run their entire outbound motion on the bundled tier.
Start free →Affiliate link — StackSwap earns a commission if you sign up for Apollo. We only partner with tools we'd recommend anyway.Seamless.AI — real-time B2B contact discovery with Chrome-extension-first UX
Affiliate link — StackSwap earns a commission if you sign up for Seamless.AI. We only partner with tools we'd recommend anyway.n8n — workflow automation without the per-task pricing wall
Affiliate link — StackSwap earns a commission if you sign up for n8n. We only partner with tools we'd recommend anyway.FAQ
Canonical URL: https://stackswap.ai/cancel-clay