PRODUCT BUILD — CASE STUDY

We stopped renting sending tools. So we built one in a day.

OutlookSender, our own tool

Same dayfrom build to a live login page over HTTPS, without disturbing the validator on the same server
25sends per account per day, the hard default
45 secspacing between sends
09:00 to 17:00sending window, Monday to Friday
30 to 40accounts the platform was built for at launch
~200account scale it was designed to grow toward
4Microsoft Graph permissions on the app registration

How it worked

STEP 1

Campaign creator with account rotation and hard caps

STEP 2

Unified inbox for every reply

STEP 3

Strict defaults, 25 a day, 45 second spacing, weekday window

STEP 4

Tracking and warmup controls

OUTCOME

Same day from build to a live login page over HTTPS, without disturbing the validator on the same server

Meet the build

OutlookSender is our own sending platform, built for a gap the big tools do not serve well: campaigns from personal Outlook accounts, rotated carefully, with hard limits that cannot be overridden by enthusiasm.

The challenge

Every rented sending tool rents you its limits and its shape. We needed the opposite: a small, strict engine that treats account safety as the product. Twenty-five sends per account per day, real spacing between sends, a weekday sending window, rotation across accounts, and one inbox for every reply. Building it had to happen without touching the email validator already running on the same server.

The solution

Ship the strict defaults first

The platform shipped with the safety settings as the defaults, not as options: 25 sends per account per day, 45 seconds between sends, sending only between 09:00 and 17:00, Monday to Friday. A campaign creator, account rotation with hard caps, a unified inbox, tracking and warmup controls completed the first version, designed for estates of 30 to 40 accounts and built to grow toward 200.

Deploy beside, never over

The build finished on September 29, 2026, packaged as a one-command installer, and went onto the existing VPS as its own service on its own port, beside the validator rather than over it. The live check the same day returned the login page over HTTPS with a 200, timezone and defaults verified to persist, and the validator on the box untouched and still running.

Unlock accounts with our own tenant

Connecting Outlook accounts needs a Microsoft app registration. The free developer route was rejected, so the registration was completed on our own Microsoft tenant, with exactly 4 delegated Graph permissions: User.Read, Mail.Send, Mail.ReadWrite and offline access. That registration unlocked the accounts page.

The results

Built and live on September 29, 2026: the login page serving over HTTPS the same day the build finished.

The honest bottleneck came next, stated as it stood: at the point the platform was unlocked, 0 accounts were connected and 0 emails had been sent, and Microsoft then rejected several account passwords in the first connection run, so those accounts wait on fresh credentials. Sending platforms are easy to build compared to account supply, which is exactly why the infrastructure around accounts matters more than the software.

The return: at its design point of 40 accounts at 25 sends each, the platform carries 1,000 sends a day on infrastructure we own, for the cost of a day of building, instead of a per-seat subscription whose price scales with our volume.

FAQ

Why build a sending tool instead of renting one?

Control over limits. Rented tools optimise for their average customer; we needed hard caps shaped for personal accounts, and defaults that protect senders even when a campaign is tempting to push.

What limits ship by default?

25 sends per account per day, 45 seconds between sends, and a 09:00 to 17:00 weekday window. Designed for estates of 30 to 40 accounts, growing toward 200.

What accounts does it support?

Personal Outlook accounts, connected through a Microsoft app registration on a tenant we control, using 4 Graph permissions and nothing more.

By the numbers

sends per account per day, the hard default25
spacing between sends45 sec
sending window, Monday to Friday09:00 to 17:00
accounts the platform was built for at launch30 to 40
account scale it was designed to grow toward~200
Microsoft Graph permissions on the app registration4

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

THE ROI
1,000/day

sends of owned capacity at the 40 account design point, with no per-seat tool rent on top

One day of building bought up to 1,000 sends a day of owned sending capacity.

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