Outbound Sequence Copy Written Against One Trigger

The trigger comes first: A first email that names something the recipient can verify in their own systems — a granted omgevingsvergunning, a notified body change on a device file, a second location signed — gets read past line two. One that opens with a description of what you sell does not. Across the eleven Dutch programmes I have written since 2023, trigger-led first touches ran 4 to 7 percent positive reply. The offer-led sequences they replaced sat under 1 percent. Everything below is a consequence of that one difference. What arrives: Four to six messages across 18 to 24 days per segment, in Dutch or English. Message one names the trigger and asks a single question that costs nothing to answer. Message two supplies the one piece of evidence a person in that role would actually check: a number from a comparable account, a screenshot of the thing itself, a named customer in their province. Message three changes the angle rather than repeating it, usually by moving from the outcome to the internal cost of the current workaround. The last message closes the file and says so, with no invitation to reply if they are still interested. Two subject lines per message, no more. Variables that can be filled: Every merge field maps to a column your data actually contains. If a field cannot be filled for nine out of ten records in a segment, I delete the sentence rather than write a fallback that announces itself as one. Copy ships as a CSV with the variable map and fallback rules, plus a platform-native import for Instantly, Smartlead or Lemlist, so nobody rebuilds the sequence by hand and drops a condition on the way through. Dutch is written, not translated: A Dutch sequence produced from an English original identifies itself inside one sentence — word order first, then register. The u/je decision is made per segment and written down: u for makelaars, notarissen and municipal buyers, je for a 34-year-old founder in Amsterdam who will find u comic. Both language versions are written from the segment, not from each other. What I read before writing: Twenty to thirty replies from your own inbox, including the rude ones, your last two lost-deal notes, and one recorded sales call. Then the register that produces the trigger: officiële bekendmakingen and Kadaster for property, EUDAMED and the CBG register for medtech, TenderNed awards for local services. If a segment has no observable trigger, I say so before writing rather than inventing a reason for the email to exist. Not included: List building, mailbox provisioning, DNS and warm-up. Separate work, and I would rather it was right before this copy arrives. Subject-line split testing as an ongoing service: below roughly 400 sends per variant you are measuring noise, and I will not bill for reading noise. No spintax. Randomised synonyms to defeat filters was a 2019 idea, it produces sentences no senior person would write, and filters read the whole message anyway. Who should look elsewhere: Anyone sending to a purchased list. Anyone who needs twelve segments written this month: I write two at a time and read the replies before starting the third. Anyone whose copy has to be signed off by a committee in which nobody has ever answered a cold email. What you can hold me to: Reply rate and positive-reply rate on the segments I wrote, measured in your platform, reviewed at day 30. I will not promise meetings booked. That number depends on your pricing, your case studies and how fast someone on your side answers, and those are three things I do not control.