Northwind Analytics had a content team that wrote well and a backlog that never shrank. Leadership wanted to double output to support a new category push. The team's honest answer: not at this quality, not with this workflow.
The Challenge
The writing itself was rarely the holdup. The delays lived in the gaps — waiting on a brief, chasing sources, reformatting between a draft tool and the CMS, and a final SEO pass that often got skipped under deadline pressure.
Five tools, four people, no single view
Ideas lived in one app, drafts in another, the editorial calendar in a spreadsheet, SEO checks in a fourth tool, and publishing in the CMS. No one could see the whole pipeline at once, so work stalled silently between stages.
The Solution
Northwind consolidated the entire idea-to-publish path into a single system and let automation carry the handoffs that used to cost days.
A calendar that is the pipeline
The kanban planner replaced the spreadsheet. Every post was a card that moved through clear stages, carrying its brief, research, and draft with it. The editorial calendar stopped being a separate artifact someone had to maintain — it was just the board.
Illustrative — monthly output before and after the workflow change.
Research that arrives with the brief
Writers stopped opening five tabs to start a piece. AI research produced cited briefs attached to each card, so the draft began with a point of view and sources already in place. The hours that used to go into setup went into the writing.
SEO built into the flow
A deterministic SEO score lived on every draft, so optimization stopped being a separate, skippable step. Posts shipped optimized by default, not when someone had time.
The Results
In one quarter, Northwind went from six posts a month to thirteen — past their target — while cutting the time from idea to live by 58%. They retired four tools in the process, and the team reported the higher cadence felt less frantic than the old one, because nothing slipped through the cracks between apps anymore.
The category push shipped on schedule. The content engine that made it possible now runs on a single board the whole team can see.
“The bottleneck was never writing. It was everything around it. SparkBlog collapsed five steps into one place, and suddenly twelve posts a month felt calm instead of frantic.”