Free · 60 s Free AI-readiness audit See your site the way ChatGPT does.
Personal reply within one business day.
OWN PRODUCT · PILOT

Social media posts · Approval on a phone · 2026

A week of on-brand posts, drafted by AI and approved from a phone

Cuckoo is my own product, now in pilot. Each client gets a workspace with its own brand voice and language. AI drafts a whole week of posts for every channel. The person who decides approves them, or asks for changes, from a phone. The connections to the social platforms are built and wait on each platform’s approval.

Pilot · core built 15–16 Sep 2026 · platform approvals pending · numbers checked 2026-10-05

01 · Before

Social posting runs on chasing Someone writes, someone waits, someone posts.

For most businesses, social media is either neglected or it quietly eats someone’s week: drafting, chasing a yes, logging in to post. The week that person is busy, the posting stops.

A typical week of posts, done by handthe problem
writing
risk: Drafts for each platform, in each brand’s voice, from scratch
approval
problem: Drafts go out by email; feedback comes back in fragments
chasing
problem: A coordinator chases the decision-maker for a yes
posting
risk: Someone logs into every platform to publish
access
problem: Client social logins shared in spreadsheets
result
problem: Posting stops the week the coordinator is busy
The job: make approval the only human step, and make it easy enough to do on a phone.

Before you distribute more, see what AI already reads on your site.Free AI-readiness audit · about 60 seconds.

02 · What I built

Approval is the only human step And it happens on a phone.

A workspace holds what makes a brand sound like itself: voice, language, rules, and which AI accounts to use. From that, the system drafts the whole week for each channel, already within each platform’s length and format rules. The client opens it on a phone, signs in with a one-time code, and approves or writes a note. The note goes straight into the rewrite.

  1. Step 1 (input): Brand workspace, voice, language, rules.
  2. Step 2 (ai agent): Draft the week, 4 AI providers.
  3. Step 3 (automated): Platform rules, length, format. Rejected here: Off-rule draft (redrafted).
  4. Step 4 (client): Approve on the phone, one-time code. Rejected here: Changes asked (note drives the rewrite).
  5. Step 5 (automated): Publishing queue, posts go out on schedule.
  6. Step 6 (pending): Publish to platforms, awaiting approvals.
FIG 02 — A week in Cuckoo One person’s approval: the client’s. A post that breaks a platform rule is redrafted. A client’s note sends a post back for a rewrite. Publishing waits on platform approvals.
PLATE 01 — Week planner, desktop · client portal, phone · mock data, fictional brand “Fernhollow Tools”

03 · Who did what

Who did what Agents propose. A human approves.

  1. agent://researcher

    Mapped how each platform lets software post, how it reviews apps, and its content rules.

    Never allowed to: post anything.

  2. agent://architect

    Designed the workspaces: one voice, language and set of AI accounts per client, with keys stored encrypted.

  3. human://vegardHUMAN GATE

    Set two rules: nothing publishes without the client’s approval, and the agency never holds a client’s password.

  4. agent://writer

    Drafts a week of posts per channel in the client’s voice, in any of 4 languages.

    Never allowed to: publish a post nobody approved.

  5. agent://tester

    Runs ~200 automated test cases on security, sign-in and publishing.

  6. human://clientHUMAN GATE

    Approves, declines or writes a note per post, per day or for the whole week. Notes feed the rewrite.

  7. agent://watcher

    Sends due posts on schedule, keeps each platform connection signed in, and emails on any failure.

  8. human://vegardHUMAN GATE

    Runs the platform reviews: app registration, business verification, and privacy pages the reviewers can read.

04 · Results

Results so far Every number dated, with how it was measured.

Cuckoo: results with method and date
NumberWhat it measuresHow it was measuredObserved
~2 days✓ verified to build the core (phases 0–4) git history 15–16 Sep 2026 2026-10-05
4✓ verified AI providers (Claude, GPT, Gemini, Grok) codebase 2026-10-05
6✓ verified publishing integrations built (LinkedIn, Facebook, Instagram, X, TikTok, YouTube), pending platform approvals codebase 2026-10-05
~200✓ verified test cases in 14 files (encryption tamper, OTP lockout, publish runner, portal) test suite count 2026-10-05
4✓ verified output languages: English, German, Norwegian, Swiss German codebase 2026-10-05
Not measured yet Posts published for pilot clients starts when the platform approvals land —
Not measured yet Minutes a client spends approving a week measured from the first pilot weeks —

Cuckoo is labelled PILOT. I won’t claim live publishing on any platform until that platform has approved it.

05 · Running costs

What it costs to run

Most of the running cost is AI use, billed to each client’s own AI account, so an agency can pass it straight through to the client it belongs to. Hosting runs on Cloudflare. Images and video stay private and are made public only at the moment a platform collects them.

06 · Ownership

What you would own If I set this up for your brand or agency.

  • A workspace per brandVoice, language, rules and history, under your account.
  • Your own AI accountsAny of the 4 providers, billed to you, chosen per channel and task.
  • Official platform connectionsConnected through each platform’s own sign-in. Never a shared password.
  • The approval historyWho approved what, when, and which note changed which post.
  • The code and the hosting accountThe system, the client portal and the queue, in your name.
  • Security by defaultKeys stored encrypted; the admin area behind a separate sign-in.

07 · What I’d build for you

A week of on-brand posts per channel, approved from your phone

If your expertise deserves more reach than your team has hours, I’ll set up the distribution module for you: your voice, your channels, your approval. Your part is a quick yes or “change this” from your phone; the rest runs on schedule.

  • A week of on-brand posts per channel, drafted in one go
  • Approval from a phone, with notes that drive the rewrite
  • Your own AI accounts and platform connections, no shared passwords
  • Pairs with the content engine, so posts point to pages AI assistants quote

Not for you if you want AI to post with nobody looking. Every post here waits for a human yes.

The offer that fits · Quoted by AI

Content Engine · Distribution Module

from €3,500$3,850 typical €3.5k–6ktypical $4k–6.5k

3–4 weeks · A week of on-brand posts per channel, approved from a phone.

Not sure which fits? Book 20 minutes with me
08 · Under the hood For your web developer: the technical detail
Runtime
Cloudflare Workers with a Hono API, a React SPA on static assets, D1 with Drizzle ORM, private and public R2 buckets, KV sessions, a Cron-driven publish runner with token refresh, Email Sending for one-time codes, Cloudflare Access for admin.
AI
4 providers (Anthropic, OpenAI, Google, xAI), with several keys assignable per workspace, channel and purpose (text, image, video) and a test-key button.
Security
Secrets encrypted at rest with AES-GCM. The admin refuses to serve in production until Cloudflare Access is configured, so a half-finished deploy can’t expose the API.
Media
Large video goes to storage in parts, because a Worker request body can’t hold it. A public copy is made only when a platform fetches it.
Editor
Live per-platform character counts and rules in the editor; output in 4 languages.
Platform review
Server-rendered privacy, terms and data-deletion pages, so the platforms’ reviewers see real text without JavaScript.
Tests
~200 test cases: encryption tamper detection, one-time-code lockout, sessions, slugging, content length rules, the publish runner and the portal.