Retorik Request a Call
How it works

An hour of writing
becomes ten minutes of judgment.

This is what happens to a post inside Retorik — from the leader’s own record to published, with their judgment the only work that stays.

Everything on this page is the product as it runs today — with a comms team, or without one. Where it describes where Retorik is heading, it says so.

i.
The draft

A post begins wherever it begins.

A topic. A pasted news link. A rough paragraph typed between meetings. A short guided conversation. Retorik helps the leader or their team build the draft from the leader’s own positions — and shows what it was built on: which of their past ideas, which outside sources, by name. Nothing invented under their name.

Each platform gets its own version — LinkedIn’s patience, X’s brevity, a thread where a thread is called for. And the same machinery drafts the long pieces: a speech, town-hall remarks, an essay — in the leader’s spoken register, exported for the podium.

Before anyone reads it, Retorik has. Every number is checked against the draft’s sources — supported, worked out, or not found. The subjects the leader will not touch stay out of every version. And when the version for X quietly drops a qualification the LinkedIn version kept, the watch line says so.

ii.
The record

Drafting is informed by what the leader has already said.

The comms team — or the leader, alone — loads the record: past posts, speeches, letters, memos, as much of it as exists. Retorik reads it and builds the picture, keeping two things deliberately separate: what they believe, drawn from their actual positions, and how they sound — their cadence, their habits, their register.

It maps what they keep returning to. And it will note, gently, when what a leader says they care about is not what they actually write about — a question, never a verdict.

And the record is not only what they bring — using Retorik builds it. Every post the leader approves and every speech marked delivered joins the library, so each draft starts from a fuller picture of them.

iii.
The judgment

Then the human work.

Comms reads each channel’s version and checks it. The leader reads, and rules: sharpen this line, cut that claim, not this week. Send it back, and a note goes with it, drafted by Retorik and for the sender to edit, saying what changed.

Approve it from a phone, between meetings. Whose turn it is, is always visible; every decision is recorded. Nothing goes out without a person choosing to send it.

No comms team? The same loop runs with one chair. The record behind it is the same.

The institution’s own account runs the same loop, with its own library and its own learned voice. Nobody logs in as it: every word it publishes belongs to a named person.

iv.
The return

Publish, and the loop closes.

The approved post goes out — now, or scheduled — and the published text joins the leader’s voice library. And every published post carries its record: one page that says who checked it, who approved it, and what it drew on. The next draft starts closer to the mark, because it learns from what the leader approved, not just what they wrote years ago. A speech delivered and marked delivered teaches the voice the same way.

That accumulated judgment is the working asset. No competitor can copy it, because it is made of the leader’s decisions about their own words.

The full list

Every feature by name, live today and coming soon.

The shape of it

Your ideas, in your voice — shaped into a post in minutes,
with a record of who stood behind every word.

Runs on servers in the European Union, operated by a Dutch company in The Hague.

Request a call →     Why I built it this way →