What this engagement includes
We connect applications to reputable ESPs/transactional providers with testable templates and observability on deliverability.
Scope can expand to SMS/push later; email is usually the first high-impact slice.
How we deliver
We tailor and sequence these workstreams around your priorities, timeline, and internal constraints.
Provider & domains
Account structure, DNS records, and environment separation.
Templates
Branded layouts, localisation hooks, and preview tooling.
Application wiring
Event triggers, idempotency, and user preference handling.
Deliverability
Seed tests, monitoring, and remediation checklists.
Our work
View our recent work below - each card links through to the live site.
We can walk through relevant case studies and references on a call - many of our clients ask for NDA-backed detail before we share specifics.
Typical flow
A reference sequence; we adapt depth and gates to your organisation.
- 01Audit
Current sending
Domains, volumes, complaint rates, and gaps.
- 02Design
Architecture
Transactional vs marketing separation if needed.
- 03Implement
Integration
SDK/API wiring, webhooks, and admin visibility.
- 04Stabilise
Tune
Throttle rules, retries, and template iterations.
| # | Stage | What happens |
|---|---|---|
| 01 | Audit Current sending | Domains, volumes, complaint rates, and gaps. |
| 02 | Design Architecture | Transactional vs marketing separation if needed. |
| 03 | Implement Integration | SDK/API wiring, webhooks, and admin visibility. |
| 04 | Stabilise Tune | Throttle rules, retries, and template iterations. |
Who we work with
Product teams launching or scaling customer comms - SaaS, marketplaces, and regulated senders with compliance review needs.
Infrastructure
SendGrid, Mailgun, Postmark, SES, Azure Communication Services - selected for region, cost, and support needs.
Deliverables
Concrete outputs, documented and handed over with the build.
- Provider selection and account setup
- Template system and test sends
- Event-driven triggers from your application
- Deliverability monitoring basics
Engagement model
Partnership patterns we document in the SOW or master agreement.
- -Quick wins for one product surface first
- -Expand to additional message types later
Commercial model
Provider choice, domain authentication, template surface, and volume affect scope; ESP fees are usually pass-through. We quote after discovery.
We start with a focused discovery (paid or unpaid, depending on complexity). You receive a written scope or SOW: milestones, acceptance tests, and a defined change process. NDAs and your procurement steps are routine.
Fixed scope
Documented requirements, milestones, and acceptance criteria. Delivery targets an agreed release or go-live.
When it applies
One product surface with transactional templates and basic deliverability checks.
Phased programme
Successive increments with checkpoints, integrations, and change control as scope evolves.
When it applies
Multiple message types, locales, or complex preference and compliance rules.
Ongoing partnership
Retained monthly capacity for maintenance, incremental features, releases, and operational support.
When it applies
Deliverability monitoring, template iteration, and provider changes over time.
Fees are quoted per engagement after discovery. Third-party cloud, licensing, and usage charges are usually billed to your accounts unless we agree otherwise.
Talk to our team