The radar produces a report. Turning that into a newsletter people can join, receive, and leave, with consent on record and one-click unsubscribe, is a second system. Everything runs itself except two human moments: you approve each issue before it sends, and you post a short version on LinkedIn after.
Published June 2026 by Balázs Turán, Creative Data Engineers.
The radar solves the content problem. Delivery is a different one: consent, deliverability, and the right to leave. A newsletter is a list, a send, and a clean way in and out, with a human deciding what goes out. That is why it is its own system, not a step in the radar.
Two rules shaped it. First, the confirmed list is the only source of truth, so consent and unsubscribe state never live in two places that can disagree. Second, a person approves every issue before it sends. The pipeline does the heavy lifting; the decision to send stays human.
Three flows: make, approve, send turns the report into an approved issue; grow the list is how readers join with double opt-in; leave is the one-click way out. The two amber boxes are the only points where a person steps in.
Hover or focus any box for a plain-language explanation. The two amber boxes are the manual points: you approve each issue, then post it on LinkedIn.
This is the system on top of the radar. The box marked "Radar report" is a whole pipeline of its own. See how the radar is built →
One list, one source of truth. Consent and unsubscribe state live on the confirmed list and nowhere else, so the send and the right to leave can never disagree.
Double opt-in is not optional. A reader confirms by email before they are added. It keeps the list clean and the consent record real, which is the part that matters under GDPR.
Two manual gates, on purpose. The pipeline drafts and renders, but a person approves the issue before it sends and posts the LinkedIn version after. Automation does the work; the decision to publish stays human.
No. Two manual gates: you approve each issue before it sends, and you post the LinkedIn version after. The drafting and rendering are automated, but the decision to publish stays human.
Subscribing uses double opt-in: a new signup confirms by email before being added. Every issue carries a one-click unsubscribe in the footer, with no personal data in the link.
On one confirmed list that is the single source of truth. The send reads only from it, so consent and unsubscribe state never disagree.
Yes. It is the same engineering we bring to client work. Book a call and we will scope it.
Consent-clean lists, branded sends, and a human gate where it counts: the same engineering we bring to client work. If you want your brand named in AI answers, the AI Search Visibility work is where we start.
We also teach operators to build systems like this, hands-on. Balázs runs the build sessions at Agent-J+.