Pre-warmed vs fresh: which path fits your client launch
Fresh infrastructure is the default for good reasons. Pre-warmed exists for the weeks you don't have.
Fresh infrastructure is the default for good reasons. Pre-warmed exists for the weeks you don't have.
Every outbound launch faces the same scheduling fact: fresh infrastructure needs preparation and a controlled ramp before it carries meaningful campaign volume. Usually that is fine because the ramp is part of the plan. Sometimes the client has signed, the campaign has a date, and the calendar does not leave enough runway.
Fresh infrastructure is the clean-slate path: new domains, no history, prepared under your program's own operating plan. It is the right default when timelines allow because the domain's history begins with your deployment.
The cost is time. Preparation is not a formality. Mailrun recommends at least two weeks before controlled campaign sending, followed by a staged increase rather than an immediate move to full volume.
Pre-warmed domains are prepared in advance on Mailrun infrastructure before they are assigned to a customer. Because the domains are prepared in advance, controlled sending can begin on day one, although full campaign volume still ramps.
The warm-up work was completed before the inventory was offered.
Two things to understand about the model:
Timeline is the honest deciding factor. With enough runway, choose fresh infrastructure and let preparation run its course. With a committed date inside that window, pre-warmed inventory provides a controlled fast lane. Plenty of agencies use both: fresh as the standing program and pre-warmed for time-sensitive onboarding.
The choice depends primarily on timing. Fresh domains build history under your own program. Pre-warmed inventory provides access to preparation completed before purchase, which can shorten the path to controlled sending.
Size domains and density to your sending target and see the capacity that holds.
Build My Sending Plan