Content drafting & publish-with-review

The draft is done before the meeting about the draft: written from your source notes, in your voice, and parked one approval away from published.

The brief

Written like you’d brief a person.

This is the whole setup - a procedure in plain language, with tools and specialist agents referenced inline. When it runs is not written here: that’s the trigger, configured beside it.

Draft the post from the source notes, add it to the content tracker with #yekar.notion.append-blocks, and send it to @editor for sign-off - never publish without it.

How it runs

From trigger to logged outcome.

Trigger

Schedule - On your content calendar's rhythm

  1. Read the sources

    Works from your notes, transcripts, and past posts - not from thin air.

  2. Draft in your voice

    Writes the post to your style guide, with sources kept alongside.

  3. Queue for review

    Lands in the tracker with the editor tagged.

  4. Publish on approval

    Ships to the site only after sign-off.

Where people stay in control

Nothing consequential runs on its own.

  • Publishing is gated on an editor's explicit approval - always.

Tools it uses

Runs on accounts you already have.

  • Notion
  • WordPress.com
  • Canva
  • Slack

Connected once, governed per agent - this use case gets only the tools listed here.

Illustrative savings

$500–$1,400 / month

Assumes 4–12 posts a month at 2–4 hours of drafting each, with editing time unchanged.

Illustrative monthly savings, estimated from typical handling time at public salary benchmarks, reviewed August 2026. Not a promise or a guarantee - your numbers depend on volume and process.

What makes this dependable

Start with the job

See how Yekar.AI would run one of your real processes.

Bring the job, the systems it touches, and the decisions that need a person.