This website runs itself.
Mostly. Benian builds autonomous systems for clients, so the seventh case study is the agency: four systems and one house rule keep benian.ai written, answered, and measured. Here is what each one does, what it refuses to do, and where its evidence lands.
The content engine
Tuesday and Thursday, 15:00 UTCTwice a week, a scheduled workflow reads the industry feeds, picks one topic that does not duplicate anything already on the blog, and drafts a post in the founder’s voice. An independent critic pass then scores the draft on six rubric items: factual, specific, relevant to operators, voice, answer-shaped, honest. Any score below the bar kills the piece before it exists anywhere public.
Two posts a week is a ceiling, not a target. Quality over quantity is the brand, and a slow cadence is what gives the gate room to say no.
Publish a weak draft. A run that ships nothing prints SKIPPED and ends green, because the gate rejecting a post is the system working, not failing.
It also refuses to invent: no statistic without a named real source, and no client result beyond the ones already published on this site.
Every engine-drafted article carries a disclosure line near the byline linking back to this page, and every run, including the skipped ones, journals itself to the operations database. Published posts land as reviewed commits in the site’s repository.
The community scout
Weekdays, 13:00 UTCEvery weekday morning, the scout gathers live forum threads where an operator is asking the kind of question Benian answers for a living, scores each one against the ideal customer profile, and drafts a reply for the few genuinely worth answering.
Post. It holds no credentials for Reddit, Hacker News, or any forum, and never will. That is the design, not a setting.
An AI reply published under a human name would be a lie about who is talking: the FTC’s Endorsement Guides treat undisclosed synthetic endorsements as deceptive, most platform rules ban undisclosed automation, and one automated reply reads as vendor spam.
Drafts land in a relationship ledger committed to the repository. A human reads each one, rewrites it in their own words, posts it from their own account with the affiliation disclosed, and owns the status column. The scout never overwrites a row a human has touched.
The chat agent
Live, on every pageThe widget in the corner answers from a knowledge base compiled out of the same data files that render this site, so it quotes the same published prices and the same labeled case-study figures a visitor would find by reading. Its tools are narrow: it can record a lead when a visitor asks to be contacted, and it can hand over the scoping-call booking link.
Returning visitors are remembered. The tail of an earlier conversation is recalled at the start of the next one, so nobody re-explains their business to a widget.
Guess. Anything outside the published facts gets a straight “that depends on scope” instead of an invented number, and it cannot offer discounts or guarantees the site does not publish.
Every exchange lands in the operations database, which is what makes cross-visit memory and the weekly digest possible. A captured lead is stored on our side first and then forwarded, so a dead webhook loses nothing.
The inbound database
Always on · digest MondaysEvery lead, from every surface, lands in one database with its first touch frozen: the landing page, the referrer, and any campaign parameters from the first visit, kept in the visitor’s own browser storage. No cookies, and nothing follows anyone across the web.
At the edge, the site logs every page fetched by 25 named AI and search crawlers, matched by user agent with no IP addresses stored: the raw evidence for which answer engines actually read this site. Each Monday, a digest composes the week from those tables: leads, inbound signals, crawler coverage, the scout’s review queue, and agent-run health.
Editorialize. The weekly digest makes no model calls; it is a mirror, not an author.
Telemetry is fire-and-forget by construction: a failed write can never slow or break a page for a visitor.
Weekly reports are committed to the repository, and the crawler telemetry is published per bot at /reports/ai-crawlers.
The evidence rule
Every number, every pageThe house rule the other four systems answer to: every figure published on this site carries one of three labels. Measured means we pulled it from production call logs or delivery records ourselves. Client-reported means the client stated it and we print it as their statement. Projection means arithmetic from current pace, labeled as such and never presented as achieved.
If a number cannot carry its label, it does not go on the site.
Round up. No unlabeled numbers, no invented industry benchmarks, no vendor stats laundered into results. The label states how we know the number, not how good it looks.
The labels render beside every figure on the case studies page, and the same dataset is served machine-readable at /evidence.json for anyone, or any engine, that wants to check.
A human reviews everything that leaves drafts.
The blog is the only surface that ships on its own, and it ships behind a gate that is allowed to publish nothing. Everything else, the forum replies and the social drafts, waits in a queue until a person reads it, edits it, and sends it under their own name. If you want systems with this kind of restraint pointed at your own business, that conversation takes half an hour.
Written August 20, 2026. Everything above describes the live configuration of benian.ai on that date: the agent code, the schedules, and the ledger are versioned in the site’s repository, and engine-drafted posts disclose themselves in the byline.