An outbound sales engine and a daily sales brief
Lead sourcing, personalization, sequenced outreach, reply and unsubscribe handling, and a 9:15am brief, built as one system
a US medical billing company (project, January to June 2026) · 2026
Problem
A small sales team was prospecting by hand: finding practice owners and billing managers one at a time, writing openers, sending follow-ups from memory, and starting each morning without knowing which deals or emails mattered most.
What I built
- Lead sourcing: a workflow that pulls prospects matching the ideal-customer profile (titles, seniority, healthcare segments) from a prospecting API, enriches each with a verified email, de-duplicates against everything already contacted, and pages through results on a schedule.
- Personalization: a language model writes one natural opening line per lead from their title, company, and industry, under strict rules (one sentence, no buzzwords, no invented facts), stored with the lead.
- Outreach: a sequenced email sender that works from a shared pipeline sheet, records each send, waits between messages, and moves the lead through steps; follow-ups run on their own cadence.
- Reply and unsubscribe handling: a reply detector that stops the sequence the moment someone answers, and a one-click unsubscribe page that marks the lead and halts everything, with the time stamped in the team's time zone.
- Website capture: form submissions on the company site trigger a personal-sounding reply from the rep within minutes.
- Daily sales brief: every morning at 9:15am Eastern the rep receives one email with the top five deals needing action, the top ten emails to answer with drafted replies, and the reasoning for each, assembled from the CRM and the inbox by three parallel model passes and formatted as a clean HTML digest.
Result
Prospecting went from manual to a pipeline with a status on every lead, and the rep started each day with a prioritized list instead of an inbox. The engagement wrapped in June 2026 with the system documented and handed over.
What it shows
A complete revenue system in n8n, with the safety valves (reply detection, unsubscribe, de-duplication, sending delays) that keep outbound from damaging a domain's reputation.