Service example
Outbound Sales
Outbound That Reads Like It Was Written for One Person
An outbound pipeline where personalisation is an enrichment problem rather than a prompt problem: source, enrich, segment, generate per lead, send from your own domain, and hand off on reply.
These examples describe workflow and implementation experience. They do not imply independent product ownership or identify a client.
The challenge
Volume was not the constraint. Relevance was. A template with a merge field reads as a template no matter how it is worded, and scaling it up damages deliverability at the same time as it damages the brand.
The approach
- 01
Sourced and deduplicated leads against what was already in the CRM, so nobody gets contacted twice by two people.
- 02
Enriched each lead before writing anything, because copy with no facts behind it can only be generic.
- 03
Segmented by what the enrichment revealed, so the angle is chosen before the sentence is written.
- 04
Generated per-lead copy from that context, then sent from the team's own domain with pacing and throttling.
- 05
Wired reply detection back into the CRM so a human reply ends the sequence and creates the task.
Architecture
Outbound That Reads Like It Was Written for One Person architecture. Main flow: Source, then Enrich, then Segment, then Generate, then Send. Connected paths: CRM sync feeding Send; Reply handoff as a conditional path from Send.
What was hard
Deliverability is a systems problem, not a copy problem. Volume, pacing, domain warmth, and reply handling all affect whether good copy is ever seen.
Enrichment quality set the ceiling. Where the data was thin, no prompt produced a genuinely personal email, so the honest fix was to send fewer.
Knowing when to stop. A sequence that keeps sending after a human has replied undoes the entire point, so reply detection had to be reliable rather than best-effort.
Related
Curious how this was built?
The full experience and skill set behind it are on the resume.
View resume