Our articles now take a 30-minute review instead of an average of six hours of writing.

We wanted to publish often without giving up half the week to writing, and a good article was taking us six hours on average. So we built a content system for our own use. We move a card on a project board and the article comes back researched and drafted, with three quality checks already done. It's then ready for a 30-minute read before it goes out across our channels, including the website and LinkedIn.

01

The problem

~6hrs an article, on average

Writing a good article properly ate most of a working day. There was the research, the structure, a full draft, then editing, fact-checking and formatting. When we timed a month of our own articles, each one took between 4 and 11 hours, 6 on average.

We were also doing the client work and the business development, so those hours were not there. The options narrowed to writing less often or dropping the quality. We were managing three or four articles a month.

02

What we built

A production flow where we drag a card across the board and the finished draft turns up ready to read. Research and drafting happen first, and three separate checks run before we look at it.

AutomaticRevise, max 2
Trigger
Boardmove a card
↓
Write
Researchgathers the factsDraftwrites + edits for voice
↓
Quality checks
3 independent checks, run in parallel
AccuracySearchVoice

A failed check sends the draft back to revise, up to twice.

↓
Review
Our review30 min
↓
Published
Publishedgoes live on its own
  1. 01

    Move a card

    We drag a card across the project board, and that's the whole trigger.

  2. 02

    It researches and drafts

    The system researches the topic and writes a full draft in our house voice, keeping a list of the sources it used. An editing pass then tightens the draft so it reads like a person wrote it.

  3. 03

    Three independent checks

    One check compares every factual claim with the sources from the research step and another looks at search structure, while the third compares the draft with our house style. A failed check sends the draft back for a revision, up to twice.

  4. 04

    A 30-minute review

    We read the finished draft and either approve it or leave a comment, which takes about thirty minutes.

  5. 05

    It publishes itself

    Once approved, the piece goes out on its own and the topic list updates so we don't repeat the same angle.

03

How we rolled it out

Built over about 6 weeks and in use since March 2026.

  1. I

    Edited everything at first

    Every draft in the first batch got a full manual edit so we could compare it with what we'd have written ourselves.

  2. II

    Moved to review only

    Once drafts needed only light changes, we switched to the 30-minute review.

  3. III

    Turned on publishing

    After a run of clean reviews, we let approved pieces publish on their own.

  4. IV

    Kept tuning

    We still read every piece before it goes out, and we adjust the checks when they start flagging the wrong things.

04

Safeguards and costs

What needs a person

Nothing publishes until we approve it, and a draft that fails its checks twice comes to us with a note instead of looping.

If something breaks

A failed run shows up on the board and sends us an email alert, so a half-finished article doesn't go out. It also stops itself if errors or spend cross a set limit.

What it can reach

The research step can read the web but has no way to publish. Only the publishing step holds the keys to our channels.

What it costs

Each piece costs under $8 to produce, so the monthly bill tracks how many we publish. A spend limit stops a stuck loop from running up the bill.

05

What we had to figure out

Early drafts were accurate but flat

The first version produced well-structured, correct articles that were dull to read. So we added an editing pass with one job, which is to make the draft sound like a person with a point of view, and it runs before the checks.

A strict check bounced almost everything

It was failing nearly every article and sending it round again. We capped revisions at two so a draft can't loop forever, and anything still flagged after two passes comes to us with a note. We then retuned that check so it only flags problems a reader would notice.

06

The result

~5.5hrssaved per article, on average

An article took 4 to 11 hours to write, 6 on average. It now takes a 30-minute review.

12-15/mopublished, up from 3-4

We now publish 12 to 15 pieces a month, including on LinkedIn. Before, it was three or four.

~7 hrs/moreview time

Twelve to fifteen reviews at 30 minutes each. Three or four articles by hand took 18 hours or more.

$50-90/morunning cost

The AI and the automation platform. Under $8 a piece.

The article timings come from a month of our own work. The rest comes from the system in use since March 2026.

We still read everything that goes out under our name, but we now start from a polished draft instead of a generic AI summary.
Antonio TetiFounder, Congruity Consulting
This is our own content system. We built it for Congruity and use it every week.

Talk through a problem like this one.

A free intro call. We'll show you where your hours are and what they're worth.