fonio.ai16 NOV 2026 · INTERNAL

Outbound handoff

What Stefan left behind

Two outbound engines are still running, and nobody owns them. This page says what exists, what runs today, what it produced, what it costs and what we can switch off.

Written by Filippo Greco for the Outbound Strategy meeting. Sources: Stefan's handoff note of 12 Nov, the two GitHub repositories (all docs and commit history), and Slack. The tools themselves were not opened: see “Not checked” at the end. Every number carries its date.

01 · The short version

Five things to know

1

Two engines, not one

A cold email engine (Instantly) and a call-list engine that feeds HubSpot. They share only the lead database.

2

Both still run

9 Instantly campaigns were sending on 12 Nov. The call-list server posts an alert every 16 minutes today.

3

Four things live on one laptop

About 70 keys, the database backup, the dashboard password and 25 scheduled jobs exist only on Stefan's Mac.

4

Last measured: 7% of cost

On 21 Sep, new strict MRR was about €1,100 a month against €16,000 of tools and salary. No newer figure exists.

5

One real decision

Does fonio keep mass cold email in DACH? Replies need an owner by 21 Nov. Domain renewals start on 18 Dec.

02 · What exists

Two engines

The handoff note describes mostly the first one. The second one is newer, runs on a server and writes into HubSpot.

Engine A

Cold email engine

Built by Emanuel (external) and taken over by Stefan. Repository outbound-campaign, 200 commits. It builds lead lists from a company database, verifies addresses and sends two-step email campaigns.

Lead database→Enrichment→Instantly→Reply→HubSpot
  • Sending: Instantly, with Zapmail mailboxes on about 1,400 domains. Lemlist for small signal campaigns. HeyReach for LinkedIn.
  • Data: one Supabase database with contacts, send history, mailboxes, attribution and 4.3 million companies from NorthData.
  • Jobs: 25 scheduled jobs on Stefan's Mac, plus cloud jobs in trigger.dev and two blocklist flows in fonio's n8n.
  • Reporting: a results dashboard and a weekly scorecard to #gtm-ext.
  • Markets emailed: DE, AT, UK, US, FR, ES, NL, and PL through Lemlist. No Italian campaign.

Engine B

Call-list engine (“Sales Academy”)

A copy of the Italian enrichment engine, taken on 28 Oct. Stefan added 130 commits in two weeks. Repository fonio-enrichment-engine. It finds companies, picks the person and delivers a contact an SDR can call.

Company source→Identity check→Person and phone→Clay→HubSpot
  • New work: German and Austrian companies proven by register number, UK through Companies House, a phone lookup, and job ads as a company source.
  • Runs on: a Hetzner server with 13 timers and its own Supabase database.
  • Output: four Clay tables. Clay writes contacts and companies into HubSpot with the campaign “Sales Academy”.
  • Same server: a job that takes each positive Instantly reply, finds a phone number and sends it to HubSpot through Clay.
  • Markets: DE, AT and UK.

03 · What runs today

Running, with no owner

Stefan's last day of commits was 12 Nov. Nothing was pushed to either repository after that.

WhatWhereStateIf nobody acts
9 Instantly campaignsInstantlySending on 12 Nov
The German webinar wave has 16,784 leads and ends about 20 to 21 Nov. Taxi and signal campaigns end by 20 Nov.
Replies arrive in the Instantly inbox and nobody reads them. Positive replies are lost.
Call-list engineHetzner serverAlerting on 16 Nov
One alert every 16 minutes in #gtm-enrichment-engine: Apify rejects 8 of 9 calls.
Daily runs keep trying, with spend caps of $20, $12, $8 and $20 a day. At 22:30 UTC it pushes leads to Clay and on to HubSpot.
Phone numbers for positive repliesSame server, every 10 minutesNot checkedIt keeps creating and updating HubSpot contacts through Clay, with nobody watching.
25 scheduled jobsStefan's MacUnknown if the Mac is onMac on: a Sunday job deletes finished leads, and a weekday job uploads Spanish leads. Mac off: sync, dashboard and backup stop.
Cloud enrichmenttrigger.devNot checked
One schedule runs every 5 minutes, two run daily.
It bills by usage, €45 to €233 a month so far.
Blocklist flowsfonio's n8nKeep
They put customers and people who complained on the Instantly blocklist.
If they stop while email still sends, customers receive cold email.
Weekly scorecardStefan's Mac, Fridays 18:05Silent
The last message in #gtm-ext is from 6 Nov.
Nobody sees the weekly numbers.

