Skip to content

Knowledge Base

Draft newsletters readers actually want

Write engaging newsletters with an AI writer that knows the give-versus-ask rhythm and pulls stories and insights from your own knowledge base.

The newsletters that keep subscribers reading follow a rhythm: give value often, ask rarely. The AI Newsletter Writer is a dedicated writing chat that knows that rhythm and drafts each issue from your own knowledge base, so your emails carry your real insights instead of recycled advice.

Open Write, then Newsletter Writer in the sidebar and click New Newsletter. On a new account it is one of the pages hidden to keep the sidebar short; see Show the pages hidden from your sidebar, or go straight to kb.noliai.com/newsletter.

The Value-Add / Value-Ask framework

The writer opens every new newsletter by walking you through the framework it works from. For every email that asks something of your readers (buy, sign up, share), send three to six emails that give something. That ratio keeps your audience engaged and receptive when you do ask.

So the first question is which type you are writing today:

  • Value-Add: for building trust and goodwill: a weekly industry roundup, a behind-the-scenes lesson learned, an actionable how-to, a curated resource list, or a personal story with a takeaway.
  • Value-Ask: for converting trust into action: a product or service launch, an event promotion, a survey, a sales campaign, or a partnership announcement.

Pick one, describe your newsletter, and iterate in the chat until the draft sounds right.

Draft from your own knowledge

Because the writer sits inside your knowledge base, it can pull from everything you have captured, meeting notes, research, customer insights, past writing. Use the filter bar to steer it:

  • Filter by tag to draft from a topic area.
  • Filter by doc to build an issue around specific documents, like last week's research notes.
  • Date and type filters limit the sources by recency or format.

With no tag or doc filter set, the writer looks first at documents tagged Newsletter (spelled exactly that way), then at the rest of your knowledge base. Save your past issues with that tag and new drafts will match their voice and format.

That is how a newsletter goes from "content" to "here is what I actually learned this week."

Manage your issues

Every newsletter is saved as its own conversation in the sidebar. Search past issues, rename them, archive finished ones, and load an old issue anytime to reuse a structure that worked.

Next