Personalised cold outreach that stops itself when someone replies

The challenge

Outreach tools tend to fail in one of two ways. Some send identical templated email at volume, which gets ignored and damages the sender's reputation. Others are powerful but assume a full engineering stack, with queues, workers and paid infrastructure, before a small team can send a single campaign. A small business needs something in between: the ability to bring its own list, write messages that genuinely refer to each company, send from its own mailbox, and have the system reliably stop emailing anyone who replies, bounces or opts out. Done carelessly, sequences keep chasing people who have already answered, which is the fastest way to lose a prospect and a sender reputation.

What we built

• Lead import from CSV or a public Google Sheets link, with dynamic column mapping, duplicate skipping per campaign, email validation, and unmapped columns kept so no data is lost.
• AI personalisation that produces a company summary, pain points, an outreach angle, a subject and a body for each lead. Drafts are editable and can require approval before anything is sent.
• Sending through SMTP (including cPanel), Mailgun, and one-click Gmail and Outlook connections, with provider secrets masked in the interface and refreshed tokens stored safely.
• A cron-driven send queue that needs no paid queue service, claiming small batches, respecting campaign and per-mailbox daily limits, and skipping anyone who has replied, bounced, complained or unsubscribed.
• Conditional follow-up steps that can depend on whether the previous email was opened or a link was clicked, with skipped steps recorded for audit.
• Open and click tracking with signed redirect links, so the link tracker cannot be abused as an open redirect, and unsubscribe links that are never rewritten.
• An audit log of lifecycle events and an activity timeline per lead, so every send, reply and status change can be explained.

What it makes possible

A small team can run personalised outreach end to end from one place, without a separate scraper, writing tool, mailer and spreadsheet. The safety rules are structural rather than a matter of discipline: daily limits, an approval step, an unsubscribe footer and automatic stop-on-reply mean the system protects the sender's reputation by default. Because the queue uses plain database state rather than extra infrastructure, it runs on a modest, low-cost stack and is simple to operate and debug. The same engineering habits, such as tested state machines, signed links and masked secrets, carry across every system we build.

Related work

Delivered

Recruitment · StaffingReal-time candidate portal

Recruitment CRM

Real-time candidate portal, document tracking and automated status updates

Next.js Node.js MongoDB

Live

Travel · Australia4 lead channels in one system

Airline ticketing CRM

Every lead from WhatsApp, Facebook, phone and walk-ins in one place, with a live KPI dashboard

React TypeScript Vite