Your clone works the cold sequence. You take the warm replies.
Four personalized touches for every new lead, stopped the moment someone replies, with a daily list of people ready to talk.
Twice a day your clone picks up new leads from your CRM, writes personal emails from your value proposition and quick research, and sends a four-step sequence from your inbox within a safe daily limit. It sorts every reply, keeps the CRM current and hands you a hot list each day.
What your clone does
Touches two through four never happen, replies get missed, and people who said no keep getting emails. Your clone runs the whole sequence the same careful way every time.
Most outbound programs die after the first email. Touches 2, 3 and 4 get forgotten, replies get buried, and someone who said "not now" gets the same email again a week later. The leads were paid for (in money or effort) and most of them never get a real sequence.
The Cold Email Sequence use case fixes that. Twice every weekday your clone:
- picks up new eligible leads from your CRM (from Clone Lead Generation Skill, a sheet import or leads already in the CRM),
- checks each one against your safety filters (no customers, no open deals, no other reps' contacts, no opted-out people),
- writes and sends personalized emails from your inbox, following a 4-touch schedule,
- reads every reply, classifies it and takes the right action (stop, pause, unsubscribe, follow up later),
- updates the CRM with the sequence step, status and last-touch date,
- sends you a daily hot list of interested replies so you can respond personally.
What you get:
| Benefit | What it looks like |
|---|---|
| Every lead gets the full sequence | 4 well-timed touches, not 1 forgotten email |
| No embarrassing mistakes | Stops instantly on reply, bounce or opt-out; never emails customers or open deals |
| Warm replies don't get lost | One daily email listing everyone who said yes, with context and a suggested next step |
| A clean CRM | Step, status and last-touch date on every lead, opt-outs flagged |
| Safe sending | Daily cap, warm-up ramp, opt-out line and business-hours sending built in |
Area What works CRM Salesforce (Salesforce Lead Operator, Salesforce Contact Operator, Salesforce Account Operator, Salesforce Opportunity Operator, Salesforce Activity Operator) or HubSpot (HubSpot Contact Operator, HubSpot Company Operator, HubSpot Deal Operator, HubSpot Engagement Operator). HubSpot has no separate Lead object in this stack: leads are contacts with lifecycle stage "Lead" and a lead source property Email (sending inbox) Gmail (Google Gmail Operator) or Outlook (Outlook email operator) Lead supply Clone Lead Generation Skill (finds NEW leads), a list import via Google Sheets Operator or Microsoft Excel, or leads already in your CRM Suppression list A sheet (Google Sheets Operator or Microsoft Excel) or the CRM do-not-email flag Hot reply alerts (optional) Slack or Microsoft Teams (delivery only) Personalization Light web research by the clone
Who it helps
- SDRs / BDRs and account executives who own outbound and want consistent follow-up without manual chasing.
- Founders and small sales teams with more leads than time.
- Marketing teams running outbound to lead lists or event attendees.
- Rev Ops teams who want one documented, compliant outbound process with clean CRM data.
It is built for new prospects only. Existing customers, open opportunities and contacts owned by another rep are excluded on purpose.
How it runs
┌───────────────────────────────────────────────────────────────────┐
│ New leads land in your CRM (Clone-Lead-Generation-Skill, sheet │
│ import or existing records), about {DAILY_LEAD_VOLUME} per day │
└───────────────────────────────┬───────────────────────────────────┘
│
Every weekday at {RUN_TIMES} (scheduled task)
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ "Cold Email Sequence" skill │
│ │
│ 1. Check the inbox first ──► replies, bounces, opt-outs, OOO │
│ 2. Classify each reply ──► stop / pause / suppress / hot │
│ 3. Update the CRM ──► step · status · last touch │
│ 4. Find due follow-ups ──► touches 2, 3, 4 that are due │
│ 5. Find new leads ──► {LEAD_CRITERIA}, then filter: │
│ (no customers, open deals, other reps' leads, │
│ suppressed or do-not-email contacts) │
│ 6. Write personalized emails (value prop + light research) │
│ 7. Send within today's cap and the lead's business hours │
│ ({DAILY_CAP}, warm-up ramp, follow-ups first) │
│ 8. Morning run: send the HOT LIST ──► {HOT_LIST_RECIPIENTS} │
└───────────────────────────────┬───────────────────────────────────┘
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ You: read the hot list → reply personally to interested leads → │
│ book the meeting. The clone never auto-replies to a hot lead. │
└───────────────────────────────────────────────────────────────────┘The 4 touches
Timing is set by {SEQUENCE_TIMING} (default: day 0, day 3, day 7, day 14, counted in business days or calendar days, your choice). Touches 2 to 4 are sent as replies in the same email thread.
| Touch | Default day | Purpose |
|---|---|---|
| 1. Intro + relevance | Day 0 | Who you are, why them, one clear reason it matters to their role or company, a light ask |
| 2. Value / proof | Day 3 | A concrete result or example (from {PROOF_POINTS}), restate the {CTA} |
| 3. Different angle / resource | Day 7 | A new angle (a different pain point or use case) or a useful resource, no pressure |
| 4. Polite breakup | Day 14 | "I'll stop here", leave the door open, make it easy to say "not now" or "wrong person" |
Example templates (the clone personalizes each one; {{double braces}} are filled per lead):
Touch 1 Subject: {{company}} and {PRODUCT_NAME}
Hi {{first_name}},
{{personal_line}} (one true, specific line about their company or role)
We help {{role}}s like you {VALUE_PROP}.
Worth a 20-minute call to see if it fits? You can pick a time here: {BOOKING_URL}
{SENDER_NAME}
Touch 2 (reply in same thread)
Hi {{first_name}}, a quick example: {PROOF_POINTS}.
If that's relevant for {{company}}, {CTA}.
Touch 3 (reply in same thread)
Hi {{first_name}}, a different angle: many {{role}}s tell us {{second_pain_point}}.
This short {{resource_name}} explains how others handle it: {{resource_link}}
Touch 4 (reply in same thread)
Hi {{first_name}}, I don't want to clutter your inbox, so this is my last note.
If the timing is wrong, or someone else owns this, just let me know and I'll
follow up accordingly. Either way, all the best.
Every email footer: {SENDER_NAME}, {COMPANY_NAME}, {COMPANY_ADDRESS}, and {OPT_OUT_LINE}Set it up, step by step
- Check requirements (10 min)Open REQUIREMENTS.md and run through the pre-flight checklist. You need Gmail or Outlook for the sending inbox, Salesforce or HubSpot operators with limited write access, and the ability to create scheduled tasks. Ask IT to confirm SPF, DKIM and DMARC are set up for the sending domain.
- Hand the instructions to your clone (2 min)Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: "Please set up this use case for me. Show me a plan before changing anything."
- Review the discovery table (5 min)The clone reports which skills/operators and connections it already has and which are missing.
- Answer the setup questions (15–20 min)See the table in section 6. The value proposition, proof points and lead criteria take the most thought, so prepare them first.
- Approve the templates (10 min)The clone drafts the 4 templates from your answers. Edit until you'd be happy to send them yourself.
- Approve the plan (2 min)The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right.
- Do your part (15–30 min)Things only you (or your admins) can do: - Sign in (OAuth) to the sending inbox and the CRM. - Create the three CRM custom fields (or agree to use activities/tasks instead). - Set up the suppression list and share it with the clone. - Confirm sending-domain authentication with IT.
- Save the skill (5–10 min)If the clone can't create custom skills directly, it gives you the full skill text in a copy-paste block with exact steps. Read it before you save it.
- Run the test plan (20 min)Run the whole sequence against test leads that are your own addresses (never real prospects), then reply, unsubscribe and send an out-of-office to check every branch.
- Approve the first real batch, then go liveThe first real run is in review mode: the clone prepares the emails and shows them to you without sending. Once you say "approved", it switches to live sending on the warm-up ramp.
The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.
Before you start
Your clone matches these to the exact skill names in your workspace. Names can differ slightly by workspace, and your clone will report what it finds.
| # | Skill / operator | What it's used for | Notes |
|---|---|---|---|
| 1 | Google Gmail Operator or Outlook email operator | Send the sequence from {SENDER_INBOX}; read replies, bounces and auto-replies; send the hot list | Must be the sending inbox, with read + send |
| 2 | Salesforce: Salesforce Lead Operator, Salesforce Contact Operator, Salesforce Account Operator, Salesforce Opportunity Operator, Salesforce Activity Operator. HubSpot: HubSpot Contact Operator, HubSpot Company Operator, HubSpot Deal Operator, HubSpot Engagement Operator | Find eligible leads; check customers, open deals and owners; update step, status, last touch; set do-not-email; log activities | Pick the one CRM you use. HubSpot has no separate Lead object: leads are contacts with lifecycle stage "Lead" |
| 3 | Scheduled task (platform) | Run the skill at {RUN_TIMES}, Monday-Friday | Platform feature; the clone may be able to create it |
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
Good to know
- Test the full sequence on yourself first. Use your own addresses (a work and a personal one) as test leads and go through all 4 touches with a shortened timing. You'll catch broken merge fields, threading problems and awkward wording before a prospect does.
- Check formatting in real inboxes. Look at the test emails in Gmail and Outlook, on desktop and phone. Plain text, short paragraphs and no images or heavy HTML look more personal and land in the inbox more often.
- Don't re-sequence existing customers. Imported lists often contain current customers or people already in a deal. The skill checks for customer accounts, open opportunities and other owners, but only if your CRM data is accurate. Fix duplicates and missing company domains first.
- Lead source quality varies. Imported or scraped data can be stale or wrong. Watch bounce and reply rates per lead source and drop sources that perform badly.
- Respect sending limits. Your email provider has daily limits, and cold outreach should stay far below them. Keep the warm-up ramp and the daily cap. Sudden volume spikes get mailboxes flagged.
- Bounces hurt your sender reputation. More than about 2–3% bounces is a warning sign. Use clean, recent lists, and let the clone skip obviously invalid or role addresses (info@, sales@) before they enter the sequence.
- Authenticate your domain. SPF, DKIM and DMARC must be set up for the sending domain. Many teams use a secondary sending domain (e.g. go.yourcompany.com) to protect the main domain. The clone can't change DNS; IT has to do this.
- Replies can arrive in other places. People reply from a different address, forward the email to a colleague who replies, or start a new thread. The skill checks the sender's domain and the subject, but some replies will land in "Needs review". Skim your inbox too.
- Out-of-office replies are not real replies. The skill pauses on OOO instead of stopping, but unusual auto-replies (ticket systems, "this mailbox is not monitored") can be misread. Check the run report's "auto-reply" section in the first weeks.
- Use exact skill/operator names as they appear in your skill catalog. Names can differ between workspaces; the clone checks them during discovery.
- Read every instruction before saving it into a skill. You're responsible for what your clone sends. Have someone check the compliance rules (opt-out, address, EU leads) against your company's policies.
Questions, answered
Does this work with my CRM?
It works with Salesforce and HubSpot, the CRMs with operators on the platform today. The clone needs read access and permission to update a few lead or contact fields. See the mapping in REQUIREMENTS.md.
Whose inbox do the emails come from?
From {SENDERINBOX}: usually your own mailbox or a dedicated sales mailbox on a secondary domain, connected to the clone through sign-in. Replies go back to that inbox, which the clone reads.
Does it track opens and clicks?
No. Open and click tracking adds tracking pixels and rewritten links that hurt deliverability, and opens are unreliable anyway. The sequence is driven by replies.
Will it reply to interested prospects for me?
No, on purpose. Interested replies go on the hot list and you respond personally. That's where deals are won or lost.
Is this legal?
Cold B2B email is allowed in many places if you follow the rules: honest sender and subject lines, a physical address, a working opt-out that you honor promptly, and (for EU/UK contacts) a lawful basis such as documented legitimate interest. Rules differ by country. This use case builds in the basics, but it isn't legal advice: check with whoever handles compliance at your company.
What if a lead is in the CRM as a contact, not a lead?
By default only leads matching {LEADCRITERIA} are sequenced. You can include contacts, but the customer and open-deal checks matter even more then.
Can several reps use it?
Yes, but set it up once per sender (each with their own inbox, owner filter and cap). Never let two clones sequence the same leads.
How much time does it take once running?
5–15 minutes a day to answer hot replies, plus a weekly look at the run reports.
Ready when you are. So is your clone.
Build your clone, paste in the Cold Email Sequence with Hot-Reply List instructions, and approve the plan it shows you.

















