What Do I Ask Before Quoting a Clay Enrichment Build?

What do I ask before quoting a Clay enrichment build?

I ask what decision the data will drive, where the records start and end, how many records move each month, who owns the Clay credits, and what happens when enrichment fails. Those answers decide the scope, the risk, and the price. Without them, any fixed quote is a guess dressed up as a number.

I price my work on a fixed fee, and most of my projects land between $1,000 and $10,000. Fixed pricing only works if the scope is clear before I start. Clay builds are where scope gets fuzzy fastest, because enrichment sounds simple and rarely is.

A founder will tell me they just need Clay to enrich their leads. That sentence can mean a two-day build or a two-month system. The questions below are how I find out which one I am looking at.

What decision will this data drive?

This is the first and most important question. Enrichment is not a goal. It feeds a decision, such as which leads get routed to sales, which accounts enter an outbound campaign, or which records get a higher score. If nobody can name the decision, the build will collect data that nobody uses.

I ask it plainly: when this table is finished, what will someone do differently because of it? Good answers sound like "route companies over fifty employees to the AE" or "skip anyone already in a customer account." Vague answers sound like "have better data." Vague answers mean I need a discovery session before I can quote.

This question also tells me which fields actually matter. If the decision is routing by company size and industry, I do not need ten enrichment providers chasing personal emails. Fewer fields mean lower cost, less maintenance, and a cleaner build.

Where do the records come from and where do they go?

Every enrichment build has an entry point and a destination. Records might come from a Webflow form, a HubSpot list, a CSV, or a signal source. They might end up in HubSpot, Salesforce, a sequencer, or a Slack alert. Each connection adds work and each one can break.

I map the path in a single sentence before I quote. Something like: form submission arrives, Clay enriches the company, a score is calculated, and the record updates in HubSpot with an owner assigned. If that sentence has more than five steps, the project is bigger than the client thinks.

The destination often hides the real complexity. Writing back to a CRM means deciding which fields Clay can overwrite, how duplicates are handled, and who wins when Clay and a rep disagree. I covered one piece of that in how to dedupe companies across Clay, Apollo, and HubSpot.

How many records move each month?

Volume decides cost, design, and risk. Enriching a few hundred inbound leads a month is a very different build from enriching tens of thousands of outbound prospects. Volume affects Clay credit spend, which providers are worth calling, and whether the build needs throttling and error handling from day one.

I ask for the current monthly volume and the expected volume in six months. If the second number is much larger, I design for it now, because rebuilding later costs more than building it right once.

Volume also shapes the enrichment order. At high volume, I want cheap checks first and expensive providers only for records that pass. My notes on how to decide which accounts get enriched first go deeper into that ordering.

Who owns the Clay account and the credits?

The client should own the workspace and pay for the credits directly. I ask this early because it affects access, billing surprises, and what happens after handover. If credits run out mid-month, the build stops, and the client needs to know that the spend is theirs to manage.

This question protects both sides. When the client owns the account, there is no awkward moment where I am paying for their data or holding access they need. It also makes cost visible. A client who sees credit usage every month makes better decisions about which fields are worth enriching.

I also ask whether they want spending guardrails. A simple cap per lead or per run prevents one bad import from draining a month of credits. I wrote about how to cap Clay credit spend per lead because it is one of the most useful safety rails in any Clay build.

What should happen when enrichment fails?

Some records will not enrich. A provider will return nothing, an email will bounce, or a company will be too small to show up anywhere. I ask what the client wants in that case: send the record through with blanks, hold it for review, or drop it. The answer changes the build.

Most clients have never thought about this, and that is fine. It is my job to raise it. But the answer has to come from them, because it is a business decision. A sales team that hates empty fields might prefer a review queue. A team that values speed might prefer to send everything and enrich later.

There is a second kind of failure worth asking about: a provider changing its output or going down for a day. I ask who should hear about it and how fast. Usually the answer is one named person on the client's team, alerted in Slack or email, with a short note on what to check first. That alert costs little to build and saves a lot of confusion when a field quietly stops filling in.

Failure handling is also where I estimate maintenance. A build with clear rules for missing data is easy to support. A build that silently passes blanks to the CRM creates support requests every week.

Why do these questions change the price?

Because each answer moves the scope. A clear decision, a short path, modest volume, client-owned credits, and simple failure rules make a small, cheap build. Unclear answers on any of those add discovery, extra steps, or ongoing risk. Pricing honestly means reflecting that before work starts, not after.

Over 6+ years and 100+ projects for 25+ clients, the pattern I trust is simple. The projects that go well are the ones where scope questions were answered on paper first. The ones that drift tend to be the ones where a question got skipped because the client seemed sure.

So I would rather spend thirty minutes asking than three weeks renegotiating. Clients usually appreciate it, because the questions show them parts of their own process they had not looked at closely.

What should you do next?

If you are planning a Clay enrichment build, write down your answers to these five questions before you talk to anyone. Name the decision, map the path, estimate monthly volume, confirm who owns the credits, and decide what happens on failure. That one page will make any quote you receive more accurate.

If you cannot answer one of them, that is useful too. It tells you where the real work is.

I build enrichment, scoring, and routing systems for B2B SaaS teams on fixed-fee pricing. If you want help scoping a Clay build before you commit to one, reach out at pravinkumar.co. Let's chat.