/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

WaPo's Arc CMS, run by ~250 staff, is now used across ~600 sites, up from ~100 last year, including Tribune Publishing, now adds BP as first non-media customer

Gerry Smith / Bloomberg :

Bloomberg Gerry Smith

Context & Ripple Effects

Arc began as WaPo's internal publishing suite before the paper started offering the tools to other newsrooms as a paid service. By late 2018, WaPo had laid out a plan to expand it beyond publishing tools into subscriptions sold to others, explicitly modeled on how AWS turned Amazon's infrastructure into a business — an AWS-style infrastructure play.

The BP deal matters because it tests whether that framing survives contact with buyers who don't publish newspapers. With roughly 600 sites now running on a team of about 250 staff — up from ~100 sites a year earlier, including Tribune Publishing — Arc is scaling fast enough that non-media revenue changes what kind of company it is.

First-order effects

  • BP's signing gives Arc its first revenue line outside media, converting the 2018 roadmap from aspiration into a shipped product category for WaPo.
  • The ~100-to-~600 site jump in one year puts real load on the ~250-person team, making enterprise deals like BP both the growth engine and the staffing test.

Second-order effects

  • Tribune Publishing and other Arc-using publishers now share infrastructure with an oil major, meaning the platform's priorities get set by non-newsroom demands like corporate-site workflows, not just editorial cadence.
  • Rival CMS vendors serving publishers must decide whether to follow Arc into general corporate web infrastructure or cede the larger market WaPo just validated.

Third-order effects

  • If non-media adoption keeps growing, Arc stops being a publisher's side project and becomes a standalone software asset — a path the corpus later bears out when WaPo explored a spinoff or sale of Arc XP, projecting $200M+ in ARR by 2027.
  • The broader structure this points toward: legacy news organizations monetizing internal engineering as B2B platforms, decoupling part of their economics from subscription counts like the 3M digital subscriber milestone WaPo was approaching.

The trend: News publishers are turning internally built platforms into B2B software businesses whose customer base extends well beyond media.

Discussion

  • @agnotology42 @agnotology42 on x
    Amazon absolutely eating Google's lunch with premium publishers. Look for Google to respond by further gutting their own longtail & then adjusting revshares w custom deals for big pubs https://disinformationindex.org/ ... https://twitter.com/... https://twitter.com/...
  • @sprakash007 Shailesh Prakash on x
    From the deep sea to the desert, from rigs to retail, BP is a “supermajor” energy giant and the world's seventh-largest company by revenue. And it looks like they know how to choose the best software as well! Thank you for choosing Arc, BP! https://www.bloomberg.com/... via @wapo…
  • @jbenton Joshua Benton on x
    Same logic as publisher content studios: Take a content-publishing skill you're good at, realize that skill is also useful to a ton of non-news companies, and sell your expertise https://www.bloomberg.com/...