Technology in practice
Email & Resend
Connect product messages to their users
A fit for confirmations, notifications and account recovery, with branded templates and traceable sending.
Let’s discuss your situation ↗01
Choose with context
What we assess before recommending it
Configuration does not guarantee inbox placement. Reputation, recipients and providers also matter. We separate service messages from marketing, including preferences and unsubscribe handling.
This capability supports those areas according to the project. If the solution is still unclear, we start by organising needs and priorities. Explore Strategy ↗
02
What we can address
We define events and recipients and connect sending to Resend or the agreed provider.
We prepare templates and domain authentication and check how messages render.
We handle errors, bounces and retries and connect preferences to the necessary tools.
Technical detail, explained
- Transactional email
- A message linked to a product action or state.
- SPF, DKIM and DMARC
- Mechanisms for authenticating the sending domain and defining its policy.
03
What you receive
We specify these deliverables in the proposal, according to what needs building or reviewing.
- An event map and templates for agreed messages.
- Domain configuration and sending records.
- Error handling and operating and integration guidance.
The proposal identifies source code and documentation to deliver, client access and third-party licences. We agree ownership and handover before starting.
04
Getting started
We review message types, volume, domains and existing tools. Templates, languages and workflows determine effort; sending-provider costs are quoted separately.
- Share the context: what exists, who uses it and what needs to change.
- Where technical uncertainty remains, we propose a bounded review before estimating implementation.
- We agree deliverables, phases, acceptance criteria, schedule and budget before building.
Timing, investment and third-party costs
We do not publish a single figure because a review and a full build are different engagements. The estimate separates our work from hosting, licences and usage-based services, and identifies dependencies such as access, content or app store approval.
What happens after handover
We define validation, handover and any included support period. Ongoing maintenance is agreed separately, with explicit coverage, channels and response times; continuous availability is not assumed.
Let’s start with your situation.
Tell us what you want to improve and what exists today. You do not need to have chosen the technology.