INFRASTRUCTURE — CASE STUDY

A full sending tenant, live in a day, at $0 per inbox

Our own inbox infrastructure

1 dayfrom accounts created to full DNS verified live, warmup started the next morning
9inboxes built, 3 per domain across 3 domains
1spare license reused serially to provision all 9
25mailboxes in the tenant when the build finished
1 to 5 minprovisioning time per mailbox
100%DMARC enforcement, quarantine at pct=100 from day one
Oct 15connected to the sending tool, warmup started

How it worked

STEP 1

3 domains added and ownership verified in one day

STEP 2

9 shared mailboxes, 3 per domain, no per-inbox license cost

STEP 3

MX at priority 0 and autodiscover on every domain

STEP 4

SPF ending in -all, the hard fail

OUTCOME

1 day from accounts created to full DNS verified live, warmup started the next morning

Meet the build

Our own sending tenant, bought on September 4, 2026, to run cold outreach inboxes we control end to end, instead of renting inboxes from resellers whose tenants we cannot see inside.

The challenge

Most teams either buy reseller inboxes and never see the tenant, or set up a tenant quickly and leave the DNS at the weakest settings: SPF soft, DMARC at p=none, DKIM half-configured. Those settings pass a casual glance and quietly cap deliverability for months, and nobody notices until campaigns underperform and the domain's reputation is already spent.

The solution

Shared mailboxes, one spare license

Nine inboxes were built as unlicensed shared mailboxes across 3 domains, 3 per domain, with roles and profile photos set properly, so the estate carries no per-inbox license cost. The provisioning trick is worth writing down: the tenant holds 2 Business Basic licenses. One runs the admin user. The second was assigned to provision a mailbox, pulled back, and reused for the next one, nine times over, at 1 to 5 minutes per mailbox, and it sits spare in the pool today. When the build finished, the tenant held 25 mailboxes in total, 24 shared and 1 user mailbox, across 9 domains.

The strict version of the DNS spec, on every domain

MX at priority 0. SPF ending in -all, the hard fail, not the soft one. DMARC at p=quarantine with pct=100 from day one, not the usual p=none placeholder. Autodiscover in place. Both DKIM CNAMEs published per domain, with DKIM signing enabled and showing Valid in Microsoft Defender for all 3 domains.

Verified on public DNS, not on hope

Every record was checked live through public DNS lookups the same day, and only then were the inboxes connected to the sending tool over OAuth.

The results

The tenant was bought on September 4, 2026. Three domains were added and ownership-verified, accounts were created on October 14, and the full DNS set was verified live the same day. All 9 inboxes were connected to the sending tool and warmup started on October 15.

The detail that matters most: DMARC enforcement at quarantine from day one. Almost every inbox setup we audit starts at p=none and stays there. This estate never had a p=none day.

The return: nine sending inboxes with no per-inbox license cost at all, running on infrastructure we own outright. The reseller version of this same estate rents by the month, forever, as the teardown study on this page shows. This one was a one-time build with a one-time cost.

FAQ

Shared mailboxes or licensed users?

For sending infrastructure, unlicensed shared mailboxes do the job and remove the per-inbox license cost entirely. We proved they connect and send from real sending tools in the teardown study on this page.

Why DMARC at quarantine from day one?

p=none only watches; it stops nothing. Quarantine tells receivers to treat spoofed mail as suspicious from the start. Setting it at build time, before any sending, means the domain never spends a day unprotected.

How many domains should one tenant hold?

Our working structure is about twelve domains with three inboxes each per tenant, scaling by adding tenants rather than stuffing more domains into one. It keeps any single tenant's blast radius small.

By the numbers

inboxes built, 3 per domain across 3 domains9
spare license reused serially to provision all 91
mailboxes in the tenant when the build finished25
provisioning time per mailbox1 to 5 min
DMARC enforcement, quarantine at pct=100 from day one100%
connected to the sending tool, warmup startedOct 15

Bars are scaled so very small and very large numbers fit on one chart. The values printed are exact.

THE ROI
$0

per-inbox license cost across all 9 inboxes, on a tenant we own outright

Nine sending inboxes at $0 per-inbox license cost, built in a day, on infrastructure we own.

What was built

The concrete pieces this engagement shipped, in one list.

Your mail is being sent unauthenticated. Here is the full fix.

Lower stack cost. Back in the inbox. Built to send at any scale.

We rebuild it properly: secondary domains, inboxes, SPF, DKIM and DMARC set to enforcement, warmup and safe sending limits, blacklist monitoring on top. Send-ready in about 17 days. No campaigns, no copy, no lead lists. Infrastructure only.

Almost a decade building cold outreach infrastructure, including his own sending and verification stack built from scratch. 20+ B2B clients at companies worth $10M and above, all in tier one countries.

Free · Written plan + fixed price · No sales call required

More case studies

Lead dataA US M&A advisory firm (name withheld)
46,000

prospects matched on LinkedIn, 93% of the final list

151,218 rows in. 49,373 decision-makers out.

READ CASE STUDY →

ROIValid decision-maker leads at $0.067 each in the pilot, then all 49,373 scored for $1.54 total.

InfrastructureA US advisory firm's cold email program (name withheld)
100%

sender health at the end of the wave, with 1 hard bounce in the final campaign

30 inboxes. 1,596 sends. Zero burned.

READ CASE STUDY →

ROIZero inboxes burned: 1,596 sends delivered and the pool ended at 100% health, ready for the next wave.

OutreachPartner outreach for a US advisory firm (name withheld)
Step 2

the follow-up, not the first touch, produced the first interested partner reply

The first yes did not come from the first email

READ CASE STUDY →

ROI958 sends across the wave produced an interested partner and a $1,000 logged opportunity.

Copied
Free tools Get an inbox plan