Every vendor cold pitch you get becomes a lead for you
Your clone spots unsolicited sales emails, adds the sender to your CRM and drafts a witty reply that shows how you do outreach better.
Twice a day your clone scans your inbox for vendor pitches, skipping your real vendors, customers and partners. Each sender becomes a CRM lead, and your clone drafts a friendly reply that critiques their email and invites them to try your product. Replies wait as drafts until you turn sending on.
What your clone does
Cold pitches fill your inbox and go straight to the trash, but every sender is a sales team that might need what you sell. Your clone turns that noise into pipeline.
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 (Salesforce Lead Operator, Salesforce Contact Operator, Salesforce Account Operator, Salesforce Activity Operator) or HubSpot (HubSpot Contact Operator, HubSpot Company Operator, HubSpot Engagement Operator). HubSpot has no separate Lead object in this stack: the clone uses a contact with lifecycle stage "Lead" and a lead source property Gmail (Google Gmail Operator) 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
Who it helps
- 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}.
How it runs
┌───────────────────────────────────────────────────────────────────┐
│ 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 |
Set it up, step by step
- 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.
- 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 (3 min)The clone reports which skills/operators and connections it already has and which are missing.
- 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).
- 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 (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).
- 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.
- 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.
- Live in draft mode for at least a weekReview 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 {DAILYCAP}.
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 | Read the last ~12 hours of mail, save reply drafts, (optionally) send replies, send the summary | Connected to {MONITORED_INBOX} |
| 2 | Salesforce: Salesforce Lead Operator, Salesforce Contact Operator, Salesforce Account Operator, Salesforce Activity Operator. HubSpot: HubSpot Contact Operator, HubSpot Company Operator, HubSpot Engagement Operator | 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.
Good to know
- 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.
Questions, answered
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 {SENDMODE} to send and confirm, and even then never more than {DAILYCAP} per day.
Will it reply to my customers or vendors?
No. Customers, partners, investors, vendors you pay, existing CRM contacts and everything on {SKIPLIST} 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 (Google Gmail Operator) 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).
Ready when you are. So is your clone.
Build your clone, paste in the Flip the Script instructions, and approve the plan it shows you.

















