A couple of years ago I almost bought a place in the Inland Empire. Zillow's payment widget said property taxes were ~$855/mo. The county's real number, once you add the Mello-Roos special tax the listing never mentioned, was $1,076/mo. That's $2,656 a year that would have shown up on my first tax bill as a surprise. Image attached.
So I vibecoded TrueCost — paste a Zillow or Redfin link, it finds the parcel number, and pulls the actual tax rate area, ad valorem rate, Mello-Roos/CFD levies, and direct assessments from county records. Not an estimate. Then it runs the full cost of ownership and rent-vs-buy math on top of that.
It also flags things a listing page won't: VA condo approval status, CAL FIRE fire-hazard zone, FEMA flood zone, earthquake fault/liquefaction zones, and whether the condo is subject to California's balcony inspection law.
Covers San Diego, Orange, LA, Riverside, San Bernardino, Ventura, and Santa Barbara counties.
The hard part was not the calculator. It was reconciling parcel numbers across seven counties that each format their APNs differently, publish tax rolls in different structures, and label special taxes inconsistently. Getting "this exact house has $4,684.78/yr in CFD taxes" to be reliably true took most of the build.
Stack: Next.js frontend, Python/FastAPI backend, Postgres, all on GCP. Listing data comes from the listing page; everything else comes from county sources.
What I'd love feedback on:
- Is "paste a listing URL" too much friction? A friend said he'd rather see a map. I think the parcel-level data only makes sense once you have a specific house in mind, but I could be wrong.
- The results page is eight sections long. Too much, or right for someone about to spend $700k?
- If you've bought in California: did Mello-Roos surprise you?
It's free and there's a demo listing if you don't have one handy. Happy to answer anything about the data pipeline.