Flip the Script: Turn Vendor Cold Outreach into Leads
Your clone turns every vendor cold pitch into a CRM lead and a witty, tailored reply that shows how your product does outreach better.
The problem
Vendor cold emails pile up and get deleted, even though every sender is a sales team that could use a better outreach tool. Flip the Script turns that noise into pipeline without anyone writing a single reply from scratch.
Flip the Script: Turn Vendor Cold Outreach into Leads
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Intermediate · Setup time: 30–45 minutes
Every vendor who cold-emails you is a sales team that clearly wants better outreach. Your clone spots those pitches twice a day, adds the sender to your CRM (Salesforce or HubSpot) as a lead, and drafts a friendly, witty reply showing how your product does their job better. You review the drafts and send the ones you like.
1. Overview and value
Your inbox gets a steady stream of unsolicited sales pitches. Most people delete them. But every one of those senders runs outbound sales or marketing, and if your product helps with outreach, sales, marketing or productivity, they are a warm-ish prospect who just told you exactly how they work today.
Flip the Script turns that noise into pipeline. Twice a day, at {RUN_TIMES}, your clone:
- scans the last ~12 hours of the inbox for vendor cold outreach,
- skips anyone on the skip list (your vendors, customers, partners, investors, existing CRM contacts and more),
- flags likely throwaway / burner addresses and doesn't spend effort on them,
- adds each real sender as a lead in your CRM (after checking for duplicates) with lead source "Inbound Vendor Outreach",
- writes a tailored reply: acknowledges their pitch, gives a short constructive (and a little witty) critique of their outreach, shows how
{PRODUCT_NAME}does it better, and invites them to sign up at{SIGNUP_URL}, - saves the reply as a draft for you to review (draft mode is the default),
- sends you a summary email, including a hot list of vendors who replied.
What you get:
| Benefit | What it looks like |
|---|---|
| Pipeline from noise | Pitches you would have deleted become CRM leads with context |
| Zero blank-page effort | Every reply is drafted and tailored to the specific email |
| A built-in demo | Your reply itself shows the quality of outreach your product makes possible |
| Clean CRM | Duplicate checks and a dedicated lead source keep these leads easy to filter |
| You stay in control | Draft mode by default, a daily send cap, an opt-out line in every reply |
Area What works CRM Salesforce (SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceActivityOperator) or HubSpot (HubspotContactOperator, HubspotCompanyOperator, HubspotEngagementOperator). HubSpot has no separate Lead object in this stack: the clone uses a contact with lifecycle stage "Lead" and a lead source property Gmail (GoogleGmailOperator) or Outlook (Outlook email operator) Hot list delivery (optional) Slack or Microsoft Teams (delivery only) Research Light web research by the clone (burner checks, reply tailoring) Scheduling Platform scheduled task
2. Who it's for
- Founders and sales leaders whose product helps other companies sell, market, or run outreach (so the people pitching you are your target buyers).
- SDR / BDR managers who want a steady trickle of inbound-style leads with zero prospecting effort.
- Marketing teams who like turning everyday moments into product demos.
- Anyone who gets a lot of vendor pitches and is tired of ignoring them.
It works best when the senders are plausible buyers of {PRODUCT_NAME}. If your product has nothing to do with how vendors sell, this use case will mostly create noise: skip it or narrow it with {TARGET_FIT}.
3. How it works
┌───────────────────────────────────────────────────────────────────┐
│ Vendors cold-email the inbox you connect ({MONITORED_INBOX}) │
└───────────────────────────────┬───────────────────────────────────┘
│
Twice a day at {RUN_TIMES} (scheduled task)
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ "Flip the Script" skill │
│ │
│ 1. Read the last ~12 hours of mail │
│ 2. Classify ──► vendor cold outreach vs everything else│
│ 3. Skip list check ──► vendors you pay, customers, partners, │
│ investors, CRM contacts, recruiters, │
│ personal, internal, newsletters, │
│ no-reply, {SKIP_LIST} │
│ 4. Burner check ──► flag throwaway addresses, no reply │
│ 5. CRM dedupe + add ──► new lead, source │
│ "Inbound Vendor Outreach" │
│ 6. Write tailored reply (critique + {PRODUCT_NAME} + signup) │
│ 7. {SEND_MODE}: draft (default) ──► save as draft │
│ send ──► send, up to {DAILY_CAP}/day │
│ 8. Check for vendor replies ──► hot list │
│ 9. Send ONE summary email ──► {SUMMARY_RECIPIENTS} │
└───────────────────────────────┬───────────────────────────────────┘
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ You: review drafts → edit or send → work the hot list │
└───────────────────────────────────────────────────────────────────┘How it decides what is "vendor cold outreach"
An email counts as vendor cold outreach only when all of these are true:
- It's unsolicited: there's no earlier thread where you or your team wrote to this sender first, and you didn't request it (form, demo request, RFP).
- It's a sales pitch: the sender is offering a product, service, agency, tool, data list, or "quick call" to sell something to you.
- It's one-to-one style: written to you personally (even if automated), not a mass newsletter or marketing blast with an unsubscribe footer from a list you joined.
- The sender is not on the skip list.
| Email type | What happens |
|---|---|
| Personal-style sales pitch from an unknown company | Kept: lead added, reply drafted |
| Follow-up #2, #3 in an automated sequence from the same vendor | Kept once: one lead, one reply on the latest email; later follow-ups are just noted |
| Vendor you actually pay, customer, partner, investor | Skipped: skip list |
| Sender already a contact (or lead you're working) in your CRM | Skipped: existing relationship (noted in summary) |
| Recruiter, job applicant, personal email, internal colleague | Skipped |
| Newsletter, marketing blast, no-reply address, receipts, notifications | Skipped |
| Lookalike domain, no website, mismatched sender, etc. | Flagged as likely burner: no reply, listed in summary |
| Unclear (could be a partner intro, could be a pitch) | Marked Needs review, no reply, listed in summary |
4. What the clone does day to day
- Runs twice a day at
{RUN_TIMES}and looks at the last ~12 hours of mail, so nothing falls between runs. - Classifies each message using the rules above. When in doubt, it does not reply and marks the email "Needs review".
- Checks your CRM before adding anyone: if the person is already a lead or contact, it doesn't create a duplicate (existing contacts are skipped entirely).
- Adds new leads with lead source "Inbound Vendor Outreach", their company, title (if given) and a short note summarizing the pitch.
- Drafts a reply tailored to the exact email, with a one-line opt-out at the bottom.
- Respects
{SEND_MODE}: indraftmode (the default) it only saves drafts. Insendmode it sends, never more than{DAILY_CAP}per day. - Watches for replies from vendors it wrote to and puts them on the hot list.
- Sends you one summary per run: new leads, drafts ready, skipped, burners, needs review, opt-outs, hot list, and which tools worked.
What it never does:
- Never replies to anyone on the skip list, including vendors you pay. Pitching your own suppliers can damage real relationships.
- Never insults, mocks or shames anyone. Witty and constructive, never snarky.
- Never sends automatically unless you have explicitly switched
{SEND_MODE}tosendand confirmed it. - Never exceeds
{DAILY_CAP}replies per day. - Never emails someone who opted out, and never writes to the same vendor twice unless they reply.
- Never promises discounts, pricing, custom terms or referral payouts beyond
{REFERRAL_OFFER}. - Never deletes, archives or marks emails as read, and never edits or deletes existing CRM records.
What a reply looks like
Each reply has five short parts: acknowledge their pitch, a friendly critique of their outreach, how {PRODUCT_NAME} does it better, the signup invite, and (optionally) a referral offer. Plus the opt-out line. Example snippets (generic):
Acknowledge: "Thanks for reaching out about your data-enrichment service. I can tell you've done this a few hundred times this week."
Critique: "Quick honest feedback, one outbound person to another: the email opened with my first name and then pivoted to a case study for a hospital chain. We're a software company. A one-line nod to what we actually do would have earned you a reply much faster."
Better way: "This is exactly what
{PRODUCT_NAME}fixes:{VALUE_PROP}. Your next sequence could reference each prospect's real context instead of a merge field."Invite: "Try it free at
{SIGNUP_URL}. Once you're a customer, let's talk about your service."Referral (optional): "And if it works for you, our partner program pays
{REFERRAL_OFFER}."Opt-out: "Not interested? Reply 'no thanks' and I won't email you again."
5. Setup walkthrough
The quickest path: download CLONE-INSTRUCTIONS.md and give it to your clone. It will check what's already connected, ask you for the placeholder values, show you a plan, and set up what it can after you approve. The steps below are what happens, so you know what to expect.
Step 1: Check requirements (5 min) Open REQUIREMENTS.md and run through the pre-flight checklist. You need an email connection (read + drafts, and send if you ever turn on auto-send), a Salesforce or HubSpot connection with permission to create leads or contacts, and the ability to create scheduled tasks.
Step 2: 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."
Step 3: Review the discovery table (3 min) The clone reports which skills/operators and connections it already has and which are missing.
Step 4: Answer the placeholder questions (5–10 min) See the table in section 6. The most important ones: your product and value prop, your signup link, and your skip list (especially vendors you pay).
Step 5: Approve the plan (2 min) The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right.
Step 6: Do your part (5–15 min) Things only you can do:
- Complete sign-in (OAuth) for the email and CRM connections.
- Make sure the CRM has a lead source value "Inbound Vendor Outreach" (or let the clone use an existing field).
- Give the clone your list of paid vendors (or a CRM view / list it can read).
Step 7: Save the Flip the Script skill (5 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, especially the guardrails and tone rules.
Step 8: Run the test plan (10 min) Send a fake pitch from a test address you control, run the skill manually and check the draft, the CRM lead and the summary against the checklist in CLONE-INSTRUCTIONS.md.
Step 9: Live in draft mode for at least a week Review every draft. Edit the tone in the skill until you'd happily send most drafts unchanged. Only then consider switching to send mode, with a low {DAILY_CAP}.
6. Placeholders to decide
| Placeholder | What it means | Example |
|---|---|---|
{CLONE_NAME} | Your clone's display name | "Ava" |
{MONITORED_INBOX} | The inbox the clone scans and replies from | you@yourcompany.com (or the clone's own inbox, {CLONE_INBOX}) |
{SENDER_NAME} | The name and signature on replies | "Jordan Lee, Head of Sales" |
{YOUR_COMPANY_DOMAINS} | Your company's email domains (internal = these) | yourcompany.com, yourcompany.io |
{PRODUCT_NAME} | Your product's name | "YourProduct" |
{VALUE_PROP} | One or two sentences on why your product makes outreach better | "it researches every prospect and writes a personal first line, so reply rates go up without more headcount" |
{TARGET_FIT} | Which senders are worth a reply (optional filter) | "any B2B company with a sales or marketing team" |
{SIGNUP_URL} | Where you want them to sign up | https://yourcompany.com/signup |
{REFERRAL_OFFER} | Optional referral / partner offer (leave blank to omit) | "20% of first-year revenue for referred customers" |
{SKIP_LIST} | Extra domains or addresses to never reply to | paid vendors, board members' firms, your agency |
{SEND_MODE} | draft (save drafts only) or send (send automatically) | draft (default) |
{DAILY_CAP} | Max replies sent per day in send mode | 10 |
{RUN_TIMES} | The two daily run times, with time zone | 8:00 AM and 2:00 PM America/Chicago, Mon–Fri |
{SUMMARY_RECIPIENTS} | Who gets the summary / hot list email | you@yourcompany.com |
{LEAD_OWNER} | Who new leads are assigned to in the CRM | you, or a round-robin queue |
Tip: in draft mode {DAILY_CAP} still applies to how many drafts are written per day, so you aren't flooded on a busy day.
7. What to expect day to day
- At each run time: the run starts and usually finishes in a few minutes.
- Shortly after: a summary email lands at
{SUMMARY_RECIPIENTS}with new leads, drafts ready to review (with links or subjects), skipped emails with reasons, likely burners, anything that needs review, and the hot list. - Your part (5–10 minutes a day): open your Drafts folder, read each reply, tweak if needed, and send. Delete any you don't like.
- Hot list: when a vendor writes back, they show up at the top of the next summary. That's a real conversation: reply yourself.
- In the CRM: new leads appear with lead source "Inbound Vendor Outreach" and a note with the pitch summary, so you can build a view or report for them.
- Quiet days: if there's no vendor outreach, you still get a short summary (or none, if you choose "only send when there's something").
8. Customizing
Tone. Ask the clone to edit the skill, e.g. "Make the critique gentler", "Drop the jokes, keep it professional", "Keep replies under 120 words", or "Always sign off with our tagline".
Who gets a reply. Narrow it with {TARGET_FIT} (e.g. "only companies with 20+ employees", "only SaaS vendors") or extend {SKIP_LIST} at any time.
Send mode and cap. Switch {SEND_MODE} between draft and send by telling the clone, e.g. "Switch Flip the Script to send mode with a daily cap of 5." The clone will repeat the change back and ask you to confirm with "yes" before switching. Switching back to draft never needs confirmation.
Referral offer. Add, change or remove {REFERRAL_OFFER} whenever your partner program changes.
Schedule. Change {RUN_TIMES} (one run a day is fine for low volume; change the look-back window to ~24 hours if you do).
Summary. Send only when there's something to report, or add a weekly roll-up of leads created and replies received.
9. Known gotchas
- Sending volume can hurt your email reputation. Replying to lots of cold emails from your own domain, especially if some bounce or get marked as spam, can damage deliverability for all your email. Stay in draft mode at first, start
sendmode with a low{DAILY_CAP}(5–10), and raise it slowly over weeks. Consider replying from a secondary mailbox if your volume is high. - Burner addresses may never be read. Many cold-outreach tools send from throwaway lookalike domains that nobody monitors, or that bounce. The clone flags these and doesn't reply or add them as leads by default, but some will slip through. Don't judge results by those.
- Never pitch your own vendors. If you pay them, they belong on the skip list. A cheeky critique to a supplier you rely on is a bad look. Give the clone your vendor list (or a CRM / finance view it can read) and keep it current.
- Review drafts before turning on auto-send. Spend at least a week in draft mode. Read every reply. Only switch to
sendwhen you'd happily send most drafts unedited. - Tone matters. Witty, warm and constructive works. Snarky, sarcastic or "gotcha" replies get screenshotted and shared. The skill tells the clone to critique the outreach, never the person, and to keep humor light.
- Follow email and privacy rules. Every reply includes a clear opt-out line and your real identity, and the clone stops emailing anyone who opts out. In the EU/UK (GDPR) and similar regimes, adding someone to your CRM and emailing them needs a lawful basis (often "legitimate interest", since they contacted you first) and you must honor deletion requests. Under US CAN-SPAM, commercial replies need accurate headers, no misleading subjects, a working opt-out honored promptly, and your business postal address if the message is mainly commercial. Check with your own legal or compliance team: this is not legal advice.
- Honor unsubscribes everywhere. If a vendor says "no thanks" or "remove me", the clone adds them to an opt-out list, notes it in the CRM, and never writes again. Make sure the same person isn't also in other sequences you run.
- Lead pollution in your CRM. Vendor leads are lower intent than real inbound. Keep them on their own lead source so they don't distort your inbound conversion numbers, and periodically clean out ones that never respond.
- One vendor, many emails. Automated sequences send several follow-ups. The skill creates one lead and one reply per sender and treats later follow-ups as the same conversation.
- The clone only sees what it's connected to. It scans the inbox you connected (
{MONITORED_INBOX}). Pitches sent to other people or mailboxes are invisible to it unless you forward them or connect that inbox. - Use exact skill/operator names as they appear in your skill catalog. Names can differ slightly 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. Make sure the guardrails match your company's policies.
10. FAQ
Does this work with my CRM? It works with Salesforce and HubSpot, the CRMs with operators on the platform today. Your clone needs permission to search and create leads or contacts. See the mapping in REQUIREMENTS.md.
HubSpot doesn't have a separate lead object. Is that a problem? No. In HubSpot the clone creates a contact (and company) with lifecycle stage "Lead" and a lead source property. In Salesforce it creates a Lead. See REQUIREMENTS.md.
Will the clone send emails on its own? Not by default. In draft mode it only saves drafts. It sends only after you explicitly switch {SEND_MODE} to send and confirm, and even then never more than {DAILY_CAP} per day.
Will it reply to my customers or vendors? No. Customers, partners, investors, vendors you pay, existing CRM contacts and everything on {SKIP_LIST} are skipped. If the clone isn't sure, it marks the email "Needs review" and doesn't reply.
Does it work with Gmail and Outlook? Yes: Gmail (GoogleGmailOperator) or Outlook, whichever email connection your clone has.
Is this going to annoy people? Some, maybe. They emailed you first, the reply is short and personal, and every message has an opt-out. Keep the tone kind and the volume low.
What does it cost in time once it's running? About 5–10 minutes a day reviewing drafts, plus whatever time you spend on hot-list conversations (that's the good part).
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| No summary email arrived | Scheduled task not created, paused, or wrong time zone | Ask the clone to list its scheduled tasks; check {RUN_TIMES} time zone |
| A real vendor pitch was skipped | Classified as newsletter, matched skip list, or marked Needs review | Check the "Skipped" and "Needs review" sections; adjust the classification rules or skip list |
| A reply was drafted to someone you pay | Vendor not on the skip list | Delete the draft, add the domain to {SKIP_LIST} or your vendor list |
| Duplicate leads in the CRM | Dedupe searched only by email, or the CRM was unavailable | Ask the clone to also match on company domain; check source status in the summary |
| "CRM: unavailable" in summary | Connection expired or missing create permission | Re-run sign-in for the CRM; confirm search + create lead permissions |
| No drafts appear in your mailbox | Email connection lacks draft permission, or drafts went to the clone's own mailbox | Check which mailbox is {MONITORED_INBOX}; reconnect with draft permission |
| Replies feel snarky or generic | Tone rules too loose, or {VALUE_PROP} too vague | Tighten the tone section of the skill; give a more specific value prop and one example reply you like |
| Bounces or spam complaints | Replying to burners or sending too fast | Switch back to draft, lower {DAILY_CAP}, tighten burner rules |
| Vendor reply missing from hot list | Reply came from a different address or after the look-back window | Ask the clone to match replies by thread and company domain |
Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Flip the Script (Turn Vendor Cold Outreach into Leads)
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
---
## 1. Role and goal
You are setting up the **Flip the Script** use case for your user.
When setup is done, twice a day at `{RUN_TIMES}` you will run a skill called **Flip the Script** that:
1. reads the last ~12 hours of mail in `{MONITORED_INBOX}`,
2. finds vendor cold outreach (unsolicited sales pitches),
3. skips everyone on the skip list and flags likely burner addresses,
4. checks the CRM for duplicates and adds each new sender as a lead with lead source "Inbound Vendor Outreach",
5. writes a reply tailored to each pitch (friendly critique of their outreach, how `{PRODUCT_NAME}` does it better, signup invite, optional referral offer, opt-out line),
6. saves replies as **drafts** (default) or sends them, depending on `{SEND_MODE}`, never more than `{DAILY_CAP}` per day,
7. checks for vendor replies and builds a hot list,
8. sends one summary email to `{SUMMARY_RECIPIENTS}`.
Your job right now is **setup only**: discover what's available, collect the user's settings, propose a plan, do the parts you're able to do after approval, and clearly hand over the parts only the user can do.
Be honest about your limits. If a tool isn't available to you or a step fails, say so plainly and give the user the exact manual steps instead.
## 2. Safety rules (read before doing anything)
- **Plan first, then act.** Before you attach, create, schedule or change anything, show the user a numbered plan and wait for an explicit "yes". No yes = no changes.
- **Approval is per plan.** If the plan changes, show the new plan and ask again.
- **Never ask for, accept or handle passwords, API keys or tokens.** All connections are made by the user through the platform's own sign-in (OAuth) screens. If the user pastes a secret into chat, tell them not to and don't use it.
- **Never email vendors, prospects or customers during setup.** Don't reply to any real pitch during setup or testing. The only emails you may send during setup are a test summary to the user and a test reply to the user's own test address (only after they approve).
- **Draft mode is the default.** Set `{SEND_MODE}` to `draft` unless the user explicitly asks for `send`. Even then, recommend starting in draft. Switching to `send` (now or later) requires you to repeat the change back, including `{DAILY_CAP}`, and get an explicit "yes".
- **CRM: add, don't change.** Setup is read-only in the CRM. The skill may only search and create new leads and notes. Never edit, merge or delete existing records.
- **Don't guess names.** Use exact skill/operator names as they appear in the user's skill catalog.
## 3. Discovery
Check what you already have. Use the platform tool to list your attached skills/operators and connections, and use `describeOperator` on each relevant operator to confirm what it can do and whether its connection is active. In particular, confirm the email operator can **create drafts** and the CRM operators can **create leads** (Salesforce) or **contacts** with lifecycle stage Lead (HubSpot).
Look for:
| Need | Required? | Examples of what to look for |
|---|---|---|
| Email | **Required** | GoogleGmailOperator or the Outlook email operator (read + drafts; send for summary and send mode) |
| CRM operators | **Required** | Salesforce: SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceActivityOperator. HubSpot: HubspotContactOperator, HubspotCompanyOperator, HubspotEngagementOperator (search + create) |
| Scheduled task | **Required** | Ability to create a recurring scheduled task |
| Web research | Optional (recommended) | Your own web research, for burner checks and tailoring |
| Chat | Optional | Slack or Microsoft Teams (post hot list, delivery only) |
| Vendor list source | Optional | GoogleSheets-Operator or Microsoft_Excel spreadsheet, or CRM account type Vendor |
**Report the results to the user in a table like this:**
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Email | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing | … | Drafts permission? Send permission? |
| CRM | … | … | Can search? Can create leads? |
| Scheduled task | … | … | … |
| Research / web | … | … | … |
| Chat | … | … | … |
| Vendor list source | … | … | … |
If you can't check something (for example, there's no way to list connections), mark it "❓ Couldn't check" and say why.
## 4. Collect placeholder values
Ask the user **once**, in a single short list. Offer the examples. Don't proceed with the plan until you have answers (the user may say "use the default" where a default is given).
> To set this up I need a few details:
>
> 1. **Inbox to scan** (`{MONITORED_INBOX}`): which mailbox receives the vendor pitches? *(I'll suggest the one I'm connected to.)*
> 2. **Reply signature** (`{SENDER_NAME}`): name, title and company as it should appear on replies. *(Include your postal address if your signature doesn't already.)*
> 3. **Your company domains** (`{YOUR_COMPANY_DOMAINS}`): e.g. `yourcompany.com, yourcompany.io`.
> 4. **Product** (`{PRODUCT_NAME}`) and **value prop** (`{VALUE_PROP}`): one or two specific sentences on why your product makes outreach better.
> 5. **Signup link** (`{SIGNUP_URL}`): e.g. `https://yourcompany.com/signup`.
> 6. **Referral offer** (`{REFERRAL_OFFER}`, optional): e.g. "20% of first-year revenue for referred customers". *(default: none)*
> 7. **Who's worth a reply** (`{TARGET_FIT}`, optional): e.g. "any B2B company with a sales team". *(default: any business vendor)*
> 8. **Skip list** (`{SKIP_LIST}`): vendors you pay and any other domains/addresses I must never reply to. *(Customers, partners, investors, existing CRM contacts, recruiters, personal, internal, newsletters and no-reply addresses are skipped automatically.)*
> 9. **Lead settings**: lead source value (`{LEAD_SOURCE_VALUE}`, default "Inbound Vendor Outreach") and lead owner (`{LEAD_OWNER}`, default: you).
> 10. **Send mode** (`{SEND_MODE}`) and **daily cap** (`{DAILY_CAP}`). *(default: `draft`, cap 10)*
> 11. **Run times** (`{RUN_TIMES}`): two times a day with time zone. *(default: 8:00 AM and 2:00 PM your time zone, Mon–Fri)*
> 12. **Summary recipients** (`{SUMMARY_RECIPIENTS}`): who gets the summary and hot list? *(default: you)*
Repeat the answers back in a table and ask the user to confirm.
## 5. What you can do yourself (after approval)
Present a plan like this, filled in with real names from discovery:
> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing skills/operators from the catalog: *[list exact names]*.
> 2. Create the **Flip the Script** skill using the text in section 7, with your values filled in and `{SEND_MODE}` = `draft`.
> 3. Create a scheduled task "Flip the Script (twice daily)" that runs the skill at `{RUN_TIMES}`, Monday–Friday.
> 4. Run one test with your test address (section 8): one test reply (as a draft, or sent to your test address only) and one test summary to you.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.
After a clear "yes":
1. **Attach skills/operators.** Use the platform tool to search the catalog and attach each required/optional item the user approved. Confirm each with `describeOperator`. If an item needs a sign-in, tell the user (it goes on their list).
2. **Create the Flip the Script skill.** Fill the placeholders with the confirmed values and save it.
- **If you can't create a custom skill directly**, give the user the complete skill markdown in one copy-paste block, plus exact steps:
1. Open your clone's settings → **Skills** (or **Custom skills**).
2. Click **New skill** / **Add skill**.
3. Name it exactly **Flip the Script**.
4. Paste the full block into the skill instructions field.
5. Read it through, then **Save**.
6. Tell me "saved" so I can verify it's attached.
(Menu names may differ slightly in your workspace.)
3. **Create the scheduled task.** Name: "Flip the Script (twice daily)". Schedule: `{RUN_TIMES}`, Monday–Friday (one task with two times, or two tasks if the platform needs that). Action: "Run the Flip the Script skill for the last 12 hours." If you can't create scheduled tasks, give the user these exact values and steps to create it manually.
4. **Report back** what succeeded and what failed, honestly.
**Switching send mode later.** If the user later asks to switch to `send`, reply with: "I'll switch Flip the Script to **send** mode: I'll send replies automatically, up to `{DAILY_CAP}` per day, from `{MONITORED_INBOX}`. Reply **yes** to confirm." Only change the setting after an explicit "yes". Switching back to `draft` can be done immediately.
## 6. What the user must do
Give the user this list, with the how-to steps, and track which ones are done.
1. **Sign in to connections (OAuth).** For each connection marked ⚠️ or ❌ (Gmail or Outlook, Salesforce or HubSpot): open the clone's **Connections** / **Integrations** page → choose the app → **Connect** / **Sign in** → approve the requested permissions. Minimum permissions: email read + create drafts (+ send for the summary and for send mode); CRM search + create leads/contacts + create notes. *I can't do this for you and I never need your password.*
2. **Set up the lead source in your CRM.** Ask your CRM admin to add `{LEAD_SOURCE_VALUE}` as a lead source value (Salesforce: Setup → Object Manager → Lead → Fields → Lead Source → add value; HubSpot: Settings → Properties → your lead source property → add option). Or tell me an existing value or tag to use.
3. **Give me your vendor list.** Share the list of vendors you pay (domains), or a Google Sheet, Excel workbook or CRM view I can read, so I never pitch them. Keep it current.
4. **Check your signature.** Make sure replies will include your real name, company and postal address, and approve the opt-out line in the skill.
5. **(Recommended) Check with legal / compliance** that the opt-out wording and your GDPR / CAN-SPAM approach fit your company's policies.
6. **Review drafts daily.** Open your Drafts folder after each summary, edit or send the ones you like, delete the rest.
## 7. The Flip the Script skill (save this in full)
Fill in the placeholders, then save as a skill named **Flip the Script**. Don't shorten it.
~~~~markdown
# Flip the Script
## Purpose
Twice a day, find vendor cold outreach in my inbox, add each real sender to the CRM as a
lead, and write a tailored, friendly reply that critiques their outreach, shows how
{PRODUCT_NAME} does it better, and invites them to sign up. Save replies as drafts
(or send, if send mode is on), and send one summary with a hot list of vendor replies.
## Settings
- Inbox to scan and reply from: {MONITORED_INBOX}
- Reply signature: {SENDER_NAME}
- Company domains (internal): {YOUR_COMPANY_DOMAINS}
- Product: {PRODUCT_NAME}
- Value prop: {VALUE_PROP}
- Signup link: {SIGNUP_URL}
- Referral offer (blank = omit): {REFERRAL_OFFER}
- Who's worth a reply: {TARGET_FIT}
- Extra skip list: {SKIP_LIST}
- Lead source value: {LEAD_SOURCE_VALUE}
- Lead owner: {LEAD_OWNER}
- Send mode: {SEND_MODE} (draft = save drafts only; send = send automatically)
- Daily cap (replies per day, drafts or sends): {DAILY_CAP}
- Run times: {RUN_TIMES}
- Look-back window: last 12 hours
- Summary recipients: {SUMMARY_RECIPIENTS}
## Tools
Use the exact names from my skill catalog. Use whatever is connected; skip what isn't.
| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Read recent mail, find vendor replies | GoogleGmailOperator or Outlook email operator | Yes | Read |
| Save replies as drafts | GoogleGmailOperator or Outlook email operator | Yes | Create drafts |
| Send replies (send mode only) and the summary | GoogleGmailOperator or Outlook email operator | Yes | Send ONLY replies to qualified vendors (send mode) and the summary to {SUMMARY_RECIPIENTS} |
| Search leads/contacts/accounts; create leads and notes (Salesforce) | SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceActivityOperator | Yes (if Salesforce) | Search + create only; never edit, merge or delete |
| Search contacts/companies; create contacts (lifecycle stage Lead) and notes (HubSpot) | HubspotContactOperator, HubspotCompanyOperator, HubspotEngagementOperator | Yes (if HubSpot) | Search + create only; never edit, merge or delete |
| Check sender domains, tailor replies | Clone web research | Optional | Read public web |
| Post the hot list | Slack or Microsoft Teams (messaging integration) | Optional | Post to one agreed channel |
## Guardrails
- SEND MODE: if Send mode is anything other than exactly "send", only save drafts. Never send a reply in draft mode.
- DAILY CAP: never write more than {DAILY_CAP} replies (drafts or sends) per calendar day across both runs. When the cap is reached, list the remaining qualified emails in the summary as "Over cap, not replied".
- SKIP LIST: never reply to, or create a lead for, anyone on the skip list (Step 3). When unsure, mark "Needs review" and do not reply.
- ONE TOUCH: reply at most once per sender (and once per company domain) unless they reply to us. Later follow-ups from the same sequence are noted, not answered.
- OPT-OUT: every reply ends with the opt-out line. If anyone says "no thanks", "unsubscribe", "remove me", "stop" or similar, add them to the opt-out list, mark them opted out in the CRM (opt-out field or note), and never email them again.
- TONE: witty, warm and constructive. Critique the outreach, never the person or their company. No sarcasm, mockery, profanity, insults or shaming. No jokes about appearance, names, language, culture, or anything personal. If in doubt, be plainer.
- HONESTY: only claim what {VALUE_PROP} says. No invented statistics, customer names, discounts, pricing or promises. Offer only the referral terms in {REFERRAL_OFFER}.
- PRIVACY: don't include anything from my inbox or CRM in replies except what the sender wrote to me. Never mention other vendors or customers by name.
- CRM: search before creating. Create new leads and notes only. Never edit, merge or delete existing records.
- MAILBOX: never delete, archive, move or mark emails as read.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that tool "unavailable" for this run, continue without it where safe (if the CRM is unavailable, do NOT reply to anyone this run: list them as "Pending CRM check"), and report it in the summary.
- Never ask for or handle passwords or tokens.
## Step 1: Read recent mail
- List emails received in {MONITORED_INBOX} in the last 12 hours (in the run time zone), including Promotions / Other folders if visible.
- For each email capture: sender name and address, sender domain, reply-to address, subject, date, body text, thread ID, and whether the thread contains any earlier message from us.
- Skip emails already handled in a previous run (check thread for an existing draft or reply from us, or a CRM note for this sender).
## Step 2: Classify each email
Mark an email "Vendor cold outreach" only if ALL are true:
1. Unsolicited: no earlier message from us or {YOUR_COMPANY_DOMAINS} in the thread, and not a response to a form, demo request, RFP or introduction we asked for.
2. A sales pitch: offers a product, service, agency, tool, data, leads, staffing, or "a quick call" to sell something to us.
3. One-to-one style: addressed to a person (even if automated), not a newsletter or marketing blast from a list we joined.
4. Fits {TARGET_FIT} (if set).
Typical signals of cold outreach: "quick question", "worth a chat?", "I noticed your company…", calendar links, case studies, "following up on my last email", sequence-style bumps, tracking links.
Not cold outreach: replies in existing conversations, invoices and receipts, product notifications, event invites from people we know, partner introductions, press, job applications, support requests, customer messages.
If it's genuinely unclear, mark "Needs review" and don't reply.
## Step 3: Skip list check
Skip (no lead, no reply), and record the reason, if the sender is:
- a vendor we pay, or on {SKIP_LIST} (match full address or domain),
- a customer, partner or investor (CRM account type, or known domain),
- an existing CRM contact, or a lead already owned and being worked (note "Existing relationship"),
- a recruiter, staffing agency pitching candidates, or job applicant,
- a personal email domain (gmail.com, outlook.com, yahoo.com, icloud.com, etc.) with no company identity,
- internal ({YOUR_COMPANY_DOMAINS}),
- a mass newsletter or marketing blast (List-Unsubscribe header, "view in browser", bulk sender footer),
- a no-reply address (noreply@, no-reply@, donotreply@, notifications@),
- on the opt-out list.
## Step 4: Burner check
Flag "Likely burner" (no reply, no lead by default; list in the summary) if two or more are true:
- The domain is a lookalike of a main brand (extra word or letter, e.g. "get-", "try-", "-hq", "-mail", different TLD) and the main brand's site is different.
- The domain has no working website, or redirects to another domain.
- The sender name, signature company and domain don't match, or the reply-to differs from the sender.
- The domain appears newly registered or has no public presence (using web research).
- The email is generic with no specific company details.
If a burner clearly points to a real main domain, you may note the main domain in the summary, but don't reply or create a lead unless the user asks.
## Step 5: CRM dedupe and add lead
For each remaining qualified email:
1. Search the CRM for the sender's email address in leads and contacts.
2. Search for the sender's company domain in accounts/companies and leads.
3. If the sender is an existing contact: skip (Step 3). If an existing lead: don't create another; add a note "Vendor outreach received {date}: {one-line pitch summary}" and continue to Step 6 only if no reply has been sent before.
4. If new: create a lead (Salesforce: SalesforceLeadOperator) or, in HubSpot, a contact with lifecycle stage "Lead" plus a company, with first name, last name, email, company, title (if given), website (from domain), lead source = {LEAD_SOURCE_VALUE}, owner = {LEAD_OWNER}.
5. Add a note/activity: "Inbound vendor outreach on {date}. Pitch: {one-line summary}. Their outreach style: {manual / automated sequence, follow-up #N}. Reply: {drafted / sent / not replied + reason}."
## Step 6: Write the tailored reply
Write a reply in the same thread, under 150 words, plain text, in my voice, signed {SENDER_NAME}. Five parts:
1. Acknowledge: thank them and show you read it (mention their actual offer in a few words).
2. Friendly critique (1–3 sentences): one or two specific, fixable things about THEIR outreach, based on this email. Examples: generic opener, wrong industry case study, merge-field errors, too long, no clear ask, three follow-ups in four days, a calendar link before any value. Light humor is fine; kindness is required.
3. Better way: how {PRODUCT_NAME} solves exactly that problem, using {VALUE_PROP}. Connect it to the critique.
4. Invite: "Sign up at {SIGNUP_URL}. Once you're a customer, let's talk about what you offer."
5. Referral (only if {REFERRAL_OFFER} is set): one sentence offering the referral partnership.
Then the opt-out line, on its own line:
"Not for you? Just reply 'no thanks' and I won't email you again."
Example tone (generic, adapt to each email; don't copy verbatim):
- "Thanks for the note about your video-prospecting tool. Honest feedback from one outbound team to another: 'I hope this finds you well' plus a 30-minute ask is a big swing for a first email."
- "Your sequence followed up three times in five days, which tells me your tool is great at persistence. Imagine if each bump added something new about my company instead."
- "Your subject line said 'Quick question' and the email had no question. {PRODUCT_NAME} would have caught that: {VALUE_PROP}."
Never: "Nice try", "Did a robot write this?", "lol", or anything that mocks the person.
## Step 7: Draft or send
- Check the daily cap first (count drafts and sends already made today).
- If Send mode = "draft" (or anything other than exactly "send"): save the reply as a draft in the thread.
- If Send mode = "send": send the reply in the thread.
- Record the result (drafted / sent / failed / over cap) in the CRM note and the summary.
## Step 8: Hot list
- Look for replies in the last 12 hours from any sender this skill drafted or sent a reply to (the user may have sent a draft manually; match by thread, then by sender domain).
- For each: name, company, one-line summary of what they said, sentiment (interested / question / not interested / opt-out), and a suggested next step.
- Opt-outs go to the opt-out list immediately (see Guardrails) and are listed separately, not on the hot list.
- Do NOT reply to hot-list messages automatically. The user replies personally.
## Step 9: Summary email
Send ONE email to {SUMMARY_RECIPIENTS} per run. Subject: "Flip the Script: {date} {morning/afternoon}: {N} new leads, {M} drafts, {H} hot".
Body:
1. Hot list (top of the email): vendors who replied, with summary and suggested next step.
2. Drafts ready / replies sent: sender, company, subject, one-line pitch, the critique point you used.
3. New CRM leads created (and existing leads noted).
4. Skipped, with reasons (skip list, existing relationship, newsletter, no-reply, recruiter, personal, internal).
5. Likely burners, with the signals that triggered the flag.
6. Needs review: what's unclear.
7. Over cap / Pending CRM check: qualified emails not replied to this run.
8. Opt-outs received.
9. Counts today vs {DAILY_CAP}, current Send mode, and tool status (worked / unavailable after retry).
If there's nothing to report, send a one-line summary with tool status.
~~~~
## 8. Test plan
Run this before relying on the schedule. Ask the user to approve the test first. Use only test data: never reply to a real vendor or prospect during testing.
1. **User sends test emails** to `{MONITORED_INBOX}` from an address they control (not a real vendor or prospect), for example a personal test account with a company-style display name and signature:
- one **fake vendor pitch** (e.g. "Quick question about your outbound" with a generic opener and a calendar link),
- one **fake newsletter** (with an "Unsubscribe" footer) so we can check it's skipped,
- optionally, an email from a domain on `{SKIP_LIST}` (or tell me to treat a test domain as a paid vendor for this test only).
- Note: a personal domain like gmail.com is normally skipped. For the test, tell me to treat your test address as a company sender.
2. **Run Flip the Script manually** ("Run Flip the Script now") with `{SEND_MODE}` = `draft`.
3. **Verify the checklist together:**
| Check | Pass? |
|---|---|
| Fake pitch was classified as vendor cold outreach; newsletter and skip-list email were **skipped** with the right reasons | ☐ |
| CRM was searched first; a **test lead** was created with lead source `{LEAD_SOURCE_VALUE}`, owner `{LEAD_OWNER}` and a pitch note | ☐ |
| Running the skill a second time did **not** create a duplicate lead or a second draft | ☐ |
| A **draft** (not a sent email) appeared in the thread | ☐ |
| Draft acknowledges the pitch, critiques it kindly and specifically, mentions `{PRODUCT_NAME}` and `{SIGNUP_URL}`, includes the referral line only if set, and ends with the opt-out line | ☐ |
| Tone is witty and kind, not snarky; the user would be happy to send it | ☐ |
| Summary email arrived at `{SUMMARY_RECIPIENTS}` only, with all sections and the draft count vs `{DAILY_CAP}` | ☐ |
| **No email was sent to anyone else** | ☐ |
| (Optional) User replies "no thanks" from the test address: it's recorded as an opt-out on the next run, not on the hot list | ☐ |
| (Optional) User replies "interested" from the test address: it shows on the hot list on the next run | ☐ |
4. Fix anything that failed, re-run, then **delete the test lead** from the CRM and the test drafts (the user does this, since I never delete CRM records).
## 9. Final status checklist
When you finish, send the user a status summary in this format:
**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] Required skills/operators attached: …
- [ ] Optional add-ons attached: …
- [ ] Flip the Script skill created in **draft** mode (or full text handed over for copy-paste)
- [ ] Scheduled task "Flip the Script (twice daily)" created for `{RUN_TIMES}`, Mon–Fri
- [ ] Test run completed; results: …
**⏳ Waiting on you**
- [ ] Sign in to: …
- [ ] Add `{LEAD_SOURCE_VALUE}` as a lead source value in the CRM (or confirm an existing one)
- [ ] Share your list of paid vendors and keep `{SKIP_LIST}` current
- [ ] Check your signature (name, company, postal address) and approve the opt-out line
- [ ] Save the Flip the Script skill (if I handed it over)
- [ ] Delete the test lead and test drafts
- [ ] Review drafts after each summary for at least a week
**💡 Optional next steps**
- [ ] Turn on web research for better burner checks and tailoring
- [ ] Post the hot list to Slack or Teams
- [ ] Add a `{REFERRAL_OFFER}` if you have a partner program
- [ ] After a week of good drafts, consider switching to `send` mode with a low `{DAILY_CAP}` (I'll ask you to confirm)
- [ ] Build a CRM report for lead source `{LEAD_SOURCE_VALUE}` to track conversions
Requirements
Requirements: Flip the Script
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 30–45 minutes
Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.
1. Required skills / operators
Use the exact operator names below. Names can differ slightly by workspace, and your clone will report what it finds.
| # | Skill / operator | What it's used for | Notes |
|---|---|---|---|
| 1 | GoogleGmailOperator or Outlook email operator | Read the last ~12 hours of mail, save reply drafts, (optionally) send replies, send the summary | Connected to {MONITORED_INBOX} |
| 2 | Salesforce: SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceActivityOperator. HubSpot: HubspotContactOperator, HubspotCompanyOperator, HubspotEngagementOperator | Check for existing leads/contacts, create new leads, log a note/activity | Pick the one CRM you use. HubSpot has no separate Lead object: leads are contacts with lifecycle stage "Lead" |
| 3 | Scheduled task (platform) | Run Flip the Script twice a day at {RUN_TIMES} | 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.
2. Required connections and permissions
| Connection | Minimum permission | Why |
|---|---|---|
| Gmail or Outlook | Read + Create drafts | Find vendor pitches; save replies as drafts |
| Gmail or Outlook (send mode only) | Send | Only needed if you later switch {SEND_MODE} to send. Also used to send the summary to {SUMMARY_RECIPIENTS} |
| Salesforce or HubSpot | Search leads, contacts, accounts/companies; Create leads (or contacts + companies); Create notes/activities | Dedupe and add leads. No delete or bulk-edit access needed |
| Web research (if used) | Read public web pages | Check whether a sender's domain has a real website (burner check) |
All connections are made by you through sign-in (OAuth). Your clone never needs your password.
3. Optional add-ons
| Add-on | Adds | Examples |
|---|---|---|
| Web research (clone) | Better burner detection (does the domain have a real site?) and better-tailored replies | Clone web research |
| Slack or Microsoft Teams | Post the summary or hot list to a channel instead of (or as well as) email | Delivery only |
| Vendor list | An always-current list of vendors you pay, for the skip list | A spreadsheet via GoogleSheets-Operator or Microsoft_Excel, or a CRM account type of Vendor |
Salesforce ⇄ HubSpot mapping
| Concept | Salesforce | HubSpot |
|---|---|---|
| Lead (new vendor sender) | Lead (SalesforceLeadOperator) | Contact with Lifecycle stage = Lead (HubspotContactOperator) |
| Contact (existing relationship, skip) | Contact (SalesforceContactOperator) | Contact with a stage beyond Lead |
| Account / company | Account (SalesforceAccountOperator) | Company (HubspotCompanyOperator) |
| Lead source = "Inbound Vendor Outreach" | Lead Source (picklist) | Lead source property (custom or Original source) |
| Note / activity (pitch summary, reply status) | Task / Activity (SalesforceActivityOperator) | Note (HubspotEngagementOperator) |
| Opt-out flag | Email Opt Out | Unsubscribed / "Do not contact" property |
| Vendor / partner type (skip list) | Account Type = Vendor / Partner | Company type = Vendor / Partner |
Field names vary by setup. If your CRM has no "Inbound Vendor Outreach" source value, ask your CRM admin to add it, or tell the clone which existing value to use ({LEAD_SOURCE_VALUE}).
Gmail ⇄ Outlook mapping
| Concept | Google Workspace | Microsoft 365 |
|---|---|---|
| Gmail (GoogleGmailOperator) | Outlook (Outlook email operator) | |
| Draft location | Drafts | Drafts |
| Mass mail signal | "Unsubscribe" link / List-Unsubscribe header, Promotions tab | "Unsubscribe" link / List-Unsubscribe header, Other / Clutter |
| No-reply signal | noreply@, no-reply@, donotreply@ | Same |
Slack ⇄ Teams (optional)
| Concept | Slack | Microsoft Teams |
|---|---|---|
| Where the hot list goes | A channel or DM | A channel or chat |
4. Data prerequisites
- You know which inbox gets the pitches (
{MONITORED_INBOX}) and it's the one connected to the clone. - A list of vendors you pay (domains), or a CRM view / spreadsheet the clone can read.
- CRM (Salesforce or HubSpot) contacts have email addresses, and customers, partners and vendors are distinguishable (so the skip list works).
- A lead source value "Inbound Vendor Outreach" exists in the CRM (or you've chosen an alternative).
- A clear product pitch:
{PRODUCT_NAME}, a specific{VALUE_PROP}, and a working{SIGNUP_URL}. - (Optional) Referral program details (
{REFERRAL_OFFER}) that your company actually honors. - Your email signature includes your company name and postal address (helps with CAN-SPAM).
5. Roles and permissions
| Who | Needs to |
|---|---|
| Clone admin (owner of the clone in the Clone platform) | Attach skills/operators, approve the plan, save the Flip the Script skill, create/approve the scheduled task, approve any switch to send mode |
Mailbox owner ({MONITORED_INBOX}) | Complete OAuth sign-in for the email connection; review drafts daily |
| CRM admin | Grant the clone search + create permissions, add the "Inbound Vendor Outreach" lead source value, confirm lead assignment to {LEAD_OWNER} |
| Finance / ops (optional) | Provide or share the list of vendors you pay |
| Legal / compliance (recommended) | Sign off on the opt-out line, signature and GDPR / CAN-SPAM approach |
6. Estimated setup time
| Step | Time |
|---|---|
| Pre-flight check (this doc) | 5 min |
| Clone discovery + placeholders + plan | 10 min |
| Your sign-ins and CRM lead source | 5–15 min |
| Save skill + scheduled task | 5 min |
| Test run | 10 min |
| Total | 30–45 min |
7. Pre-flight checklist
- I'm the clone admin (or have one available)
- Gmail or Outlook connection attached (or can be), with read + draft permission
- Salesforce or HubSpot operators available, and I can sign in with search + create permissions
- I can create scheduled tasks (or the clone can)
- I have my list of paid vendors and other domains for
{SKIP_LIST} - I've written
{PRODUCT_NAME},{VALUE_PROP}and{SIGNUP_URL} - I've decided whether to include a
{REFERRAL_OFFER} - I've decided
{RUN_TIMES},{DAILY_CAP}and{SUMMARY_RECIPIENTS} - I'll start in
draftmode - I have a test email address (not a real vendor or prospect) for the test run
8. You're ready when…
- ✅ Every required item in section 1 is attached and its connection is signed in.
- ✅ You have answers for all the placeholders (blank is fine for
{REFERRAL_OFFER}). - ✅ Your skip list includes every vendor you pay.
- ✅ The CRM has a lead source value for these leads.
- ✅ You're starting in draft mode.
- ✅ You've set aside ~10 minutes today for the test run.
Then download CLONE-INSTRUCTIONS.md and give it to your clone.
Was this use case helpful?
Thanks!