Day 2 was the Brevo review. This is the piece that follows it: what to do after you sign up, when you put cold outbound on a dedicated IP and need it to land in the inbox, not the spam folder.
A fresh dedicated IP has zero sending history. Google and Microsoft have nothing to judge it on, so a sudden blast of thousands of emails reads as spam by default. Warming is the fix: send a little, to people who will open it, and grow the volume on a fixed schedule over 30 days.
The 30-day schedule
This is the schedule from the full guide — https://whoisalfaz.me/blog/brevo-cold-email-ip-warming-guide/ — walked through, not re-invented:
- Week 1 — 50 emails a day. Only your most engaged contacts: people who open, click, and reply. The point of week one is engagement signals, not reach.
- Week 2 — 100 emails a day. Double the volume, keep watching hard bounces. Stay under 1% — if bounces pass that line, pause and clean the list before sending more.
- Week 3 — 250 emails a day. Start adding cold prospect cohorts, a few at a time, while reply monitoring stays on.
- Week 4 — 500 to 1,000 emails a day. The IP now has a month of clean history behind it. This is the first week the volume looks like a real outbound programme.
Ramp 25% a day inside those weeks if you want it smoother, but do not skip a week. The schedule is the product: ISPs trust a predictable pattern, and a jump from 50 to 5,000 in a day is the pattern that gets an IP burned.
Before day one: the DNS
No schedule saves a sender that fails authentication. Before the first email:
-
SPF:
v=spf1 include:spf.brevo.com ~all— authorises Brevo's servers to send for your domain. -
DKIM: publish Brevo's public key under
mail._domainkey— signs every message so receivers can check it came from you. -
DMARC: start at
p=nonewith a reporting address, then move top=rejectonce the records pass. Verify all three inside Brevo until every check is green.
Use a sending subdomain — mail.yourcompany.com, not the bare domain — so a deliverability problem on outbound never touches your main domain's mail.
The numbers that decide it
Three thresholds, checked every day during the 30 days:
- Hard bounce rate under 0.5%. Over 1%, stop sending and clean the list. Bounces are the fastest way to burn a new IP.
- Spam complaints under 0.05%. Anything higher tells Gmail and Outlook your mail is unwanted, and they will act on it.
- Open rate above 30%. That is why week one goes only to engaged contacts — opens are the reputation signal the ISPs can see.
Check the IP against blacklists with Google Postmaster Tools and MXToolbox while you go. A listing caught on day 10 is a fix; the same listing found on day 30 is a rebuild.
Automate the throttle in n8n
Hand-counting daily volume is how a warm-up slips. The guide wires it into n8n: a Code node counts today's sends against the daily cap stored in workflow static data, and before the Brevo SMTP node fires it checks the count. Hit the cap and the rest of the prospects wait in a queue table until the next day's run.
Same idea for bounces: Brevo webhooks for hard bounces and spam complaints feed an n8n listener that marks the contact unmailable and adds the domain to a suppression table at once. A bounced address that keeps getting mailed is a reputation leak you can close in one workflow.
The Cron node that used to drive that daily reset is gone in n8n 3.0 — it becomes a Schedule Trigger. The 3.0 guide has the replacement list: https://whoisalfaz.me/blog/how-to-upgrade-to-n8n-3-without-breaking-workflows/
What worked
The ramp is boring, and that is why it works. 50 a day feels slow in week one. It is the week that buys the inbox placement in week four.
Engaged-first sending is the whole trick. The first emails are not prospecting — they are reputation. Send them to people who will open.
The n8n throttle removes the human error. A cap enforced in code cannot be talked into "just one more batch".
What broke — or rather, what is hard
A dedicated IP costs about $251 a year (about $20.90 a month) on Brevo. Shared IPs are free, and for transactional mail they are fine. You pay for the dedicated IP when cold outbound is the job, because then your reputation is yours alone — good and bad.
Brevo's shared tiers are opt-in only. Cold outbound on a shared IP is not the deal. Dedicated IP via SMTP is where this schedule applies, with strict list hygiene and bounce rates under 1.5%.
The guide's own checklist prints faster numbers than its schedule. One checklist line says day 7 at 500 and day 14 at 2,000. The schedule in the body of the guide — 50, 100, 250, 500–1,000 across four weeks — is the one to follow. When a source disagrees with itself, follow the slower ramp.
Who it is for
This fits if you run cold outbound for an agency or a SaaS and you own the sending reputation — dedicated IP, your domain, your list. It does not fit if you only send transactional mail or a newsletter to opted-in subscribers: shared IP, no warm-up, no 30-day schedule.
The deal, plainly
Brevo through my link: https://whoisalfaz.me/go/brevo — €100 per paid signup, €5 per free signup, through PartnerStack. The full 30-day schedule, the DNS matrix, and the n8n throttling code are in the guide: https://whoisalfaz.me/blog/brevo-cold-email-ip-warming-guide/
Warm the IP before you need the volume. By the time the pipeline depends on it, the reputation should already be there.
Alfaz Mahmud Rizve — GTM & RevOps Architect. I build autonomous revenue systems for scaling agencies and SaaS: SEO & organic growth, high-speed Next.js apps, and self-healing n8n workflows. whoisalfaz.me
Top comments (0)