Choose the listings you want to compare
Start with a shortlist you have selected. Give your AI the listing identifiers and the buyer's stated requirements. A fixed set makes it easier to inspect the work and notice when a record is missing.
If you need the AI to search first, make that a separate request. Confirm the market and filters before it retrieves a shortlist. Then review the properties you want included in the comparison.
Use a table with the same meaning in each column
Choose the fields that support this buyer's decision. Put units in the headings where they matter. Preserve a source's description of area or parking so the AI doesn't silently treat different measurements as equivalent.
Use the record identifiers to distinguish a unit from the building that contains it. An address alone can leave that difference unclear. Ask the AI to stop if two source records appear to describe different properties.
| Field | Keep with the comparison |
|---|---|
| Asking price | Currency and retrieval date |
| Area | Unit of measurement and source label |
| A required feature | The returned fact or an explicit unknown |
| Listing status | Source status and retrieval time |
| Open question | Who can confirm it before the client relies on it |
A prompt to adapt
Compare these listings for my review.
Listing identifiers: {{approved shortlist}}
Buyer's stated requirements: {{requirements}}
Comparison fields: {{fields and units}}
Retrieve the available records through my authorized Farmhand connection. Confirm that each identifier matches the intended property.
Create a comparison table using the same field definitions. Keep asking prices separate from past sale prices and estimates. Include source labels and retrieval dates. Mark missing fields as unknown.
Explain which stated requirements each home meets based on the records. Separate your interpretation from confirmed facts. List questions for the showing. Do not assign a final recommendation or share the result without my review.Leave an unknown unresolved
In a fictional shortlist, one listing says it has a dedicated office. Another record doesn't mention an office. Mark the second as unknown. You haven't established that it lacks one.
If a buyer requires a specific feature, that unknown becomes a showing question. The comparison is useful because you can see where the records support a decision and where you still need an answer.
Keep valuation work in its own request
A buyer shortlist compares homes against that buyer's requirements. A pricing analysis needs its own selection of relevant evidence and professional review. Don't let a request to compare listings turn into a claim about fair value.
If you need sold records, confirm that your Farmhand account can retrieve the required data and that you can use it for the purpose. Ask your AI to explain the selection criteria before you use the records in a pricing discussion.
Refresh the facts before sharing
Read the source for the facts that will shape the conversation. Check listing status and price again when you prepare the client version. Save the retrieval date on the document so a colleague can tell which version you reviewed.
Keep the reusable prompt, but replace the shortlist and buyer requirements on the next job. Farmhand's listed $29/mo rate covers the directory offering; confirm your account's records and permissions before relying on this workflow.
Sources and review notes
Product information and starting prices checked October 17, 2026. These guides use documented product information and suggested workflows. We have not tested these connections for the directory. Farmhand's supplied directory rate is $29/mo. Provider plans, coverage, and permissions can change.