Service exampleAutomationProduction
MarqReach
Writes a genuinely different cold email for every lead, sends it from your own inbox, and tracks opens and replies.
The problem
Generic outbound gets ignored, and blasting it from a shared sending service burns your domain reputation along the way.
What I built
Enriched each prospect first, then wrote per-lead copy from that context instead of filling a template. Sending goes out over the user's own SMTP, so reputation stays with their domain.
The outcome
Personalised outreach at volume without handing the sending domain to a third party.
How it works
- 01
A lead list is enriched before anything is written, because personalisation with no facts to personalise on is a merge field.
- 02
Copy is written per lead from that enrichment, then sent over the user's own SMTP credentials.
- 03
Sending is paced and throttled rather than blasted, which is what keeps a domain deliverable.
- 04
Opens and replies come back into the same view, and a reply stops the sequence.
The AI layer
Per-lead generation conditioned on enrichment output. The quality ceiling is set by the enrichment, not by the model: a better prompt over no facts still produces a generic email.
The engineering layer
SMTP integration per user, send scheduling and rate limiting, open and reply tracking, and sequence state that knows to stop when a human replies.
Key technical decisions
The user's own SMTP, not a shared pool.
Shared sending infrastructure means someone else's spam complaints affect your delivery. Sending from the customer's own domain keeps the reputation and the consequences in the same place.
Enrich first, write second.
Personalisation is a data problem wearing a copywriting costume. The order matters more than the prompt.