Media, Community & Web3

Email that lands in the inbox, not the spam folder:
infrastructure, not just a template

Most email problems are not a copywriting problem, they are a deliverability problem: a missing DKIM record, a shared sending domain with marketing and transactional mail mixed together, no warm-up before a cold outreach campaign. We fix the infrastructure first, because no subject line fixes a message that never reaches the inbox.

from$1,200
Timeline1 to 3 weeks
What is includedSPF, DKIM and DMARC records configured and verifiedSeparate sending domains or subdomains for transactional vs marketing vs outreach mailWarm-up schedule for a new sending domain or IP before full volumeBounce, complaint and unsubscribe handling wired into your listDeliverability monitoring (spam placement, blacklist checks, sender reputation)
9email templates built for one client's outreach playbook, three-touch sequence with warm-up
0shared IP reputation risk between transactional and outreach mail, kept on separate domains
1-3 weeksto a verified, monitored sending setup

What it is

Email infrastructure is everything that happens between clicking send and a message landing in an inbox: DNS authentication records that prove you are who you say you are (SPF, DKIM, DMARC), the reputation of the sending domain or IP built up over time, the separation between transactional mail (receipts, password resets) and marketing or outreach mail so one does not poison the other’s reputation, and the handling of bounces, complaints and unsubscribes that mailbox providers watch to decide whether to trust you.

When you need it (and when you do not)

You need a proper setup the moment email is more than an occasional manual send: a product that sends password resets and receipts, a marketing list beyond a few hundred people, or any kind of cold outreach campaign where deliverability failures are invisible until someone checks whether messages actually arrived. A new domain sending at volume without warm-up, or a shared sending domain mixing transactional and marketing mail, are the two most common causes of mail landing in spam that we see in audits.

You do not need a custom infrastructure build if you are sending low-volume transactional mail through a provider that already handles authentication correctly out of the box and you have verified your deliverability is fine. The setup pays off once volume, sender reputation risk, or the need to separate mail types justify the engineering.

How we build it

We configure SPF, DKIM and DMARC records for your sending domain, which together prove to receiving mail servers that a message claiming to come from your domain actually does, and verify them against real test sends rather than just checking the records exist. Transactional mail (receipts, password resets, security alerts) goes through Postmark or Amazon SES, chosen for speed and deliverability track record on time-sensitive mail, on its own subdomain so its reputation stays isolated from marketing and outreach.

For outreach or cold email at volume, we set up separate sending domains with a warm-up schedule, a gradual increase in daily volume over one to three weeks that builds sender reputation before relying on the domain for real campaigns, the same approach behind the mailbox warm-up layer in a sales outreach pipeline we built for a certification body’s email campaigns. Bounce, complaint and unsubscribe handling gets wired directly into your list so a hard bounce or a spam complaint automatically suppresses future sends to that address, which mailbox providers track and reward.

We add deliverability monitoring, spam placement tests, blacklist checks, sender reputation scores, so a problem shows up in a dashboard instead of in a client’s silence.

What to watch

Deliverability is a reputation system, not a one-time configuration: a domain’s standing can degrade from a single bad campaign, a purchased list, or a sudden volume spike, and recovering a damaged sender reputation takes weeks, not a quick fix. We build in the separation and monitoring that prevents this, but ongoing sending discipline is on your team.

Vendor lock-in is minimal for infrastructure (DNS records and templates move with you) but mailing list and warm-up history do not transfer between providers, so switching providers mid-warm-up resets the clock.

Price and timeline

Option Price What it covers Timeline
Core setup from $1,200 SPF/DKIM/DMARC, domain separation, bounce handling 1 to 3 days
Full outreach infrastructure from $2,800 Warm-up schedule, multiple domains, deliverability monitoring 2 to 3 weeks

Running cost is usually $10 to $100 a month in provider fees depending on sending volume, separate from any marketing platform subscription.

Pairs with SMS and WhatsApp notification service when outreach spans more than one channel, and with the setup and integrations service for the rest of your marketing stack. See the development service page for custom transactional email builds. For a sales pipeline we built with mailbox warm-up and templated outreach, see the certification body AI sales case study, and for a content system that produces email copy as one of its output types, the content agent case study.

Not sure why your email is landing in spam? Get in touch and we will audit the actual DNS and sending setup.

FAQ

How much does email infrastructure setup cost?

From $1,200 for SPF/DKIM/DMARC configuration, domain separation and bounce handling on your existing email provider. A full outreach infrastructure with warm-up, multiple sending domains and deliverability monitoring runs $2,500 to $5,000.

How long does it take?

1 to 3 days for the core authentication records (SPF, DKIM, DMARC) once DNS access is confirmed; 1 to 3 weeks for a full setup including warm-up and monitoring, since warm-up itself is a gradual process.

Which email providers do you work with?

Postmark and SES for transactional mail, where deliverability and speed matter most; standard marketing platforms for campaigns; and dedicated outreach infrastructure (separate domains, mailbox warm-up tools) for cold outreach, which needs a different reputation profile entirely from transactional mail.

Why separate transactional and marketing sending domains?

Because they have different reputations and different risk profiles. A marketing campaign that gets flagged as spam should not be able to drag down the deliverability of a password reset email or an order receipt, and keeping them on separate (sub)domains contains the damage when one campaign goes wrong.

What is email warm-up and do we need it?

Mailbox providers trust a new sending domain or IP less than an established one, so sending full volume on day one gets flagged. Warm-up is a gradual increase in sending volume over one to three weeks that builds sender reputation before you rely on the domain for real campaigns. You need it for any new domain doing meaningful outreach or marketing volume.

Start here

Tell us the problem.
We bring the system.

A 30-minute call, a written plan with numbers within 48 hours, no obligation. If we are not the right fit, we will say so and point you to someone who is.