Run
Email and deliverability
Do your automated emails actually arrive? Usually, some of them do not.
The emails that matter most are the ones nobody ever looks at: order confirmations, password resets, quote notifications. Nobody notices they have stopped arriving — the customer does, and they either call or leave. The causes are nearly always the same: incomplete domain authentication, sending from an address that does not belong to the sending domain, or a saturated sending quota with nobody watching the counter.
The method
How we work
- 01
We authenticate your domain properly
SPF, DKIM and DMARC in place and verified. Without all three, a growing share of your mail goes straight to spam — Gmail and Outlook have tightened their rules.
- 02
We separate transactional from marketing
A poorly received campaign must not damage the reputation that gets your password resets delivered. Two uses, two separate sending channels.
- 03
We watch bounces and complaints
Invalid addresses removed automatically, complaints tracked, sending quota under alert. Continuing to write to dead addresses degrades the reputation of the whole domain.
- 04
We make sent mail inspectable
A screen showing what went out, to whom, and with exactly what content. The day a customer says they received nothing, the discussion takes thirty seconds.
What you get
Deliverables
- check_circleSPF, DKIM and DMARC records set on your domain and validated
- check_circleA sending account in your name, with its quotas and alerts
- check_circleEmail templates that also read well on a phone and in plain text
- check_circleThe sent-mail viewer, showing the exact content the recipient received
The proof
Where we have done it
FlatBay
Since 2015Agencies drowning in incomplete files. An assistant that chases missing documents, computes the affordability ratio, and only passes on complete applications.
Read the case studyarrow_forward
Pilotage & support IA
Since 2025Requests arrive by email, by WhatsApp, by web form. They are qualified, attached to the right project, and a reply is drafted — a human approves before it is sent.
Read the case studyarrow_forward
Notre flotte
Since 2010Git, continuous integration, image registry, SSO, DNS, metrics, logs, monitoring: all of it runs on our own machines, on open-source components. Not out of principle — because it holds load better, costs a fraction, and does not stop when a vendor changes its mind.
Read the case studyarrow_forwardFrequently asked questions
- Why do my emails go to spam?
- In order of frequency: incomplete domain authentication, sending from a domain different to the one displayed, reputation damaged by invalid addresses, content too close to an advert. The diagnosis takes an hour; the fix, often less.
- Do you provide the sending platform?
- We configure an account in your name with a sending provider. In your name, because sender reputation is built over time and belongs to you — sharing it with other clients means inheriting their mistakes.
- What about newsletters?
- Technically yes, but we will raise consent first: a list built without explicit agreement exposes you, and it costs you anyway in complaints that degrade your transactional mail.
Also in “Run”
Infrastructure and hosting
Your servers, held by people who administer them daily for other clients too.
account_treeCI/CD and DevOps
Deploying should be a non-event, several times a week, with no meeting.
speedWeb performance
A slow site loses customers before it has introduced itself. That can be measured and fixed.
monitor_heartMonitoring and on-call
Knowing the site is down before your customer calls to tell you.
Let's talk about your project
Thirty minutes is enough to tell whether we are the right fit. We reply within 48 hours, and we say no when it is not for us.