This week, The Common News reached 100 cities.
That means the product now serves places representing nearly 42 million people across the United States.
On paper, that sounds like a growth milestone. In practice, it felt more like a systems milestone.
Going from a smaller footprint to 100 cities did not just mean adding more coverage. It changed how I think about civic data, product architecture, publishing workflows, and what it actually takes to make local government information usable at scale.
That is what I think is interesting about the milestone. The headline matters, but the real story is what breaks, what has to become more structured, and what you learn once the product stops being a city-by-city experiment and starts becoming a broader civic information system.
Why 100 Cities Matters
The obvious reason it matters is reach.
A product covering 100 cities has the chance to help far more people understand what is happening in their local government. But the more important reason is that scale reveals whether your product is built on real structure or on a collection of local workarounds.
At small scale, you can get away with a lot:
- manual cleanup
- city-specific assumptions
- one-off fixes
- fuzzy entity handling
- inconsistent publishing logic
At 100 cities, those shortcuts stop holding.
If the system is weak, scale exposes it quickly.
The Biggest Lesson: Every City Is Similar Until They Are Not
One of the easiest mistakes in civic tech is assuming municipal information is more standardized than it actually is.
At a distance, many cities look similar. They have councils, committees, agendas, hearings, votes, departments, and planning issues. That creates the illusion that once you solve one city, you have mostly solved the category.
That is not really true.
Once you expand, you run into real variation:
- different meeting structures
- different naming conventions
- different committee systems
- different agenda formats
- different levels of source quality
- different ways projects and places get referenced
The pattern is there, but the implementation details vary constantly.
That forces the product to be more disciplined. You need a model that can absorb local variation without turning every city into a custom integration.
Scale Forces Better Data Modeling
The biggest technical shift was that more of the product had to become explicitly structured.
At smaller scale, you can sometimes hide inconsistency behind decent summaries and a usable UI. At larger scale, the weak points become obvious. If committees are noisy, project names are inconsistent, or geographic references are too loose, the product becomes harder to navigate and harder to trust.
That is why scale pushed us further toward:
- canonical entities
- stronger municipality scoping
- cleaner committee and project records
- more structured summary metadata
- more reliable relationships between meetings, summaries, and recurring civic concepts
This is one reason I keep coming back to the idea that civic products are data-model problems as much as interface problems. Once you are spanning 100 cities, the product quality is heavily downstream of whether the system can represent local government structure cleanly.
Publishing Workflows Matter More Than You Think
Another thing that became obvious at 100 cities is that publishing quality cannot depend on heroic manual effort.
The only way a product like The Common News can expand responsibly is if the publishing pipeline does more of the work consistently:
- generating clean slugs
- producing usable SEO metadata
- linking summaries to real entities
- preserving municipality context
- keeping page structure stable across many local coverage surfaces
Without that, scale creates content volume but not content quality.
That distinction matters. A large archive is not automatically a strong archive. What matters is whether the system can keep producing pages that are understandable to users and legible to search engines even as the footprint grows.
Search Gets Better When the Product Gets More Specific
One thing I have learned repeatedly is that broader coverage does not mean more generic content. In fact, scale makes specificity more important.
If you want local civic pages to rank well, they need to be tied to concrete issues:
- real committees
- real projects
- real neighborhoods
- real streets
- real governing bodies
That is even more important across 100 cities, because search intent is local by definition. People are not usually looking for abstract municipal content. They are looking for the issue that affects their own area, their own council, or their own commute.
So the SEO opportunity at this scale is not just "more pages." It is a larger long-tail surface built from real local specificity.
What 100 Cities Changed Product-Wise
Reaching 100 cities also changed how I think about the product experience itself.
At that point, the challenge is not just surfacing information. It is helping users stay oriented inside a much bigger civic graph.
That means the product has to get better at answering:
- What happened?
- Where did it happen?
- Which governing body is involved?
- What ongoing issue is this part of?
- What related coverage should I read next?
Those questions become more important as the archive grows, because users need guidance, not just access.
This is where entity pages, internal linking, summary structure, and municipal scoping all start to matter even more. Scale increases the value of context.
What I Think This Milestone Actually Proves
For me, reaching 100 cities is not interesting because it sounds big.
It is interesting because it proves that the product is moving beyond a narrow pilot and into something that looks more like civic infrastructure.
That does not mean the work is done. If anything, scale raises the bar. It creates more pressure to improve:
- data quality
- entity resolution
- summary reliability
- geographic specificity
- publishing consistency
But that is also why the milestone matters. It shows that the system is large enough now for those problems to be worth solving rigorously.
Where We Go From Here
The next stage is not just adding more cities for the sake of coverage count.
The more interesting challenge is making the system better as coverage expands:
- better local relevance
- cleaner structured entities
- stronger issue and committee hubs
- more navigable archives
- more trustworthy civic summaries
That is the real compounding value. Growth matters, but growth with structure is what makes the product durable.
Closing
Expanding The Common News to 100 cities and nearly 42 million people did not just make the product bigger. It made the weaknesses and strengths of the system much clearer.
The biggest lesson is that civic scale is not mostly about ingestion volume. It is about whether the product can keep turning messy local government information into something structured, readable, connected, and trustworthy across many different municipal contexts.
That is what I think this milestone actually represents.