Automation
Email Follow Up System
Sending the same email twice loses the customer you were chasing.
People sign up, get distracted and never come back. This writes to them on a schedule, collects their replies onto one screen, and one person can work through the lot in a morning.
This one was built for a client. The name on it is theirs to give out, not ours.
Where it runsOn a server the business rents, not on anyone's laptop. It has to stay awake to catch the replies coming back.
Who is this for?
A business sitting on a list of people who nearly became customers, with nobody free to chase them one by one.
What the numbers mean
Most of them about not sending the wrong thing to the wrong person.
The system grew ten times over without losing a contact or a conversation.
One person, one screen. No shared inbox, no spreadsheet beside it.
How it actually works
Someone starts signing up, gets pulled away, and never finishes. A week later nobody remembers them. The system does: it writes to them on a schedule, in a sequence somebody approved in advance.
The hard part of a mailing system is not sending. It is not sending twice. If the machine crashes halfway through a batch, a simpler system starts the whole batch again when it comes back up. So we made that impossible: the place the emails are recorded cannot physically hold two entries for the same email to the same person, and the second attempt fails instead of embarrassing you.
Unsubscribes are checked in the second before each email goes out, not on the day the list was built. A list put together on Monday and sent on Thursday will otherwise write to the people who asked to be left alone in between, and that is the one mistake that turns a mailing list into a complaint.
Replies come back into the same place they went out from, so one person works from a single screen instead of a shared inbox with a spreadsheet next to it.
It is deliberately small. One program, one file holding all of the data, and nothing else that has to be kept running beside it. The only outside thing it needs is something to actually deliver the mail. And it can be stopped in the middle of a send and started again, and it carries on from where it was without repeating itself.
The people who almost bought from you are the cheapest customers you will ever get, and they are exactly the ones nobody has time to call.
We build things like this. Tell us what you are stuck on.
What it is built with
- Next.js
- TypeScript
- SQLite
- Resend
- Docker