The Decision
The math behind local news is simple and brutal. You need journalists. Journalists cost money. The revenue model that used to pay for them — print advertising, classifieds, subscription bundles — is gone. The digital replacement pays a fraction of what print did and rewards volume over quality. So you either raise outside capital and burn through it, find a patron and hope they stay interested, or you accept that the old staffing model is dead and design around it.
I designed around it.
The Wrong Assumption
The traditional newsroom worked because its economics worked. Beat reporters, editors, copy desks — all of it was underwritten by a revenue model that no longer exists. When the money left, the model didn't adapt. It contracted. And it kept contracting until what remained couldn't do the basic work.
Most attempts to revive local news start from the same assumption: rebuild the staffing model. Hire the reporters back. Find the money. The instinct is generous. The assumption is wrong. That staffing model was a product of a specific economic era. Rebuilding it without rebuilding the economics is just running the same experiment and expecting different results.
Why AI Is an Architecture Decision
When I started designing Mercury Local, the question wasn't whether to use AI. The question was: what kind of system produces consistent, high-quality local journalism at a cost that doesn't depend on outside money?
AI answered that question because of what it does to the production layer. The expensive part of publishing was never editorial judgment — knowing what to cover, why it matters, what angle to take. The expensive part was always production — turning that judgment into finished articles at volume, on deadline, every day. AI compresses that production cost by an order of magnitude.
That compression is what makes everything else possible. It's what allows The Charlotte Mercury to cover eight beats across city government, sports, business, and culture. It's what allows The Farmington Mercury to cover a Connecticut town of fewer than 30,000 people with the kind of consistent attention that used to require a dedicated newsroom. It's what allows one infrastructure to power three publications and more than 800 articles without a single round of fundraising.
The Platform Thesis
Mercury Local isn't a publication. It's the system underneath the publications. One codebase, one database, one editorial architecture — deployed across multiple independent news brands, each with its own identity, its own coverage priorities, its own audience.
Most local news startups build one publication and try to make it sustainable. I built the infrastructure first and launched publications on top of it. The marginal cost of adding a new city is a fraction of launching from scratch. The editorial architecture, the publishing pipeline, the quality controls — they're already built. A new market needs local knowledge and coverage priorities. It doesn't need a new platform.
What This Means
The local news crisis is usually framed as a loss — something taken away that needs to be restored. I see it differently. The old model served its era. What comes next isn't a restoration. It's a new system designed for a new set of economic realities.
I didn't build Mercury Local because AI is interesting. I built it because the math works. Because one operation with the right architecture can produce coverage that used to require a team. Because the system scales across markets instead of multiplying costs.
Every city that lost its local paper is a market that needs this architecture. That's not a pitch. That's the reason I built it.