Define the dataset you actually need.
A useful real estate data request begins with the relationship between the person and the property. A homeowner list, a past seller inquiry, and a buyer inquiry are different products. Defining that distinction first helps you evaluate relevance before considering how many records are available.
Buyer and seller intent
If you need past inquiries, specify buyers or sellers and the original request type. A person’s presence on a property list is not proof of a plan to move. Keep general homeowner audiences separate from records with a documented inquiry.
Match the local market
Identify cities, counties, or ZIP codes and state any areas to exclude. If property attributes are needed, name them explicitly. Availability of a property address, property type, or ownership-related field must be reviewed for the requested area.
Keep people and properties distinct
One person can be associated with more than one property. Decide whether the requested quantity refers to unique people, households, or properties, and agree on how duplicates should be treated before a file is prepared.
A useful project brief
Residential seller inquiries for selected ZIP codes in Arizona, 90+ days old. Keep documented inquiries separate from general homeowner records; report unique contacts and available property fields.
Is a property mailing list the same as a seller lead list?
No. A property mailing list can identify an audience without documenting an intention to sell. Specify whether a past seller inquiry is required.
How your request is reviewed
Share your requirements through Request Data. Our team reviews availability, field coverage, and project fit before responding with the options and next steps. Submitting a request does not create an order or start a payment.
