LLOYDENS

Learn what’s beyond the door.

In development · Houston, Texas

Lloydens is developing around a simple question: how much can we actually know about a home? We’re working to synthesize property records, licensed data & locally sourced property information to build a more complete view of individual properties over time—and to explore how far that information can take us beyond what is already known.

Progress

Lloydens logs its work here, day by day.

  1. Completed the core of the first working version of Lloydens, running on synthetic test data: Bay City market statistics, a property report that shows each audience only what it is permitted to see, property photos and observations with full source tracking, and a test confirming that removing a data source leaves property records intact. Setup documentation is written, and lloydens.com is registered. Next: a full rebuild test from the documentation.

View previous days

  1. Set up the local build environment and built the Lloydens database: property records, listing history, photos, observations, and source tracking. Synthetic listing files now load through the ingestion pipeline, with invalid records rejected and near-duplicate addresses held for review rather than merged. Bay City’s official Census boundary is loaded.

  2. The first planning deliverable was approved, and Lloydens moved into implementation. Confirmed the data fields available for property history, days on market, and display permissions.

  3. Set up the Lloydens code repository and completed the first planning deliverable: architecture, database design, data sources, permissions, costs, and test area. Bay City single-family homes confirmed as the first test market.

  4. Built a practice database and verified every calculation by hand. Drafted a permissions matrix defining who may see each type of property data, based on our data license and MLS rules. Researched public-record sources: county appraisal records, FEMA flood maps, and Census boundaries.

  5. Work on Lloydens began. Reviewed the project plan, started the project log and glossary, and reviewed the data license terms that govern what Lloydens may store and show.