I’m Charles Green. I build AI systems for companies, usually multi-agent orchestration, usually on Cloudflare. Content Loop Studio is the product version of work I’ve been doing as a consultant for years.

Why this product, why now

In 2026, three things are simultaneously true for B2B SaaS:

  1. You can’t ignore content. Your competitors are publishing, your category needs explanation, and your prospects search before they buy.
  2. You can’t afford a full content team. A content marketer, a strategist, an SEO specialist, an editor. That’s $300K+/year fully loaded.
  3. You can’t trust pure AI either. ChatGPT alone produces hallucinated stats and AI-cadenced prose your audience can spot.

There’s a gap between “DIY in ChatGPT” and “hire a content team”. Content Loop Studio fills it. AI does the volume, I do the tuning, and you stay in control over what ships.

Why this is a service, not a SaaS

I considered shipping this as self-serve SaaS. Sign up, set up your own tenant, off you go. I decided against it for the early phase for one specific reason: brand voice tuning needs a person, not a configurator.

You can give a self-serve product a “describe your brand voice in 200 characters” form. The output will be mediocre. The thing that gets the Writer agent from “sounds like AI” to “sounds like your team” is iteration with someone who reads the drafts critically, not against generic style rubrics but against your specific business and audience. That’s what I do in the first month with every tenant.

After we’ve onboarded ten customers, the playbook for brand voice tuning will be repeatable enough to package as a self-serve offering. Not yet.

What I won’t do

A few commitments worth stating up front:

  • I won’t sell to anyone where I can’t deliver the result. If your traffic baseline is too low, your category too niche, or your stack incompatible (no Hugo, no chat backend, no GSC access), I’ll tell you on the discovery call and not take your money.
  • I won’t oversell. Content Loop Studio is good at certain things and bad at others. The Features page lists what it deliberately doesn’t do.
  • I won’t disappear. As long as Content Loop Studio exists, the founding cohort has my direct Slack. If I sunset the product, you get six months’ notice and full data export.

The technical pedigree

If it matters to you: Content Loop Studio is built on TypeScript, Cloudflare Workers, Durable Objects with SQLite-backed storage, the Cloudflare Agents SDK, Vectorize, R2, Workers AI for embeddings, and Anthropic Claude (Sonnet for reasoning, Haiku for plumbing). Observability is Langfuse. Multi-tenant isolation is structural (tenant ID = Durable Object name). Every tool is unit-tested. Every Durable Object migration ships with a paired migration test because DO migrations are forward-only in production. The full architecture is documented in the Platform PRD and Content Generator PRD.

If that means nothing to you, it doesn’t have to. The right level of abstraction for you is: it works, it’s reliable, and I’m the person who’ll fix it if it doesn’t.

What’s next

I’m working on:

  • WordPress and Astro support. Hugo first because dogfood (this site is published by Content Loop Studio). The abstraction lands after the second concrete target.
  • Long-tail keyword automation. Watching for queries where you’re newly ranked and don’t have content, drafting on a cadence without you asking.
  • Multi-language drafting. Spanish and German are the most-requested.

The roadmap is shaped by what founding cohort members ask for. You’ll have direct input.

Talk to me

The discovery call is 25 minutes. We’ll cover your stack, your content goals, and whether Content Loop Studio is a fit. If it isn’t, you’ll leave with a clearer picture of what to do instead. If it is, the next step is a written proposal within 48 hours.

Email me directly: hello@charles.green.