Skip to content

The content crew you never had to hire.

Creating is not your main job. Oat researches, drafts in your voice, checks, publishes and repurposes. You approve one exact revision.

Sources visible. Every claim links to its excerpt or is held for you. Exact-version approval. One revision by its hash. An edit sends it back. Nothing publishes without you. Live means confirmed live, never a submitted job.

Creating was never your main job.

You run a business or a day job and also feed a site, a list and a channel. A chat window writes a draft. The hours go to sources, checks, edits, sign-off, posting and repurposing. That is a content team's week, done alone.

Oat is that crew. You keep the judgment.

Prompt-first
Oat

How a piece moves from topic to what got read.

Eight steps in one loop. The decisions stay yours.

DiscoverA topic inside your brief, checked against what you already covered.

  1. 01 / 04

    The work arrives before you sit down.

    Set a brief. Oat picks topics inside it, reads your archive so it never repeats you, and lands finished drafts on your desk at your cadence.

    More about the Desk
  2. 02 / 04

    Every claim shows its source.

    Each claim links to the excerpt it rests on. A claim Oat could not back is held and shown to you, never smoothed over.

    More about research and evidence
  3. 03 / 04

    Corrections teach Oat only when you say so.

    Comment on a passage and Oat fixes that draft. If the comment reads like a rule, Oat proposes it and waits for your yes.

    More about voice
  4. 04 / 04

    Approval binds to one exact revision.

    The approver signs off one revision by its hash for one destination. Edit a word after that and it goes back to review.

    More about approvals

What got read decides what comes next.

Oat reads your Google Analytics and Search Console, sees what people read to the end, and proposes the next brief item. You accept it first.

  1. What got read

  2. What Oat proposes next

More about performance

One approved piece becomes every output.

Every output traces back to the approved revision by hash and gets its own sign-off. When the source moves, the outputs say so.

Approved source

The hostel curfew, priced in missed shifts

Revision
3 of 3 · 9a30c2e
Earlier
8d1f04a
Approved
  • Based on revision 9a30c2e. Current. Its own approval, its own destination.

More about repurposing

Review and approve from WhatsApp or Apple Messages.

Ask what is waiting or for another angle. Before you approve, Oat names the piece, the revision and the destination. A bare yes does nothing.

  • WhatsAppOne Oat number, linked to your account.
  • Apple MessagesMessages for Business on iPhone and Mac.
More about messaging

Works with what you already run.

Your site, analytics, channels and chats connect once, scoped to your workspace. Posting stays off until you switch it on.

Every integration, with what it needs

You stay in charge, by design.

Oat drafts, checks, flags and proposes. Only a person with the approver role approves, one exact revision at a time.

Read how Oat is built
The decisionA person approves one exact revisionModel output and imported pages are data, never instructions.
Exact approval
One revision, one hash, one destination. Later edits need a fresh sign-off.
Roles
Owner, Editor, Approver, Viewer. Membership never grants approval on its own.
Workspace isolation
Every record and job is scoped to your workspace and checked on the server.
Encrypted connections
Tokens live encrypted on the server. A model never holds publishing credentials.
Audit trail
Who did what to which revision, and when, with the text redacted.

Access starts with a conversation.

A person sets up your desk and hands it over with work already waiting. Tell us about your site.

Request access

A person reads every request.

What is included

  1. 01Archive imported, voice and brief prepared, first drafts waiting.
  2. 02Site, analytics and channels connected, each on its own permission.
  3. 03Review and approval on the web, WhatsApp and Apple Messages.

Questions

How good is the draft?

Good enough to judge. Written from your archive and rules, every claim sourced or held, checked by Dollop before it reaches you. You still read it.

Does Oat publish on its own?

No. The approver signs off one exact revision for one destination. Any edit voids it, and Oat shows the real delivery state afterwards.

Will it learn my voice without asking?

No. A comment fixes one draft. If it reads like a rule, Oat proposes it and waits. Rules live in Context and can be undone.

Do I have to move my site?

No. Oat publishes to WordPress, Vercel or GitHub, posts to LinkedIn, Instagram and YouTube, and exports Markdown and HTML. Posting stays off until you switch it on.

Who can see my writing?

The people in your workspace. Records live in your workspace's database, files in a private bucket, tokens encrypted. Imported pages and model output are data, never instructions.

Your next piece is already written.

Request access and arrive to a desk with work waiting and the last word yours.

Request access