Newsletter Engine is live: the system from my last post, now a product

Two weeks ago I published a long post about Newsletter Engine: the system I built to turn my blog archive into a weekly newsletter in 10 minutes. The post described the architecture in enough detail that a technical reader could rebuild the whole thing from scratch.

I am now selling the packaged version. Same system, installed in about 30 minutes instead of rebuilt from scratch.

This is the launch post. It is shorter than the pillar piece for a reason: if you want the architecture, read that one. If you want to skip the architecture and install the system, this post is for you.

What changed since the pillar post

The pillar post described a working production system. Mine. The one I write my own newsletter on. What it did not describe was how to install it on someone else’s account in under an hour. That is the gap I have spent the last two weeks closing.

The full stack now ships as a single purchase. You duplicate one Notion workspace, import one Make.com blueprint, paste one Anthropic API key, swap four placeholder strings with your own Notion IDs, and you have a working pipeline. The Voice DNA framework comes pre-filled with my voice profile as a starting reference, then you customize from there using the 12-question questionnaire baked into the template.

30 minutes start to finish, per my own re-install test. I timed it.

What you actually get

• The Make.com scenario blueprint. 8 modules. One import. Two Claude passes (generate, edit). The em-dash strip enforcement is baked into the pipeline, which solves the most common “this sounds like AI” tell that survives most other newsletter systems.
• The Notion workspace template. Three databases (Sources, Inputs, Drafts), a Voice DNA System Prompt sub-page, and the in-product Setup Guide. Duplicates with one click. Pre-populated with 3 sample sources and a demo issue + draft so your first run produces a real newsletter before you have configured anything.
• The Voice DNA system. This is the actual product. The pipeline is plumbing. Voice DNA is what makes the drafts sound like you instead of like ChatGPT. 12 questions, a structured template, and a worked example using my own voice profile so you can see what “specific” looks like before answering for yourself.
• The Setup Guide. 8 sections with screenshots, 3 toggles for the deeper walkthroughs, and a troubleshooting section covering the top 5 issues. Public preview at optimyzehq.com/newsletter-engine-setup-guide if you want to read it before buying.

The Founding offer

First 50 buyers get Newsletter Engine at $67. After that, the Founding link closes and the price moves to the regular $97. Both prices buy the same product. No feature difference. Founding buyers get a 14-day check-in email asking what worked, what broke, and what they wish was different, and that feedback shapes v1.1.

It is a one-time purchase. There is no subscription to OptimyzeHQ. The only ongoing cost after install is your own Anthropic API usage, which runs about 5 to 6 cents per newsletter (about $3 of API credits per year for a weekly cadence). You also use your own Make.com account, which is free at the volume most weekly newsletters operate at.

30-day refund. One-time purchase. No subscription.

Why this is separate from Creator Content Engine

OptimyzeHQ already ships a different workflow product called Creator Content Engine. CCE takes one piece of long-form content (a blog post, a podcast episode, a course module) and produces five social platform drafts: LinkedIn, X, Threads, Bluesky, and an email-style post. Different output, different workflow, different price.

Newsletter Engine is for the specific job of producing one complete email newsletter draft from a topic plus a few source pieces. Different output structure (subject lines, preview text, body, P.S., CTA instead of platform-shaped variants), different polling cadence (weekly typically, not multiple-per-week), different cost profile (cheaper to run because it is one Claude call cycle instead of five).

Both products share the Voice DNA framework. If you already own CCE, your Voice DNA profile transfers over to Newsletter Engine. The two products are sold separately for now; a bundle is on the roadmap for v1.1.

The honest read

Three reasons not to buy this:

• You have no back-catalog. Newsletter Engine pulls from your existing content. If you have no blog posts, no podcast transcripts, no prior newsletters, no course material, the system has nothing to work with. Build the catalog first.
• You want zero setup. 30 minutes of technical work is real. There is an Anthropic API key to create, a Notion integration token to generate, four placeholder strings to swap. If you have ever installed a WordPress plugin or built a Zapier zap, you can do this. If you have not, it will feel like real work the first time.
• You want the system to send the emails. Newsletter Engine drafts the newsletter. You still own your sending tool. MailerLite, Beehiiv, ConvertKit, Substack, whatever you already use. The system stops at “ready to paste into your email tool.”

The reason I am shipping this now

A handful of readers replied to the pillar post asking if I would ship the system as a package. Enough that it made sense to do it. The pricing, the founding window, and the timing all reflect that: small product, fair price, ship it while the interest is fresh.

If the architecture in the pillar post made sense to you and you want to skip rebuilding it, this is the package. If you want to install it from scratch on your own, the pillar has the full blueprint and that path is also fine. Both paths produce the same thing.

30-day refund. One-time purchase. No subscription.

Questions? Reply to your purchase confirmation email, or write to info@optimyzehq.com. Replies within 24 hours.