Service
Resend Development
We send transactional email through Resend, with authenticated domains, typed templates, idempotent sending and delivery events written back to the record.
Usage
What we build with Resend
- Transactional email for quotes, bookings, receipts and notifications
- Domain authentication with SPF, DKIM and DMARC alignment
- Typed email templates rendered from application data
- Delivery, bounce and complaint handling wired to the customer record
- Suppression lists and preference handling
- Inbound routing where replies must reach a system rather than a mailbox
Rationale
Why we choose it
Transactional email is not marketing email
A booking confirmation has to arrive in seconds and land in the inbox. Sending it from a marketing platform is how it ends up delayed or filtered.
The API is small
Less integration surface means fewer places for a send to fail in a way nobody notices.
Templates as components
Rendering email from the same component model as the application keeps content and data in step.
Practice
Architecture patterns we use
Authenticate the domain first
SPF, DKIM and a DMARC policy are set before any volume. Deliverability problems are far cheaper to prevent than to recover from.
Idempotent sends
Each send carries a key derived from the record and the message type, so a retry after a timeout does not deliver twice.
Delivery events on the record
Delivered, bounced and complained events are written back against the customer, so a hard bounce suppresses future sends automatically.
Separate sending identities
Transactional and marketing mail use separate subdomains, so a marketing reputation problem cannot stop a receipt arriving.
Related work
Case studies to explore
These projects share relevant engineering concerns. Each study identifies its documented technology choices.
- B2B Lead Intake & CRM AutomationA completed integration for an anonymous B2B services client: website lead funnel, quote forms, CRM API ingestion, pipeline and AI automations, Resend email, and n8n orchestration.
- Apparel Ecommerce & Fulfillment PlatformApparel commerce connecting catalog administration, Stripe Checkout, payment-driven orders and Printful fulfillment on Railway.
- Contractor Website & Service Request SystemA nine-page HVAC contractor website connecting service information, membership options and a customer service-request flow.
Writing
Articles about Resend
- 13 September 2026 · 4 min readAutomations that stop when the customer repliesThe most damaging automation failure is not a missed send. It is a sequence that keeps chasing someone who already answered.
- 26 September 2026 · 4 min readService request forms that give dispatch useful informationAsk for enough context to route a home-service request without turning the first contact into a diagnostic questionnaire or a false booking confirmation.
Build with our Resend engineers
Tell us what you are building and what it has to connect to. We will come back with an approach, a scope and what it would take.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.