Industry · Media & Publishing
Write it once. Publish it everywhere it's owed, on the minute.
We build the editorial desk (the content model, the workflow, and the schedule) that carries a story from filed to live across every brand, channel, and feed you publish to, without anyone retyping it into a fourth system.
Run sheet · 4 stories
desks: 4
Port authority names interim chair
News · R. Okafor · 15:42
The quiet consolidation of regional freight
Business · M. Halloway · 16:00
Eight months inside the housing appeals board
Features · S. Devereaux · 18:30
What the archive tells us about the 1994 season
Culture · A. Winterbourne · 07:00
One entry goes to
LEDGER-118 held for 16:00: one entry, four destinations, released on the same second
A working-desk mockup: slugs, desks, and destinations, shown for illustration
The desk
The audience
Where a desk loses the thread
Six ways one story becomes four wrong ones
The same story, typed four times
Web, app, newsletter, and the print file each get their own version, and by Thursday none of them match.
Embargoes that lift by hand
Someone sits waiting to press publish at four o'clock, and the one afternoon they're in a meeting, a competitor is first.
Corrections that don't travel
The web piece is fixed, the newsletter already went out wrong, and the syndication partner is still running the old line.
An archive nobody can search
Decades of work sits behind a system that only really knows how to find last week.
A paywall set by guesswork
The meter treats a wire brief and a six-month investigation the same way, so it converts neither of them.
Rights kept in a spreadsheet
Who may run what, where, and until when lives in a file that three people each hold a different copy of.
What we build
The software that keeps one story true everywhere
Editorial workflow & scheduling
Filed, edited, scheduled, live: one board the whole desk reads, with embargoes that release across every channel on the same second.
LEDGER-118 · embargo 16:00
Scheduled · releases in 00:16
Content modeling & multi-brand publishing
One structured entry serves every brand site, app, and feed, so a change lands everywhere at once, including the places nobody remembered.
No duplicate entries: one record, three mastheads.
Paywalls, subscriptions & newsletters
Metering, offers, and sends that read what a piece is actually worth to a given reader, where a flat rule treats everything the same.
Archive, rights & asset intelligence
Back issues, images, and clips made searchable, with rights terms and embargo dates attached to each one, so what you can republish is always clear.
Built on top of what you already run. The CMS, the print system, the asset library, and the rights records all stay where they are.
In this edition
Built for every kind of publisher, on its own terms
Filed and cleared
Copyedited, legally reviewed, and scheduled against the embargo clock.
Held
Every destination is staged and waiting. Nothing is published.
Released
Web, app, newsletter, and four syndication partners, on the same second.
Correction filed
A figure in paragraph nine is wrong. Corrected once on the record.
Correction propagated
All four destinations updated, partners notified, note appended.
Flagship · the timed release
The four o'clock lift, and the correction that caught up with it
An embargoed piece doesn't need a person watching a clock. The desk holds it, releases it to every destination on the same second, and when the correction lands at 16:41, carries the fix back through all four without anyone chasing a syndication partner by email.
- Holds an embargoed piece until the second it's cleared to run
- Releases to web, app, newsletter, and syndication at once
- Carries a correction back through every destination that already ran it
- Leaves one audit trail: who changed what, and when it reached each channel
How it runs
From a desk we've watched to a desk that runs itself
Read the desk as it runs
We follow a story from pitch to published: every hand it passes through, and every place it currently gets retyped.
Model the content once
We build the structure your journalism actually has, so a single entry can serve every brand, channel, and feed.
Wire the schedule and the channels
Embargoes, sends, feeds, and syndication all read the same clock, so a release becomes one action instead of five.
Open the archive and the meter
Back issues become searchable and licensable, and the paywall starts reading what each piece is worth to each reader.
We build on top of the systems you already run. The CMS and the print workflow stay put.
Connects to your stack
It plugs into the newsroom you already run
Editorial & content
Audience & revenue
Distribution
What changes
A desk that publishes once and stops correcting itself in four places
One entry, not four
A story is written once and reaches every brand, channel, and feed from the same record.
Releases that hold the clock
Embargoes lift on the second, without anyone sitting on a publish button waiting for it.
Fixes that travel
A correction reaches every destination that ran the piece, syndication partners included.
An archive worth having
Decades of work becomes searchable, licensable, and reusable, far more than merely stored.
Put one of your own stories through the desk
Bring a real piece (a wire brief, an embargoed feature, whatever ran badly last week) and we'll model it, schedule it, and release it to four destinations in the same view your desk would use.
Selected work
Three publishers who stopped keeping four copies of the truth
Questions
What editors ask first
Q.Do we have to leave our CMS?
Usually not. Most builds model the content properly and connect the CMS, print system, and asset library you already run. The desk sits over them and leaves them in place.
Q.How does an embargo actually hold?
The piece is scheduled once against a single clock, and every destination (web, app, newsletter, syndication) releases from that same schedule. Nothing goes early and nothing gets forgotten.
Q.What happens to a correction after publication?
It propagates. The record is corrected once, and every channel that ran the piece receives the update, partners included, with an audit trail of exactly what changed and when.
Q.Can one platform serve several titles?
That's usually the reason to build one. A shared content model with per-brand presentation means an entry is created once and reaches every masthead that should carry it.
Q.Can you make our archive searchable?
Yes. Back issues, images, and clips get indexed with full text and structure, with rights and embargo terms attached, so what you're free to republish is clear at the point of use.
Related services
The systems underneath the desk
Explore other industries
The same thinking (one record, every destination, and a correction that travels) carries into the industries below.
Let's talk
Running a large platform, shaping a first MVP, or getting a product ready for a funding round? Tell us where you are. We'll shape the process around it, and stay with you after launch.
