Idea to Production

Email

Email that lands in the inbox, not the spam folder.

Transactional email is invisible when it works and a support crisis when it does not. Most of the difference is domain configuration nobody thinks about until delivery fails.

  • Mailgun & SendGrid live
  • SPF, DKIM, DMARC
  • Bounce handling
  • Delivery visible

← All integrations

Password resets, receipts, notifications, approvals — a surprising amount of a product's usefulness travels by email, and it only works if the mail actually arrives. That depends on sending from an authenticated domain with SPF, DKIM and DMARC configured correctly, keeping the sending reputation clean, and handling bounces and complaints instead of continuing to mail an address that no longer exists.

Off until you need it. Turning it on is a toggle — not a project, not a rebuild. See how capability arrives as you grow.

Providers

What we connect to

Available means built and running in production today. On request means we will build it for your application — it is not pre-built, and we will not imply otherwise.

Available

  • Mailgun
  • SendGrid

On request

  • Amazon SESWhere volume makes cost the deciding factor
  • PostmarkStrong transactional deliverability
  • Microsoft 365 / Gmail send-asWhere mail must come from a real mailbox

What you get

The part that is not just an API key

Authenticated sending domain

SPF, DKIM and DMARC set up on your domain, so receiving servers trust the mail and your messages are not filtered before anyone sees them.

Templates you can change

Content that can be edited without a deployment, with the branding consistent across every message the application sends.

Bounces and complaints handled

Hard bounces suppressed, complaints honoured, and repeated failures surfaced — which is what protects your sending reputation over time.

Delivery you can see

Whether a specific message was accepted, delivered, bounced or opened. When a customer says "I never got it", there is an answer.

Inbound email as a trigger

Mail sent to an address can start a workflow in the application — a reply files itself, an attachment gets processed, a request becomes a ticket.

For example

What this looks like in practice

01

Account lifecycle mail

Verification, password reset and invitation emails that arrive within seconds, because they are the messages users are actively waiting for.

02

Document delivery

Invoices and reports emailed as PDFs, with delivery confirmed and failures visible rather than assumed.

03

Release announcements

The weekly or monthly digest telling your customers what you shipped, sent automatically from the help centre through this same provider.

04

Inbound processing

Suppliers email documents to a dedicated address; an agent reads them, files them and flags only the exceptions.

Start here

Tell us what you want. In a sentence.

A 30-minute call is enough for us to tell you whether we can build it, what it will cost to run, and when it goes live.