Clay
Each of these is a real decision Clay is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Clay is a subscription-based go-to-market data and workflow automation platform that lets sales, marketing, revenue-operations, and growth teams build prospect lists, enrich records from many data providers, research with AI, and sync results to downstream systems. It focuses on orchestrating multiple external data sources and custom logic rather than relying on a single proprietary database. Clay is a Series D company with $100M+ ARR and a rapidly expanding customer base. Roughly half of its business runs through a sales-led motion serving mid-market, enterprise, and strategic accounts. Its current tech stack includes AWS services: Aurora (Postgres), Elasticache (Redis), Docker + Elastic Container Registry (ECR), ECS (Fargate), Lambda, and OpenSearch.
Your first one is free. No card.
16 live right now.
The rest
Win a second run from new accounts without overpromising CRM results
New enterprise accounts are starting tables but not returning to run a second workflow. You have to weigh a fast activation path against a promise that still feels safe for RevOps.
Decide on a roadshow while pipeline evidence conflicts
The roadshow generated executive meetings, but attended accounts and sourced opportunities do not reconcile before a nonrefundable deposit is due. You have to weigh Strategic-account access against evidence strong enough to defend the remaining budget.
Recover demo leads without flooding the SDR queue
High-intent demo requests are being enriched but bypassing SDR assignment. You must weigh faster coverage against the qualification rule that protects SDR time.
Cut the time to an approved summary while engineers own the fix
Workflow failures take 45 minutes to turn into an engineer-approved investigation summary. You have to weigh faster context assembly against the evidence an engineer needs before acting.
Trace workflow actions so CRM admins can trust agent-driven changes
Administrators can see completed workflow actions but cannot see which data or logic justified them. You must weigh fast workflow execution against enough explanation for CRM governance.
Stop stale data from overwriting the CRM during a 12-day cutover
Verified CRM fields are being replaced during a high-volume Workflows migration. You must weigh refresh coverage against a schema change that is costly to reverse.
Skip excluded records so workflow runs stop retrying
Excluded records are retrying and pushing 100,000-record workflow completion to 31 minutes. You must weigh faster completion against keeping every skipped record explainable in the run trace.
Cut next-step prep to four hours without AI inventing buyer commitments
Strategic follow-up takes up to two business days because account context must be rebuilt after discovery. You must weigh speed against seller control over every buyer-facing commitment.
Win five evaluations through partners without custom pricing
Enterprise prospects want buyer-intent workflows, but partners cannot yet position a repeatable commercial path. You have to weigh fast partner activation against a package RevOps leaders can govern and buy.
Win the contract while CRM controls face procurement
A $250,000 strategic deal could move to an incumbent because the buyer cannot verify enrichment controls before contract review. You have to weigh a closeable commercial commitment against promises that will not hold once data reaches the CRM.
Earn the executive meeting before the partner backs an incumbent
A strategic referral is stalled because RevOps sees stale CRM data while procurement sees unbounded credit spend. You must weigh a narrow proof of value against the partner’s limited executive access.
Prepare renewal conversations before account context goes stale
Strategists currently spend about 90 minutes assembling each strategic-account conversation brief. You must weigh faster preparation against evidence that is strong enough for a human account judgment.
Prove the return on agent enrichment before finance blocks expansion
Pilot customers need a credible explanation for rising credit use before they expand agent-led workflows. You must weigh fast experimentation against an ROI story that finance and RevOps will both accept.
Decide which CRM values to keep before Friday's outreach
Conflicting enrichment may have changed CRM values across a 180,000-record campaign list. You must weigh the board deadline against the risk of committing bad data to outreach.
Fix gaps in records sent to routing while prospecting continues
Routed accounts are missing required firmographic fields despite completed enrichment attempts. You must weigh immediate sales continuity against safe CRM updates and credit use.