Source intake and relevance scoring
The platform collects news, filters sources, scores each story for relevance, and removes duplicates so the team sees a cleaner set of candidates before deciding what should become content.
Case study
News to reviewed publishing workflow
Turning property news and market updates into reviewed articles, branded social content, carousels, translations, and scheduled publishing.

Client
Private real estate client
Status
Private client build
Category
AI Integration & Workflow Automation
Timeline
2026
The client needed to keep up with property news, market updates, and ongoing editorial opportunities without making the team manually move every story through research, drafting, design, translation, and publishing tools.
The platform brings that work into one content operation. Useful stories can be identified first, content can then be prepared in different formats, and the team keeps the ability to edit, reject, regenerate, schedule, or publish before anything reaches an audience.
Product context
Faster generation still left the team with decisions about which stories were worth using, what needed review, and how long-running content jobs should run without slowing down the main dashboard.
The workflow had to handle both volume and judgment. Not every news story was worth turning into content, and generated drafts still needed editorial review before publishing. At the same time, article generation, translation, image work, carousel rendering, scraping, and scheduled publishing could take long enough that they could not safely run inside the main user request.
We built the platform around a clear path from source material to reviewed publishing, with separate systems handling story selection, content creation, team approval, and background processing.
The platform collects news, filters sources, scores each story for relevance, and removes duplicates so the team sees a cleaner set of candidates before deciding what should become content.
Approved source material can be turned into long-form articles, social captions, platform-specific copy, branded images, stories, and carousels from the same content workflow.
Every generated item moves through review states where the team can edit, approve, reject, regenerate, schedule, or publish it instead of giving AI direct control over what reaches the audience.
Article generation, carousel rendering, translation, image processing, scheduled publishing, and source scraping run through worker queues so longer jobs do not block the main dashboard.
The client now has one internal platform for managing the path from incoming news to reviewed, scheduled content. The team can work from the same dashboard instead of moving repeatedly between source websites, draft documents, design tools, translation tools, and publishing screens.
The system can also keep recurring and time-consuming work running in the background while editors continue using the dashboard, giving the client a content operation that can run repeatedly without removing human approval from publishing.
3x daily
automated content pipeline schedule for recurring news and post generation
Multi-format
feed posts, story assets, carousels, long-form articles, and translations
Review-first
approval, rejection, editing, regeneration, scheduling, and publish states
Worker-backed
queues for generation, scraping, rendering, translation, and publishing
Client feedback
“They brought structure to a workflow that had many moving parts. The process was clear, the implementation was dependable, and the final system was easier to operate than what we had before.”
Name withheld
Founder, Private Real Estate Product
The value came from what these decisions changed for the people using the product and the team responsible for running it.
The team can move from useful source material to drafts, review, scheduling, and publishing without rebuilding the same workflow across several separate tools.
AI can help prepare content, but the team still decides what is edited, rejected, regenerated, scheduled, or allowed to go live.
Long-running generation, rendering, translation, scraping, and publishing jobs can run through workers while the team continues using the main product.
Share what you are building, what is not working, or what you need to achieve. We can help turn that context into a clear technical plan.
A rough idea, current blocker, or target outcome is enough for an initial conversation.
What to share
What exists today, what needs to change, your timeline, and what a good result looks like.