Book a discovery call

11 Construction software · United States Live

A publishing pipeline that now runs unattended on the platform's own blog

It learns from what reviewers reject. Twenty-six posts were approved by a person before the first one went out with nobody in the loop.

Part of Six tools built inside a live construction-tech platform

Before
Posts drafted when someone had time and published by hand, so sites meant to bring in leads went quiet
After
The platform's own blog publishes unattended; client sites publish on human review, each with a record of who approved what
26 of 26 posts approved by a person before the first unattended publish
The work, before and after
Before and afterBefore: Site brief, then Drafted when free, then Published by hand, then Site goes quiet. After: Site brief, then Producer drafts, then Reviewer approves, then Scheduled publish, then Learning recorded. Result: 26 of 26, posts approved by a person before the first unattended publish.BEFORE3 OF 4 PAIN POINTSAFTER3 OF 5 AUTOMATEDSite briefDrafted when freePublished by handSite goes quietSite briefProducer draftsReviewer approvesScheduled publishLearning recorded26 of 26posts approved by a person before the first unattended publishBefore and afterBefore: Site brief, then Drafted when free, then Published by hand, then Site goes quiet. After: Site brief, then Producer drafts, then Reviewer approves, then Scheduled publish, then Learning recorded. Result: 26 of 26, posts approved by a person before the first unattended publish.BEFORE3 OF 4 PAIN POINTSAFTER3 OF 5 AUTOMATEDSite briefDrafted when freePublished by handSite goes quietSite briefProducer draftsReviewer approvesScheduled publishLearning recorded26 of 26posts approved by a person before the firstunattended publish
159
pages across six sites checked live
30 Sep
first unattended publish, on the platform's own blog
How the system runs
Input
  • Site brief and voice
  • Publishing schedule
ArrAI
Producer and review queue
Output
  • Approved post, published
  • Record of who approved it

01 What changed

  • The platform's own blog publishes on a schedule with nobody in the loop
  • Client sites keep a person approving, by the client's choice
  • Every post has a record of who approved it and what the producer learned
The full story The problem, how we approached it, and what we built

A software platform serving builders, clinics and estate firms needed its sites to publish on a schedule without a writer on staff. We built the producer and publishing pipeline, ran it with a reviewer approving every post, and the platform's own blog now publishes unattended while its clients' sites stay on human review.

Built for
Founder, and the owner of each client site
Engagement
Construction-tech platform
Sector
Construction software
Region
United States
Year
2026

02 The problem

Each site had a cadence it could not keep. Posts were drafted when there was time and published by hand.

The platform needed one pipeline that could serve every site it hosts, each with its own review rule, and that got better rather than worse the more it ran.

03 The approach

We built a producer that drafts from each site's own briefs and search data, a review queue with an approval mode per site, and a scheduler that publishes only what has been approved.

Each run records what it learned from search results and from drafts a reviewer turned down. It ran with a person approving every post, twenty-six in a row. Then the platform's own blog went unattended, and on 30 September the producer steered around two angles a reviewer had rejected on its own.

04 What we built

  • Producer that drafts from each site's briefs, voice and search data
  • Review queue with an approval mode per site: every post, or unattended
  • Learning record per run: what search rewarded, what a reviewer rejected
  • Draft preview checked live across 159 pages on six sites

Want this kind of result mapped for your business?

Book a discovery call