// proof
We ran it on ourselves first.
Every number on this page is pulled from the live kanban on bailian — the same infrastructure that runs this site. No estimates.
// case study #0 — tacavar
The Tacavar pipeline
Situation → Automations deployed → Outcome
Situation
We had the same recurring-work problem we sell against: blog cadence, SEO monitoring, research aggregation, lead follow-up. None of it was getting done reliably by humans.
Automations deployed
A multi-profile agent fleet on cron: signal-collector → signal-enricher → writer → editor → verifier → distributor, plus SEO strategist and analyst profiles. Specialist profiles pick up cards on the board; cron dispatches the cadences.
Outcome
1,300+
jobs completed
700+
this week
15+
agent profiles
140+
auto-recovered
Reliability improved as the fleet was dialed in: crash rate fell from 86% in May to 17% in June to ~4% today. Average runtime per completed job is ~6 min. The verifier profile alone has 340+ completed runs — verification is structural, not a tagline.
pipeline.bailian
live · daily cadenceentry / verifiedagenthuman escalationflow particles indicate active work moving through the pipeline
// case study #0 — in practice
The pipeline, unedited.
A real content job moving through the board, and the daily digest the system produces. Nothing staged.
// case study #1 — marketing
SEO & content pipeline
Situation
An SEO/content operation where blog cadence and rank tracking were the first things to slip when ops got busy.
Automations deployed
Weekly editorial calendar generation, per-site SEO refinement passes, rank tracking on a weekly cron, and drafts written → verified → published on schedule.
Outcome
83 posts in the live corpus, published and verified by the pipeline. We don’t publish invented organic-growth percentages here — we ship what’s verifiable.
// case study #2 — healthcare ops
Healthcare distribution operations
Situation
A biologics and specialty-products distribution operation drowning in document triage, intake, and recurring reporting.
Automations deployed
Document triage and routing, intake follow-up, and recurring operational reports — each a recurring card on the board.
Outcome
The recurring work runs on cadence instead of waiting for a human to remember it. (We describe the automations deployed rather than invent revenue figures.)