Skip to content

Everything the crew does, one page each.

Oat prepares researched work from your posts and brief, brings it to you with sources beside it, and moves only the exact revision you approve to your site, your list and your channels.

Oat is a desk, not a chat. It holds your posts, your brief and your voice rules, and it uses them to bring you work that is already researched and already written the way you write. Your part is the read: correct what is wrong, approve the exact version you want out, and decide where it goes.

The loop is closed on purpose. What gets approved goes to your site and your channels and comes back as what got read, from Google Analytics and Search Console, with the source and the sync time on every figure. That evidence feeds the next brief item, which you accept before Oat follows it.

Around that loop sit the rules that keep you the authority. Every claim is linked to a source or held for you. Every edit is a revision. Every approval binds to one hash and one destination. Every output traces back to the piece it came from, and nothing is shown as live until the destination confirms it.

Six parts, one desk.

  1. The draft is on your Desk before you are.

    Oat drafts from your own posts with a source on every claim, and your part is the read, the correction and the sign-off.

    • The queue puts the piece that needs you first.
    • Every claim links to a source or stays held.
    • Read, comment and approve from your phone.
    More about the Desk
  2. Every line in a draft names its source.

    Oat reads your posts first, dates every source, links each claim to an excerpt or holds it, and Dollop checks the piece.

    • Your posts are read first, so drafts never repeat you.
    • Each source keeps its excerpt and retrieval date.
    • Dollop shows a missing result as missing, never passed.
    More about research and evidence
  3. One person approves one exact revision for one place.

    An approver signs off one exact revision for one destination, an edit sends it back, and live means the destination confirmed it.

    • One approval is required before any piece leaves.
    • Approval binds to a revision hash and a destination.
    • A queued job never reads as a live page.
    More about approvals and publishing
  4. Google Analytics and Search Console feed your next brief.

    Oat reads Google Analytics and Search Console, shows every figure with its source and sync time, and proposes the next brief item.

    • Both connect read-only, so Oat never touches your settings.
    • Every figure carries its source, range and last sync.
    • You accept a proposed brief item before Oat writes.
    More about performance
  5. Every output traces back to the revision you approved.

    The revision you approved is the source for every post, issue, video and clip, and each output gets its own approval.

    • Every output names the approved revision it came from.
    • Each output is its own revision with its own sign-off.
    • A new revision marks every output for review again.
    More about repurpose
  6. Your Desk answers in the thread you already have open.

    On WhatsApp and Apple Messages you ask what is waiting, push back in plain words and approve an exact revision.

    • Both channels reach the same workspace under the same rules.
    • The packet names the piece, revision and destination.
    • Nothing posts from a chat on its own.
    More about messaging

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.

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

Arrive to a desk that already has work on it.

Create your account

Email sign-up. Connect one account and Dollop starts reading your posts.