Plain-language, shareable explanations of what we built for Foundation, plus the reusable template.
In one sentence: Every morning, this automation looks at everyone who signed up for Foundation's newsletter in the last 24 hours, figures out which ones are real business opportunities, writes each a personalized intro, and lines them up in the right outreach campaign — ready for a human to review before anything sends.
Kicks off and opens a logbook entry so we have a record of every run.
Grabs everyone who joined the newsletter in the last 24 hours, along with the details they gave at signup.
Drops anyone using a personal address (Gmail, Yahoo, etc.) because we can only pursue business contacts. Example: on a recent run, 44 signups came in and 31 were personal, leaving 13 business contacts.
Bundles the remaining people by their company (using their email domain), so each business is looked at as a whole rather than one person at a time.
For every company, the system researches who they are and sorts them into one of a few buckets:
Cross-checks each contact against Foundation's existing systems so nobody who's already a lead or customer gets a duplicate cold intro.
For the real opportunities, the system writes a tailored opening line based on what the company is up to, then places the contact in the correct campaign for the right rep (e.g. David or Julia). Example intro it generated: "Caught the Qflex launch, smart move giving automotive drying that energy-flexible edge."
Records what happened, remembers where it left off so tomorrow's run doesn't repeat anyone, and sends a short recap to the team.
| Tool | What it's for |
|---|---|
| Cloudflare | The engine everything runs on, plus the memory/logbook |
| Kit | Where newsletter signups come from |
| AI (OpenRouter) | Does the sorting and writes the personalized intros |
| Instantly | Where the outreach campaigns live (currently drafts) |
| HubSpot | Foundation's CRM, used to avoid duplicates |
| Telegram | Where the daily recap is sent |
Everything runs inside Foundation's own Cloudflare account. No data leaves Foundation's systems except the tools listed above, which are already part of Foundation's stack.
In one sentence: The moment a real person browses Foundation's website, this automation identifies who they are, researches their company, checks we don't already know them, writes them a personalized intro that references what they were looking at, and lines them up in the right outreach campaign — ready for a human to review before anything sends.
Foundation's visitor-ID pixel (RB2B) spots a real, named person on any page of the site and instantly sends their details over. The automation records it and gets out of the way — no waiting.
New arrivals wait in a short queue. Every 30 minutes the automation picks up the latest batch. This keeps costs down and lets it treat someone who viewed five pages as one person, not five.
Checks its memory. Anyone who's already been added to one of our campaigns is skipped for good, so no one is ever pitched twice, even if they come back months later.
Anyone on a personal email (Gmail, Yahoo, etc.) or with no company is set aside — we only pursue business contacts.
If the pixel didn't hand over a work email (or company size/revenue), the system looks the person up to fill those in, finds the most likely email, and confirms it's a real, deliverable address.
Cross-checks each person against Foundation's existing systems so nobody who's already a lead or customer gets a duplicate cold intro.
For every visitor's company, the system researches who they are (using the company size and revenue as a read on whether they fit Foundation's budget sweet spot) and sorts them into a bucket:
For the real opportunities, the system writes a tailored opening line, and because it knows which pages they looked at (pricing, a case study, the AI-visibility service), the intro can speak to exactly what they came for. Then it routes them to the right campaign:
Records what happened, remembers who it has handled, and sends a short recap to the team.
| Tool | What it's for |
|---|---|
| RB2B | Identifies the real people browsing the website |
| Cloudflare | The engine everything runs on, plus the memory/logbook |
| Apollo | Looks up the person to fill in email, company size, and revenue |
| Hunter | Finds a work email when Apollo and the pixel don't supply one |
| Email List Verify | Confirms an email is real and deliverable |
| Instantly | Where the outreach campaigns live (currently drafts) |
| HubSpot | Foundation's CRM, used to avoid duplicates |
| AI (Claude via OpenRouter) | Sorts each company and writes the personalized intro |
| Exa + Firecrawl | Live research on each company |
| Telegram | Where the recap is sent |
Everything runs inside Foundation's own Cloudflare account. No data leaves Foundation's systems except the tools listed above, which are already part of Foundation's stack.
Subscriber Miner wakes up once a day and works a list of newsletter signups. Visitor Miner is always on — it reacts the instant someone lands on the site, and its personalization uses the pages they actually browsed as the intent signal.
In one sentence: {{ONE_SENTENCE_WHAT_IT_DOES}}
{{WHAT_HAPPENS_IN_PLAIN_WORDS}}
{{WHAT_HAPPENS}}
Add one block per meaningful step. Fold pure housekeeping (logging, saving state) into a single simple step so the list stays readable.
| Tool | What it's for |
|---|---|
| {{TOOL}} | {{PLAIN_PURPOSE}} |
Everything runs inside {{CUSTOMER}}'s own {{ACCOUNT}}. No data leaves their systems except the tools listed above, which are already part of their stack.