04 · Single points of failure

What exists in one place only

The first step is to keep Stefan's Mac as it is until these are copied.

Only on Stefan's Mac

  • The key file with about 70 keys, including the two domain registrar logins and the backup password.
  • The database backup itself.
  • The password of the results dashboard. The published dashboard is encrypted today, so without it nobody can open it.
  • State files the jobs need, and the 25 job definitions.
  • A folder with legal correspondence, which is not in the repository.
  • Possibly newer engine code: GitHub has the state of 11 and 12 Nov.

Accounts fonio does not own yet

  • One Pliant card in the team “Emanuel Extern” pays almost every tool. If it is blocked, every renewal fails.
  • The link between Zapmail and Instantly ran on Emanuel's login.
  • Dashboard hosting and a second dashboard project sit in personal accounts.
  • The call-list server uses Apify, Parallel, OpenRouter and treg keys from Stefan's accounts, and a Clay session that expires.
  • Owner and admin rights to check: Instantly, Zapmail, Lemlist, HeyReach, trigger.dev, Clay, both Supabase projects, the Hetzner server.

When Stefan's fonio account is closed, everything tied to it stops. The Apify failures of today may be the first sign. This is not verified.

05 · What it produced

Results, in Stefan's own numbers

All figures come from his documents on the dates shown. “Strict” means a demo or a deal counts only when the contact replied or was called by the phone agent.

209deals attributed to outbound, €31,451 MRR (19 Aug). Strict counting keeps about 22% of that MRR (21 Sep).
500positive replies from 126,758 people contacted in the 30 days to 18 Sep.
47.7%of all 23,358 replies are automatic, such as out-of-office (15 Oct).
7%of monthly cost covered by new strict MRR (21 Sep). Target was 100% by 15 Nov.

Worked

  • DACH email: 238 positive replies from 46,481 contacts (30 days to 18 Sep).
  • Callback offers: 42% of all positive replies came from campaigns that offer a call back.
  • Phone agent: 69 demos and 37 won deals, €6,852 MRR, since Dec 2025 (29 Oct).

Did not work

  • US, UK, FR, NL email: 8 positive replies from 23,031 contacts (same 30 days).
  • Fax to pharmacies: 18,993 contacts, 3 deals, none under strict counting.
  • Retargeting: no deal from 114,981 contacts (22 Sep).
  • Hotels: two waves, no deal. Postcards: two deals, €84 and €99.
  • US webinar wave: 0.3% replies on 27,000 sends, stopped on 9 Nov.

Call-list engine

  • Stock on 3 Nov: 941 contacts in 828 DACH companies, 97% with a phone number.
  • Not called: 634 of 640 engine contacts in HubSpot had no call date and were in no call list (3 Nov).
  • UK, 11 Nov: two runs of 100 companies for $2.62 and $3.26.
  • Mobile numbers: 36 found for 513 people (2 Nov).

No results were found for the Lemlist signal campaigns, the German webinar waves 8 and 9, or anything after 29 Oct.

06 · Money

What it costs each month

Running cost

Tools (21 Sep)
about €8,000
Target Stefan set
€2,500

The largest line is the Zapmail mailboxes. Instantly (about €600) and Clay (about €800) are estimates, because they are not paid by card.

Mailboxes in Instantly on 20 Oct

All accounts
5,260
Alive
900
Deleted at the provider
823

