Book a call
Menu

Interactive Clay lead generation planner

Model a lead stream before you build it

Set one month of account research, the buyer roles you need and the signals worth checking. See the records your team might review before anything enters HubSpot.

The planner models your own assumptions.

01 / Explore the flow

What could one monthly sourcing cohort produce?

Change the inputs to match your market and operating capacity. Each stage stays visible, including the data that would need review.

These are targeting assumptions for the brief. They do not query Clay or independently change estimated volume.

The number of companies you plan to research each month.

The share expected to pass your company fit and exclusion rules.

Buyer roles to look for

Each checked role creates one target role slot per fit account. A slot is not a found person.

Signals to inspect

Signals can overlap. The estimate counts an account once if it shows at least one selected signal. Website visits require tracking on your own site.

Adjust data quality and overlap assumptions

Share of target role slots where a relevant person is found.

Share of discovered records that pass your data checks.

Share of accepted records matched to existing CRM records.

Share of fit accounts expected to show one or more selected signals.

Illustrative defaults / monthly scenario

No live Clay data

Target profile: B2B SaaS, 51-200 employees, North America. Buyer roles: Revenue leaders and Marketing leaders.

Preset rates are examples; replace them with your own. Check your own source coverage and CRM overlap before planning capacity.

175Fit accountsCompany records to examine
156Net-new contacts for reviewAfter assumed data checks and CRM overlap
26Signal-priority accountsAccounts showing one or more selected signals
01 / Scan500companies
02 / Fit175accounts
03 / People245found records
04 / Check196accepted records
05 / Review156net-new records

With 500 companies researched, 175 might fit the ICP. After people discovery, data checks and CRM overlap, 156 net-new contact records could enter a human review queue. 26 accounts might merit a signal check.

These are model outputs from your assumptions. They are not verified leads, valid email addresses, outreach permission, or expected sales results.

Selected signal types: New hires, Job changes.

Of the net-new records, approximately 22 could belong to signal-priority accounts. These records are already included in the net-new total.

Discuss this build ↗

How the estimate is calculated

Fit accounts = companies researched × assumed ICP-fit share.

Net-new contacts for review = fit accounts × selected role slots × role discovery rate × data acceptance rate, then reduced by estimated CRM overlap. Each stage is rounded down.

Signal-priority accounts = fit accounts × assumed selected-signal incidence. Signals are not added together, because the same account may show several. A signal is a reason to review the account.

Open downloads

Keep your sourcing scenario.

Use Download brief in the planner to save your current assumptions and modeled results. No email address is needed.

02 / How it becomes operational

From target market to a reviewable HubSpot record

Built by AGI Technologies as an independent scenario planner for Clay workflows. It models your assumptions.

The model is the starting point. The live workflow needs account rules, source checks, matching, ownership and a clear exception path.

01

Define the market

Choose firmographic filters, exclusions and target buyer roles. Clay can source companies and then search for people at accepted accounts.

02

Add evidence

Check company news, hiring, job changes or tracked company visits where those sources are available. Keep the signal and its date with the record.

03

Verify and match

Use enrichment providers selectively, inspect coverage and match against existing HubSpot companies and contacts before creating records.

04

Route the next step

Send accepted records to a named owner or review queue in HubSpot. Hold incomplete, duplicated or ambiguous records for a person to decide.

03 / What the signals mean

Prioritize accounts with a reason to look

A new hire, job change or relevant company announcement can justify fresh research. Website company visits can add first-party context when tracking is installed. None proves purchase intent, identifies an individual visitor or grants permission to contact them.

Clay’s people-search data can lag job changes. A working process checks source dates, record matches and data quality before assigning action.

04 / Build the first cohort

Turn the scenario into a working system

Share your target segment and the part of sourcing that needs work. We can review one real cohort, test the data checks and define what should enter HubSpot.

Take the scenario with you

Copy the scenario above, or download the brief for your notes. Book a scoping call to discuss the assumptions you want to test and the part of the workflow you need help building.

  1. 01Copy your scenario from the planner
  2. 02Open the contact form
  3. 03Paste the scenario and add your question
Book a 30-minute call Open the contact form ↗

Calculating, copying or downloading a scenario stays in your browser. A contact submission sends the information you include and does not subscribe you to a newsletter.

Before you use the numbers

Planner questions

Does this tool search Clay or count live leads?

No. It models one monthly cohort from the assumptions you enter. A real Clay search, data-provider coverage and CRM audit are needed to size your actual market.

Are signal-priority accounts ready for outreach?

No. Signals can overlap or be stale. Review fit, source dates, existing relationships, contact data and applicable outreach rules before taking action.

What does a net-new contact record mean?

It is an estimated person record that passed the model’s discovery and data-acceptance assumptions and did not match the assumed CRM-overlap share. It is not a validated email or sales-qualified lead.

What happens to the values I enter?

The calculator runs in your browser. Copying or downloading does not submit the scenario. If you use the contact form, we receive the information you include, and it does not subscribe you to a newsletter.