1. Offer Shaping
Recommended offer: a focused GTM workflow diagnostic and public-data demonstration around one prospect-selected bottleneck. The prospect gets a concise assessment of the current problem, a sample showing how Clay could address it, and explicit limitations covering missing data, research accuracy, and implementation dependencies. Start with one of four deliverables: an enrichment coverage assessment, a source-linked target-account shortlist, a qualification and routing example, or a map of overlapping enrichment tasks. These are proposed campaign offers, not verified existing Clay service packages; Clay would need to establish its ability to deliver them before making the promise. The first engagement should produce something useful even if the prospect does not proceed to a product evaluation.
Why it’s compelling
A bounded diagnostic gives the buyer a concrete way to judge relevance before evaluating a broad platform. Each version answers a specific question: can we fill important information gaps, identify accounts using our actual qualification criteria, reduce qualification work, or remove redundant enrichment steps? Keep the deliverable tied to the list: a RevOps buyer discussing field conflicts should receive a reconciliation example, while a growth buyer launching a product should receive an explainable account shortlist. Use public company information for the initial demonstration and clearly distinguish observed facts from inferred fit. Do not promise access to the prospect's operational baseline or imply that a public demonstration establishes production performance.
The primary problem
Save Time
Differentiation
Clay publicly describes a marketplace of more than 200 data and AI vendors, custom research, and orchestration in one platform. The supported distinction is the combination of multiple sources and workflow execution, rather than an assertion of universally superior data. Clay website Clay's OpenAI story reports enrichment coverage moving from the low 40% range to the high 80% range, while its Vanta story describes resolving conflicting enrichment sources and simplifying workflows. These provide relevant examples for a diagnostic-led offer, not transferable guarantees. OpenAI customer story Vanta customer story
Evidence and gaps
Public evidence supports product capabilities and named customer use cases, but it is vendor-published and does not independently establish causality or typical results. No campaign evidence establishes that the proposed offers, segments, or messages will generate interested replies. Treat every hypothesis below as an untested 0-to-1 research campaign. Unknowns include Clay's willingness to deliver these diagnostics, delivery capacity, prospect-specific economics, current tool contracts, actual data gaps, and buyer priorities. Public job descriptions and product pages can establish operational context; they cannot establish dissatisfaction, budget, purchase intent, or an individual's awareness stage.
2. Campaign Hypotheses
H1 Find the enrichment gaps that create manual work
If we target RevOps leaders publicly evaluating enrichment and say Clay can demonstrate a focused coverage assessment, they may reply because it gives them a practical way to investigate missing information before committing to a platform evaluation.
- Audience
- Head of Revenue Operations at B2B software companies publicly evaluating enrichment
- Awareness
- Solution Aware
- Problem
- Save Time
- Tone
- Warm
List criteria
- B2B software company with a sales-assisted motion, a named RevOps function, and public evidence of an established CRM workflow.
- A recent company-authored post, public talk, or job description explicitly discusses evaluating enrichment providers or improving enrichment coverage.
- Target the operational owner of enrichment; record the public evidence supporting the angle and exclude generic sales hiring alone.
- Offer a company-data sample with missing fields and uncertainty visible; do not claim to have audited the prospect's CRM.
Why it could work
- The deliverable makes a broad platform proposition assessable through a narrow operational question.
- Explicit evaluation evidence gives the list and message a shared basis without assuming dissatisfaction.
Why it might not
- A public evaluation initiative may already be completed or owned by someone else.
- Public company-data coverage may not represent the contact fields or regions that matter to the buyer.
- The incumbent workflow may already meet requirements, leaving little reason to investigate.
Medium confidenceClay's OpenAI story directly supports the relevance of multi-source enrichment to coverage gaps. Segment demand and offer appeal remain untested, and public evaluation evidence may be scarce. OpenAI customer story
H2 Identify product-fit accounts beyond broad firmographics
If we target growth leaders launching a specialized B2B product and say Clay can provide a source-linked shortlist built around observable product-fit criteria, they may reply because it offers a concrete way to investigate who should enter the new product's target market.
- Audience
- VP of Growth at B2B software companies launching a specialized product
- Awareness
- Unaware
- Problem
- Make Money
- Tone
- Cool
List criteria
- Company has a recent public product launch or expansion into a distinct business use case.
- Its public product documentation identifies qualification characteristics that can plausibly be researched on company websites.
- A growth or GTM owner is publicly identifiable; do not infer poor targeting or pipeline pressure from the launch.
- Exclude products whose qualification depends almost entirely on nonpublic information; frame the shortlist as exploratory research.
Why it could work
- A source-linked sample gives the prospect useful market research before any broader commitment.
- Observable qualification criteria connect the account list directly to the proposed benefit.
Why it might not
- The prospect may already have a strong account universe and qualification model.
- Public signals may be weak proxies for actual product need.
- An unaware audience may not consider targeting research a current priority.
Medium confidenceClay's Intercom story describes using product-specific signals beyond firmographics to identify accounts. A launch establishes context, but neither targeting pain nor awareness is verified. Intercom customer story
H3 Reduce manual inbound qualification
If we target marketing operations leaders who publicly describe manual qualification work and say Clay can demonstrate one qualification-and-routing example, they may reply because it helps them assess whether the bottleneck can be reduced without beginning with a broad workflow redesign.
- Audience
- Director of Marketing Operations at sales-assisted B2B software companies discussing qualification friction
- Awareness
- Problem Aware
- Problem
- Save Time
- Tone
- Warm
List criteria
- Company offers a public demo or enterprise inquiry path and has a marketing operations function.
- A company-authored source explicitly mentions manual lead research, qualification delays, or a routing improvement initiative.
- Identify the owner responsible for qualification rules or routing, rather than targeting demand generation by title alone.
- Use a synthetic inquiry and public company facts for the demonstration; describe routing as illustrative until the prospect validates its rules.
Why it could work
- The offer addresses an explicitly observed operational concern.
- A single example exposes missing fields and rule dependencies before a larger evaluation.
Why it might not
- Routing friction may come from ownership rules or organizational decisions rather than missing data.
- Existing marketing automation may already handle the relevant work adequately.
- A public inquiry path does not establish meaningful inbound volume.
Medium confidenceClay publicly supports inbound enrichment, qualification, scoring, and routing. Whether manual work is material at a particular prospect requires direct confirmation. Inbound enrichment
H4 Assess redundant enrichment work
If we target RevOps leaders with publicly documented multi-tool enrichment workflows and say Clay can map overlapping tasks and identify consolidation questions, they may reply because it gives them a structured way to assess avoidable duplication.
- Audience
- Director of Revenue Operations at B2B software companies publicly using multiple enrichment tools
- Awareness
- Solution In Use
- Problem
- Save Money
- Tone
- Direct
List criteria
- Company-authored technical content, public talks, or current job descriptions document multiple enrichment tools in the same workflow.
- Evidence concerns active operational use; exclude vendor logos or technology mentions without workflow context.
- Target the RevOps or GTM systems owner and connect the offer to the specifically documented overlap.
- Offer a task-overlap assessment, with cost savings left unquantified unless the prospect later establishes the relevant economics.
Why it could work
- Documented tool usage supports a direct discussion of workflow trade-offs.
- The assessment can reveal duplicated tasks without promising that every tool should be replaced.
Why it might not
- Different tools may serve necessary, nonoverlapping purposes.
- Migration effort and Clay's total costs could outweigh any savings.
- Public descriptions may reflect an outdated stack or omit important dependencies.
Low confidenceClay's Vanta story supports the relevance of conflicting sources and redundant tools. Public evidence rarely establishes contractual overlap, total costs, or whether consolidation is economical. Vanta customer story
3. Priority Order
- H1 Closest connection between a bounded diagnostic, explicit evaluation context, and published customer evidence. Prioritize only accounts with credible enrichment-related evidence.
- H3 A specific operational pain and a small demonstration create a clear learning opportunity; qualification rules remain a material dependency.
- H2 Public launches make the segment identifiable and the research deliverable tangible, but the underlying pain is inferred and requires discovery.
- H4 Potentially relevant to established users of enrichment tools, but actual duplication and savings are hardest to establish publicly.
4. Testing Plan
Test angles first
First compare the four pain-and-list combinations: missing enrichment coverage, manual inbound qualification, specialized account discovery, and duplicated enrichment work. Treat each as a separate research hypothesis, preserving its evidence requirements and matching deliverable. Keep the initial engagement structure comparable: one bounded diagnostic with a concrete output. This tests the relevance of each segment-angle combination; it does not isolate wording effects across different audiences.
Within a winning angle
After an angle produces repeated, substantive interest from suitable prospects, refine one variable at a time: hook, length, deliverable scope, then temperature where the awareness evidence supports it. Retain the winning pain and list definition while making those comparisons. Do not reclassify an unaware prospect as Direct merely because stronger wording appears attractive. A winning angle is provisional evidence of relevance, not proof of repeatable commercial performance.
When to iterate
Iterate when replies reveal a specific mismatch: the wrong owner, an adjacent problem, unclear deliverable value, doubts about public-data quality, or excessive effort required to engage. Change the variable implicated by the feedback. Questions about scope indicate curiosity but count as interest only when they concern applying the offer to the prospect's situation. Silence warrants checking the list evidence and clarity of the proposition; it does not identify the cause by itself.
When to stop
Stop a hypothesis when repeated substantive feedback rejects the underlying problem, required list evidence cannot be established, or the proposed deliverable cannot be credibly fulfilled. Pause after a completed review shows silence without substantive interest; do not preserve the angle indefinitely through cosmetic copy changes. Define the review boundary before any separately authorized test, without assuming that this report authorizes launch.
When to continue
Continue when multiple suitable prospects independently acknowledge the same problem and ask to examine the proposed diagnostic or sample. Preserve the list criteria and offer long enough to determine whether that interest recurs. Customer-story relevance alone is insufficient; continuation should depend on observed responses to the actual hypothesis.
What to measure
Record interested replies, objections, negative replies, substantive questions, and silence by hypothesis and evidence quality. Separate requests for the deliverable from polite acknowledgments, referrals, and general curiosity. Use interested replies relative to delivered messages as a descriptive comparison, alongside qualitative reasons; never use open rates. Record missing evidence and avoid declaring differences meaningful when observations are sparse. These are evaluation rules, not outcome forecasts.