[ FINANCIAL_MEDIA ]

Editorial & Research Operations Console

2026Internal Tools & AdminIn-depth

What it is

The back office for a financial news operation — research, production, publishing and audio.

Client work is shown without identifying imagery

[ THE_PROBLEM ]

Why this existed

A daily newsroom running on five SaaS subscriptions and a shared drive spends more time moving content between tools than producing it — and nothing is searchable across the whole workflow.

[ WHAT_WE_BUILT ]

What we built

A single console covering an unusually wide surface: auto-research, article processing and today's-articles queues, an RSS feed reader, market data views, government data, a CSV analyser with generated analysis, PDF generation, a media library with uploads, podcast management with an audio timeline, script management and controls, a recap generator, newsletter assembly, a dictionary manager for house style, and a bulk Excel-to-database uploader. A Python service handles article generation, bond uploads and PDF-to-image conversion; a companion Chrome extension pulls sources from the browser.

Auto-research, article processing and daily article queues
RSS feed reader and market data views
CSV analyser with generated analysis and PDF generation
Media library with uploads
Podcast management with an audio timeline and script controls
Recap generator and newsletter assembly
Dictionary manager for house style consistency
Bulk Excel-to-database uploader
Companion browser extension for capturing sources
Python service for article generation and document conversion

[ HOW_IT_IS_USED ]

How a company uses it

A newsroom or research desk that publishes daily gets research, drafting, media, audio and distribution in one place — instead of five SaaS subscriptions and a shared drive.

Built with

ReactViteExpressPythonChrome ExtensionMUI

[ COMMON_QUESTIONS ]

Questions clients ask

Is one console for all of this actually better than specialist tools?

When the workflow is a pipeline, yes. Research feeds drafting, drafting feeds the newsletter and the podcast script, and all of it needs the same house style. Every tool boundary is a copy-paste and a chance to lose a version. The counter-argument is real though — specialist tools are better at their one job, so the trade only pays when the handoffs dominate.

What does the browser extension do?

It captures sources from the page the journalist is reading and pushes them into the research queue, rather than requiring them to switch context to the console and paste a URL. Small, but it is used dozens of times a day.

Why a separate Python service?

Document conversion, PDF-to-image work and generation pipelines have a mature Python ecosystem and different scaling characteristics from the web application. Splitting them means a slow generation job cannot degrade the editorial interface.

[ RELATED_WORK ]