All projects

Service exampleAutomationProduction

MarqReach

Writes a different cold email for every lead, verifies the address first, sends from your own inbox, and follows up until someone replies.

Visit live site
MarqReach interface screenshot

Result

Write, verify, send, and follow up

The problem

Generic outbound gets ignored, and blasting it from a shared sending service burns your domain reputation along the way.

What I built

Each lead's name, company, and role go into the generation step, so every email is written for that person rather than filled into a template. Addresses are verified before anything sends, mail goes out over the user's own Gmail, Outlook, or SMTP account, and follow-ups run until a reply arrives.

The outcome

Personalised outreach at volume without handing the sending domain to a third party.

How it works

  1. 01

    A lead list is uploaded and every address is verified first, so bad addresses never touch the sending reputation.

  2. 02

    A model writes each email from that lead's name, company, and role, so no two read like the same template.

  3. 03

    Mail goes out from the user's own connected inbox, paced rather than blasted, which is what keeps a domain deliverable.

  4. 04

    With no reply after a few days a follow-up goes out. IMAP watches the inbox, and a reply stops the sequence.

The AI layer

Per-lead generation with Claude and GPT-4 models, conditioned on what is known about each lead. The quality ceiling is set by that context, not by the model: a better prompt over no facts still produces a generic email.

The engineering layer

Inbox connection per user over Gmail, Outlook, or SMTP, address verification before send, scheduling and rate limiting, open tracking, IMAP reply detection, 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.

Verify before send.

One bounced address damages the domain for every email after it. Checking each address before it goes out is cheaper than repairing a sender reputation.

Built with

Next.jsClaudeOpenAISMTPIMAP

Related