01
Breaking news does not wait
Editorial has to publish in under a minute. A CMS that is slow or needs a deploy is simply not used.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
Editorial workflows, paywalls and delivery for audiences that arrive all at once.
We build editorial and publishing software: newsroom workflows and CMS, paywalls and subscriptions, delivery and search, and the syndication and rights handling that moves content between platforms.
Publishing has an unusual pair of constraints. Editorial needs to move in minutes - a breaking story cannot wait for a deploy or a slow CMS - while the archive has to remain correct and citable for decades, including corrections and takedowns.
Commercially it is a subscription and attention business now. Paywall mechanics, registration walls and the trade-off between reach and revenue are product decisions with immediate, measurable consequences, and they belong in the same system as the editorial workflow rather than bolted alongside it.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
Editorial has to publish in under a minute. A CMS that is slow or needs a deploy is simply not used.
Corrections, takedowns and citations mean history has to be preserved and amended at the same time.
One story can outweigh the rest of the site, and it is never the one that was planned for.
Metering, registration and hard walls all move both numbers, and the balance is a constant product decision.
Success is expensive. Caching strategy is a commercial decision as much as a technical one.
Defamation, embargoes and image rights all have real consequences and short timescales.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
Authoring, editing and scheduling built around a newsroom's actual speed.
Edge delivery that absorbs a spike without a bill nobody expected.
Metered, registration and hard walls with subscription billing and entitlements.
A durable, citable archive with corrections, takedowns and image rights handled.
Discovery, syndication and email delivery from the same content model.
Reporting journalists and editors will actually use to decide what to do next.
Engagements across sectors - the same team, the same standards.
Partnering with Thinkdebug to develop the Forever 52 mobile app has been a game-changer for us. They were always open to feedback, and it was clear they were as invested in our success as we were. What really sets them apart, though, is the amazing support we've received since the app launched. They’ve made sure the app continues to run smoothly and are always ready to fix any issues that come up.DMDhruv MehtaBusiness Head, Forever 52
Chosen for fit and long-term maintainability, never for novelty.
Send us the scope and we come back with an itemised estimate - no discovery fee, no obligation.
What we design and document against, from the first commit rather than the week before an audit.
Certification itself belongs to your entity and its assessor. What we provide is software built and documented so the assessment is about evidence rather than remediation.
Most of our work comes from clients we already shipped for. These are the reasons they give.
The editorial path is the fastest thing in the system, because a CMS that slows a newsroom gets worked around instead of used.
The read path is cached hard, so an unexpected story is a good day rather than an incident and a surprise invoice.
Corrections and takedowns are modelled as versioned events, so history is amended without being erased.
Metering and entitlement rules are server-side and adjustable, so reach and revenue can be balanced without a deploy.
Takedown, de-indexing and rights expiry are workflows with audit trails, because these arrive with short deadlines.
Reporting framed around editorial decisions rather than a generic dashboard nobody opens.
Let's start with you.
Your information stays private. We reply within 24 hours.
Still have a question we have not answered?
Ask an engineerWhat we build for publishing & news, the work we have shipped, and what we have written about it.
