Sixteen Thousand Profiles. Fifty Nine Thousand Sources. That Is Not a Website.

When an owner asks me whether I only build websites, I send them to RepWatchr.

Not because it is pretty. Because it is a database with a search layer and paid tiers on top, and it runs on the exact same stack I install for clients.

The numbers this morning

Sixteen thousand eight hundred thirty four public profiles. People and institutions on the record.

Fifty nine thousand six hundred fifty seven source URLs. Links a voter can open and share, not citations you have to take on faith.

That ratio is the point. Roughly three and a half sources for every profile in the whole database. A record built on links instead of opinions.

What it does that a website cannot

Search across every level of government. Federal, state, county, city, school boards.

Scorecards with published weights, where hot button issues get turned into traceable votes instead of arguments. Water rights, land and property rights, taxes, government transparency, and voting record, each carrying twenty percent of the overall score.

A citizen source desk, so a reader is not just a reader. Submit the roster, the vote, the agenda, the filing, the clip, the correction, or the missing link, and it lands on the right record.

An accountability packet builder. A live wire of local and national coverage. And paid research tiers that start free and go up.

Free tools cover search, source intake, and the public lanes. Paid services are for deeper research, race pages, clean writeups, and source backed packets.

Why this is the proof piece

Every agency in America will tell you they can build you a platform.

Almost none of them are running one. They have templates and a portfolio of brochure sites with a contact form at the bottom.

RepWatchr has ingestion, a source chain attached to every record, a search layer, official profiles, scorecards, a packet builder, a submission workflow, a methodology page that publishes the grading rules, and paid tiers with checkout behind them.

Next.js, Supabase, Vercel. Same stack I put in a dental school and a fleet washing company. The difference is not the tools. It is knowing what to build with them.

If you have a data problem, not a page problem

Some businesses do not need a better website. They need a system that holds records, searches them, and lets somebody pay for the deeper version.

Directories. Registries. Membership databases. Compliance archives. Inspection histories. Anything where the value is in the collection and the proof, not the paragraph.

That is a software build, and it is a different conversation than a website. It is the conversation I would rather be having.

Go search the record yourself and see whether it holds up. Then if you have a data product sitting in a spreadsheet somewhere, let us map it.