The client who never existed
GALAPA* is a digital agency. Like many agencies, we keep a bilingual blog: it's how a prospective client finds us, and increasingly it's also how an AI assistant decides to cite us when someone asks it a question about our field. Since the spring of 2026, the articles on that blog have been produced by three programs working in sequence, with two points where a person decides.
That's not how it started.
On June 2, 2026, while reviewing an article our automated writer had just finished, we found a complete case study. A B2B logistics client, a visibility score that had climbed from 38% to 68% between March and April, a precise figure for how many queries ChatGPT answered by recommending the company. Three convincing paragraphs, written in the right tone, ready to publish.
That client never existed. None of those measurements had been taken. The second article reviewed that day had the same defect, which ruled out an accident. Our engineering log carries the note, dated the same day: structural.
What follows is what we built from there: why the chain now runs on three separate programs instead of one, what broke along the way, and what it changes in a week of actual work.
The hard part was never the writing
Writing a 1,500 to 2,000 word article takes a few days of full-time work. That's slow, but it's the visible part of the problem and the cheaper one.
The part that wears you down is keeping up. Staying current in a field that shifts every week, opening dozens of links, telling signal from noise, gathering sources, deciding which subject deserves an article now rather than in three months. For a small business whose trade isn't publishing, that load is unmanageable. It never appears on a schedule, and it's always the first thing to go.
An agent that writes quickly doesn't solve that. It moves the bottleneck one step down the line, and often makes it worse: the more you produce, the more you have to verify.
Three agents, three jobs
The chain runs on three separate programs. Each has its own codebase, its own release cycle, and its own rhythm.
