Welcome mail without an ESP rabbit hole on day one.
Template render + mock Resend/SMTP send with a delivery log. Use with Signal waitlists or Harbor receipts.
~710 words · field guide
Transactional email is critical path. Treating it like a weekend chore is how users feel ghosted.
Email procrastination
- “We’ll send mail later.”
- Copy-pasted HTML.
- No log of what you “sent.”
The shape of the solution
render() + send() with mock provider and in-memory log.
- Templates
- Mock send
- Delivery log
- Welcome route
What's in the download
- emailer.py
- app.py
- verify
- LICENSE
What Transactional Email Kit is for (and what it isn’t)
Transactional Email Kit lives in the Email lane. It’s a downloadable workshop folder — code you unzip, run in mock mode, and adapt — not a hosted product with seats, SLAs, or a customer success manager named Chad.
In plain terms: render() + send() with mock provider and in-memory log.
If you came here for a soft-focus brand story about ‘empowering data journeys,’ you’re in the wrong harbor. This is notes from people who got tired of rebuilding the same bridge on every engagement.
The Tuesday-afternoon version of the problem
These kits start on a Tuesday afternoon. Someone asks for a ‘thin wrapper’ or a ‘quick sync.’ Three weeks later you’re debugging pagination while Slack blinks like a smoke alarm.
For this one, the pain usually shows up as: (1) “We’ll send mail later.” (2) Copy-pasted HTML. (3) No log of what you “sent.”
Transactional email is critical path. Treating it like a weekend chore is how users feel ghosted.
Mock the mailbox
Prove content before DNS and DKIM join the party.
Logs > vibes
A delivery log beats “I’m sure it sent.”
How to evaluate it without vibes
Open the README. Copy .env.example. Run the verify script or mock path. You want a boring green signal that the contract works. Flashy demos that only run on the author’s laptop are how ‘kits’ earned a bad name.
Then read the modules like a colleague’s PR. If the structure looks reusable, keep going. If it feels like generated goo, close the tab — life’s short.
You’ll see pieces aimed at: Templates; Mock send; Delivery log; Welcome route.
A realistic first week (no hero montage)
Day 0: unzip, skim the license, run verify/mock. Day 1: point env vars at non-prod credentials if you have them. Day 2: hang it behind ADF, your app, or cron — depending on what this kit is — and watch one happy path.
Day 3 is when you stop treating it like a demo: logging, retries, secrets in a real secret store, and the inevitable ‘can we also support X?’ You own the code. Extend it. That’s the whole point of a workshop asset versus renting another logo.
If your process requires a design doc before a Dockerfile, paste the architecture from this page into the doc and skip inventing folklore from Slack threads.
Where the jokes stop
Humor is here so the page isn’t a funeral. It is not a substitute for signature checks, pagination, role gates, or private networks. If you smirked and skipped verify, that’s on both of us.
Checklist: secrets out of git, mock before prod, verify in CI if you can. The ZIP is the workshop. This page is the field notes.
Dark Lighthouse is a consulting alias with a product habit — reusable bridges because rewriting them from scratch was getting old.
Where it fits
Transactional Email Kit is aimed at data, platform, or SaaS engineers who recognize the pain bullets above and want a deployable starting point instead of a six-week inventing contest.
It won’t replace a fully managed sync, a white-glove marketplace app, or a promise that vendors never change APIs. Sharp tools, not frozen oceans.
Wrap-up
That’s the field notes for Transactional Email Kit. Next step is the ZIP and the verify script — not another meeting. Questions: admin@darklighthousesolutions.com.
More bridges in the same style live on the kit guides index.
FAQ
Resend/Sendgrid?
Swap provider when MOCK_MODE=false.
Templates UI?
Strings first — CMS later.
Download on Polar if you want the ZIP · All guides