Dates that cost money

  • 18 Dec 2026: about 400 domains renew at Namecheap. Last time: €2,702.
  • 12 Jan 2027: about 1,000 domains renew at Dynadot. Last time: €10,964. Auto-renew already failed three times on the card.
  • Every month, on spread dates: the Zapmail subscriptions.
  • 1st of each month: trigger.dev, by usage.

A proposal of 12 Oct to stop auto-renew on 1,379 domains, worth about €15,200 a year, was not carried out. The documents give four different domain counts, from 1,202 to 2,046.

07 · Proposal

Switch off, keep, decide

This is Filippo's proposal from the documents. The decision belongs to the meeting.

Switch off now

  • Fax and postcards. No strict deal.
  • Lemlist. Nine small campaigns, four to seven weeks old. Export the replies, then pause. Do not delete leads: in Lemlist a delete unsubscribes the person for the whole team.
  • The Sunday cleanup job. It deletes data and nobody checks it.
  • The weekday Spanish upload. The campaign bounced 20.4%, and it overlaps the Spanish call lists.
  • Three campaigns that are finished in practice: Ecommerce Sports, US Insurance, ski rental. Stefan advised the same.
  • The UK webinar campaign. Stefan flagged it as slow, on a shrunken mailbox fleet.
  • Old finder subscriptions the email engine used, after a look at the card: LeadMagic, BounceBan, QuickEnrich.

Keep, whatever is decided

  • The lead database. Its send history says who must not be contacted again. It also holds the attribution.
  • The Instantly blocklist and the two n8n flows. They hold the opt-outs and protect customers.
  • Keys, state files and the backup from the Mac.
  • Stefan's 130 commits. The DACH and UK work is reusable and already on GitHub.
  • The running German campaigns until they end, with one person reading replies.

Decide

1. Mass cold email in DACH

If yes: name an owner, keep the 900 live mailboxes and their domains, cancel the rest.
If no: export history and blocklist, cancel Zapmail, let the domains expire on 18 Dec and 12 Jan.

2. The call-list engine

If SDRs call these leads: one owner and one codebase with the Italian engine.
If not: stop the server timers. On 3 Nov almost none of its contacts had a call date.

08 · First week

Six steps, in order

  1. Keep the Mac untouched

    No reset before the key file, state files, backup and legal folder are copied to a fonio place.

  2. Name who reads Instantly replies

    Until about 21 Nov, about 15 minutes a day. Positive replies go to an SDR.

  3. Stop the jobs that change data

    The Sunday cleanup and the weekday Spanish upload.

  4. Move ownership and billing to fonio

    Admin rights on every tool in section 04, and every active provider from the Pliant card to a fonio card.

  5. Look at the server

    Why Apify rejects the calls, what the server spent since 12 Nov, and whether SDRs call the leads it puts in HubSpot.

  6. Decide on mailboxes and domains

    Before 18 Dec, the first renewal date.

09 · Italy and Spain

How this meets the Italian engine

Italy is separate

The Italian engine has its own code, server, CRM hub and sender (SmartLead). Email and calls are live since 9 Nov. First week: 1,496 people reached, 1.1% human replies, 1.6% bounces (14 Nov). Stefan's engine never emailed Italy.

Spain overlaps

Stefan's engine ran Spanish campaigns and a weekday Spanish upload. The Italian hub holds 2,081 Spanish call-list rows. The two sides need one shared list of who was already contacted.

Three copies of one engine

The live Italian engine, its snapshot of 23 Oct, and Stefan's DACH and UK copy. Proposal: merge them into one codebase with one adapter per market. The Italian code is not on fonio's GitHub yet.

10 · Not checked

What this page does not know

Not opened, no access

Instantly, Lemlist, HeyReach, trigger.dev, Clay, both Supabase databases, the Hetzner server, Stefan's Mac and the Pliant card. Campaign states are Stefan's of 12 Nov, not today's.

Where the documents disagree

The domain count. Whether the monthly job for job ads runs. One document says the dashboard is open without a password: checked on 16 Nov, it is encrypted. Whether the Mac holds engine code newer than GitHub.