Home services companies use the physical facts of a property: building and living area, stories, year built, roof material and construction, foundation, heating and cooling equipment, utilities, pool and garage, and lot dimensions, plus the owner of record and the last recorded sale. Nearly all of it is public record from county assessor, recorder, and GIS offices. Companies either pull it county by county or license it from a provider that normalizes roughly 3,000 county formats into one schema and delivers it by API or bulk transfer.
A roofing, HVAC, flooring, fencing, solar, or lawn-care business runs on the same two questions for every job: what is the property, and what is it going to take to do the work. The county assessor already answers most of the first, with building area, stories, year built, roof material and construction, heating and cooling equipment, and lot dimensions on file for nearly every parcel. The recorder adds the ownership record and the most recent transfer, which keep a customer file accurate. What neither office offers is a consistent format, because roughly 3,000 counties publish on their own schedules in their own layouts. A normalized property data provider keys everything to the address and parcel, standardizes the field names, and delivers the record by API for estimating and CRM tools or by bulk file for territory analysis.
Four groups cover most home services work. Structure and systems decide the method and the crew: roof material and style, construction, exterior wall and foundation, heating and cooling equipment and energy source, water, sewer, gas, and electric service, stories, and basement. Size and layout set the materials and labor: building and living area, bedrooms and bathrooms, year built, and effective year built. Lot and outdoor fields scope fencing, landscaping, paving, and exterior work: acreage, lot area, frontage, depth, pool, and garage. Ownership and sale history keep the customer record accurate: owner of record and the recording date, transfer date, and price of the last sale.
The same record serves every stage. Intake reads size and structure to open the call with the right questions. The estimate reads all of it to price the job. Scheduling reads lot dimensions to size the visit, and planning reads the aggregate by area to see where the housing stock matches the services on offer and how to size crews.
Nearly all of it is public record. County assessors publish building characteristics, lot dimensions, and year built as part of the tax roll. County recorders file deeds and transfers, which is where owner of record and sale history come from. GIS departments publish parcel boundaries and zoning. Values that are not on file, such as an automated valuation, are modeled from those records and recorded sales.
The difficulty is scale. Each county chooses its own field names, formats, identifiers, and publication cadence, so a company operating in more than a few markets ends up maintaining a parser per county or buying a one-off extract per market. A provider like Realie collects at the source, normalizes the counties into one schema keyed by parcel, refreshes it on a rolling, per-county cycle as counties publish, so vintage varies by county, and delivers it through an API for per-address lookups or bulk transfers for territory-wide work.
Property data describes a parcel, not a person. It is not a credit report, and Realie is not a consumer reporting agency. Realie's Terms of Use prohibit using the data as a factor in an individual's credit eligibility or for any other FCRA-regulated purpose, and Realie does not market owner lookups by name.
Home services workflows sit inside that boundary because they start from an address or an area: the request that just came in, the customer already on file, or the neighborhoods a company serves. The data describes the property, not the person. Starting from the address is both the compliant pattern and the one that produces the cleanest data.