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.
