Launch a newsletter engine your clients actually read

The engine, not the newsletter

The newsletter itself was never the hard part. The hard part is the invisible machinery around it: noticing what happened this month that is worth telling, getting it drafted while it is fresh, formatted, scheduled, and sent - every month, including the months when you are underwater. That machinery is what you are building here, with your AskEleven Employee running every stage except the two that must stay yours: deciding what you believe, and approving what goes out.

The division of labor, fixed from day one: your Employee gathers material continuously, drafts each issue on schedule, and manages the list and the sending through Mailchimp. You spend fifteen minutes a month as the editor - cutting, sharpening, approving. If your monthly involvement ever grows past twenty minutes, something in the setup below needs tightening, because the whole point is an issue that ships whether or not you had a free afternoon.

Setup is one session. The first issue goes out within two weeks of it.

Before you start: gather four things

• Your list, honestly audited. Export what you have - Mailchimp, HubSpot, the address book, the spreadsheet of collectors and past clients. Only people with a real relationship to your business belong on it; a small list of people who know you beats a large list that marked you as spam in 2022.
• Three newsletters you actually read. Forward them to your Employee with one line each on why you open them. This does more to set the bar than any abstract description of tone.
• Your raw-material sources. Where the month's events already leave traces: your sent mail, your calendar, your Instagram, HubSpot notes, the folder of installation photos. The engine works because it harvests these instead of asking you to remember.
• A decision: what your newsletter is for. One sentence, written down. "Keep collectors close to the program between openings." "Stay on the desk of every referral source." Every issue gets judged against this sentence, so argue about it now, once.

Step 1: The format prompt

Design the issue once; reuse the shape forever. Recurring sections are what make a newsletter draftable by someone other than you - and readable in three minutes.

What to expect: a format proposal to argue with - and you should argue, because this argument happens once and then never again. A gallery might land on: one paragraph from the director (yours), what is on view and what is coming, one work looked at closely, and three lines of house news. Cut any section you cannot imagine filling in a slow month. The format that survives a slow August is the right one.

Step 2: The gathering habit

This standing instruction is the engine's heart - it runs all month, invisibly:

What to expect: the mid-month digest quickly becomes the most pleasant surprise of the system - a running record of what actually happened in your business, assembled by someone paying attention. Your only job is the thirty-second reply: "lead with the Marden drawing, drop the fair mention, the rest is fine." The "tell me early" clause saves you from the newsletter's traditional cause of death: discovering on deadline day that the month has no material.

Step 3: Drafting, approval, and the send

Once a month, the folder becomes an issue:

What to expect: a draft that is 85 percent right, with honest questions at the top. Edit as an editor, not a rewriter: cut, sharpen, fix facts, write your 100 words. The forwarded replies deserve more attention than the open rate - a collector replying "is the Riley still available?" to a newsletter is precisely the event this entire engine exists to create.

A worked example: the October issue

A contemporary gallery, list of 640 collectors and contacts. The October issue folder, gathered without the director lifting a finger, holds: install shots from the fall opening, four separate client emails asking whether the large Okafor canvas had sold (it had not, then), a museum's loan request for a 2019 painting, and a calendar note that the gallery turns ten in November.

The draft arrives on the 25th with its questions on top: "Confirm the Okafor is still available before we print that. Is the museum loan public? Your 100 words - suggest it look ahead to the tenth anniversary." The director confirms, approves the loan mention, writes 90 words in the back of a taxi. The issue - one paragraph from the director, the fall show with three install shots, the Okafor looked at closely with its provenance told properly, three lines of news ending with the loan - goes out the first Tuesday of October at 10am.

By Thursday there are nine replies, two asking to see the Okafor in person. Total director time for the month: sixteen minutes. The issue before the engine existed - the one that was going to get written in September - never went out at all.

Quality tests, and keeping the engine honest

• The three-minute test. Time yourself reading the draft. Over three minutes, cut a section - do not compress everything, remove something whole.
• The stranger test. Could a stranger to your business have written this issue from public information? If yes, it is content, not correspondence. The fix is always the same: more from the issue folder, less connective prose.
• The skim test. Read only the section headings and bolded lines. They should carry the issue on their own, because that is how most of the list will read it.
• The absence test. The real one, and it takes a quarter to run: does anyone notice when it arrives? Replies, mentions in conversation, a forward you get shown. Three issues of total silence means the format is serving you rather than the list - go back to step 1 and re-argue the purpose sentence.

And the standing rule that keeps trust: in a month with genuinely nothing to say, send nothing. Your Employee will warn you by the 20th; a skipped month costs you almost nothing, while a padded issue teaches the list not to open the next one. The engine's job is never "send monthly." It is "never send emptiness."