Property research · Live
Black Label Real Estate
A property-research workflow connecting parcel records, owner context, nearby sales, estimates, and the next visit.
The brief.
County records arrive through different systems and inconsistent formats. Researchers need both the underlying source and a practical way to work with it.
What we built.
- County data integrations and parcel research.
- A guided, database-first research workflow.
- Deal estimates, notes, exports, and routes under the user’s control.
How it works.
- 01Choose a county and research a known property.
- 02Inspect the source record and resolve ambiguous matches.
- 03Add your assumptions, compare nearby sales, and plan the next visit.
The result.
The product brings the research steps together while keeping county scope and source differences visible.
Where it stands.
Coverage and source dates vary. Deal estimates depend on the inputs and are not appraisals or investment returns.
Platform availability
Windows: Black Label Real Estate 1.0.0 unsigned early access is available through the buyer account. The Mac edition is sold directly and through the App Store, which also carries the iPhone and iPad app.
Earlier engineering notes · July–August 2026
Preserved from the original build record. Product status and offers may have changed; the current project summary appears above.
- Problem: three copies of the app — the website download, the notarized package, and the installed dev build — were all different, with no automation keeping them in sync. Buyers were downloading an older build than the one we tested, and that build still defaulted to a developer machine address instead of the production API. Fix: committed the production default, established one canonical download, and added an in-app updater.
- Problem: the app opened into a paste-first screen while the property database sat invisible. Fix: rebuilt navigation database-first with a guided List Builder; pasting external data was demoted to a menu item.
- Problem: the app reported the live index offline for six days. It was not. An overnight install had replaced the application bundle underneath a copy that was still running and had never been relaunched, so it kept executing a binary that had already been deleted from disk. Fix: a full quit and relaunch, and installs are now expected to prove the running process is the build we just installed. Both bundles carried the same version number — which is exactly why a version number is not an identity.
- Problem: an idle animation burned measurable CPU forever — an uncancelable repeat-forever effect. Fix: purged that effect class from every app we ship; idle CPU measured at zero afterward, verified live.
- Rule we keep: the test floor only ratchets up — 556 to 712 during one repair — so a rebuild can never quietly ship with fewer passing tests than the one before it.