What this is
Anyone can generate a draft now. Almost nobody can trust what comes out.
Volume is cheap. A brand standard is not.
Answer engines don’t cite slop. They cite work that’s original, sourced, and consistent.
Brands need a custom operation that keeps the work honest.
The work
We design the writing operation around what the brand publishes, or wants to begin publishing — newsletters, executive writing, thought leadership, marketing, answer-engine work. Sources in, checked drafts out, on a cadence. We can run it from our side so the brand just gets the output, or hand the operation over and onboard the team.
If it reads like everyone else, it doesn’t go out. Custom voice systems are built to fit the brand. Every claim is checked. The standard stays on whether a person reviews the piece or it publishes on its own.
People ask ChatGPT, Perplexity, and Google now. Those systems cite writing with sources and a point of view. That’s what a custom operation is built to produce.
Search buries pages that aren’t worth reading. Slop wastes the reach the brand already paid for.
— Google core update, March 2024The questions that used to go to Google now go to ChatGPT. Slop doesn’t get cited.
— ChatGPT, Perplexity, GoogleOne season of slop undoes years of trust.
The standard
Sources on every claim
unverified claims get flaggedChecked before it publishes
every piece goes through a gateManual to full auto
the operation sets how it shipsBuilt to be cited
original, sourced, consistentExamples
Custom operations we’ve built, around what the brand publishes or wants to begin publishing.
A letter that runs on a cadence, in the brand’s voice, without a blank page every send.
Articles, op-eds, and notes under a leader’s name, held to the brand’s standard.
A point of view, published on a cadence, so the brand shows up as the one with something to say.
Company blogs, resources, and campaigns as one operation, on a cadence.
Writing built to be cited when someone asks ChatGPT, Perplexity, or Google — sourced, consistent, with a point of view.
Who runs WriterOps
Alex McFarland
Founder
Alex founded WriterOps after years as a working writer who moved into building AI agents and the cloud operations that keep them running. He writes about AI to 13,000+ readers, and builds the systems he writes about: custom writing operations already in production, with real publications and editorial gates.
A brand comes in with something to publish, or a plan to start. It leaves with an operation that publishes — and the brand keeps the name, the standards, and the operation.
alex@writerops.ai — replies come from a human