Know which version is live, and who may watch it.
A documentary, a podcast series or a magazine issue passes through drafts, edits, legal checks and scheduling before the audience sees it, then lives under access and rights rules for years. We build the publishing tools and audience products behind that work.
Staff work and audience access.
Behind the screen, an editor commissions a piece, a contributor files a draft, a sub-editor sends it back with notes and a legal reviewer flags a line about a named person. Video adds rough cuts, subtitles and thumbnails. Most teams run this through email, chat threads and a shared drive, and whatever was attached last is what goes live.
Software here means a submission and review flow with numbered versions, named approvers and a release calendar. Our page on approval workflows explains how we treat sign-off.
In front of the screen, readers and viewers sign up, pay, cancel, share passwords and write in when something refuses to play. Access depends on the plan, the region and sometimes the device.
That side is about accounts, entitlement rules and payments, plus support tools for the moment a paying subscriber cannot open an episode. Heavy video delivery runs on specialist streaming services, which we integrate instead of rebuilding.
Products we might make for you.
Editorial workflow tool
Commissions, drafts, review rounds, legal flags and a release calendar. Each piece shows its current version, who holds it and what is blocking it.
Rights and licensing register
Which titles you may show, in which territories, on which platforms and until when, with a warning before a licence window closes.
Subscriber product
Sign-up, plans, payments, entitlements and a help-desk view, wired to your player or reader and your payment gateway.
Decisions we ask for early.
- Formats and file sizes. Articles and images behave very differently from hours of high-resolution video, and storage and delivery choices follow from that.
- Who approves what. Which roles may publish, which items need a second sign-off, and what happens when the approver is away.
- Rights data. Where licence terms live today, and whether the contracts are clear enough to become rules.
- Access model. Free, metered, subscription, one-off rental or a bundle with a partner. See payments and billing.
- Launch audience. A rough idea of concurrent viewers at a premiere or live event, so hosting is planned and not discovered on the night.
- Takedowns. How quickly content must come down after a complaint or a lapsed licence, and who is allowed to do it.
When the rules really matter.
The episode goes out at 8pm.
An editor approved cut three, but cut four fixed a sound problem. The schedule has to point at the approved cut, and swapping it needs a fresh sign-off.
A film's window ends at midnight.
The rights register pulls it from the catalogue on time and warns the programming team a week ahead.
A subscriber paid but can't watch.
Support sees the plan, the last payment, the registered devices and the entitlement check together, and fixes it without calling an engineer.
A published article needs an edit.
The change goes through review, the live page updates, and its history records what changed and who approved it.
Questions from editors and producers.
We already have a CMS. Does the review flow have to replace it?
No. Many publishing systems can receive approved content through an interface, so the review tool feeds the CMS and your site keeps running as it does now.
Can freelancers submit work without seeing everything else?
Yes. Contributors get access to their own commissions, briefs and feedback, and nothing beyond them.
Talk to us about your release process.
Tell us how a piece gets from draft to audience today and we will suggest where software belongs.