← All Proof
Live Now

MO Bill Watch

Every bill filed in the 2026 Missouri session, tracked on one site, and built solo in 36 hours.

mobillwatch.com →

My role
All of it, alone: the idea, the data model, the build, the launch, the upkeep.
When
Blank screen to live domain in 36 hours. Live since July 26, 2026.
Stack
Static site on Vercel, accounts and watchlists on Clerk and Upstash Redis, two hermetic ingest scripts.
Team, funding, vendor, CMS
None.
Cost to run
About the price of the domain.
Outcome
3,403 pages covering all 3,142 bills, with plain-language summaries for the 102 that became law.
No. 01The Problem

I read bills for a living once, as a legislative budget analyst, so I know exactly where the official record fails you. Bills are hard to track: the real work isn't watching a status line, it's reviewing what changed from version to version, the substitute that swaps out the whole text, the new statutes quietly added along the way. And the same statute can be written into several bills at once, so following one bill never means you've seen the change coming. Bills are hard to understand: they're written as instructions for amending statute, not as an explanation of what they'd actually do. The people who need that picture (lobbyists, associations, reporters, citizens) rebuild it by hand, and everyone else goes without it.

No. 02The Call I Made

Treat the whole session as data. Every bill gets a page. Every sponsor, every topic, and the shape of the session itself: how many bills go in, how few come out. Say what a bill does in plain language, because the bill text won't. Then a watchlist so a reader can follow the ten bills they care about instead of scanning three thousand.

No. 03What Shipped

3,403 pages: a page for every one of the 3,142 bills filed in 2026, including each of the 3,040 that died, plus 191 sponsor pages, 17 topic pages, and a live visualization of the session's attrition. Plain-language summaries for the 102 that became law. Accounts and watchlist sync. Two ingest scripts, both hermetic, so a slow upstream can never break the site.

mobillwatch.com
The MO Bill Watch homepage: search across 3,142 bills, the FY2027 budget by department, and what passed this session.
The live site on September 16, 2026: the session, the budget, and what passed, on one page.
No. 04What AI Did, and What It Didn't

AI wrote most of the code and architected the database, which is why 36 hours was enough. What it couldn't do was decide what was worth building. Knowing that the real pain is version-to-version review, that the same statute hides in several bills at once, that a summary has to say what a bill does and not what it amends: that came from years of reading bills for a living. Speed without a clear sense of purpose just means you'll ship the wrong thing faster than ever before.

No. 05The Numbers
3,142bills filed 102passed both chambers 89now in effect
3,142 filed, 102 passed, drawn to scale. Every one of them has a page.
3,403pages
3,142bills tracked
36 hrsblank screen to live
~$0runs for about the cost of the domain
No. 06What I Learned

The site factory I built for exactly this (a manifest, a scaffold, a QA gate, a launch packet) turned a niche I know cold into a live product before the week was out. That's the whole argument for the AI moment in one build.

Common Questions

Building a site like this with AI

How long does it take to build a website with AI?

MO Bill Watch went from a blank screen to a live domain in 36 hours. I built it solo with AI, and it's been live since July 26, 2026, with a page for every one of the 3,142 bills filed in Missouri's 2026 session.

Can one person build a website this size without a team?

Yes. I did all of it alone: the idea, the data model, the build, the launch and the upkeep, with no team, no funding, no vendor and no CMS. The site is 3,403 pages, including 191 sponsor pages and 17 topic pages.

What does AI actually do when you build a site, and what doesn't it?

AI wrote most of the code and architected the database, which is why 36 hours was enough. It couldn't decide what was worth building. Knowing that the real pain is version-to-version review, and that a summary has to say what a bill does and not what it amends, came from years of reading bills for a living.

How much does it cost to run a site like MO Bill Watch?

About the price of the domain. It's a static site on Vercel, with accounts and watchlists on Clerk and Upstash Redis, and two hermetic ingest scripts, so a slow upstream source can never break the site.

Can you build something like this for my business?

Yes, that's the work I do. Tell me what you're working on and I'll follow up personally. If you'd rather build it yourself, start with the free 30-Day AI Starter Plan or join the waitlist for the Build Your AI Chief of Staff class.

The first site off this production line →

If you're sitting on an idea, waiting until it's ready, I get it. I spent years learning that ready is a moving target, and the only thing that actually moves it is doing the thing. That's the Growth Strategy work: find the opening, then build enough of it to know.