Something big has just happened. Your reporter files within minutes, an editor pushes it live in ArcXP, the homepage updates, the app pings, social goes out. The newsroom did its job. Now somebody on the newsletter team has to send the email, and that is where twenty minutes disappear.
Open the email tool. Find the breaking news template. Copy the headline across, paste the deck, watch the typography break, fix it. Find the right image, drop it in, discover it is too wide on mobile, resize. Send a test. Wait. Open it on your phone. The link is wrong. Go back, fix it, send another test, get approval, send.
By the time the alert lands, half your audience has seen the story on social, on the homepage, on the app. The newsletter, the channel you tell investors is your most direct relationship with readers, was the slowest channel you own.
Daily editions hide this problem because they run on a schedule. An editor blocks an hour every morning, the work gets done, nobody counts the cost. Breaking news exposes it. Same workflow, compressed into minutes, with the whole audience watching to see whether you got there first.
The workarounds are worse than the problem. Hand-coded HTML through a transactional API. Static templates with placeholder slots. An internal tool maintained by the one engineer who left in 2023. Each of these trades the speed problem for a brand consistency problem, an editorial control problem, or a maintenance problem you find out about on a Saturday.
Breaking news used to mean a few times a year. Now it is weekly, sometimes daily, and the workaround that was tolerable when you sent four breaking alerts a year is unacceptable at fifty.
This is one of the workflows we built Embrin for. The editor publishes the article in ArcXP and tags it as breaking. Embrin assembles the alert from the breaking news template, pulls the headline, deck, image, and link straight from the article, runs validation against payload size and broken links, generates a live mobile and desktop preview, and queues the send through your ESP. The editor confirms the preview. It ships. Three actions, ninety seconds, no email tool, no copy-paste, no engineer paged on a Saturday. The template was set up once and now it just runs.
Time it the next time a story breaks in your newsroom. Stopwatch on when the article goes live, stopwatch off when the alert hits your inbox. Under two minutes and your stack works. Twenty minutes and you have a production layer problem.
The next story is on its way.
Embrin is a newsletter production platform that connects your CMS to your ESP. Your editorial team shapes each edition and sends it to the right audience in about 90 seconds. No custom code. No production bottleneck. No reason your next breaking alert should take longer to send than it took to write. See it with your own content →