How to run Clay & Gmail cold email outreach guide today

1. Manual cold email outreach: the baseline playbook

‍

Before you automate anything, it helps to understand the "analog" version of the workflow. This is what most founders, agency owners, and SDRs slog through in the early days.

‍

Step 1: Define your ICP and offer

• Write down the tightest version of your ideal customer (industry, size, role, tech stack, geography).
• Clarify one core problem you solve and one simple call to action (CTA), e.g. “15‑minute teardown of your outbound” or “3‑month pilot at no risk.”

‍

Step 2: Build a prospect list by hand

• Search LinkedIn, company sites, and industry directories.
• Copy names, roles, company, email (if visible), and notes into a spreadsheet.
• Aim for 50–100 highly relevant contacts, not 1,000 random ones.

‍

Step 3: Research for personalization

• For each prospect, scan their LinkedIn and website.
• Add 1–2 "hooks" in your sheet: recent post, product launch, hiring signal, tech they use.

‍

Step 4: Write cold emails manually in Gmail

• In Gmail, create a simple text‑only template:
  • Line 1: personalized hook from your research.
  • Line 2–3: problem + outcome you help with.
  • Line 4: low‑friction CTA.
• Manually paste in each prospect’s name, company, and hook.

‍

Step 5: Send and log

• Send emails in small batches (15–25 per day) to protect deliverability.
• Log status in your spreadsheet: Sent, Opened, Replied, Positive, Negative.

‍

Step 6: Manual follow‑ups

• After 3–5 days, reply to your own email with a short bump: "Any thoughts, {{first_name}}?" or a new angle.
• Repeat 2–3 times over 2–3 weeks.

‍

Pros (manual)

• Deep learning about your market.
• High quality personalization.

‍

Cons (manual)

• Brutally time‑consuming.
• Easy to drop follow‑ups and lose track of threads.

‍

‍

2. No‑code automation with Clay and Gmail

‍

Once you know what works manually, you can layer in tools.

‍

Clay becomes your data engine and brain for list building and enrichment. Gmail remains your sending channel.

‍

Step 1: Set up Clay for lead generation

• Create a Clay account and review the docs at https://docs.clay.run.
• Build a table with columns for: name, role, company, email, LinkedIn URL, website, personalization fields, status.
• Use Clay’s data sources to pull in prospects that match your ICP (e.g. by technology, headcount, geography).
• Add enrichment steps (firmographic data, social links, hiring signals) so each row becomes a mini one‑page brief on the prospect.

‍

Step 2: Design your personalization logic

• In Clay, add computed columns (formulas) that turn raw data into copy snippets, like:
  • "Saw you’re hiring for {{role}}" when a hiring signal exists.
  • "Congrats on launching {{product}}" when a press mention is scraped.
• Test a few rows to confirm the snippets read like a human.

‍

Step 3: Prepare Gmail for outbound

• Review Gmail’s official help to configure your sending account and basic settings: https://support.google.com/mail.
• Set up a professional signature with your name, role, site, and physical address.
• Create labels like "Outbound – Wave 1" and filters to keep replies organized (see Gmail filters help: https://support.google.com/mail/answer/6579).

‍

Step 4: Export from Clay and import/send via Gmail tools

• Export a CSV from Clay with only the fields you need (email, first name, personalization lines, company, etc.).
• Use a mail‑merge tool that works on top of Gmail (GMass, YAMM, etc.) and follow their guides on uploading a CSV and mapping columns.
• Or, use Clay’s integrations (see docs at https://docs.clay.run) with third‑party senders that plug into Gmail.

‍

Step 5: Automate follow‑ups

• In your Gmail‑based sending tool, define 3–5 follow‑up steps:
  • Day 0: main value email.
  • Day 3: short nudge.
  • Day 7: new angle or case study.
  • Day 14: “Should I close the loop?”
• Make sure sequences automatically stop when a prospect replies.

‍

Pros (no‑code with Clay + Gmail)

• Clay turns messy prospecting into clean, enriched lists.
• Gmail keeps you in a familiar inbox with good deliverability.
• No engineering required; mostly clicks and formulas.

‍

Cons (no‑code)

• You still have to orchestrate multiple tools.
• Edge cases (bounces, odd formatting) require manual cleanup.
• You or your team still spend hours hopping between Clay, CSVs, and Gmail.

‍

‍

3. Scaling with an AI agent as your outreach operator

‍

This is where an AI computer agent like Simular steps in—not as a smarter mail‑merge, but as a digital SDR that can actually use your computer.

‍

Sai agents are designed to operate across your desktop, browser, and cloud tools with production‑grade reliability. That means they can:

• Log into Clay in your browser.
• Run or adjust enrichment flows.
• Export or sync data.
• Open Gmail, create drafts, apply labels, and send.
• Update tracking sheets or CRMs.

‍

Method 1: Agent‑as‑you for daily outbound

1. You record or demonstrate your ideal workflow once: how you filter Clay tables, inspect rows, tweak personalization, and start a Gmail sequence.
2. In Sai, you configure an agent with this goal: "Every weekday, send 30 highly personalized cold emails from my Clay table via Gmail, and label replies for review."
3. The agent executes those steps directly in your desktop/browser environment, action by action, with full transparency (you can read and inspect everything it does).

‍

Pros

• Offloads the repetitive grunt work while preserving your existing tools.
• Transparent: every click and keystroke is visible and editable.
• Easy to pause or override if you see something off.

‍

Cons

• You still own the strategy and copy; the agent is the executor.
• Initial setup takes some thought to demonstrate the right workflow.

‍

Method 2: Agent‑driven experimentation and iteration

1. Define a playbook for testing variations: new subject lines, CTAs, or ICP slices.
2. Use Simular to duplicate a workflow and point each copy at a different Clay view or Gmail template set.
3. The agent runs A/B tests at the workflow level: different segments, different copy, same reliable execution.
4. It then writes results into a sheet or doc you review weekly.

‍

Pros

• Turns tedious experimentation into a background process.
• Helps you treat outbound as a system, not a one‑off blast.

‍

Cons

• You must still interpret the data and decide which variants win.

‍

Method 3: End‑to‑end SDR copilot
For agencies or teams doing outbound as a service, you can:

1. Have Simular agents log into multiple client Clay and Gmail accounts (with appropriate permissions).
2. Run client‑specific workflows—building lists, enriching, sending, triaging replies, even updating a CRM or Google Sheet.
3. Standardize quality via shared prompts and checklists the agent follows every time.

‍

Pros

• Massive leverage for agencies and revenue teams.
• True multi‑tenant operations across many clients.

‍

Cons

• Requires disciplined onboarding and governance so the agent knows which account it’s in and what “good” looks like.

‍

By combining Clay’s data engine, Gmail’s deliverability and familiarity, and Simular’s autonomous execution, you get a cold email machine that behaves like a diligent human operator—just one that never gets bored, forgets a follow‑up, or loses a CSV.