week 1 isn't about sending at scale. it's about building the rails that everything else runs on.

every day has one single objective, and if you try to compress this into three days, you'll skip the pre-launch checks that separate campaigns running cleanly for 100 days from campaigns that crater somewhere around day 30.

before you start, you run the pre-launch checklist below.

PRE-LAUNCH CHECKLIST

Each of these lines must be green before day 1.

if any line is red, fix it before day 1. launching with red flags means 30 days wasted before you realise the foundation was broken from the start.

DAY 1: CONFIGURE THE SPREAD

Open your sending tool and assign your inboxes to the campaign. Set the daily send cap per inbox at 10 if the inbox is new, or 12 to 15 if the inbox has 6+ months of clean sending history behind it.

Confirm that parallel warmup is still running on every inbox. You never turn warmup off. It has to run alongside the campaign so the provider continues to see consistent behaviour.

Load a segmented list of at least 500 prospects, which gives you 5 days of send runway before you need to refill the list. Write down the single variable under test for this week, which should be the OFFER only. No subject line or CTA changes yet.

Measure at end of day: sends launched, bounces recorded, warmup scores holding steady or improving.

DAY 2: DRAFT THE BASELINE EMAIL

Use the PPQ framework: one problem, one proof point, and one question, capped at 80 words total. This email is your baseline, and every future test you run will measure against it.