The client
A publisher running several content properties across SE Asia. The economics rest on a steady drip of long-form articles and practical guides for travelers, expats, and people researching a move to the region. The content team was six people. All capable. All quietly burning out.
The problem
The business needed roughly forty pieces a month across its properties. The team could comfortably do twenty. Everything else slipped, got rushed, or never happened. The bottleneck was not any one step. It was every step: finding the right angle, doing the research, drafting, fact-checking, adding references, tuning for search, formatting for the CMS, and running editor review.
Each step took meaningful time, and each had to happen for every piece. The editor-in-chief described it in a way that stuck: “None of it is hard. It is just that there is always more of it than people.”
The team had tried writing with the consumer AI tools already on the market. The output was passable for a first pass but needed so much editing that the time saved disappeared into review. It also kept producing the same bland, inoffensive prose that their readers would not come back for.
The approach
The pipeline broke the job into the steps the team was already doing and put an AI layer on the right ones. A new piece started as a brief submitted through a simple internal form. The pipeline ran the brief through a research step (an LLM with a search API for sources), produced a structured outline, drafted the piece in the house voice using examples from their own archive, ran a fact-check pass against the cited sources, and applied the SEO checklist.
The editor saw the output inside a purpose-built dashboard. Every fact linked to its source. Every stylistic call the AI had made was flagged for confirmation. The editor could accept, reject, or rewrite at the paragraph level. Publishing always required a human pressing the button.
What was automated was the mechanical work. What was preserved was every step that needed editorial judgment.
The result
Production time per piece dropped about seventy percent. The team went from twenty pieces a month at capacity to forty-five pieces a month comfortably, with editorial quality holding steady on internal review scores. Two of the six team members shifted into roles that use their judgment rather than their typing: commissioning, editorial strategy, and partnerships. The other four work shorter days.
The editor-in-chief now spends most of her week on strategic editing and voice training of the drafting layer, rather than on production. She has called it, more than once, the first year in a decade that feels sustainable.
What this is not
It is not AI replacing writers. The team is the same size, doing better work, on a sane schedule. It is also not a magic content machine. Every piece still goes through a human editor, and that step matters most. What the build did was remove the mechanical bottlenecks that were eating the team alive.
"For the first time in a decade, my Friday afternoon does not feel like a panic. The team is publishing more, the editorial quality is holding, and two of my writers got their lives back."